You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@jakarta.apache.org by Ted Eiles <te...@learningmachines.com> on 1999/08/31 03:28:37 UTC
Requirement: command-line interface to pre-compile .JSP
Hello ---
I'm new to this list so I don't haven't seen the current Josper
requirements (are they available?). I have a requirement.
I want to be able to pre-compile all my .JSP's in the servlets. I would
expect both the JSP engine would need to have a "static main" and that the
naming convention for generated servlets be manageable w.r.t. deploying the
generated .class files (or jar's) into production.
Reason 1: I can't afford run-time errors that could've easily been found
by either a JSP translator or a java compiler.
Reason 2: I want to consider .JSP's as source code and not to deploy them
in my production environments.
--- Ted
Re: Requirement: command-line interface to pre-compile .JSP
Posted by "Craig R. McClanahan" <cm...@mytownnet.com>.
Ted Eiles wrote:
> Hello ---
>
> I'm new to this list so I don't haven't seen the current Josper
> requirements (are they available?). I have a requirement.
>
> I want to be able to pre-compile all my .JSP's in the servlets. I would
> expect both the JSP engine would need to have a "static main" and that the
> naming convention for generated servlets be manageable w.r.t. deploying the
> generated .class files (or jar's) into production.
>
> Reason 1: I can't afford run-time errors that could've easily been found
> by either a JSP translator or a java compiler.
> Reason 2: I want to consider .JSP's as source code and not to deploy them
> in my production environments.
>
> --- Ted
>
The JSP 1.1 specification (not yet implemented by the released JSWDK, but
likely to be soon) addresses this need. Section 3.4 describes a protocol for
requesting pre-compilation of your JSP pages in a development environment.
This is useful not only for the reasons you have identified, but also to allow
deployment of JSP pages where there is no compiler available (such as a server
based on a JRE implementation, rather than a JDK. This feature will be
required of *all* 1.1-compliant JSP engines, not just the Jakarta reference
implementation.
Craig McClanahan