Win a copy of Practical SVG this week in the HTML/CSS/JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

JAX-RPC vs JAXM

 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
I would like to have your feedback here, according to your understanding and experience of the webServices technology.
In a near futur, what will be the best architectural aproach to send coarse-grained xml requests with web services ?
OPTION 1 : JAX-RPC with a document in SAAJ
OPTION 2 : JAXM with a document in SAAJ
or other options ???
JAXM seems to be designed for that, but the fact it is not part of J2EE 1.4 is puzling me.
So maybe OPTION 1 is better for evolutivity and futur compliance.
What should help to choose between the 2 technologies ?
 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
An element of answer, from the BluePrint team
Btw, this forum has calmed down since the books have been won

3.7.5 Use JAXM and SAAJ Technologies for Handling Documents
The J2EE platform provides an array of technologies�including mandatory technologies
such as JAX-RPC and SAAJ and optional technologies such as JavaTM API for XML Messaging (JAXM)�that enable message and document exchanges with SOAP. Each of these J2EE technologies offers a different level of support for SOAP-based messaging and communication. (See Chapter 2 for the discussion on JAX-RPC and SAAJ.)
An obvious question that arises is: Why not use JAXM or SAAJ technologies
in scenarios where you have to pass XML documents? If you recall:
� SAAJ lets developers deal directly with SOAP messages, and is best suited for
point-to-point messaging environments. SAAJ is better for developers who
want more control over the SOAP messages being exchanged.
� JAXM defines an infrastructure for guaranteed delivery of messages. It provides
a way of sending and receiving XML documents and guaranteeing their
receipt, and is designed for use cases that involve storing and forwarding XML
documents and messages.
SAAJ is considered more useful for advanced developers who thoroughly
know the technology and who must deal directly with SOAP messages. However,
SAAJ is not recommended with services that require you to pass XML documents.
Using JAXM for scenarios that require passing XML documents may be a
good choice. Note, though, that JAXM is optional in the J2EE 1.4 platform. As a
result, a service developed with JAXM may not be portable.
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I wouldn't work with JAX-M, especially on WebSphere. There are no plans to support it. JAX-RPC, however, will be fully supported.
Kyle
 
Steve Watson
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
BEA also has no plans to support JAXM. I also hear rumors that JAXM's future is doubtful - that much of it's functionality will be included in a futre version of JMS.
Steve Watson
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!