[
https://issues.apache.org/activemq/browse/CAMEL-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56006#action_56006
]
Claus Ibsen commented on CAMEL-1707:
------------------------------------
This looks really ugly
I would prefer to configure that on the JmsComponent and leave it out of the URL
And there is also a destinationResolver you can use to lookup in JNDI etc. But
maybe some properties on JmsComponent to set JNDI stuff and then it will lookup
in JNDI also.
> Added JNDI support in camel-jms URI
> -----------------------------------
>
> Key: CAMEL-1707
> URL: https://issues.apache.org/activemq/browse/CAMEL-1707
> Project: Apache Camel
> Issue Type: New Feature
> Reporter: Willem Jiang
> Fix For: Future
>
>
> URI Scheme for Java(tm) Message Service 1. 0 [1] has the definitions of JNDI
> like this
> {code}
> jms:jndi:SomeJndiNameForDestination?jndiInitialContextFactory=
> com.example.jndi.JndiFactory&priority=3
> {code}
> {code}
>
> jms:jndi:REQ_QUEUE?jndiURL=file:/C:/JMSAdmin&jndiInitialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory&jndiConnectionFactoryName=CONNFACT
> &replyToName=RESP_QUEUE
> {code}
> We may need to implement this URI in camel-jms.
> [1] http://tools.ietf.org/id/draft-merrick-jms-uri-05.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
