On Sat, May 2, 2009 at 9:02 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > Hi, > > I don't know if it will take lots of time to create the LDAP Context? > If so, we could think to cache the context in a thread local variable. There could be some hook how to get it and then end users can configure their own pooled ldap connection aka like the JDBC or JMS pools.
And if it was a big problem there would be examples on the web how to. 30 min with google and you should be able to find out. Chris do you mind checking this? Anyway its better that it works reliable (being thread safe and all) than being ultra fast. I will take reliable, robust integration over anything any time. > > > Willem > > Claus Ibsen wrote: >> On Sat, May 2, 2009 at 6:22 AM, huntc <hu...@mac.com> wrote: >>> Hi there, >>> >>> Any comments? I'm thinking that I'll patch the ldap component so that it >>> obtains the context and closes it within the process method each time. >>> Thoughts? >> Great that would be +1 from me. >> >> >>> Kind regards, >>> Christopher >>> -- >>> View this message in context: >>> http://www.nabble.com/LDAP-producers-and-re-entrancy-tp23266701p23342889.html >>> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com. >>> >>> >> >> >> > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus Apache Camel Reference Card: http://refcardz.dzone.com/refcardz/enterprise-integration
