ouch...that sounds like a serious deployment problem.... so the need for tools.jar is for the compiler then? I'm sure I'm rehashing old topics (so feel free to tell me so), but what about things like Jikes?
> ---------- > From: Berin Loritsch[SMTP:[EMAIL PROTECTED]] > Reply To: [EMAIL PROTECTED] > Sent: Thursday, January 24, 2002 11:22 AM > To: [EMAIL PROTECTED] > Subject: Re: JDK 1.4 pre > > Lewis, Andrew J wrote: > > > tools.jar must be in the WEB-INF/lib? > > > > is that only if you use existing binaries instead of compiling yourself? > > > > > No, that is so that Cocoon can compile the Sitemap and any XSPs properly. > > > Remember that Cocoon does alot under the hood. While there is an effort > > to convert the sitemap to an interpreted file instead of compiled class, > it is not *quite* done yet. The initial reports are encouraging. It > beats > out the compiled sitemap in some tests, but their performances are fairly > comparable overall. > > > Until that time, and the time when XSP is no longer needed, tools.jar > needs > to go in WEB-INF/lib. > > -- > > "They that give up essential liberty to obtain a little temporary safety > deserve neither liberty nor safety." > - Benjamin Franklin > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
