Re: Backward incompatible changes

[Costin Manolache <costin@tdiinc.com>]

> 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.

Also, I think it will be very usefull to be able to change the maping between
JSP files and servlet names.
You might want to use JSP only for development, and use the generated servlets for
deployment.
That is possible right now ( except that out.close() hangs the latest JSDK :-),
except the naming that is
not so "friendly". Having a "Custom Mapper" option ( and a Mapper interface ) will
"enable" many
ideeas.

Regards,
Costin