One question I'd ask - what particular use case the JPA ticket registry solves for you that other more lighter weight implementations would not provide? If no particular reason to use it, I'd suggest switch the implementations to avoid all of these complexities and headaches.
Cheers, Dmitriy. Sent from my iPhone > On Sep 30, 2014, at 04:45, Anshul <anshul09...@iiitd.ac.in> wrote: > > Hi John, > > I manually added a new column without not null constraint as suggested. As > the column type of "supplemental_authentication" is oid, what should be the > default value to be added for each ticket present in database. Moreover i am > facing 1 more issue, as in table ticketgrantingticket some columns > expiration_policy, authentication, services_granted_access_to are of type > oid, there serialVersionUID for CAS 4.0.0 is different from CAS 3.5.2, thus > while upgrading, it creates problem in deserialization of object. > > Is there any way, i can upgrade cas and still use TGT's created earlier? > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > dkopyle...@unicon.net > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
