|By Dave Chappell||
|November 10, 2003 10:16 AM EST||
IBM has published the results. The publishing of the results is something that the legal agreement allows the spec authors to do. A public version of the legal agreement and the test scenario document can be found here.
The interop participants included -
BEA Systems, Inc
Blue Titan Software, Inc.
NEC Laboratories America, Inc.
Sonic Software Corporation
TIBCO Software, Inc.
The results, as written in the public report, exceeded expectations. We actually finished early.
The way the workshop works is all the vendors sit in a room and fire messages at each other. The test scenario, as outlined in the publicly available test scenario document, is relatively simple. It's a simple ping test of sending 3 sequenced messages to another WS-ReliableMessaging enabled endpoint. The receiving endpoint responds with an acknowledgement message that contains the range of message sequence numbers that it received. That's it. Sounds simple, but Rome wasn't built in a day. You have to start somewhere.
A new Yahoo! groups discussion forum has been established. IBM's Doug Davis has also extended an invitation to multiple places, including the SOAPBuilders Interoperability group. The new WS-ReliableMessaging discussion forum is a private list, but anyone can join provided they sign a legal agreement that basically says anything you contribute to the list becomes donated to the spec authors on a royalty free basis.
The participating companies are in the process of putting up a list of publicly available WS-ReliableMessaging endpoints so that we can continue our testing without necessarily having to sit in the same room. The endpoints are referenced here, and will be updated as more of us get our endpoints out there.
|Joseph M. Chiusano 11/17/03 09:11:36 PM EST|
Was there any indication that WS-ReliableMessaging might transition to an open standards consortium in the near-term or medium-term future?
- ESB Myth Busters: 10 Enterprise Service Bus Myths Debunked
- ESB Integration Patterns
- Universal Middleware: What's Happening With OSGi and Why You Should Care
- Guaranteed Messaging With JMS
- Benchmarking JMS-Based E-Business Messaging Providers
- Distributed Logging Using The JMS
- Reconstructing J2EE-Java Business Integration Meets the Enterprise Service Bus
- Service-Oriented Integration: Making the Right Choices to Support Next-Generation Integration
- The Java Message Service
- A Real-World Example