Re: [ebxmlms-general] idea : use ebXML to bridge the gap, through JMS

[Patrick Y. <kc...@ce...>]

Christophe Hartwig-Peillon wrote:

> Hi all,
>
>>        What do you think if the interface between the client and Hermes
>> is Web Service? (Maybe with reliability as well.) In this case, the 
>> client
>> side need not be JMS API call at all while Hermes server need not use
>> a JMS provider and it already sits there to receive HTTP Web Service 
>> call.
>> So far, Hermes does not yet touch the J2EE, JMS features and can be thus
>> deployed in an app server as simple as Jetty that SMEs' may feel a 
>> little
>> bit light-weight.
>>  
>>
> As far as I know, Hermes and the client already rely on an HTTP based 
> protocol... The problem is reliability : when two processes cooperate, 
> you take the risk of having one down (hermes in our case). In this 
> case, the whole system is down...
> Relying on JMS, in the context of an app server, suppresses this problem.
> Another interest of JMS is load balancing/fault tolerance.
> Maybe other free JMS implementations could be used... there are many 
> of them !
>
Another concern is exclusivity of Java world. A postoffice, by its 
nature, does not imply Java. MQSeries does provide JMS interface, but 
JMS is definitely not the only way to access MQ. Some demands we have 
here is to make a postoffice neutual enough to let clients from other 
worlds (e.g. .net) to use it.

> I must confess I have an app server in my system (jBoss, clustered for 
> fault tolerance). Does it mean that the protocol between Hermes and 
> the client should be made pluggable ? This suits the J2EE spirit...
>
Pluggable? Hmm.... do you mean allowing multiple ways for the client to 
connect to Hermes? In the best case, we can find a standard and 
everybody connect to Hermes (and others message servers) in the same 
way. I believe that one day we will have it.

> Anyway, I tried to correlate the kind of architecture hermes could 
> have with requirements for inclusion into J2EE...
> ebXML, with JAXM is out of J2EE.


Afterall, I must confess that it makes sense to include ebXML into J2EE. 
It's enterprise thing.

Regards, -Patrick