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

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

> Hmm.. i wonder btw what transport protocol JMS is using if the client is
> outside the appserver? HTTP? RMI? RMI over HTTP? Some proprietary 
> protocol?
>
Isn't it proprietary?

>>>
>> 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.
>
>
> OpenPostoffice ->JMS ->J2EE
> MS-PostOffice -> MS-MQ -> MS
>

We don't want to exclusively use Java. By the same token we don't want 
to exclusively use .NET. The philosophy of web service is the separation 
of dependency between the client and server platform, which I think is a 
good idea.

>>
>> Afterall, I must confess that it makes sense to include ebXML into 
>> J2EE. It's enterprise thing.
>
>
> I agree... will hermes start using all of the functionality that is
> present in J2EE servers then? (connectionpooling, transactions) ;-)
>
Can you wait till next version? ;-)

Regards, -Patrick