Re: [gatein-dev] clustering sso, exo.profiles and wsrp webservice security

On Mon, Mar 21, 2011 at 2:56 PM, Matt Wringe <mwringe(a)redhat.com&gt; wrote: When the server boots it shows the active profiles on the console like: Mar 21, 2011 11:57:38 PM org.exoplatform.container.RootContainer <init> INFO: Active profiles [tomcat] The server determines a profile by itself (tomcat for tomcat, etc...), additional profiles are added with the -Dexo.profiles VM argument with a comma separated list When you want to activate a part of the configuration you have to depend on a profile, here again you can specify a list of profile with a comma separated list. You can determine which elements of the configuration accepts a profile by looking at the http://www.exoplaform.org/xml/ns/kernel_1_1.xsd schema, normally it should answer your needs if you are going to activate some part of the server this way. This makes sense to me, although the clustered sso filter is configured differently because it's a servlet filter, it uses (unfortunately) programmatic hardcoded profile selection with the code: ExoContainer.getProfiles().contains("cluster") Also I would like to move this server dependent code to the WCI module at some point (I wanted to do it currently in trunk, so this code would move to a proper location and could be more easily tested), but doing that would need to bring a dependency of this filter onto the exo kernel which is something we would like to avoid. Perhaps there is something creative than can be done, to keep flexibility and avoid the duplication in WSRP. Actually I don't know exactly how you plan to use it in WSRP, would it be on producer side in the producer war file ? Also this code could be stay in GateIn but in a JBoss specific module instead. My concern is that any activation of the cluster code in tomcat could lead to a class not found exception of the org.jboss.web.tomcat.security.login.WebAuthentication class. But this is a different concern than the one you are expressing here of course.