Lee, Any ticket returned from a distributed CAS is proxied. The proxies detect when changes are made and automatically call the correct put method:
http://developer.ja-sig.org/source/browse/jasigsvn/cas3/trunk/cas-server-core/src/main/java/org/jasig/cas/ticket/registry/AbstractDistributedTicketRegistry.java?r=42070 Is this not working? -Scott On 10/25/07, Lee Braddock <[EMAIL PROTECTED]> wrote: > > Scott, > > > > Although this is a question regarding Jboss tree cache and replication, > since you are using it within cas, you may have an answer. > > > > It would seem that replication across nodes in a clustered cache is > triggered ONLY by way of 'cache.put()' and 'cache.remove()', which are > called by ja-sig 'JBossCacheTicketRegistry.addTicket()' and > 'JBossCacheTicketRegistry.deleteTicket()', respectively. That is, changes > made to a ticket which has been retrieved from the registry will not be > recognized by the cache and will therefore not be replicated (unless, > possibly, that ticket is again 'put()' into the cache). > > > > If that is so (which it may not be), how then, when the ticket state of a > ticket granting ticket retrieved from the registry is updated > (updateState()) after granting a service ticket ( > TicketGrantingTicket.grantServiceTicket()), will that change in the ticket > granting ticket's state be replicated across the cluster since that ticket > granting ticket has already been 'put' into the tree cache (and I do not > believe it is 're-put()' into the cache)? > > > > Thanks. > > > > Lee > > > > _______________________________________________ > cas-dev mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas-dev > > -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ cas-dev mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas-dev
