>> Just after that I am seeing a SEVERE message that it can not find my >> classes where I extend javax.security.Principal. These classes can be >> found in the deployed war file. > > Which is not where they're supposed to be. To quote from the doc: "Place > the compiled classes on > Tomcat's classpath"; note this is not the webapp's classpath. This can be > specified in Tomcat's startup > scripts, or the classes can be put in whatever you have java.endorsed.dirs > set to. The principal and role > classes must not be packaged with the webapp, since the Realm is independent.
Is "Tomcat's classpath" defined somewhere in the docs ? I see a Classloading section: http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html but it does not really talk about "Tomcat's classpath". > Here's the doc: > http://tomcat.apache.org/tomcat-5.5-doc/realm-howto.html#JAASRealm Can the realm doc get updated to say: 3. Place the compiled classes on Tomcat's classpath ( e.g. $CATALINA_HOME/commons/endorsed ) > Packaging with the webapp may have erroneously "worked" in the past if you > fiddled with the > CLASSPATH environment variable, which can lead to lots of other nasty issues. This setup has worked out of the box on both 5.5.23 and 6.0.16 without any changes to my CLASSPATH environment variable. This has been working very well since it allows me to run different versions of my Realm inside 1 instance of tomcat. If I need to run multiple versions of a realm am I now forced to run multiple instances of tomcat ? -Steve More --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
