0 Replies Latest reply on May 29, 2013 11:34 PM by nav

    Externalizing MDB configurations in Jboss 7.1.1

    nav Newbie

      Hi Guys,

       

      I'm using Jboss as 7.1.1 and I have my EJB MDB annotation such as below:

       

      @MessageDriven(activationConfig = {
              @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
              @ActivationConfigProperty(propertyName = "destination", propertyValue = "XXX.IN"),
              @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"),
              @ActivationConfigProperty(propertyName = "hostName", propertyValue = "XXX.com"),
              @ActivationConfigProperty(propertyName = "port", propertyValue = "3434"),
              @ActivationConfigProperty(propertyName = "queueManager", propertyValue = "A01"),
              @ActivationConfigProperty(propertyName = "channel", propertyValue = "CLIENT.TO") }, name = "MQMDB")
      public class MyMessageListener implements MessageListener {
      

       

      I know it can be moved to ejb-jar.xml but can I move this configuration out of the code and into jboss standalone.xml file?

       

      The reason is we will be having seperate standalone.xml for each of our environments like dev, test and live and therefore would prefer to move all the configurations out of the application deployment.

       

      Thanks!