Scott, This is one of the things I think that can be a value-add of JBoss/Tomcat integration and something we can pitch to the Tomcat-only community. Marc has talked before about having a JBoss minimal and Tomcat bundle.
XXXXXXXXXXXXXXXX Bill Burke Chief Architect JBoss Group, LLC XXXXXXXXXXXXXXXX > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Scott M > Stark > Sent: Wednesday, January 01, 2003 1:58 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Standalone Tomcat 4.1 and JAAS > > > The java:comp context is a component specific environment indexed > by the thread context > class loader associated with the deployment. Web app1 cannot look > into the java:comp > context of web app2. A standalone tomcat server will also have to > impose this behavior, > but how this is done is container specific. Because of this there > cannot be more than one > web app subcontext under java:comp/env/security as the java:comp > context is already web > app specific. You need to create the java:comp/env/security on > initialization of the web app > to point to the actual remoted binding of the > AuthenticationManager and RealmManager > interfaces. If you have a patch that you think is generally > useful post it to the patches > section of the JBoss SourceForge project. > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > > ----- Original Message ----- > From: "Brian Topping" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, December 31, 2002 7:00 PM > Subject: RE: [JBoss-user] Standalone Tomcat 4.1 and JAAS > > > Thanks for the response, sorry for the delay in digesting this... > > It seems like the AuthenticationManager and RealmManager interfaces don't > have any particularly sensitive methods related to them, so my > guess is the > only reason that these aren't already available remotely is > because they are > different per web application? Correct me if I am wrong, but > this solution > seems like it would only support one login context per JNDI tree. > > If that's the case, one option would be to parameterize the > instantiation of > JBossSecurityMgrRealm with the name of a java:comp/env/security > subcontext to > use. This would solve this issue, but are working patches of this nature > something that you would consider applying or is this a misguided hack? > > happy ny! > > -b > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
