Re: [ebxmlms-general] Axis incompatibilities

[David W. \(XML\) <da...@dr...>]

Mattias,

I think you are missing the point here.

You have two incompatible library JAR files.

Whenever this happens you need to create two new instances (installs)
of the server.  One for each JAR file.

Completely separate sub-directories - and so the
path settings in each case just reference the one instance.

Then config each one on a separate port.

DW

----- Original Message ----- 
From: "Mattias J" <mj...@ex...>
To: <ebx...@li...>
Sent: Wednesday, June 15, 2005 9:58 AM
Subject: RE: [ebxmlms-general] Axis incompatibilities


> At 2005-06-15 15:31, you wrote:
> > > Unfortunately I have no experience with JMS. What would the message
sent
> > > between the application and the Hermes client application contain?
> >
> >The same as would be the case with registering a normal messagelistener
in
> >hermes.
>
> But the Hermes message listener receives a
> hk.hku.cecid.phoenix.message.packaging.EbxmlMessage...?
>
> (Besides the fact that I cannot see the meaning of the separate Hermes
> client, this will not work since I cannot produce correct EbxmlMessage
> objects in my application because of Axis).
>
>    /Mattias J
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>