[jboss-dev-forums] [Design of JBoss ESB] - JMS Listener Mapper and JCA activation

https://jira.jboss.org/jira/browse/JBESB-2538 raises an issue with the mapping of properties onto activation contexts, specifically maxSession but in reality a more general issue. The JMS listener mapper has an explicit binding between some of the properties in the configuration and those required for activating the JCA context and, at present, these are specific to JBoss. We need to generalise this behaviour now that we are working with other providers. The current properties specified are "destination" <- messageFilter.getDestName() "providerAdapterJNDI" <- jmsJcaProvider.getProviderAdapterJNDI() "destinationType" <- Queue.class.getName() or Topic.class.getName() "messageSelector", messageFilter.getSelector() "maxSession" <- listener.getMaxThreads() To solve this I am proposing to create an adapter interface, an implementation of which can be specified using the listener properties (no schema changes) with the default being the JBoss mappings. The implementation will probably look something like the following | public interface ActivationAdapter | { | public void setDestination(final String name) | throws ConfigurationException ; | | public void setProviderAdapterJNDI(final String providerAdapterJNDI) | throws ConfigurationException ; | | // true for queue, false for topic | public void setDestinationType(final boolean queue) | throws ConfigurationException ; | | public void setMessageSelector(final String messageSelector) | throws ConfigurationException ; | | public void setMaxThreads(final String maxThreads) | throws ConfigurationException ; | } | Can anyone see anything I have missed? Any other suggestions? Thanks Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226423#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...