On Tue, 28 Aug 2001 00:09, Berin Loritsch wrote:
> Your problem is largly due to the fact that _EVERY_ WebApp is loaded in a
> different classloader with no access to each other. Anything else is a
> violation of the Servlet spec and a security hazzard.
thats what I thought ;)
> For non-J2EE installations, we can use Excalibur's naming package (Memory
> based JNDI and RMI based JNDI providers). You are still limited to one
> classloader with this solution, but it would allow Cocoon to use one root
> instance. (BTW, the RMI based solution will work with any number of
> webapps, but you would need your own script to get it started before the
> app server). Neither of these provide authentication, so they are not
> considered secure yet.
Another solution would be to put it in application scope from jsp ... err
forget what that is in real terms. I think application scope roughly
translates into something like
getServletContext().
setAttribute( "my-global-root-CM-that-is-unsafe", myComponentManager );
This will be exposed to all servlets in same webapp.
--
Cheers,
Pete
*------------------------------------------------------*
| "Computers are useless. They can only give you |
| answers." - Pablo Picasso |
*------------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
