Re: Implementing 2 new scopes using Struts

[Dan Connelly]

You would think that the ALL WEB APPs scope (or hierarchicial scopes) would be easy to do.  It is not.  I had thought that by having one app run another app, the controlling app could "peek".   Doesn't work that way either.  (Too bad.)   One can fetch the sessionid's of other HttpSessions from the the HttpSessionContext.  However, this does not grant access to objects in the session scope of the other sessions (as I had once thought).  Prohibited by (7.3) of the Servlet Specification.   Craig McC. recently posted that the standard mechanisms are EJBs and (persistent) database.  I am intrigued with the idea of a hierachically scope managed by an EJB.  (The database thing is always possible but seems totally inelegant for this purpose.)   Has anyone tried to coordianate objects between app (in Struts) using EJBs?   ----- Original Message ----- From: Jonathan Asbell To: [EMAIL PROTECTED] Sent: Monday, June 25, 2001 8:23 AM 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