Given the finality of the class, one shortcut would be to use composition instead of inheritance. In other words, in your custom ehcache ticket registry, have it extend the distributed ticket registry class and implement the ticket registry state, etc. Then, inject the true ehcache ticket registry into your custom class through spring and delegate all requests to its proper methods. Leave the registry state methods unimplemented.
If you'd like, I can prepare a small sample for you in a little bit and post it back here to get you started. -Misagh > -----Original Message----- > From: Andres [mailto:[email protected]] > Sent: Monday, July 23, 2012 1:51 AM > To: [email protected] > Subject: RE:[cas-user] CAS 3.5 EhCache ticket registry + clearPass > conflict > > EhCacheTicketRegistry cannot be extended as it's a final class. > However, I can write a custom EhCacheTicketRegistry that makes what you > say, but I don't know how to make it override the > EhCacheTicketRegistry.class included in the cas-server-integration- > ehcache jar file via Maven overlay. > -- > 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
