Return-Path: 
 <camel-user-return-353-apmail-activemq-camel-user-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org
Received: (qmail 13014 invoked from network); 5 Oct 2007 13:01:37 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 5 Oct 2007 13:01:37 -0000
Received: (qmail 23652 invoked by uid 500); 5 Oct 2007 13:01:26 -0000
Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org
Received: (qmail 23597 invoked by uid 500); 5 Oct 2007 13:01:26 -0000
Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:camel-user-help@activemq.apache.org>
List-Unsubscribe: <mailto:camel-user-unsubscribe@activemq.apache.org>
List-Post: <mailto:camel-user@activemq.apache.org>
List-Id: <camel-user.activemq.apache.org>
Reply-To: camel-user@activemq.apache.org
Delivered-To: mailing list camel-user@activemq.apache.org
Received: (qmail 23588 invoked by uid 99); 5 Oct 2007 13:01:26 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2007 06:01:26 -0700
X-ASF-Spam-Status: No, hits=1.1 required=10.0
	tests=FORGED_HOTMAIL_RCVD2,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2007 13:01:27 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1Idmnj-0003zh-7D
	for camel-user@activemq.apache.org; Fri, 05 Oct 2007 06:01:07 -0700
Message-ID: <13058760.post@talk.nabble.com>
Date: Fri, 5 Oct 2007 06:01:07 -0700 (PDT)
From: "Bob G." <aerosteak@hotmail.com>
To: camel-user@activemq.apache.org
Subject: Re: How camel resolve JNDI End point
In-Reply-To: <af2843cd0710040654g895e236nc797641bcbcca55@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: aerosteak@hotmail.com
References: <13039322.post@talk.nabble.com>
 <af2843cd0710040654g895e236nc797641bcbcca55@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org


Thank you Hiram, 

I will download the lates version. 

Question: Was the JNDI working before in Camel? Was it the way I am using
Spring JNDI it that was not working?

Thank you again.




Hiram Chirino wrote:
> 
> Hi Bob,
> 
> I just committed a change so that the DestiantionResolver property is
> supported on the camel JMS component.  So once you pick up that
> updated.  You should be able to do the following:
> 
> <beans>
>        <bean id="camel"
> class="org.apache.camel.spring.CamelContextFactoryBean">
>                <property name="packages" value="com.abc.poc.camel.jms"/>
>        </bean>
> 
>        <bean id="jms" class="org.apache.camel.component.jms.JmsComponent">
>           <property name="connectionFactory"
> ref="internalJmsQueueConnectionFactory"/>
>           <property name="destinationResolver"
> ref="jmsDestinationResolver"/>
>        </bean>
> 
>        <!-- JMS Destination Resolver -->
>       <bean id="jmsDestinationResolver"
> class="org.springframework.jms.support.destination.JndiDestinationResolver">
>        <property name="jndiTemplate" ref="jndiTemplate"/>
>        <property name="cache" value="true"/>
>       </bean>
> 
>       <!-- JMS Queue Connection Factory -->
>       <bean id="internalJmsQueueConnectionFactory"
> class="org.springframework.jndi.JndiObjectFactoryBean">
>        <property name="jndiTemplate" ref="jndiTemplate"/>
>        <property name="jndiName"> <value>jms/myConFactory</value> 
> </property>
>       </bean>
> 
>       <bean id="jndiTemplate"
> class="org.springframework.jndi.JndiTemplate">
>                <property name="environment">
>                        <props><prop key="java.naming.factory.initial">
> 
> com.ibm.websphere.naming.WsnInitialContextFactory
>                                </prop>
>                        </props>
>                </property>
>        </bean>
> </beans>
> 
> I have also made the JMS component support auto wiring the
> destinationResolver property so that the above example should also
> work even if you don't define the "jms" component explicitly.  But I
> figure being explicit is sometimes more clear.
> 
> Please let me know if this fixes it for you.
> 
> On 10/4/07, Bob G. <aerosteak@hotmail.com> wrote:
>>
>> Hello
>>
>> I am trying to configure Camel to use JMS end point into Websphere 6.1
>> (was). My end point cannot be found because of some Spring JNDI lookup
>> problem.
>>
>> Some question :
>> -  How do I tell Camel to use my Spring JndiTemplate or
>> JndiDestinationResolver so that my jms queue will be resolved properly?
>>
>> In the documentation, it says that Camel uses Spring JmsTemplate. How can
>> I
>> tell Camel to use my JmsTemplate configured for Websphere?
>>
>> There is my config:
>>
>> <beans>
>>         <bean id="camel"
>> class="org.apache.camel.spring.CamelContextFactoryBean">
>>                 <property name="packages" value="com.abc.poc.camel.jms"/>
>>         </bean>
>>
>>
>>          <!-- ?? My JmsTemplate is not injected or Used in any Camel
>> Classes ?? -->
>>         <bean id="jmsQueueTemplate"
>> class="org.springframework.jms.core.JmsTemplate">
>>           <property name="connectionFactory"
>> ref="internalJmsQueueConnectionFactory"/>
>>           <property name="destinationResolver"
>> ref="jmsDestinationResolver"/>
>>           <property name="pubSubDomain"> <value>false</value> 
>> </property>
>>           <property name="receiveTimeout"> <value>20000</value>
>> </property>
>>         </bean>
>>
>>     <!-- JMS Destination Resolver -->
>>     <bean id="jmsDestinationResolver"
>> class="org.springframework.jms.support.destination.JndiDestinationResolver">
>>         <property name="jndiTemplate" ref="jndiTemplate"/>
>>         <property name="cache" value="true"/>
>>     </bean>
>>
>>   <!-- JMS Queue Connection Factory -->
>>   <bean id="internalJmsQueueConnectionFactory"
>> class="org.springframework.jndi.JndiObjectFactoryBean">
>>         <property name="jndiTemplate" ref="jndiTemplate"/>
>>     <property name="jndiName"> <value>jms/myConFactory</value> 
>> </property>
>>   </bean>
>>
>>   <bean id="jndiTemplate"              
>> class="org.springframework.jndi.JndiTemplate">
>>                 <property name="environment">
>>                         <props><prop key="java.naming.factory.initial">
>>                                        
>> com.ibm.websphere.naming.WsnInitialContextFactory
>>                                 </prop>
>>                         </props>
>>                 </property>
>>         </bean>
>> </beans>
>>
>>
>> Thank you.
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/How-camel-resolve-JNDI-End-point-tf4568653s22882.html#a13039322
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> Regards,
> Hiram
> 
> Blog: http://hiramchirino.com
> 
> 

-- 
View this message in context: http://www.nabble.com/How-camel-resolve-JNDI-End-point-tf4568653s22882.html#a13058760
Sent from the Camel - Users mailing list archive at Nabble.com.