Stuart Clayton [http://community.jboss.org/people/stuartclayton22] created the discussion
"Re: Using JNDI to connect to Websphere MQ, without hardcoded info" To view the discussion, visit: http://community.jboss.org/message/629707#629707 -------------------------------------------------------------- One of the people at my current project hit on the best solution of all: no ejb-jar.xml and jboss.xml, and only one "hard-coded" configurable property in the class annotations that nevertheless can be put in a single, central place in your code: the name of the resource adapter jar. @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = CommonValue.JMS_QUEUE_CLASS), @ActivationConfigProperty(propertyName = "destination", propertyValue = "AgwIncomingGpsQ4"), @ActivationConfigProperty(propertyName = "DeliveryActive", propertyValue = "false"), @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "true") }) @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) @ResourceAdapter(value = CommonValue.JMS_RESOURCE_ADAPTER_NAME) @AspectDomain("AgwIncomingGpsDomain4") public class IncomingMdbQ4 implements MessageListener { -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/629707#629707] Start a new discussion in JNDI and Naming at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2083]
_______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
