OME/common/lib/*.jar
TOMCAT_HOME/shared/lib/*.jar
as well as any web-app specific classpaths ( probably WEB-INF/lib/*.jar )
Steph
> -Original Message-
> From: Dmitry Beransky [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 13, 2003 12:55 PM
> To: [EMAIL PROTECTED]
> Subjec
At 01:16 PM 8/13/2003, Subir Sengupta wrote:
Try using jspc with the -compile flag and see what happens. Your code is
probably not setting something (I don't know what), which is causing it to
not compile.
You're right. I found a conflict in option settings between the output
directory and the j
to compile. It's much
much faster than javac.
Subir
-Original Message-
From: Dmitry Beransky [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 11:50 AM
To: Tomcat Users List
Subject: RE: Jasper2's JspC
At 10:42 AM 8/13/2003, Subir Sengupta wrote:
>Use the -compi
At 10:42 AM 8/13/2003, Subir Sengupta wrote:
Use the -compile argument.
At 10:42 AM 8/13/2003, Steph Richardson wrote:
Otherwise, JspC will not create .class files for you, but the java files
that JspC creates can just be compiled with javac, using
Tomcat's classpath
Here's the thing. Setting -c
Use the -compile argument.
-Original Message-
From: Dmitry Beransky [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 9:55 AM
To: [EMAIL PROTECTED]
Subject: Jasper2's JspC
Hi,
I'm having partial luck manually invoking JspC and compiling JSP pages on
demand. I get
Hi,
I'm having partial luck manually invoking JspC and compiling JSP pages on
demand. I get as far as precomiling to .java, but for the world of me
can't figure out how to get the java class compiled to bytecode. Looking
at the source code for org.apache.jasper.compiler.Compiler, it appears t