Makes sense! The problem is, that I have different ORB configurations in
each webapp. So, the realm should use the same orb as the webapp because
the realm is accessing a corba server...

Can I access the realm name in my custom realm implementation?
<login-config>
   <auth-method>BASIC</auth-method>
   <realm-name>TEST</realm-name>
</login-config>




                                             
              "Cox, Charlie"                      
              <ccox@(protected)>
              >                Kopie:            
                              Thema:  RE: Realm class, Classloader
              02.06.2003 15:37                      
              Bitte antworten                      
              an "Tomcat Users                      
              List"                            
                                             
                                             




actually it is loaded by tomcat's internal classes, to determine if your
webapp should be called. So the tomcat classes need to be able to see it
and
they cannot access classes loaded by the Webapp classloader. Therefore it
belongs in /server/lib as you have seen.

See the classloader doc for more information on classloading in tomcat.
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html

Charlie

> -----Original Message-----
> From: Oliver Wulff [mailto:oliver.wulff@(protected)]
> Sent: Monday, June 02, 2003 3:23 AM
> To: tomcat-user@(protected)
> Subject: Realm class, Classloader
>
>
>
>
>
>
> I'm using Tomcat 4.1.24 and JDK 1.3.1.
>
> I've created a custom realm which is configured like this:
> <Context path="/sec_test" docBase="sec_test" debug="0"
>            reloadable="true" crossContext="true">
>     <Realm className="test.RacfRealm"/>
> </Context>
>
> The implementation class "test.RacfRealm" can be found only if it is
> deployed to the server/lib directory.
>
> If the Realm is configured for the context "sec_test", the
> class should be
> loaded by the corresponding WebAppClassLoader.
> What do you think?
>
>
>
>
>
>
> ******************* BITTE BEACHTEN *******************
> Diese Nachricht (wie auch allfällige Anhänge dazu) beinhaltet
> möglicherweise vertrauliche oder gesetzlich geschützte Daten oder
> Informationen. Zum Empfang derselben ist (sind) ausschliesslich die
> genannte(n) Person(en) bestimmt. Falls Sie diese Nachricht
> irrtümlicherweise erreicht hat, sind Sie höflich gebeten, diese unter
> Ausschluss jeder Reproduktion zu zerstören und die absendende Person
> umgehend zu benachrichtigen. Vielen Dank für Ihre Hilfe.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
> For additional commands, e-mail: tomcat-user-help@(protected)
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)




---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)