The problem he was having was not being able to find EJB interfaces after moving the WAR file outside of the EAR. That does not appear to be a bug since you would expect to lose visibility in that case. Putting the EJB interfaces in a jar file under WEB-INF/lib will solve his problem without editing deployment descriptors. I am also using a WAR inside an EAR and that works fine and he actually had that working also.  
----- Original Message -----
Sent: Friday, February 21, 2003 8:14 AM
Subject: Re: [JBoss-user] Separating a WAR from its EAR

Hi Jonathan,
 
I never thought that we'd talk to each other using the jboss mailing list :)
 
Make sure you have all jars in your war file that are needed and add the web resource
entries to web.xml. Do not forget your ejb class files.
 
We went through this process as well when we deployed our application (an ear with a war inside)
on JBoss2.44 and Tomcat3.2.3 or something). Since there is a bug you have to deploy this
separately.
 
If you have more questions then you can contact me directly. Just put a dot between the first and the lastname
and replace the yahoo.de with our company account.
 
CU
 
Andreas
 
----- Original Message -----
Sent: Friday, February 21, 2003 2:18 PM
Subject: [JBoss-user] Separating a WAR from its EAR


Folks,
We have our front end in a WAR living inside our EAR file. For reasons I won't go into here, we thought it might be an idea to take the WAR out of the EAR and deploy it separately.
However, when we try using it, we get JNP errors complaining about not finding remote interfaces.

Do you need to add resoure references in the WAR to get access to the Remote interfaces, much like you do for a session bean to access entity beans that live in another JAR/EAR?
Ciao,
Jonathan O'Connor
Development Manager
XCOM Dublin
Phone: +353 1 872 3305
Mobile: +353 86 824 0736

Reply via email to