axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Volkmann, Mark" <Mark.Volkm...@AGEDWARDS.com>
Subject RE: javax.xml.soap
Date Thu, 21 Mar 2002 22:33:58 GMT
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-RPC is more specific about the content of the SOAP body?
If this is the case then I don't see why Axis shouldn't fully support JAXM.

> -----Original Message-----
> From: Tom Jordahl [mailto:tomj@macromedia.com]
> Sent: Thursday, March 21, 2002 4:06 PM
> To: 'axis-dev@xml.apache.org'
> Subject: RE: javax.xml.soap
> 
> 
> 
> 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:glyn_normington@uk.ibm.com]
> Sent: Thursday, March 21, 2002 11:01 AM
> To: axis-dev@xml.apache.org
> Subject: javax.xml.soap
> 
> 
> Before the beta, I started plumbing the javax.xml.soap 
> interfaces into the
> Axis message classes such as javax.xml.soap.SOAPElement. I 
> didn't get very
> far - MessageElement now implements SOAPElement. The reason 
> was in order
> better to support a UDDI server based on Axis which needs to 
> get involved
> in deserialisation. The javax.xml.soap interfaces are likely 
> to be more
> stable than the corresponding concrete classes in Axis such as
> MessageElement.
> 
> Since then I've read a number of disparaging remarks about 
> JAXM and wonder
> if it is likely to fall into disuse.
> 
> The options appear to be:
> 
> 1. Complete the plumbing.
> 2. Rip out the current plumbing and do without separate interfaces.
> 3. Rip out the current plumbing and define separate 
> interfaces analogous to
> the javax.xml.soap interfaces.
> 
> I don't like 2 if, as appears to be likely, it will be useful 
> to expose the
> classes/interface as published Axis externals.
> 
> 3. would give us more freedom and might be the best option 
> *if* JAXM is on
> the way out.
> 
> Thoughts?
> 
> Glyn
> 


***************************************************************************************
WARNING:  All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
***************************************************************************************

Mime
View raw message