Dave wrote:
I don't want folks to have to modify the contents of the WAR at all,
that's one of he reasons I don't like Acegi -- users have to modify
security.xml for SSO, LDAP and any other alternate configurations.
I'm pretty sure we could drive security.xml from JNDI and/or properties
files. I'm 100% sure we can do it for the keys, but I'd have to look at
the SSO and LDAP configurations.
I'd like the WAR to be immutable -- there should be no need to edit
it's contents. To deploy Roller you create a roller-custom.properties
file with your settings and/or create the App Server resources you
need and drop in the un-altered WAR that you downloaded.
It would be nice to have a way to get roller-custom.properties via
JNDI. Right now you have to either put in in the WAR or modify your
Tomcat installation. You could put the file path in a JNDI String
(similar to the JVM option method) It would be even nicer to be able to
get an actual properties object via JNDI, but I don't know how or if
there is a way to do that.
