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

[Ng C. Y. [Cyng] <cy...@cs...>]

Hi,

> The point is : would the J2EE JCP comittee accept an implementation
> (ebXML) which would not rely on a standard (J2EE postoffice ?) to remain
> abstract ? I don't think so, and I would not either. The second question
> is: if ebXML is not part of J2EE, does it mean it's not an Enterprise
> feature ? The answer is definitely no, so a solution must be found !
> Abstract API is the Java-way solution...

        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.

Regards,
CY

----------------------------------------------------------------------------
Ng Chi Yuen, CY.       cy...@cs...       http://www.cecid.hku.hk/
Technology Officer,
Centre for E-Commerce Infrastructure Development,
The University of Hong Kong
----------------------------------------------------------------------------