Hi,

We are running into the problem of EJB's requiring environmental configuration 
such as ports remote hosts etc. The obvious solution seems to be to use the 
env-entry in ejb-jar.xml or to use a properties file inside the jar file but 
this means that to reconfigure the bean you must rebuild or at least manipulate 
the jar file. I don't want to go down this road really because I need to deploy 
the same bean in a lot of places with different config and it will become 
tiresome...

I would have thought that there would be a way for the container to provide 
configuration to the bean, specifically to over-ride the ejb-jar.xml or resolve 
names provided in there. It can be done for Datasources but this doesn't seem 
to be the case for name, value pair type resources like env-entry in 
ejb-jar.xml. 

One solution is to use system properties provided on the command line eg 
-Dx.y.z=blah  referenced in the Bean code but this doesn't seem very nice.

Any advice would be appreciated, thanks.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881366#3881366

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3881366


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to