cas.properties, externalized from the .war, has been a successful pattern in CAS server. I look forward to similar advantages in externalized properties-file based CAS client configuration. At the least, this helps adding the CAS client to applications to not make the applications worse as regards war-embedded environment-specific configuration.
Misagh, you have a fine idea here for improvement to the Java CAS client. On Sat, Feb 2, 2013 at 5:16 AM, Marvin Addison <marvin.addi...@gmail.com>wrote: > > I’d like to propose the idea of extracting the client > > configuration out of the web.xml file and into a single external property > > file resource. Some of that work is already made available via [1]. > > Strong +1 from me. I anticipate this will simplify configuration, with > consequent reduction in support traffic for the Java CAS Client. > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > ape...@unicon.net > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
