[switchyard-issues] [JBoss JIRA] (SWITCHYARD-673) Consolidate HornetQ and ClientUtil classes used in quickstarts

[Keith Babo (JIRA)]

Keith Babo created SWITCHYARD-673:
-------------------------------------

             Summary: Consolidate HornetQ and ClientUtil classes used in quickstarts
                 Key: SWITCHYARD-673
                 URL: https://issues.jboss.org/browse/SWITCHYARD-673
             Project: SwitchYard
          Issue Type: Task
          Components: quickstarts, test
    Affects Versions: 0.4
            Reporter: Keith Babo
            Assignee: Tomohisa igarashi
             Fix For: 0.4



These classes are starting to pop up over and over again in JMS-related quickstarts.  Instead of just copying them over and over again, we should create one version that can be shared amongst all quickstarts.  There are two use cases here:

1) Test cases which need to use JMS and/or a JMS server.  These tests should be using the HornetQMixIn alone. Any additional dependencies on the ClientUtil classes need to be rolled into HornetQMixIn.

2) Most of these quickstarts also offer the option to use "mvn exec:java [options]" to test the application independently with the quickstart deployed to AS7.  This case also relies on the ClientUtil classes.  We need to change this to use HornetQMixIn (e.g. static methods on the class) or something else packaged in the switchyard-test module.  This module should be included in the test classpath and if the exec plugin is configured to include test dependencies in the classpath, all should be good.

BTW, it would be great if we could build the configuration for the exec plugin into the pom.xml, like I have done in multiApp/demos/consumer-service.  This makes it much easier for the user to simply type "mvn exec:java" without having to pass a bunch of -D options. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira