Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <13060247.post@talk.nabble.com>
Date: Fri, 5 Oct 2007 07:20:57 -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: <ec6e67fd0710050632x5fc83d3dm280ecc78d43398fa@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <13039322.post@talk.nabble.com>
 <af2843cd0710040654g895e236nc797641bcbcca55@mail.gmail.com>
 <13058760.post@talk.nabble.com>
 <ec6e67fd0710050632x5fc83d3dm280ecc78d43398fa@mail.gmail.com>


Just to let you know that Camel, with the last snapshot,  works inside
Websphere App Server 6.1 using the Default JMS Provider (the SIBUS). 

And I am very happy about that. 

Thank you again . 


James.Strachan wrote:
> 
> On 05/10/2007, Bob G. <aerosteak@hotmail.com> wrote:
>>
>> 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?
> 
> Before Hiram's patch I don't think the JmsComponent let you specify
> the DestinationResolver; to use JNDI to resolve destinations etc.
> 
> -- 
> James
> -------
> http://macstrac.blogspot.com/
> 
> Open Source SOA
> http://open.iona.com
> 
> 

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