On Tue, 03 May 2011 13:07 -0400, "Marvin Addison" <[email protected]> wrote: > > Just to check my understanding since this is all new and a bit out of my > > comfort zone, this strategy basically amounts to building a custom > > ExpirationPolicy, and in this customization querying ThreadLocal
Just to revisit this briefly, I've made the customizations (thanks, ThreadLocal made it pretty easy) and tested so I'm set on the actual functioning end. The question for me now is if there's a best practice as far as applying the customization. I'm already using Maven as per the recommended practice for overlaying the various .xml files. What I'm wondering if it's best to just take my new .java file and throw it into the existing project, or to make a separate project for it and bring it in as a dependency to the main "CAS" project. It's a fairly trivial bit of code and I don't forsee many other customizations for my environment, but I don't want to make a maintenance misstep I'll be kicking myself about later. Matt -- 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
