Re: [ebxmlms-general] Axis incompatibilities

[Ronald v. K. <rtv...@xs...>]

No, not neccesarilly. All combinations are possible.

db sharing with triggers via jms/webservice/file/... or also passing the full content via
jms/webservice/file is possible.

Look at how the monitor application communicates with the server. Two different jvm's and it
works. That is the main part of the solution, two different jvm's

Ronald


Mattias J probeerde me het volgende duidelijk te maken:
> So JMS is only used for triggering while the actual data is transferred
> elsewhere?
> That means the addressing (URL, CPA-ID, service, action) of the message
> must be handled by (or transferred to) the "second" application.
> Probably possible, but not too appealing...
>
> At 2005-06-15 17:05, you wrote:
>>Mattias,
>>
>>Yes - JMS is complicated if you are not using it already.
>>
>>I think the idea here is that both instances share the same databases, so
>>you can have a handler in the second instance triggered by a data handler
>>fromt he first instance placing the XML string object into the database.
>>
>>DW
>>
>>----- Original Message -----
>>From: "Mattias J" <mj...@ex...>
>>To: <ebx...@li...>
>>Sent: Wednesday, June 15, 2005 10:40 AM
>>Subject: Re: [ebxmlms-general] Axis incompatibilities
>>
>>
>> > Yes, but the question is how I communicate between the two instances -
>>what
>> > is their "interface". You suggested JMS, and since I am not familiar with
>> > JMS I asked what kind of message to send.
>> >
>> > You said "same as would be the case with registering a normal
>> > messagelistener in hermes", which I interpreted as an
>> > hk.hku.cecid.phoenix.message.packaging.EbxmlMessage instance object.
>> > Do you mean to send this as an XML string?
>> >
>> > At 2005-06-15 16:30, you wrote:
>> > >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
>> > > >
>> > >
>> > >
>> > >
>> > >-------------------------------------------------------
>> > >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
>> >
>> >
>> >
>> > -------------------------------------------------------
>> > 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
>> >
>>
>>
>>
>>-------------------------------------------------------
>>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
>
>
>
> -------------------------------------------------------
> 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
>


-- 
Kijk niet terug, maar kijk naar mij
Against all odds