I think it would be feasible to pull the engine out and use it and then
attempt to put it back in. The key would be that at the end of the road
the next JSP specification dictates a pluggable JSP engine and an
API/configuration for plugging them in. Anyone have any experience with
Jasper?
-bp
Ted Husted wrote:
Would it be feasible to use Jasper 2 instead?
Historically, it seems that the specifications that were based on a
working technology have been more successful than "speculative"
specifications. I think everyone involved in the process agrees that
it's much cleaner to create a standard around existing technology.
-Ted.
On Nov 20, 2007 1:25 PM, mraible <[EMAIL PROTECTED]> wrote:
I don't think their implementation would be useful. Their JSP compiler
doesn't support taglibs or JSP EL - the only thing it has that resembles JSP
is the extension. ;-)
Matt
Ted Husted wrote:
On Nov 20, 2007 11:57 AM, mraible <[EMAIL PROTECTED]> wrote:
The best thing is to probably see what's on tap for JSP 2.2 and see if we
can
get it on the EG's radar.
Matt
If Matt's client were willing to contribute the IP, another way to
proceed would be to open source a proof of concept for the EG to
consider (and the rest of us to actually use!). Depending on the
extent of package, the contribution could be setup as a top-level ASF
project or Commons component.
Call me crazy, but I believe in folding my own parachute :)
-Ted.
---------------------------------------------------------------------
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]
