Sorry this got missed in the holiday shuffle.So any delegate beans that you use with the mediating bean must be marked as lazy-init="true" This prevents spring from trying to create the beans when the app starts up. The mediating bean will do the creation and handle the bean creation exception gracefully.
-Eric On 11/24/2009 04:00 PM, Susan Bramhall wrote:
I am struggling with SmartLdapGroupStore spring configuration. I would like to use the org.jasig.portal.spring.beans.factory.MediatingFactoryBean to allow two versions of the ldap config - one has the parameter values in the SmartLdapGroupStore.xml and the other uses parameter values that are defined as jndi resources in the Tomcat context.xml. The idea allow commands such as ant crn-import run without changing the ldap config files.The configuration works fine when running under Tomcat but not on the command line. The strategy also works perfectly for the portal datasource but from the command line the SmartLdapGroupStore initialization fails even when using the mediating bean. Can anyone shed some light on this?My SmartLdapGroupStore.xml (except for some redacted values) is attached. Thanks for any insights. Susan -- Susan Bramhall ([email protected] <mailto:[email protected]>) Senior Developer, Infrastructure Systems and Architecture (formerly T&P) Yale University Information Technology Services (ITS) 25 Science Park, 150 Munson St, New Haven, CT 06520 Phone: 203 432 6697 -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
smime.p7s
Description: S/MIME Cryptographic Signature
