Hi Paul
I have been reading through these specs again last weekend and was
preparing to make the enhancements to the current implementation to be
consistent. I also wanted the JMS transport to be able to address the
open issues filed against it.. I hope to embark on this. Would you be
willing to help in this effort or its testing?
asankha
Paul Denning wrote:
What is the status of this effort?
Paul
At 09:03 AM 2007-01-12, Glen Daniels wrote:
Hi Axis-Dev'ers:
As some of you may know, several companies (BEA, IBM, Progress, and
TIBCO) have been working on a formal set of specifications for binding
SOAP to the Java Message Service API. These specs consist of a) a SOAP
binding, and b) a description of the "jms:" IRI scheme which is used for
addressing. The specs do NOT cover an interoperable wire-level
representation which could bridge different vendors' JMS implementations
- though a future version might go there. This version has been
designed so that plugging in a different implementation should work
seamlessly without recompiling any code; as such we define a
BytesMessage encapsulation of SOAP (and MTOM), a "Content-Type" JMS
header, and a few other needed parts.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
