On Tue, Nov 25, 2003 at 04:51:21PM +0100, Anders Engström wrote:
> On Mon, Nov 24, 2003 at 04:27:44PM +, Matthew Oatham wrote:
> > Hi,
> >
> > Is there any way to prevent JSP pages being recompiled everytime JBoss
> > restarts? i.e I deploy the web app - run the jsp - restart JBoss and tr-run
On Mon, Nov 24, 2003 at 04:27:44PM +, Matthew Oatham wrote:
> Hi,
>
> Is there any way to prevent JSP pages being recompiled everytime JBoss
> restarts? i.e I deploy the web app - run the jsp - restart JBoss and tr-run
> a JSP - instead of using a cached copy of the jsp page it is re-compile
Scott M Stark wrote:
This is an invalid warning due to the fact that the check used by Jetty to determine
if the javac compiler is visable does not apply to the 1.4.2 tools.jar.
Thanks, Scott.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
-
I think the exception says it all...
You haven't the tool.jar accessiblein your classpath ! ! !
Either you should define your classpath right or you could define your
JAVA_HOME variable correctly
Issuing the follwoing command :
"which java"
you may have the GCJ compiler / runtime installed inst
I had a problem just like this recently. I ended up hacking around it by
putting a second copy of common.jar in WEB-INF/lib. As far as the
ejb1.jar - create a client version of the jar (home and remote i/f classes
only) and put that in WEB-INF/lib.
Sorry this isn't more helpful!
- Origin
Each classloader has its own space, so I guess there is a loader problem.
Ive had similar problems using the URL Class loader. Basically need to
ensure that all the classes are available in each class loader
HTH
J
-Original Message-
From: Adison [mailto:[EMAIL PROTECTED]]
Sent: 26 Septe
