[
http://jira.jboss.com/jira/browse/JBMESSAGING-554?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-554:
-------------------------------------------------
The classes I forsee using are:
* Admin class - which defines the administration interface (reused from JOram test
framework)
* AdminFactory class - which provides a mechanism for specifying an Admin implementation
and loading it into memory (reused from JOram test framework)
* JBossMessagingAdmin class - which implements Admin methods using Messaging specific
JMX method calls, and so requires an embedded JBossTestServices instance. Based on
existing JBossMQAdmin class.
* JMSTestCase - the base class for all generic JMS tests. This subclasses from
JBossTestCase, to provide access to the AS and common functions. As most of the JBossMQ
test cases subclass from JBossTestCase, this will reduce the amount of refactoring
involved in making the JBossMQ test cases generic. This class will also be resposible for
locating and setting up the Admin instance.
Thus, in order to refactor a JBossMQ test into a 'generic' JMS test which can be
run against either Messaging or JBossMQ, it should be possible to leave most of the code
in place, and just change the code related to administrative functions. The
generic-fication of thes test cases thus only applies to the pluggable Admin interface -
general operations for security, logging, etc, are still AS specific.
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