I have to disagree with this, jspc is a pre compiler, not a webapp packager.
John > I agree that JSPC needs to be simplified and that the webapp > mode should be retained. But the webapp mode should allow > for a war file to be generated which is self contained > including the precompiled JSP classses. And for the > generated war to be able to run from the war file with no > need to unpack it. > > Also I agree that this feature is a proprietary feature of > Tomcat and we should no longer try to generate a war that can > be deployed in any container. > > There may be a way to do this: > > Put the generated JSP class files in a /WEB-INF/jspwork/ > directory. This work directory would only be used by jasper > for loading jsp pages, the normal work directory would still > be used for all other things. > > Add the "jspwork" attribute to the DefaultContext and Context > config elements. This attribute would specify the directory > path within the war file to use for loading the JSP page > classes from by Jasper. > > This would allow JSPC to create a war file which was self > contained including the precompiled JSP page classes and be > runnable directly from the war or unpacked into a directory. > > +1 if we modify Tomcat & Jasper to support precompiled JSP > pages running > +from a > self contained war file. > > Regards, > > Glenn > > > > > -- > To unsubscribe, e-mail: > <mailto:tomcat-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
