When I attended the JavaOne conference in June I asked one of the speakers/JAX-RPC developers from Sun why the JAXM (Java API for XML Messaging) was not included in the latest release of the Java Web Services Developers Pack (1.2). She said that it was because the JAXM library was not developmentally mature, which really concerns me since I have 5 production application using JAXM. She recommended using JAX-RPC (Remote Procedure Calls) instead, which I've been researching.
So, I found it interesting that the author has chosen to include JAXM in his book. I have no beef against JAXM, it works as stated. But the threat of abandoned developments concerns me... Does JAXM have some life left in it yet? Does the author know something we don't?
Slashdot Mirror
So, I found it interesting that the author has chosen to include JAXM in his book. I have no beef against JAXM, it works as stated. But the threat of abandoned developments concerns me... Does JAXM have some life left in it yet? Does the author know something we don't?