Could this be added to the release notes? I don't recall info about deleting tickets/incompatibilities between versions. We spent a LOT of time (2 weeks) going back over this upgrade and redoing it several times and trying to figure out what the issue was.
thanks, Steve On 10/02/2012, at 7:17 AM, Scott Battaglia wrote: > We've been typically trying to make sure that we don't change them because of > issues like this. Apologies that this happened. > > We've got APIs that attempt to alleviate some of these serialization issues. > As a development team, prioritizing the migration to some of these APIs > should become a priority. > > Cheers, > Scott > > > On Thu, Feb 9, 2012 at 9:27 AM, Marvin Addison <[email protected]> > wrote: > > Are TicketGrantingTickets, created under 3.4.10, compatible with 3.4.11? > > No, they are not compatible in the context in which you're asking, > which is serialized form. This brings up an important issue that we > the dev team need to address in the near to mid term. We have been > very sloppy with the serialized representation of objects when almost > all storage backends depend on serialization in one form or another. > I plan to bring up this issue in further detail on the dev list, so > hop on that list if you care to know more and participate in further > discussion. > > > When I start 3.4.11, the runs of the ticket cleaner, produce errors like > > the following > > ... > > nested exception is javax.persistence.PersistenceException: > > org.hibernate.type.SerializationException: could not deserialize at > > org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:273) > > It's a known issue, although it may not be widely known and it's > certainly not documented afaik. I would recommend deleting all > tickets from your store immediately following an upgrade. That is our > standard practice and I would argue it's best practice for the > limitations at present. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
