Paul
Paul Denning wrote:
Sorry that my colleagues and I have not been able to help in this
effort, but I have two questions:
1. Are the specs stable and are there any plans to submit them to
OASIS, W3C, IETF, or some other organization?
Probably Glen could answer this...
2. Does Axis2 implement these specs?
Not yet as our current implementation was done before these came out.
But we are quite close to these, and have plans to be fully implement
this in the future
asankha
Paul
At 12:35 PM 2007-03-21, Asankha C. Perera wrote:
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]
