in the conf directory, open jetty.properties and change it like so....
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?
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
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?
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
I posted an explanation of this on a more recent thread about RH/Jetty in this forum - you may want to take a look.
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.
> 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
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.