Hi
Class loader is first on my to do list.
I've separated server lib loader (in branch already), want to have per web app loaders used in WebAppAdapter as next.
So each WAA will contain it's CL and activate it for servicing requests.
H.
-original message-
Subject: Re: Deployer refactoring
From: Survivant 00 <survivant00_at_gmail.com>
Date: 27-08-2009 14:34
perfect.
One thing about the classloader.
with the actual code, we have one problem. All the classes, jars on loaded
in the same classloader.
so if we have
structs1.2.jar and 1.4.jar in 2 differents webapps.. both of them will
use the same.
Another thing
I only added jars that were into /classes and /lib
look like other web container include other folders that contains jars.
like /lib-otherlib/a.jar
2009/8/27 Hubert Iwaniuk <neotyk_at_kungfoo.pl>
> Hi *
> Since I'm not only one interested in improving deployer, I've branched my
> refactoring to
> https://grizzly.dev.java.net/svn/grizzly/branches/deployer-refactoring So
> it's easy to follow what is happening there.
> For now I've started Structuring classloaders and started creating
> WebAppAdapter plus lots of minor improvements.
>
> Cheers,
> Hubert.
>