On 03/07/2015 07:37, Fjodor Vershinin wrote: > Hi! > Unfortunately, commit rearrangement requires some more effort from me, so I > haven't finished it yesterday. > I need some more time to fix checkstyle errors and so on.
OK. >> We can change the way users have to configure it. For example, we could >> say they have to use programmatic configuration via the standard JASPIC >> interfaces if they want to use non-default settings. > > > I see your point. The best option in my opinion is is to pass this options > through LoginConfig/Context in ContextConfig. > We can figure out how to set these options in a programmatic way and then > refresh the context provider in order to reinitialize authenitcation > modules. Why do you say reinitialize? I'd expect a new instance of the module to be created when the web application starts and that instance to be used until it stops (requiring a stop/start to update config happens a lot in Tomcat - not that much configuration is configurable dynamically). Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
