How do we externalise the configuration of a Message-Driven bean using Websphere MQ, so that the package contains no environment-specific configuration within it, either as compiled annotations on the bean, or XML configuration packaged inside the jar. The reason or this we move the app from one env to another the queue will be different and we had to change this in our code( app) and repackage it everytime.
- Red Hat Enterprise Application Platform (EAP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.