Dmitriy, I am assuming the YAML version as well as the CAS 4.1 JSON implementation do not support clustered environments either, correct? I would still need to make use of your earlier suggestion in order to get away from using a database with data guard to ensure synchronization.
Linda Linda Toth University of Alaska - Office of Information Technology (OIT) - Identity and Access Management 910 Yukon Drive, Suite 103 Fairbanks, Alaska 99775 Tel: 907-450-8320 Fax: 907-450-8381 [email protected] | www.alaska.edu/oit/ On Thu, Nov 20, 2014 at 6:44 AM, Dmitriy Kopylenko <[email protected]> wrote: > Hi Milt. Sorry for the confusion (I’m responsible for this confusion). > I’ll fix the README. So here’s a summary of things as far as add ons go: > > Current monolithic cas-addons library has served us well for the 3.5.1+ > line of CAS (and continues to do so). But it has grown quite a bit since > its inception and became kind of like a “kitchen sink” or a "Swiss army > knife” if you will, of the useful addon bits stuffed into a single jar > which brings with it some extra dependencies even if one doesn’t use some > parts of the functionality, etc. > > So we have thought to create a next generation of “micro addons” as > separate projects with small, cohesive set of functionalities and > dependencies, so folks could choose the appropriate one to use without > bringing the ”extra baggage” with them - and that’s exclusively for 4.0+ > line. While Monolithic cas-addons is alive and still supported for CAS > 3.5.1+, we are not investing our time into the new development of it and > shifting our focus to develop and maintain new micro add ons for CAS4 where > it makes sense - as CAS4 is gaining momentum here. > > Now, as far as JSON service registry - since CAS 4.1 is bringing its own > JSON service registry into the core, I’ve decided to drop it completely as > it would be a meaningless exercise to have an extra one out there. On the > other hand, one of the most useful properties of the JSON addon registry is > the support for extra metadata Map attached to an extension type namely > “RegisteredServicesWithAttributes" which allowed us to build all kinds of > useful extension features with it over the years. And also a lightweight > nature of JSON svc registry implementation and dynamic runtime reloading > feature. > > Thus for the replacement of it, I have recently implemented a YAML > services registry to exhibit same behaviors as current JSON registry addon, > as well as added benefit of more human readable format that is YAML (IMHO) > than JSON, giving it more of a DSL-like look and feel. The current > implementation is very fresh (few days old), but I’ve done good amount of > local testing and it works like a charm. The plan is for it to be supported > on CAS 4.0+ and be a main alternative to the native CAS4 JSON svc registry > (I will change that confusing README message), as well as add wiki > documentation and release 1.0 GA some time next week. In the mean time, > here’s how the services definition file looks like: > > > https://github.com/unicon-cas-addons/cas-addon-yaml-services-registry/blob/master/src/test/resources/net/unicon/cas/addon/serviceregistry/yaml/servicesRegistry.yml > > Hope this helps clearing things up a bit. > > Best, > Dmitriy. > > > > On Nov 20, 2014, at 10:18 AM, Milt Epstein <[email protected]> wrote: > > OK, I'm getting a little confused, so I thought I'd ask here for > pointers. I'm trying to get a CAS verson 4.0 setup going, and I was > thinking of using the JSON services registry. We're using it with our > current version (3.4.12), and we're happy with how it's working. I > had to install a little bit of extra java and groovy code, but > otherwise it was quite simple to install and configure, quite easy to > use, and sufficient for our needs. > > From things I had seen on the list since I did that installation, I > had gotten the impression that it had gotten even easier to install > and configure, more well integrated with CAS, put into its own > complete package (e.g, part of the Unicon cas-addons packages), and > more functional. So it seemed like a no-brainer to use it again. And > I thought it'd be very easy to find and install. But that doesn't > seem to be the way things are going. > > For instance, when I go to this page: > > https://github.com/Unicon/cas-addons/ > > There's a NOTICE that states: > > ... 1.x series of cas-addons is not supported on CAS 4.x. For CAS > 4.x support look for the upcoming series of micro addons libraries > grouped by distinct features in upcoming months. > > So I follow the link for the micro addons: > > https://github.com/unicon-cas-addons > > There's no json services registry package there. But there is one for > yaml, so I have a look at that: > > https://github.com/unicon-cas-addons/cas-addon-yaml-services-registry > > This one states: > > This library replaces cas-addons 1.x JSON ServiceRegistry and serves > as an alternative to the new JSON Service Registry in CAS core version > 4.1. > > CAS core version 4.1? Does that exist yet? I thought 4.0 was the > latest. And is there a version of the JSON Service Registry that I > can use with 4.0? > > Or perhaps I should use this YAML version -- it seems like it provides > similar functionality. But how do I do that? Do I just reference it > in the pom.xml in my maven overlay directory, and add a bit of config > somewhere? What config, where? > > Thanks for any assistance with this. > > Milt Epstein > Applications Developer > Graduate School of Library and Information Science (GSLIS) > University of Illinois at Urbana-Champaign (UIUC) > [email protected] > > > -- > 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 > > -- 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
