Re: [ebxmlms-develop] Sun WSDP1.2 without jaxm

[Ng C. Y. [Cyng] <cy...@cs...>]

Hi,

> I just read the releasenotes of  WSDP 1.2 and there does not seem to be
> a  JAXM anymore (neither in j2ee 1.4 draft 3). Not that I realy care for
> that, but since it is not there anymore, shoudn't we try to remove it
> from Hermes as well?
> Can anybody summarize what the open issues are to fully move to axis? I
> still have limited time, but in a few weeks I could give it a try

        I note that the name "SAAJ" is still in the description. According
to my interpretation, since JAXM 1.1.1, those classes under
javax.xml.soap.* (such as SOAPMessage) are grouped into SAAJ while
those under javax.xml.messaging.* (such as JAXMServlet, ProviderConnection)
are so-called JAXM. It seems that SAAJ are used for over 90% of the time
for composing SOAPMessage (and thus ebMS packaging), implementations
of ProviderConnection, ReqRespListener for ebMS are seldom met.

        So, it's really a great idea to remove all these kinds of stuff
(SAAJ and JAXM) from Hermes. In the current 1.0 branch, Http.java has
already sent a SOAPMessage using direct HTTP (HttpURLConnection) instead
of SAAJ's SOAPConnection.call(). Patrick also implemented the file-based
EbxmlMessage by adding our own PayloadContainer instead of SAAJ's
AttachmentPart. The remaining work should be on SOAPMessage inside
EbxmlMessage only. After removing this part, Hermes should be SAAJ and
JAXM free. SAAJ just rides on DOM4J which then rides on JavaMail's
MimeMultipart. Personally speaking, I like jdom which works much
faster and efficient. How about if we introduce jdom into packaging/* ?

Regards,
CY

----------------------------------------------------------------------------
Ng Chi Yuen, CY.       cy...@ce...       http://www.cecid.hku.hk/
Technology Officer,
Centre for E-Commerce Infrastructure Development,
The University of Hong Kong
----------------------------------------------------------------------------