Initializing LdapContextSource localy instead of using spring xml

Sat Jul 04 10:14:23 UTC 2009

  • Home
  • Posts
  • Contact
If you decide to work with internal coded LdapContextSource initialize instead of using spring injection (external application context xml file). There is one important thing you shouldn't forget:
Call "afterPropertiesSet()" method to finish up initialization.
Failing to do so would probably led you to this failure / exception as i had:
"org.springframework.ldap.core.support.AbstractContextSource.getAuthenticatedEnv(AbstractContextSource.java:449) etc.."

Hopefully that this helps...
Dor

Links

  • Arman Gal
  • Naor Levi
  • Giyora Alon
  • My Blog
  • My Linkedin profile
  • My Company
  • Jboss
  • Spring
  • Glassfish
  • Eclipse
  • Quartz
  • Maven
  • Subversion
  • TrekEarth
  • TrekNature

Posts

  • Skype & Websphere Application Server
  • Websphere admin console doesn't work
  • Salesforce AXIS API
  • SRVE0255E
  • Eclipse is running in a JRE, but a JDK is required
  • myeclipse unable to load project metadata
  • ParserInitializationException: Error initializing parser
  • World Community Grid
  • java.lang.ClassNotFoundException: No ClassLoaders found
  • HtmlSelectOneMenu does not have a converter
  • Spring LDAP dynamic connecting
  • Changing IE "View Source" editor
  • Why i need the serialVersionUID?
  • Jboss 4.2.2GA deployment sequence
  • Initializing LdapContextSource localy instead of using spring xml
  • Spring LDAP dynamic connecting
  • java.lang.ClassNotFoundException: No ClassLoaders found
  • Websphere Application Server Admin
  • GWT DateTimeFormat
  • Quartz CronExpression
© Copyright by dorbendov.com | Design by Cruise Memories, 1193