Tracking document for changes implementors will need to make during the upgrade to 5.0 which are related to Rice 2.0.
Configuration Property Changes
XAPool / Bitronix / BitronixXa
Old Property Name
New Property Name
TODO: remainder of datasource properties
Impacting Data Changes
The Rice team stepped on some of our KIM data. So some updates will need to be made before importing the Rice 2.0 data:
UPDATE krim_typ_t SET kim_typ_id = 'KFS69' WHERE kim_typ_id = '69' / UPDATE krim_role_t SET kim_typ_id = 'KFS69' WHERE kim_typ_id = '69'
TODO: krim_typ_attr_t data
Impacting API Changes
Role Type Services
Derived role type services have changed three of their method names:
JSP Constant Class Changes
In KFS 4.x (and earlier) there were properties in the build system which controlled which classes were exposed to the JSP layer as constants. These properties have been removed due to a new system of constants used by Rice. If you have added any of your own constant classes, you will need to add code to your module Spring override file like the following:
The JSTLConstants parent class has been removed in favor of this new method, so you will need to remove it as a superclass from any custom constants classes.
<bean id="GeneralLedgerConstants" class="org.kuali.rice.core.api.util.collect.ConstantsMap"> <property name="constantClass" value="org.kuali.kfs.gl.GeneralLedgerConstants" /> </bean> <bean class="org.springframework.web.context.support.ServletContextAttributeExporter"> <property name="attributes"> <map> <entry key="GeneralLedgerConstants" value-ref="GeneralLedgerConstants" /> </map> </property> </bean>