JNDI is expensive.  Then second one is a restriction of data storage visibility to a sub-directory of a Web app.  Ex. I have a web app called myWebApp, which has its own WEB-INF directory with a web.xml inside. Below myWebApp I hav 3 directories called Jon, Nanduri, and Ted.  I want to store things that pertain to the Jon branch which neither the Ted branch nor the Nanduri branch can see.
----- Original Message -----
Sent: Monday, June 25, 2001 8:21 AM
Subject: RE: Implementing 2 new scopes using Struts

Jonathan,
 
>One scope will work across (between) web-applications:  Ex. user logs on, and an object representing the users values and state is
 >placed into a scope where ALL WEB APPLICATIONS can see it.
 
   Use JNDI and throw the user info up the jndi tree
 
I didn't understand your second scope. Can you elaborate. Thanks.
 
cheers,
Amar..
 
     
-----Original Message-----
From: Jonathan Asbell [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 25, 2001 8:24 AM
To: [EMAIL PROTECTED]
Subject: Implementing 2 new scopes using Struts

I will be implementing new scopes using Struts for our unique needs, and they need to be application server independent. 
 
One scope will work across (between) web-applications:  Ex. user logs on, and an object representing the users values and state is placed into a scope where ALL WEB APPLICATIONS can see it.
 
Another scope is restricted to specified directories inside of an application:  Ex. data saved would only be visible when inside a specific sub-directory.
 
I am currently examining the 2.3 servlet spec.  Does anyone have any advice as to what to watch out for in implementing this considering I want to be able to be compatible with servlet containers in general and leverage container management and web.xml configuration.  Could anyone refer me to some specific sections in the servlet spec that you feel I should pay specific attention to while I am doing this.
 
Thank you
Jonathan

Reply via email to