[rogerparkinson]

I have a session bean that needs several custom env properties. I define these in ejb-jar.xml and fetch them via a call to context.lookup() (ie JNDI). This all works just fine.

My question is about how I manage these properly. Tthe bean will get deployed on my production server which has different values for the env properties. If I just copy the .jar directory to the deploy directory on the target I will overwrite these.

Am I correct to use the ejb-jar.xml file for this or should I put the env properties somewhere else?

Thanks

System Setup ——————————-
Operating System and version: win2ksp4
Eclipse version: 3.0.1
Eclipse build id: 200409161125
Fresh Eclipse install (y/n): n
If not, was it upgraded to its current version using the update manager? yes
Other installed external plugins: no
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 13
MyEclipse version: 3.8.4
Eclipse JDK version: 1.4.2
Application Server JDK version: 1.4.2
Are there any exceptions in the Eclipse log file? no

– Message Body ——————————-

[Riyad Kalla]

Moving to OT > Soft dev, this is an EJB question.

I will ask our EJB guy to have a look at this if he has time, in the mean time I encourage any users to share their ideas.

[rogerparkinson]

I ought to have said I’m using JBoss 4 earlier, but I think the question is somewhat generic
Roger

[Author]

Posts