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

[Christophe Hartwig-P. <chr...@re...>]

Hi all,

At the beginning, I considered ebXML as an alternative to Web Services...
But this mistake was due to my lack of understanding.

My understanding now is that ebXML is a MOM protocol, but this kind of 
assertion is found nowhere, hence the ambiguity with Web Services. So 
assertions like "Web services will take over ebXML" are just plain 
nonsense : you can't compare MOM with RPC.
Then JAXM has added its load of ambiguity, since it has added one more 
API in the Java world, despite the existence of a proven API for MOMs, 
JMS...

Don't you think that there would be a place in the ebXML for a JMS based 
implementation of ebXML MSH for its encoding and transport ?
I can imagine implementing ebXML on top of an existing JMS 
implementation would make things easier : JMS already has reliable 
messaging semantics, and already offers transactional persistent 
messages, etc... Many features of Hermes are already supported by JMS 
implementations... And JMS supports temporary queues (and reply-to) for 
request-response messages... And JMS already offers Message Beans 
integration... and JMS is most often clusterable... and ... I like that 
idea :-)

I think such an implementation would make the use of ebXML simpler, 
better integrated with J2EE environments, would reduce the learning 
curve, would make ebXML an obvious choice for reliable messaging...

Your thoughts ?

Bye
Chris

PS : I think my idea means a new implementation, not just an adaptation 
of Hermes...

---------------------------------------------------------------------
 Christophe HARTWIG - Interface Technologies   cha...@re...
 17, avenue Andre Roussin                    http://www.reservit.com
 ZAC de Saumaty-Seon                        Tel : + 33 4 91 03 64 90
 13016 MARSEILLE - FRANCE                   Fax : + 33 4 91 03 64 92
---------------------------------------------------------------------