Skip to content

Webservices up and running

May 9, 2012

“always” compliant with WS-I by allowing only one child element under soap:Body.
t. So, if two distinct operations of a Web Service have the same type of method parameter, then dispatching will be difficult for SOAP Engine.
The operation information is available with RPC style of messaging. The document literal wrapped
design pattern resolves this shortcoming of document/literal style by adding a wrapper element
around the document representing the input parameters of the operation.

The relationship between the WSDL’s XSD and the single XML element in the SOAP body is well defined
Why do we need this in the first place? = BECAUSE IT IS WRAPPED !!!!!!!!! 🙂 🙂 🙂

The wsgen artifacts are the Java types from which the XML Schema types for the messages are derived.

Point is that the WSDL does not come from Java.
Artifacts generated from wsimport can be used to support a Java client against a web service or
to implement web service in Java. With a WSDL in hand,
a Java implementation of the service is within reach.

soap 1.2 – smpt, not an acronym, body last element of the xml structure.
can be manipulated through handlers.

LogicalHandler has access only to the message payload in the SOAP body,
whereas a SOAPHandler has access to the entire SOAP message,
including any optional headers and attachments

JAXB transfers the MIME types – image as Image and remaining as DataHandlers.
3 ways to transfer binary data:
– SwA (SOAP with Attachments),
– DIME (Direct Internet Message Encapsulation),
– MTOM (Message Transmission Optimization Mechanism),
which is based on XOP (XML-Binary Optimized Packaging).

if ETagFromServer != ETagOnClient || LastModifiedFromServer != LastModifiedOnClient

In doc literal the messages do not have data type definitions – but only ONE part name that points to xml elements
One part for input, One part for output.

In RPC the messages themselves have all the method parameters with their data types as well.

rpc encoded -method name with data types
rpc literal – no datat type – method name

doc literal – no method, only one op
doc literal wrapped – method name also included

port is the interface, binding is the concrete implementation which has the detail of which style is used

The setting:

use = ‘literal’

means that the service’s type definitions literally follow the WSDL document’s XML Schema. By contrast, the setting:

use = ‘encoded’

means that the service’s type definitions come from encoding rules, typically the encoding rules in the SOAP 1.1 specification. As noted earlier, the document/encoded and rpc/encoded combinations are not WS-I compliant.

No comments yet

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: