Darryl Pentz wrote:
You would think so but it isn't that easy. Which is good to some degree,
because that would seem like a scary security vulnerability. Nevertheless,
besides that, Tomcats classloader hierarchy also prevents this mechanism.
So if I'm understanding you correctly, different webapps use different
class loader instances and so the singleton is actually instantiated
separately
for each class loader? If that's the case then yeah, that would blow a big
hole in that idea. I didn't realize it was like that. I guess it's a
good thing
I haven't needed to do this so far.
As far as security, presumably the OP would be in control of both webapps
so that should be manageable if it was possible in the first place, which it
apparently isn't.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
