[cas-dev] CAS Server 3.3.1 Release

[Dale Ogilvie]

What is the best way to migrate an existing services database over to
the new schema? Our deployment of the new code failed with the following
exception, I suppose due to the evaluationOrder change in
http://www.ja-sig.org/issues/browse/CAS-708

2008-11-11 11:07:49,422 ERROR
[org.springframework.web.context.ContextLoader] - <Context
initialization failed>
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'servicesManager' defined in ServletContext resource
[/WEB-INF/spring-configuration/applicationContext.xml]: Instantiation of
bean failed; nested exception is
org.springframework.beans.BeanInstantiationException: Could not
instantiate bean class
[org.jasig.cas.services.DefaultServicesManagerImpl]: Constructor threw
exception; nested exception is
org.springframework.orm.hibernate3.HibernateSystemException: Null value
was assigned to a property of primitive type setter of
org.jasig.cas.services.RegisteredServiceImpl.evaluationOrder; nested
exception is org.hibernate.PropertyAccessException: Null value was
assigned to a property of primitive type setter of
org.jasig.cas.services.RegisteredServiceImpl.evaluationOrder

We will also need to migrate our service attributes over due to bug# 5
in the notes below:

Fixed service schema generation to support Oracle (NOTE: this will
require you to update the table being used to store attributes, even if
you're not using Oracle!)

Any advice on how to migrate our existing services to the new database
format? Or is this a manual re-entry job? This is on MySQL.

Thanks

Dale