-
1. Re: Jetty compile problem [JBoss 3.0.0-alpha]
foglesa Nov 19, 2001 4:23 PM (in response to pazu)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 -
2. Re: Jetty compile problem [JBoss 3.0.0-alpha]
pazu Nov 20, 2001 6:06 AM (in response to 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?
-
3. Re: Jetty compile problem [JBoss 3.0.0-alpha]
schaefera Nov 20, 2001 1:32 PM (in response to pazu)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 -
4. Re: Jetty compile problem [JBoss 3.0.0-alpha]
pazu Nov 21, 2001 5:45 AM (in response to 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? -
5. Re: Jetty compile problem [JBoss 3.0.0-alpha]
schaefera Nov 21, 2001 2:08 PM (in response to pazu)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 -
6. Re: Jetty compile problem [JBoss 3.0.0-alpha]
jules_gosnell Dec 4, 2001 4:07 PM (in response to pazu)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 -
7. Re: Jetty compile problem [JBoss 3.0.0-alpha]
timhowe Jan 11, 2002 2:19 AM (in response to pazu)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.
-
8. Re: Jetty compile problem [JBoss 3.0.0-alpha]
marc.fleury Jan 11, 2002 8:41 AM (in response to pazu)
> 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 -
9. Re: Jetty compile problem [JBoss 3.0.0-alpha]
zerosleep Feb 20, 2002 6:37 PM (in response to pazu)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.