Does the JMS specification require compatibility between JMS implementations, or will all parties involved have to use the same vendor?
Location: http://www.jguru.com/faq/view.jsp?EID=26394 Created: Mar 20, 2000 Modified: 2000-03-20 19:12:22.788 Author: Jerry Smith (http://www.jguru.com/guru/viewbio.jsp?EID=9) Question originally posed by Michael Prescott (http://www.jguru.com/guru/viewbio.jsp?EID=25013 The JMS specification, like many specifications, is an attempt to specify a software system with both core and optional functionality. As with many specifications, there are design and implementation issues that are unclear, or not fully specified. Sometimes, specifications are unclear in certain areas by accident; sometimes, ambiguities are inevitable, simply because the technology is new and it is virtually impossible to fully anticipate every issue. Over time, feedback from the developers who implement the specification helps clarify certain issues and the specification is then revised. Vendors who provide JMS implementations must implement the core functionality; implementing optional functionality is, of course, op
Related Questions
- Does the JMS specification require compatibility between JMS implementations, or will all parties involved have to use the same vendor?
- Does the specification require that all JMS implementations provide both point-to-point and publish/subscribe messaging?
- What are the risks involved in letting a vendor use a proprietary interface specification?
