JAX-WS: Java API for XML Web Services. Does message oriented as well as RPC oriented services. Hides complexities of SOAP. No need to generate or parse SOAP messages (or understand the structure or format).
The JAX-WS endpoints must be annotated with @WebService or @WebServiceProvider. The business method must be annotated @WebMethod – a Service Endpoint Implementation (SEI) will be generated for this. JAXB compatible parameters are required.
Um, if you think Web Services or Clouds are NOT important, I hope the following stat will convince you.
The Client needs @WebServiceRef – the reference to the service (or wsdlLocation). Get the port from the service and then invoke the exposed method on the service. Yes you need the interface to the service.
JAX-WS 2.0 Support WS-I Basic Profile Version 1.1, SOAP 1.1 and WSDL 1.1.
There is support for doc/lit, rpc/lit, static ports, dynamic proxies, and DII.
All in all JAX-WS seems like a winner!
Well, can you still use SAAJ? Yes – it gives you direct access to the SOAP protocol and the SAAJ 1.3 API supports SOAP 1.1 and SOAP 1.2 specifications.
<Message>
<Part>
<Envelope>
<Header>
</Header>
<Body>
</Body>
</Envelope>
</Part>
</Message>
You can have Attachment Parts as peers to the Part. all Under the soap message but outside the envelope.
The attachment part will contain MIME headers and the content (any).
Um – BTW – you can use JAX-B to send SOAP Attachments too – so why would you want to bother with the SAAJ APIs is going to remain a mystery. But it’s there.
