[
http://jira.jboss.com/jira/browse/JBMESSAGING-554?page=all ]
Richard Achmatowicz closed JBMESSAGING-554.
-------------------------------------------
Resolution: Done
I've tested the base classes which I added to define and incorporate an Admin
abstraction for generic JMS test cases and have committed the changes. The single test
case ConcurrentDeliveryTestCase now subclasses from JMSTestCase, which is the base class
for all generic JMS tests.
In order to have the right Admin implementation picked up, make sure that (i) the correct
version of provider.properties gets incorporated into the jar containing the tests and
(ii) thejar containing the tests gets seen first on the client-side classpath for the
tests, before any other jar containign a provider.properties file.
You can see the target tests-jbossmessaging in the AS testsuite for an example.
Create an Admin abstraction that would allow running generic JMS
tests regardless of provider implementation
------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-554
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-554
Project: JBoss Messaging
Issue Type: Sub-task
Components: Tests and Performance
Reporter: Ovidiu Feodorov
Assigned To: Richard Achmatowicz
Fix For: 1.2.0.Beta1
Since Messaging and JBossMQ use slightly different ways of deploying their administered
objects (destinations and connection factories), we need to create an unified Admin
interface that would allow to deploy these artifacts regardless of provider
implementation, and then create plug-ins for Messaging and MQ.
Initial work in this direction has been done by Adrian, see
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=72570
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira