« Java 5, XPath and independent namespace declarations | Main | Document-based Web services »
March 10, 2006
The other way round...
I was able to reproduce the main problem of RPC concering loose coupling (see Reproduction of main problem with RPC).
Now I tried it the other way round, i.e. using JAXM. JAXM is used to access, create and process the SOAP messages directly. The same Hello World sample was developed using JAXM. It took a litte bit longer, because the messages must be created and parsed by hand.
The lucky result is:
Adding another parameter that caused the problems with JAX-RPC did not make any problems, the application runs perfectly with this changed interface.
It must be examined which changes cause problems with JAX-RPC and which cause problems with JAXM. These may be (incomplete list):
- Adding parameters
- Changing parameter sequence
- Deleting parameters (important / optional ones)
- Changing datatypes
- Changing result values / datatypes
- Adding / deleting methods
- Renaming methods
Posted by Dominik Marks at March 10, 2006 11:48 AM
Comments
JAXM is clearly much better. Unfortunately, it seems to be no longer under active development -- I seem to recall that Sun officially declared it dead some time ago, but I can't seem to find the link.
Posted by: Stefan Tilkov at March 10, 2006 2:32 PM
7FirUt hi! http://msn.com my site
Posted by: gosha03 at February 12, 2009 10:19 PM
b3b1252054diazepam prescription
Posted by: how at February 14, 2009 6:06 AM