[esb-issues] [JBoss JIRA] Commented: (JBESB-3471) CamelGateway does not support JNDI lookups
David Ward (JIRA)
jira-events at lists.jboss.org
Sun Oct 31 17:48:54 EDT 2010
[ https://jira.jboss.org/browse/JBESB-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560469#action_12560469 ]
David Ward commented on JBESB-3471:
-----------------------------------
Your assumption is correct, Tom.
> 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: Tom Fennelly
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list