To be able to say the implementation is JMS compliant you would need to
pass the Sun JMS TCK (part of the J2EE TCK)
http://java.sun.com/scholarship/
I'm just saying this since otherwise it's very likely Sun will get quite
upset, since I know they are very particular about these kinds of things.
Marnie McCormack (JIRA) wrote:
Setup JMS Compliance test suite to run against Qpid broker
----------------------------------------------------------
Key: QPID-31
URL: http://issues.apache.org/jira/browse/QPID-31
Project: Qpid
Issue Type: New Feature
Components: Java Broker
Environment: All
Reporter: Marnie McCormack
The JMS CTS application generates reports on JMS compliance (see
http://jmscts.sourceforge.net/index.html).
The JMS CTS jars/scripts are currently in svn
(client\test\src\org\apache\qpid\cts) but have never been run as we not
preivously have the required management tools to run the tests e.g. the ability
to purge queues programmatically.
There will be other associated setup tasks to be completed as part of this work
i.e. create required configuration files to point test suite at running broker,
setting classpath in env script ? etc.
The output from CTS could be very useful in generating the task list for Qpid
for the next few weeks.
