Re: LDAP producers and re-entrancy

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. Willem Claus Ibsen wrote: > On Sat, May 2, 2009 at 6:22 AM, huntc wrote: >> Hi there, >> >> Any comments? I'm thinking that I'll patch the ldap compo

Re: LDAP producers and re-entrancy

On Sat, May 2, 2009 at 9:02 AM, Willem Jiang 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

Re: LDAP producers and re-entrancy

Hi Me again. I have used spring LDAP in the past. And I kinda remember the ldap.jar implementations such as sun etc. do have pooling under the covers. But I think spring LDAP have surfaced some configuration for this in their 1.3 framework. Maybe a good place to start to look into their reference

Re: stopping a route in spring dsl

Hi You might want to double check your predicate works as expected ${in.body} != null The simple language might not work with null as such. I guess I need to double check myself. And it reminds me we might want to add a better syntax error detection as well. I will go create a ticket about this

Re: stopping a route in spring dsl

On Sat, May 2, 2009 at 9:25 AM, Claus Ibsen wrote: > Hi > > You might want to double check your predicate works as expected >  ${in.body} != null > > The simple language might not work with null as such. I guess I need > to double check myself. > And it reminds me we might want to add a better syn

Re: stopping a route in spring dsl

Ticket created https://issues.apache.org/activemq/browse/CAMEL-1582 On Sat, May 2, 2009 at 9:25 AM, Claus Ibsen wrote: > Hi > > You might want to double check your predicate works as expected >  ${in.body} != null > > The simple language might not work with null as such. I guess I need > to doubl

Re: LDAP producers and re-entrancy

JIRA now raised: https://issues.apache.org/activemq/browse/CAMEL-1583 I shall write the patch very shortly. -- View this message in context: http://www.nabble.com/LDAP-producers-and-re-entrancy-tp23266701p23344787.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.

Tailing a Rotating Log

I have information that is coming to me in the logs of an application that I don't control. I want to take the lines of the log as they are written (like tail -f in unix) and process each line with Camel. Unfortunately for me, the "current" log file name changes because the app uses log rotation.