Bear Bibeault wrote:The classpath is only used during compilation. At runtime the jar file must be placed where Tomcat will load it into its own classpath. If using container-managed connection pooling (highly recommended) place the jar in Tomcat's lib folder.
And please be sure that you are not doing this, or any other Java code, inside a JSP. That is a poor, but all-too-common, practice.
what do you mean, can you explain what i'm doing wrong?Bear Bibeault wrote:So much for my advice on not writing JSP like it's 2001.
Bear Bibeault wrote:
And please be sure that you are not doing this, or any other Java code, inside a JSP. That is a poor, but all-too-common, practice.
How would it be done outside the jsp then, in a servlet? can you provide a more detailed explanation? why isn't java code good inside a jsp?Bear Bibeault wrote:Repeated from my first reply:
Bear Bibeault wrote:
And please be sure that you are not doing this, or any other Java code, inside a JSP. That is a poor, but all-too-common, practice.
karl czukoski wrote:How would it be done outside the jsp then, in a servlet? can you provide a more detailed explanation? why isn't java code good inside a jsp?
SCJP 6
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |