Page Comparison

...

For example the following xml snippet from the uPortal 2 file:

<constructor-arg index="0">
    <bean class="org.springframework.beans.factory.config.MethodInvokingFactoryBean">
        <property name="staticMethod">
            <value>org.jasig.portal.RDBMServices.getDataSource</value>
        </property>
    </bean>
</constructor-arg> 

Should be replaced with the following in the uPortal 3 file:

<constructor-arg index="0" ref="PortalDb" />

LdapPersonAttributeDaoImpl

The ldapServer property which expected an ILdapServer has been replaced with the contextSource attribute which expects a ContextSource See the next section on getting access to the portal's ContextSource

LDAP Server Access

In the uPortal 2 file access to the Portal LDAP server was done via Spring's MethodInvokingFactoryBean. uPortal 3 and Person Directory are now using the Spring-LDAP framework to manage LDAP access. The portal's LDAP servers are now configured in the ldapContext.xml file and the appropriately named ContextSource from that file should be used instead.

For example the following xml snippet from the uPortal 2 file:

<property name="ldapServer">
	<bean class="org.springframework.beans.factory.config.MethodInvokingFactoryBean">
		<property name="staticMethod">
			<value>org.jasig.portal.ldap.LdapServices.getDefaultLdapServer</value>
		</property>
	</bean>
</property>

Should be replaced with the following in the uPortal 3 file:

<property name="contextSource" ref="defaultLdapContext" />

This supposes that there is a ContextSource named defaultLdapContext configured in the ldapContext.xml file.