You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2006/10/10 17:53:19 UTC
[jira] Created: (QPID-31) Setup JMS Compliance test suite to run
against Qpid broker
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Created: (QPID-31) Setup JMS Compliance test suite to
run against Qpid broker
Posted by Tim Fox <ti...@jboss.com>.
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.
>
>
>
Re: [jira] Assigned: (QPID-31) Setup JMS Compliance test suite to run against Qpid broker
Posted by Rajith Attapattu <ra...@gmail.com>.
I will reply as soon as I have something.
Regards,
Rajith
On 11/10/06, Carl Trieloff <cc...@redhat.com> wrote:
>
>
> FYI - Rajith and I have been trying to sort out the details so that the
> project can
> use CTS test from JCP. Suggest following up with Rajith.
>
> Carl.
>
> Tejeswar Das (JIRA) wrote:
> > [ http://issues.apache.org/jira/browse/QPID-31?page=all ]
> >
> > Tejeswar Das reassigned QPID-31:
> > --------------------------------
> >
> > Assignee: Tejeswar Das
> >
> >
> >> 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
> >> Assigned To: Tejeswar Das
> >> Fix For: M2
> >>
> >>
> >> 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.
> >>
> >
> >
>
>
>
Re: [jira] Assigned: (QPID-31) Setup JMS Compliance test suite to
run against Qpid broker
Posted by Carl Trieloff <cc...@redhat.com>.
FYI - Rajith and I have been trying to sort out the details so that the
project can
use CTS test from JCP. Suggest following up with Rajith.
Carl.
Tejeswar Das (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/QPID-31?page=all ]
>
> Tejeswar Das reassigned QPID-31:
> --------------------------------
>
> Assignee: Tejeswar Das
>
>
>> 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
>> Assigned To: Tejeswar Das
>> Fix For: M2
>>
>>
>> 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.
>>
>
>
[jira] Assigned: (QPID-31) Setup JMS Compliance test suite to run
against Qpid broker
Posted by "Tejeswar Das (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-31?page=all ]
Tejeswar Das reassigned QPID-31:
--------------------------------
Assignee: Tejeswar Das
> 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
> Assigned To: Tejeswar Das
> Fix For: M2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (QPID-31) Setup JMS Compliance test suite to run
against Qpid broker
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-31?page=all ]
Marnie McCormack updated QPID-31:
---------------------------------
Fix Version/s: M2
> 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
> Fix For: M2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (QPID-31) Setup JMS Compliance test suite to run
against Qpid broker
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-31?page=all ]
Marnie McCormack closed QPID-31.
--------------------------------
Resolution: Incomplete
Assignee: (was: Tejeswar Das)
No progress on this task and was then overtaken by TCK testing. Closing as now redundant and CTS removed from project by QPID-169.
> 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
> Fix For: M2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira