Message format between client and web service server

As we known, data transferred between web services server and client are xml-format. There are lots of web service client invoke types:
a)    JAX-RPC SOAP invocation. This approach eschewed generating remote interfaces. Instead one used fixed Service and Call interfaces to explicitly invoke WSDL operations, without going through the WSDL-to-Java mapping stage. This is JAX-RPC ,need more java library support and does not use http protocol.
b)    The Dispatch<Source> Interface. This approach eschewed generating remote interfaces. Instead one used fixed Service and Call interfaces to explicitly invoke WSDL operations, without going through the WSDL-to-Java mapping stage. This is use Http protocol.
c)    The Dispatch<SOAPMessage>  Interface. This approach eschewed generating remote interfaces. Instead one used fixed Service and Call interfaces to explicitly invoke WSDL operations, without going through the WSDL-to-Java mapping stage. But this is a bit more complex, largely because we have to explicitly construct the request message using the SAAJ API.
d)    The Dispatch<Object>  Interface. The first approach was to use a WSDL-to-Java mapping tool to generate service classes and service endpoint interfaces from WSDL.
e)    Others invocation types, such as Axis, CXF and so on. These types depends on lots of additional libraries from corresponding open sources projects.