Re: Backward incompatible changes

[Vincent Partington <vincentp@xs4all.nl>]

Hi Costin,

Costin Manolache wrote:
> 
> > 4) The jsp class loader will be modified in two ways:
> >    - classes whose name does not start with "_jsp." will be passed
> >      directly to the next class loader.
> >    - instead of directly trying the system class loader, the servlet
> >      class loader will be tried first (by calling
> >      JSPServlet.getClass().getClassLoader()).
> 
> One usefull feature will be to be able to change some java classes ( used by
> JSP files), and have them reloaded ( when the servlet is reloaded at least,
> but having a timestamp and checking all classes loaded from the jsp directory
> is also good ). You should be able to store all "JSPJavaBeans" in the same
> directory as jsp generates files, and have them reloaded - that means the
> first change should not be done.

You've got a point here. The idea was that all beans used from a JSP
page should be placed in the servlet repository (or the system
classpath). They would be loaded by the servlet class loader, and that
is why the JSP class loader calls the servlet class loader when it
cannot find a class. This setup would allow you to set your JSP
repository to be the same as the servlet repository without different
class loaders loading the same class file (which causes ClassCastException's).

Regards, Vincent.