Hi Maybe you can contribute this to Apache Camel. We could maybe allow to configure the endpoint or exchange header to which ldap context to use. http://camel.apache.org/contributing
On Thu, Mar 17, 2016 at 9:31 AM, Kostov, Andreya <[email protected]> wrote: > Hello Thomas, > > Thank you for the suggestion. However I'm not sure this would help as the > issue that the LdapProducer reads the beans from Spring context still remains > - we still cannot do anything with the beans by adding/removing routes at > runtime. > > Anyway, for future reference - we have managed to work around this altogether > by extending the LdapProducer and overriding the method which reads the > LdapContext to use an exchange property, rather than Spring > WebApplicationContext. This means that the LdapEndpoint and LdapComponent > classes have to be extended too and the component manually registered with a > different scheme. But in the end, it works as expected. :) > > Best regards, > Andreya > > -----Original Message----- > From: Walzer, Thomas [mailto:[email protected]] > Sent: Wednesday, March 16, 2016 11:05 AM > To: [email protected] > Subject: Re: Use LDAP component to connect to different backend systems > > Hi, > > I would remove/add the routes via the context API > This was already discussed here: > http://stackoverflow.com/questions/15248776/dynamic-change-endpoint-camel#15254698 > > Cheers, Thomas. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
