I'll come back and add more detail later. I need to get to a meeting. After converting our database to 2.6, we were unable to start Sakai. It failed in metaobj, but this failure causes Sakai not to be able to start.
rg.springframework.beans.factory.BeanCreationException: Error creating bean with name 'structuredArtifactDefinitionManagerTarget' defined in file [/army/sunone/sakai2/apach\
e-tomcat-5.5.20/components/sakai-metaobj-component/WEB-INF/components.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: org.sakaiprojec\
t.exception.IdUniquenessException: /group/PortfolioAdmin/system/formCreate-100.xslt id=/group/PortfolioAdmin/system/formCreate-100.xslt
java.lang.RuntimeException: org.sakaiproject.exception.IdUniquenessException: /group/PortfolioAdmin/system/formCreate-100.xslt id=/group/PortfolioAdmin/system/formCreate-100\
Here's the fix, which unfortunately I don't have time to explain now:
+ <property name="replaceViews"><value>false</value></property>
<property name="securityService"><ref bean="org.sakaiproject.authz.api.SecurityService"/></property>
The problem is that it keeps trying to create new versions of /formCreate-100.xslt, but the call to addresource says only to create 100 copies. So it fails at the 100'th start. The solution it not to allow a milliion copies, but to stop it from trying to create a new one each time. Somehow that patch does it, but I've forgotten the details.
This might reasonably be considered a blocker for all releases after metaobj was integrated into the default version, since it will stop the system from coming up.