[cas-dev] Switching from AtomicBoolean to Boolean

[Scott Battaglia]

All,

We have one open JIRA issue related to switching from AtomicBoolean to
Boolean so that people who want to use Terracotta can (Terracotta currently
doesn't support AtomicBoolean):

http://www.ja-sig.org/issues/browse/CAS-660

Doing so will change the table structure used/expected by the JPA component,
thus those people would need to clear out their database, else they'll get
errors.  Do any of the people using the JPA component have an objection to
making this change?  We're trying to minimize the changes to TGT and ST
classes as much as possible becaues of their sometimes persistent storage,
but this seems like a good change to make if it will support Terracotta
(plus then Terracotta can be used for persistent storage).

I'll wait to hear any feedback.  If I don't get any, I'll assume its okay
and any release notes would make it clear about the change.

-Scott

-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20080619/9c0064ea/attachment.html