I'm up for it. Perhaps a proposal that everyone can "sign" would help?
Matt, any other ideas on how to get it moving?
-bp
mraible wrote:
I think the community is ripe for a change in JSPs. We should definitely
start voicing opinions about changing the spec so they can be loaded from
the classpath - or some other resource loader. My current client has their
own JSP compiler and they leverage Spring's Resource Loader stuff to load
JSPs from a JAR on a remote server. It's technically feasible - let's make
it part of the spec!
Matt
Ted Husted wrote:
Has anyone tried encapsulating Jasper behind a standalone servlet and
have it load the JSP template independently of the container (a la
Freemarker and Velocity) but not independently of the servlet API
(which would be the second biggest upgrade to the spec).
-Ted.
On Nov 19, 2007 8:06 PM, Martin Cooper <[EMAIL PROTECTED]> wrote:
On Nov 19, 2007 9:55 AM, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
<huge-snip/>
I'd even go one step further and
abstract out JSPs so that they didn't require a container and provide a
javax package to access and use them outside of containers.
Good luck with this part. ;-) I went down that path for a while, a few
years ago, and it's a major pain to try to work around all the
dependencies on the servlet API, especially in a way that allows
arbitrary tag libraries to continue to work. We ended up having to
create an artificial request in order to get the right context for the
container to invoke the JSP. Yuck.
--
Martin Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
