Allow the JMS RAR to determine the destinationType at runtime ------------------------------------------------------------- Key: JBAS-5841 URL: https://jira.jboss.org/jira/browse/JBAS-5841 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Adrian Brock Assignee: Jesper Pedersen Fix For: JBossAS-5.0.0.CR2 Currently the JMS RAR requries the destinationType in the activation config properties to be configured, see required activation config properties in ra.xml This is as per the spec recommendation in JCA 1.5 Appendix B Instead, we try to determine the destinationType from the destination. Proposed change: 1) Remove destinationType as a required activation config property from ra.xml 2) Rework org.jboss.resource.adapter.jms.inflow.JmsActivation::setupDestination() to cater for not having destinationType, i.e. lookup the destination in jndi and determine its type from the interfaces 3) Store the resulting type in JmsActivation and use it in setUpConnection() instead of spec.isTopic() 4) Remove the isTopic() helper from JmsActivationSpec since it is now potentially misleading -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira