Re: [ebxmlms-general] Axis incompatibilities

[Mattias J <mj...@ex...>]

That is not the problem. It is about using Axis as the SAAJ implementation; 
i.e. replacing saaj-ri.jar with axis.jar.

I need to do this, because we have an application that responds to SOAP 
requests using Axis, so axis.jar is already there and then we also wanted 
to send ebXML messages from it. So adding Hermes msh.jar (with 
dependencies; but not saaj-ri.jar) for communicating with Hermes server 
creates erroneous messages, for the reasons detailed in the Axis JIRA entry 
below.

At 2005-06-11 18:04, you wrote:
>Can you just put up two instances of Apache - on different ports -
>one for Axis, the other Hermes, to avoid this conflict?
>
>DW
>
>----- Original Message -----
>From: "Mattias J" <mat...@ex...>
>To: <ebx...@li...>
>Sent: Saturday, June 11, 2005 1:43 AM
>Subject: [ebxmlms-general] Axis incompatibilities
>
>
> > As stated in the (currently) bottom-most post, this isn't really an issue
> > for me any more, but possibly somebody want to have a look at the
> > incompatibility between Apache Axis and Hermes. Problems arose when trying
> > to send ebXML messages from an application already using Axis for SOAP.
> > See http://issues.apache.org/jira/browse/AXIS-1469