My Article at OTN: Oracle Service Bus and Coherence caching example

Today I’ve published an article at Oracle Technology Network (OTN) about Oracle Service Bus and Oracle Coherence integration. It shows a case study example and how you can use caching strategies for  Web Services.

It’s a step-by-step tutorial on how to setup a Coherence Server with Weblogic, how to access this server with Coherence console and how to use out-of-process caching strategy to scale your caching with no impact on the Enterprise Service Bus.

To read the full article click here.

References:

HTTP Status codes for RESTFul Services

A good understanding of the HTTP protocol is crucial for a successful RESTful implementation. Although I know that REST is not dependent of HTTP, we all know that it’s the most common implementation.

Below I made a quick overview of HTTP status codes and the intent is to help during the development and test of REST services.

General HTTP Codes

1xx – Informational: Request received, continuing process.

2xx – Success: Action successfully received, understood, and accepted.

3xx – Redirection: Client must take additional action to complete the request.

4xx – Client Error: Request contains bad syntax or cannot be fulfilled.

5xx – Server Error: Server failed to fulfil an apparently valid request.

In the table below you have the description of the most common response codes:

Code Meaning Description
200

201

202

204

206

OK

Created

Accepted

No Content

Partial Content

– Successful HTTP request.

– New resource created.

– Accepted for processing, but not yet completed.

– Successfully processed, but no return content.

– Only part of the resource returned.

300

301

303

304

Multiple Choices

Moved Permanently

See Other

Not Modified

– Multiple options for the resource that the client may follow.
– This and all future requests should be directed to the given URI. 

– Response can be found at URI using GET method.

– Resource has not been modified since last requested

400

401

403

404

405

406

409

410

412

415

417

418

Bad Request

Unauthorized

Forbidden

Not Found

Method Not Allowed

Not Acceptable

Conflict

Gone

Precondition Failed

Unsupported Media Type

Expectation Failed

I’m a teapot

– Request contains bad syntax or cannot be fulfilled.- Request refused, when authentication is possible but has failed or not yet been provided.

– Request was legal, but the server refuses to respond to it.

– Resource could not be found but may be available again in the future.

– Request made using method not supported by that resource.

– Resource can only generate content not acceptable given Accept headers sent in.

– Request could not be processed due to conflict in the request.

– Resource no longer available and will not be available again.

– Server does not meet precondition put on the request.

– Request did not specify any media types the resource supports.

– Server cannot meet requirement of Expect header field.

– Response entity “MAY be short and stout”.

Weblogic 11g – Supported specifications

Standard Version
Web Services Java EE 1.2, 1.1
Web Services Metadata for the Java Platform (JWS) 2.0, 1.0
Java API for XML-Based Web Services (JAX-WS) 2.1, 2.0
Simple Object Access Protocol (SOAP) 1.1, 1.2
Web Services Description Language (WSDL) 1.1
Java API for XML-based RPC (JAX-RPC) 1.1, 1.0 (deprecated)
SOAP with Attachments for Java (SAAJ) 1.3, 1.2
Web Services Security (WS-Security) 1.1, 1.0
Web Services Policy Framework (WS-Policy) 1.5, 1.2
Web Services Security Policy (WS-SecurityPolicy) 1.2
Web Services Policy Attachment (WS-PolicyAttachment) 1.5, 1.2
Web Services Addressing (WS-Addressing) 1.0, 2004/2008 member submission
Web Services Reliable Messaging (WS-ReliableMessaging) 1.1, 1.0
Web Services Trust Language (WS-Trust) 1.3
Web Services Secure Conversation Language (WS-SecureConversation) 1.3
Universal Description, Discovery, and Integration (UDDI) 2.0 (deprecated in WebLogic Server 10.3.1)
Java API for XML Registries (JAX-R) 1.0
Java Architecture for XML Binding (JAX-B) 2.1, 2.0
Security Assertion Markup Language (SAML) 2.0, 1.1
SAML Token Profile 1.1, 1.0
Web Services Atomic Transaction (WS-AtomicTransactions) 1.2, 1.1, 1.0
Web Services Coordination (WS-Coordination) 1.2, 1.1, 1.0

This usually is good information for RFPs when you have to check if your platform is compliant or not.

Note that this information is public in the product documentation.

Sources: