Differences between revisions 3 and 4
Revision 3 as of 2005-01-12 04:59:44
Size: 862
Comment: Fixing a broken link
Revision 4 as of 2009-09-20 22:47:44
Size: 866
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
Other Java-based implementations of the [http://jcp.org/aboutJava/communityprocess/first/jsr101/index.html JAX-RPC] Other Java-based implementations of the [[http://jcp.org/aboutJava/communityprocess/first/jsr101/index.html|JAX-RPC]]
Line 9: Line 9:
Also, Axis supports both [http://www.gotdotnet.com/team/xml_wsspecs/dime/draft-nielsen-dime-01.txt DIME] and SwA; defaulting to SwA client side, and handling either on the server. JAX-RPC only mandates SwA support, so you must use SwA for attachments. Also, Axis supports both [[http://www.gotdotnet.com/team/xml_wsspecs/dime/draft-nielsen-dime-01.txt|DIME]] and SwA; defaulting to SwA client side, and handling either on the server. JAX-RPC only mandates SwA support, so you must use SwA for attachments.

Interoperability with other JAX-RPC implementations?

Other Java-based implementations of the JAX-RPC spec should be strongly interoperable with Axis, because there is a simple 1:1 mapping of Axis datatypes to those at the far end, and because the JAX-RPC compliance tests add extra testing to the process.

Note that Axis serializes many datatypes that JAX-RPC does not cover: the unsigned types, Maps, and the like. You are only guaranteed interop with those datatypes covered in the JAX-RPC specifications.

Also, Axis supports both DIME and SwA; defaulting to SwA client side, and handling either on the server. JAX-RPC only mandates SwA support, so you must use SwA for attachments.

FrontPage/Axis/JaxRpcInterop (last edited 2009-09-20 22:47:44 by localhost)