Why "durability" of the TicketRegistry is required? Is that something that's being utilized by some other external components? If the "durability" is really just a "phantom requirement", I'd recommend taking a look at the EhCache TicketRegistry - which is lightweight, embedded, and natively has a clustering functionality baked in, should one choose to use it later on. An it is part of CAS core in 3.5
Otherwise, there is also a memcached option, but that would require setting up an external memcached process. Cheers, Dmitriy. On Fri, Aug 31, 2012 at 1:44 PM, Morley Howell <[email protected]>wrote: > ** ** > > Thanks Dmitriy & Carlos.**** > > ** ** > > Is there a recommended/preferred persistent ticket registry implementation > that works in both 3.4.7 and 3.5.0? Currently we need something as simple > as possible, e.g. no need for clustering support, minimal/no runtime setup > or maintenance, etc.**** > > ** ** > > Morley**** > > ** ** > > *From:* Dmitriy Kopylenko [mailto:[email protected]] > *Sent:* August-31-12 11:35 AM > *To:* [email protected] > *Subject:* Re: [cas-user] 3.5.0 release of > cas-server-integration-berkeleydb?**** > > ** ** > > This might be helpful: > https://groups.google.com/forum/#!searchin/jasig-cas-user/berkeleydb/jasig-cas-user/bV7BPCIl3SY/VEXdWXev-68J > **** > > ** ** > > Cheers,**** > > Dmitriy.**** > > On Fri, Aug 31, 2012 at 10:53 AM, Morley Howell < > [email protected]> wrote:**** > > We’re using the berkeleydb ticket registry under 3.4.7, but we’re looking > at upgrading to 3.5.0. The latest version of the > cas-server-integration-berkeleydb > module in maven central is 3.5.0-RC2. Will this version work with CAS > 3.5.0? Any idea when a 3.5.0 version of the berkeleydb integration might be > available?**** > > **** > > Thanks,**** > > **** > > *Morley Howell***** > > This e-mail message is confidential, may be privileged and is intended for > the exclusive use of the addressee. Any other person is strictly prohibited > from disclosing, distributing or reproducing it. If the addressee cannot be > reached or is unknown to you, please inform us immediately and delete this > e-mail message and destroy all copies. Thank you.**** > > -- > 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**** > > This e-mail message is confidential, may be privileged and is intended for > the exclusive use of the addressee. Any other person is strictly prohibited > from disclosing, distributing or reproducing it. If the addressee cannot be > reached or is unknown to you, please inform us immediately and delete this > e-mail message and destroy all copies. Thank you.****** > <#1397dc9073318a9f_> > > -- > 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
