[esb-issues] [JBoss JIRA] Updated: (JBESB-3471) CamelGateway does not support JNDI lookups

CamelGateway does not support JNDI lookups ------------------------------------------ Key: JBESB-3471 URL: https://jira.jboss.org/browse/JBESB-3471 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.9 Reporter: David Ward Assignee: Kevin Conner Fix For: 4.9 CP1 Attachments: camel-jms-2.4.0.jar, CamelGateway.java, CamelGateway.java.diff, CamelMessageComposer.java, CamelMessageComposer.java.diff, jboss-esb.xml One of the more common Camel components that a user might want to employ is the JMS Component: http://camel.apache.org/jms.html To use this component, one needs to specify the JMS ConnectionFactory. There is a parameter called "connectionFactory", but unfortunately, it does not take a String, but an actual javax.jms.ConnectionFactory. This would be fine if we depended on Spring to wire together the Camel components, but we don't want to enforce that dependency. In the absense of a parameter that simply takes the JNDI name of the ConnectionFactory and does the lookup for us, the CamelGateway should register a Camel TypeConverter that can convert from String (the JNDI name) to a ConnectionFactory (via JNDI lookup). Without this fix, users cannot use the JMS Component.