Uploaded image for project: 'SwitchYard'
  1. SwitchYard

Consolidate HornetQ and ClientUtil classes used in quickstarts


    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 0.4
    • Fix Version/s: 0.4
    • Component/s: quickstarts, test
    • Labels:


      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.

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  igarashitm tomohisa igarashi
                  kcbabo Keith Babo
                • Votes:
                  0 Vote for this issue
                  2 Start watching this issue


                  • Created: