> I am curious -- given that authentication modules, etc, are configured > at build time
The VMs are playing around with a wholly different approach, one I'm considering expanding upon via Debian packages in the future. Using an unpacked WAR in a well-known filesystem location, it's just a matter of additional libraries and configuration files, and possibly some config file merges. That's to say it could be made to be no different than installing any other software on a unix-like system. > Or ... would this appliance really be a Tomcat appliance, with a CAS > source + maven installation, so that configuration and deployment is > greatly simplified? The objective for me of any alternative deployment strategy is to take Maven out of the mix. Maven is for developers; the alternative has to be something targeting tools and strategies familiar to sysadmins. (I hope I'm not insulting anyone; good sysadmins can certainly know Maven and/or be good devs. But hopefully it's reasonable to take at face value that someone who is really good in both roles is rare.) > Or ... would a new app (analogous to the Service Manager) be added for > on-the-fly (re)configuration? I'm not thinking anything with a GUI. I know Andrew thinks it'd be cool, but it sounds insanely complex to me. M -- 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
