ause of the JSP compilation issue.
That would be nice to avoid but it's not a show-stopper that we have to run
the tests serveral times.
Rod
- Original Message -
From: "Jules Gosnell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 25, 2003 2:31
Guys,
I understand that it would be nice for you not to have to worry about
when/how your JSPs get compiled.
This fn-ality should be a part of Jasper. I only do the Jetty/JBoss
integration.
If you really want it, and I am always dealing with traffic on this
subject - so many people do, then y
bjørn Ravn Andersen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 18, 2003 12:32 AM
Subject: Re: [JBoss-user] classpath for JSP compiling
Jules Gosnell wrote:
> This step is problematic to perform in an automated manner, due to the
> need for developme
Jules Gosnell wrote:
This step is problematic to perform in an automated manner, due to the
need for development time knowledge (which jsps are servlets and which
are just included, etc...).
I understand there is a problem detecting this automatically, but would
it be hard to implement given
>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 17, 2003 1:56 PM
Subject: Re: [JBoss-user] classpath for JSP compiling
> Used to use -package to specify the base package name and then JspC would
> assume that the directory structure of your JSPs was the fully qualified
> package
l" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 17, 2003 10:50 AM
Subject: Re: [JBoss-user] classpath for JSP compiling
> Rod Macpherson wrote:
>
> >To summarize,
> >
> >1. deploy-time compilation precludes a specific optimization.
vey useful...
- Original Message -
From: "Jules Gosnell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 17, 2003 2:38 AM
Subject: Re: [JBoss-user] classpath for JSP compiling
Rod Macpherson wrote:
Can we specify that we want all JSPs compiled at deplo
>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 17, 2003 2:38 AM
Subject: Re: [JBoss-user] classpath for JSP compiling
> Rod Macpherson wrote:
>
> >Can we specify that we want all JSPs compiled at deploy time? The servlet
> >approach has shortcomings such as losing the abi
ell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, February 16, 2003 9:35 AM
Subject: Re: [JBoss-user] classpath for JSP compiling
Jasper expects it's classpath to be passed as a string via an init-param.
This string is generated by walking up the classloader hi
Rod Macpherson wrote:
Can we specify that we want all JSPs compiled at deploy time? The servlet
approach has shortcomings such as losing the ability to just update a page
on the fly. Since jetty controls the package structure and the location of
class files it would be nice to have a compile-on-
least
an interface to point to a war and say "compile this".
- Original Message -
From: "Jules Gosnell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, February 16, 2003 9:35 AM
Subject: Re: [JBoss-user] classpath for JSP compiling
> Jasper expec
Hi,
it certainly was deployed, otherwise the servlets wouldn't work
either...
But I've solved the issue by creating an .ear with the .jar and the .war
listed as modules in the application.xml...
I didn't know this was obligatory though...
I thought an .ear wasn't really needed because the .jar
Jasper expects it's classpath to be passed as a string via an init-param.
This string is generated by walking up the classloader hierarchy and
adding all relevant dirs/jars to it.
This generation is done on deployment of the war.
It looks s if it is missing the classes in your ejb-jar.
was it
Hi,
I'm writing a simple JSP in which I try to access an Entity EJB. Yet
while accessing the jsp, I get javac errors in the JBoss log, like this:
Error compiling file:
/usr/local/jboss-3.0.4_tomcat-4.1.12/tomcat-4.1.x/work/MainEngine/localhost/eenloketsysteem/jsp/stTest_jsp.java
/usr/local/jbos
14 matches
Mail list logo
