Simon Laws wrote:
Has anyone in Tuscany made a binding that ships SOAP messages over JMS
instead of HTTP? Looking at the current code base and at the old code in
the
sandbox I don't see anything.
Simon
Simon,
Shouldn't this be a "simple" extension of the Web services binding?
The interesting question is how to indicate that a JMS transport should
be used instead of HTTP. The spec only allows for this to be done via
WSDL at the moment - not so good if you didn't want to create the WSDL
yourself.
How about the idea of adding an intent for the Web services binding
which can be used to indicate the transport??
eg:
transport.http = use the HTTP transport (default)
transport.jms = use the JMS transport
transport.foo = use the foo transport....
The Web services binding can indicate which of these intents it supports
- since that depends on the support being available in the Web
services stack that you are using.
Yours, Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
