All of our JSP
compiles fail under 3.2.2. We get a "package does not exist" error
in that version of JBoss. The same ear works fine in 3.2.0 and 3.0.X
and weblogic. We have an ear that contains a war and that war's manifest
file lists all of the necessary jar files. Those jar files are assembled
with the ear so they are available for loading. The jar files are
not listed in application.xml because they are utitlity jars and not EJBs
or executable java applications.
The jar files are
not in WEB-INF/lib nor are the loose classes found in WEB-INF/classes and
perhaps that is the issue? We really want to keep the jars in the ear
root and that has been working great on all platforms. Has JBoss 3.2.2 tightened
the reigns on what a war file can "see" in terms of classes? Must war file
classes now be included in WEB-INF/lib or WEB-INF/classes? Before you could
put them in, say, /jboss/server/default/lib or
/jboss/server/default/deploy or in the root of the ear (which we settled
on) but now that breaks.
12:13:20,962 ERROR [STDERR]
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:454)
12:13:20,978 WARN [jbossweb] WARNING: Exception for /
org.apache.jasper.JasperException: Unable to compile class for JSP
12:13:20,978 WARN [jbossweb] WARNING: Exception for /
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: -1 in the jsp file:
null
Generated servlet error:
[javac] Compiling 1 source file
[javac] C:\tmp\Jetty_0_0_0_0_8080__\Logon_jsp.java:65: package verilet.page.user does not exist
[javac] verilet.page.user.LoginPageBean pb = null;
[javac] ^
[javac] Compiling 1 source file
[javac] C:\tmp\Jetty_0_0_0_0_8080__\Logon_jsp.java:65: package verilet.page.user does not exist
[javac] verilet.page.user.LoginPageBean pb = null;
[javac] ^
