[
https://issues.apache.org/activemq/browse/CAMEL-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Hunt resolved CAMEL-1499.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
2.0-M1
Documentation has been updated.
> LDAP documentation could be improved
> ------------------------------------
>
> Key: CAMEL-1499
> URL: https://issues.apache.org/activemq/browse/CAMEL-1499
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-ldap
> Affects Versions: 1.6.0, 2.0-M1
> Environment: Wiki pages
> Reporter: Christopher Hunt
> Fix For: 2.0-M1, 1.6.0
>
>
> On familiarising myself with the ldap component I found that I had to trawl
> through the source code to gain a good understanding of how it should be used.
> For example (http://camel.apache.org/ldap.html):
> "In the sample below we fetch the rows from the customer table.
> First we register our datasource in the Camel registry as testdb:"
> is entirely incorrect. Perhaps it should say:
> "In the sample below we create a JNDI DirContext and register it with our
> Camel context's JNDI registry. The key used for registration is the remaining
> part of the ldap URI i.e. the part without the ldap: and URI parameters. The
> DirContext should establish any authentication requirements with the LDAP
> repository."
> I then think that the example should illustrate how an anonymous DirContext
> can be established outside of any ApacheDS dependencies e.g.:
> {code}
> Hashtable<Object, Object> env = new Hashtable<Object, Object>();
> env.put(Context.INITIAL_CONTEXT_FACTORY, initialContextFactory);
> env.put(Context.PROVIDER_URL, providerURL);
> env.put(Context.SECURITY_AUTHENTICATION, "none");
> DirContext ctx = new InitialDirContext(env);
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
