[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-554) Create an Admin abstraction that would allow running generic JMS tests regardless of provider implementation
[ http://jira.jboss.com/jira/browse/JBMESSAGING-554?page=comments#action_12... ]
Ovidiu Feodorov commented on JBMESSAGING-554:
---------------------------------------------
Ideally, I (or anyone else) should be able to do this:
- check out the AS trunk
- build the AS: ./build/build.sh
- run the Messaging installation procedure (this is reduntant, Messaging should come as
default provider, but for the time being, this is fine): ant -f release-admin.xml
- run ./build/build.sh tests-messaging (or whatever target name you went for) and get a
full set of JMS integration tests passing
- run ./build/build.sh test-jbossmq and get a full set of JMS integration tests passing
How close are you to this?
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