IL PROTECTED]>
Sent: Friday, March 22, 2002 6:37 AM
Subject: RE: javax.xml.soap
> Based on those helpful comments, I'll continue plumbing in javax.xml.soap.
>
> Glyn
>
Based on those helpful comments, I'll continue plumbing in javax.xml.soap.
Glyn
Title: RE: javax.xml.soap
I hesitate to show my ignorance about this, but maybe in doing so I'll learn something. It seems to me that if you have an implementation of JAXM then you could create an implementation of JAX-RPC on top of that. Isn't the main difference that JAX-R
I believe we need to complete the plumbing at least as much
as we need to be JAX-RPC compliant.
Anything else is just gravy, as I don't think Axis
claims that JAXM is something we (will ever?) fully support.
--
Tom Jordahl
Macromedia
-Original Message-
From: Glyn Normington [mailto:[E
Title: RE: javax.xml.soap
I think whatever problems exist in the design of JAXM will eventually be worked out. My preference is to complete the plumbing. Until the JAXM issues are resolved, Axis could offer both an Axis-specific way of supporting document-based messaging and the JAXM way
Sorry to bother the "dev" list with this, but I think you folks will know a
lot more about this than the user community.
In looking at the CVS history for javax.xml.soap.MessageFactory.java, the
first commit comment says:
First cut of javax.xml.soap package from JAXM Spec.
- This is a subset of
