JBoss Community

JBoss 7.1.1 MDB with IBM MQ - MessageDriven Annotation not configurable

created by Bharadwaja Dasari in EJB3 Development - View the full discussion

I have implemented MDB with Jboss 7.1.1 using IBM MQ Listener. My Listener Code is below

 

@MessageDriven(

                    activationConfig = {

                            @ActivationConfigProperty(propertyName = "hostName", propertyValue = "111.11.11.11"),

                            @ActivationConfigProperty(propertyName = "port", propertyValue = "1420"),

                            @ActivationConfigProperty(propertyName = "channel", propertyValue = "Channel Name"),

                            @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"),

                            @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),

                            @ActivationConfigProperty(propertyName = "destination", propertyValue = "Name of Destination Queue"),

                            @ActivationConfigProperty(propertyName = "queueManager", propertyValue = "Queue Manager Name"),

                            @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),

                            @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "50")

                    })

@ResourceAdapter(value="wmq.jmsra.rar")

 

All this works perfectly(only change here is I have masked the actuals and replaced it with dummies in property values) but the problem is this is all hardcoded. I want it to be configurable, like say if I am in one environment, I want to pick it from properties files for that particular environment

 

OR  if I use the command to start ./standalone -c standalone-full-xyz.xml, and this standalone-full-xyz.xml should have all the config properties for that environment, so atleast that will help make it configurable

 

How can I acheive this? Any help.

Reply to this message by going to Community

Start a new discussion in EJB3 Development at Community