[cas-dev] JBoss ticket registry tree cache replication ofchanges made to Ticket already in the cache

[Lee Braddock]

Scott,

 

I am sure it is working fine.  Since we have added our own support for
single sign off (and utilize the distributed cache), I wanted to employ
a comparable mechanism and your proxied instance (which I overlooked) is
just the ticket (pun intended).

 

Thanks!

 

Lee Braddock

Sr. Applications Developer

Enterprise Framework

ITG Applications 

Campus Crusade for Christ

407-826-2166 office

http://itg.ccci.org <http://itg.ccci.org/> 

________________________________

From: cas-dev-bounces at tp.its.yale.edu
[mailto:cas-dev-bounces at tp.its.yale.edu] On Behalf Of Scott Battaglia
Sent: Thursday, October 25, 2007 11:05 AM
To: Mailing list for CAS developers
Subject: Re: [cas-dev] JBoss ticket registry tree cache replication
ofchanges made to Ticket already in the cache

 

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/AbstractDistributedTic
ketRegistry.java?r=42070

Is this not working?

-Scott

On 10/25/07, Lee Braddock <lee.braddock at ccci.org> 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
cas-dev at tp.its.yale.edu
http://tp.its.yale.edu/mailman/listinfo/cas-dev




-- 
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20071025/bbc3f591/attachment-0001.html