What I found was that running up the app caused Hibernate to update the schema, adding the column and creating the new attribute table. The exception was not due to a missing column, but due to the fact that the column was all null.
So our 3.3->3.3.1 database upgrade was: update RegisteredServiceImpl set evaluation_order = 100; insert into rs_attributes ( RegisteredServiceImpl_id, a_name, a_id ) select RegisteredServiceImpl_id,element,allowed_attribute_id from RegisteredServiceImpl_allowedAttributes; -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Battaglia Sent: Wednesday, 12 November 2008 2:22 p.m. To: Mailing list for CAS developers Subject: Re: [cas-dev] CAS Server 3.3.1 Release I don't know of an automated way (we're currently not using these tools yet). The easiest manual way is to create the extra column and give it a default value (i.e. 1) and then rename that table to the new name. Obviously, in test first ;-) -Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Mon, Nov 10, 2008 at 5:33 PM, Dale Ogilvie <[EMAIL PROTECTED]> wrote: > > 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 > _______________________________________________ > cas-dev mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas-dev > _______________________________________________ cas-dev mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas-dev _______________________________________________ cas-dev mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas-dev
