My approach has been to take numerous small steps, and at each step,
refactor some org.apache.axis.message classes to closely match
javax.xml.soap and then make the Axis classes implement the corresponding
JAXM interfaces. Then the Axis and JAXM interfaces co-exist.
I don't think the Axis interfaces (i.e. the methods of the Axis classes
which are not inherited from JAXM) are likely to disappear as some
committers prefer them to JAXM. For example, the JAXM method for adding a
header unnecessarily throws an exception, which the corresponding Axis
method doesn't.
I'm not able to comment on JAXP.
Glyn
"L Rutker"
<lrutker@hotmail. To: [EMAIL PROTECTED]
com> cc:
Subject: Re: What is the Relationship
between JAXM and AXIS?
23/04/02 15:50
Please respond to
axis-user
Thanks.
The JAXM interfaces seem to overlap and provide the same interfaces that
the
Axis classes do.
Will these Axis classes become implementations of JAXM? Will they coexist?
Will the Axis interfaces disappear?
I guess my expectation is that something like JAXP will unify all Java
implementations so that a common interface can be used no matter what
implementation will be used.
Thanks
>From: "Glyn Normington" <[EMAIL PROTECTED]>
>
>
>JAXM is a specification (NB. not an implementation) of two sets of
>interfaces: javax.xml.soap and javax.xml.messaging.
>
>Axis currently implements *some* of the javax.xml.soap interfaces,
although
>these are not mentioned in the list of published interfaces in the Axis
>Users Guide as the job is only partly complete. I hope to implement the
>other JAXM SOAP interfaces as a low-priority, background task, but would
>welcome help from anyone who is keen to see them implemented sooner.
>
>There is also an Axis to-do item to implement javax.xml.messaging, but
>no-one has agreed to take that on.
>
>Glyn
_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
