I had the same problem, it was due to a small bug
When I did the changes outlined below it worked.
I was told that the changes would be inserted into
CVS a few days ago.
retrieving revision 1.2
diff -r1.2 JBossWebApplicationContext.java
> // fileClassPath+=jar;
> fileClassPath+= System.getProperty("path.separator") +jar;
> // fileClassPath+=":"+jar;
> fileClassPath+= System.getProperty("path.separator") + jar;
JSPs are very problematic.
Jetty is only explicitly control of what goes on it the WAR, but many classes are loaded into it's classloader before it takes control.
If you could just pass a ClassLoader to the JSP compiler, there would be no problem - but you cannot. You have to pass it a classpath string.
Extracting one of these from a hierarchy of ClassLoaders in non-trivial.
For this reason, JSP on-the-fly compilation will lag a little in RH (it probably never worked properly in 2.4 anyway - we are talking Jetty) .
When Marc checks in his new scoped ClassLoader I shall try to sort out a proper solution for JSP compilation - anything up until then is a temporary hack.
The best solution until then is to precompile you JSPs - all your problems will go away magically.....
I'm a bit new to this... but, how do we precompile our JSPs? Is it pretty easy to do? I'm trying to use JBoss3.0 with Jetty also. I'm not finding anything on how to precompile the JSPs. I'm just seeing messages that say it solves some problems and performance issues.
Look on the web.
Try the jakarta site. There must be something in the jasper (JSP engine used by Tomcat and Jetty) doc about it.
From memory I think the compiler is called jspc.
It just does what Jasper would do the first time you hit a page, but before deploy time, whilst you have full control over the classpath.