Thank you for your quick reply !... I'm looking forward for "Global JNDI Resources" and how to adapt my code to this ...
>On Fri, 15 Mar 2002 [EMAIL PROTECTED] wrote: > > > Date: Fri, 15 Mar 2002 11:40:02 -0500 > > From: [EMAIL PROTECTED] > > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Realm configuration in jsp > > > > Hello all ! > > > > I'm currently developping a web application under tomcat, and I've a > > question for you all. > > Like a lot of us, I had to develop jsp pages which permits the remote user > > to manage user accounts that can use the application... I'm facing a little > > design problem : Tomcat realms (and jsp/servlet specification) permit to > > Authenticate a user, not change its configuration... > > No problem with that, but when it comes to develop the jsp that I did, you > > have to access the same Realm repository (JDBC/ Memory / LDAP) that the one > > used in Authentication. > > > > My current implementation force me to define JNDI resources that are clones > > of realm entries defined in server.xml, which I dislike (if you change > > something in realm configuration, don't forget to change it in Realm Write > > Access properties) > > > > My Question: > > > > How to get the Realm configuration used in the current application > Context / > > Container ??? I looked into JNDI Resource HOW-TO, but I see nothing to get > > server.xml configuration ... > > > >In Tomcat 4.0.x, you're pretty much stuck having to remember to change two >sets of configuration entries to access the underlying resources like >this. > >In the HEAD branch of Tomcat 4 (i.e. what is built in the nightly builds, >and what will become Tomcat 4.1) there is the notion of "Global JNDI >Resources" where you can declare a shared resource once, and then link to >it from multiple places. The admin webapp (also being built for the HEAD >branch) uses just this kind of trick to have a webapp that is able to >administer the very same user database that Tomcat is using to >authenticate, but without having to configure the access properties more >than once. > > > Please, help ! > > > > Fabien Nisol > > > >Craig > > >-- >To unsubscribe: <mailto:[EMAIL PROTECTED]> >For additional commands: <mailto:[EMAIL PROTECTED]> >Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
