Jetty compile problem [JBoss 3.0.0-alpha]

[pazu]

JBoss has been unable to compile some of my JSP files. It seems that javax.ejb.* isn't in JBoss classpath, nor any of my ejb jars.

My app is deployed in a ear file containing a jar with my beans and a war with jsp pages. Shouldn't JBoss set Jetty classpath to include my beans jar and javax.ejb.* jars?

Here is the stack trace:

[Jetty] WARNING: Servlet Exception for /erp-test/cliente.jsp
org.apache.jasper.JasperException: JASPER: Unable to compile class for JSP/tmp/JettyContext1826.tmp/_0002fcliente_0002ejspcliente_jsp_0.java:19: Class javax.ejb.FinderException not found in import.
import javax.ejb.FinderException;
^
/tmp/JettyContext1826.tmp/_0002fcliente_0002ejspcliente_jsp_0.java:20: Package com.tld.erp.cliente.interfaces not found in import.
import com.tld.erp.cliente.interfaces.*;
^
/tmp/JettyContext1826.tmp/_0002fcliente_0002ejspcliente_jsp_0.java:21: Package com.tld.erp.cliente.model not found in import.
import com.tld.erp.cliente.model.*;
^
3 errors

at org.apache.jasper.compiler.Compiler.compile(Compiler.java:249)
at org.apache.jasper.servlet.JspServlet.doLoadJSP(JspServlet.java:448)
at org.apache.jasper.servlet.JasperLoader12.loadJSP(JasperLoader12.java:146)

(...)

it goes on for some lines.

[foglesa]

in the conf directory, open jetty.properties and change it like so....

tc_path_add=../lib/ext/org.apache.jasper.jar:../lib/ext/javax.servlet.jar:../lib/ext/jboss-j2ee.jar

Al

[pazu]

Ok, now it doesn't complain about javax.ejb.* anymore. However, it still can't find my com.tld.erp classes. These classes are packaged in a jar inside the ear. Shouldn't JBoss add them to Jetty classpath when deploying the application?

[schaefera]

The JSP pages in a WAR file need to contain the necessary classes by themself as well. Note that the EAR file is just a container for WAR and JAR files but does not provide class sharing.

Add you classes either unpacked into the WAR file under
/WEB-INF/classes or packed put the JAR file under /WEB-INF/lib. Note that only home/remote interfaces and other helper classes must be put into the WAR file and not the EJB Bean classes.

Have fun - Andy

[pazu]

The application works fine under JBoss 2.4.x, however -- even without adding the bean classes to the war. What behavior should I expect as "correct"?

Or better yet: shouldn't JBoss really show what's integrated deployment and dismiss the need to deploy such classes more than once?

[schaefera]

I think JBoss 3 is not going along with EJB 2.0 spec. where the packaing and class loading is specified in greater details than EJB 1.1.

Therefore we just have to wait - Andy

[jules_gosnell]

I posted an explanation of this on a more recent thread about RH/Jetty in this forum - you may want to take a look.

Jules

[timhowe]

Did you ever get an answer to your problem? I'm having the same problem with a similar application. I even added the jar files in the source directory and the deployment directory to the classpath - still I get "not found in import". Thanks for your help.

[marc.fleury]

> Or better yet: shouldn't JBoss really show what's
> integrated deployment and dismiss the need to deploy
> such classes more than once?

That is what I am working on... if ... only... I ... could... .commit

[zerosleep]

I fixed this problem by including the ejb.jar from java.sun.com/ejb in my war's /lib folder and of course I included all of my ejb's classes as part of the war.