EJB deployement: jar versus ear

Question

WLS 6.1 SP2, NT4
Hi,
if I deploy an ejb-jar-1 to be used by a Java client for instance and
have requirements for a new web client using ejb-jar-1 and a new ejb-jar-2
six months later,
what should I do ?
1/ Deploy a newapp.ear including my war file, my ejb-jar-2 and again
ejb-jar-1.
This ejb-jar-1 will be referenced as newapp.ear\ejb-jar-1.jar compared
to the one previously deployed (ejb-jar-1)
In this case, how does JNDI work if I lookup "MyBean" especially if both
ejb-jar-1
and newapp.ear\ejb-jar-1 have one common JNDI entry. Do have I to
include a new ejb-jar-1-bis instead and change the
jndi entry in its descriptor ?
2/ Deploy a newapp.ear including my war file and only my new ejb-jar-2.
3/ Deploy a newapp.ear including my war file and only my new ejb-jar-2 but
referencing/attaching the ejb-jar-1.
4/ Anything else ?
Generally speaking, I am a bit confused when comes the deployment of several
applications
potentially using common components. Can we have duplicate deployed
components ? Is there any JNDI issues
associated with such practice ?
Could somebody clarify how does it work when comes to deploy single EJBs
versus applications including EJB ?
What is the best practice etc ... ?
Thanks
Arnaud

Answer 1

STARTMODE is only available in WLS 6.1 and not WLS 6.0.
Deepak Vohra wrote:
Tom
Edit the startWeblogic Command Script.
set STARTMODE=false
Deepak
Tom Gerber wrote:
Is STARTMODE available in 6.0??? I thought that was new to 6.1.
I'm running on NT so do I set this on the Java command line as a
-DSTARTMODE=false or is it a regular environment variable?
Tom
Deepak Vohra wrote:
Tom
In startWebLogic script set STATRTMODE=false
STARTMODE=false starts server in development mode.
Deepak
Tom Gerber wrote:
We are using wl 6.0 sp2 rp2 - with 2 WL instances on the same box.
We have always seemed to have had this headache with WL - getting EJB's
to reload consistently.
Does anyone have a sequence of steps they follow to get good consistent
reloading results from both an EJB in its own JAR or an EAR file?
If we just copy the file over sometimes it seems to reload and sometimes
not.
If we try to use the console to "install an application" again sometimes
it deploys the EJB's to the wrong server instance!
Also is there anyway in the Weblogic deployment descriptor to specify
which instance the EJB should be deployed against?
Thanks
Tom
Rajesh Mirchandani
Developer Relations Engineer
BEA Support