AFAIK the EARs will be loaded before the WARs so initialization so that
initialization code should be happy once you give it access to the EJB
interfaces at load time.
Here's a couple handy ANT FYIs in case you were not aware of these. You can
exclude your implementation files and jar up the inter
ublin
Phone: +353 1 872 3305
Mobile: +353 86 824 0736
Rod Macpherson <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
21.02.2003 17:02
Please respond to jboss-user
To: [EMAIL PROTECTED]
cc:
Subject: Re: [JBoss-user] Separating a WAR from its EAR
The
] 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.
h our company
account.
CU
Andreas
- Original Message -
From:
Jonathan.O'[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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 insi
ECTED]
To: [EMAIL PROTECTED]
Sent: Friday, February 21, 2003 5:18
AM
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
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
