-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 19 May 2006, Carsten Ziegeler wrote:
Date: Fri, 19 May 2006 09:46:10 +0200
From: Carsten Ziegeler <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: [2.2] Classloading
Giacomo Pati wrote:
How does this work if one has added ServletFilters or a top level
Spring applicationContext? Does he has to take care of it's own to
deploy the necessary jars at the right place?
Hmm, good question.
Do we need to clone the maven webapp-plugin (the one creating a
war/webapp structure)?
No, I think/hope that we can do this in our deployer tool.
Not sure we can (Reinhard?)
At the first glance it doesn't seem so easy to me
Yes, you're right. Now I see two solutions (perhaps there are more?):
a) We forget about the paranoid class loading completly as this causes
too much problems with other servlets or filters defined in the webapp.
This would require to rely on the application server when it comes to
class loading.
b) We require that every servlet and filter use our paranoid class
loader. We could achieve this by wrapping our ParanoidServlet and our
ParanoidFilter class around the real servlet/filter in the web.xml. So
all you have to do is a little bit more configuration in web.xml.
Instead of directly configuring your servlet/filter you configure the
wrapper and give your class as a parameter. Together with the deployer
tool everything else should be transparent.
I would try to go for b)
b) might work, but since you want it to be the default ClassLoader I
expect problems users forgot about wrapping their stuff in web.xml.
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEbXx4LNdJvZjjVZARAm06AKDy+im44BQGReqTkvb3/95zI9iv0ACg5HeF
5lEmkhjGegX+9cVFHRzesJI=
=T6+R
-----END PGP SIGNATURE-----
