This content has been marked as final.
Show 3 replies
-
1. Re: Can Jboss.xml be Externalised ?
jaikiran Nov 20, 2008 4:04 AM (in response to shetty_ritesh)"shetty_ritesh" wrote:
Example if i need to change the JNDI name <destination-jndi-name> in a MDB to a different value without changing the build ?
Instead of moving the jboss.xml to some other location, you can use replaceable system properties to configure the destination-jndi-name.
Here's an example:<jboss> <enterprise-beans> <message-driven> <ejb-name>MyFirstMDB</ejb-name> <destination-jndi-name>${myqueue.placeholder}</destination-jndi-name> </message-driven> </enterprise-beans> </jboss>
Then you can pass the myqueue.placeholder as a java system property as followsrun.bat -Dmyqueue.placeholder=queue/testQueue
-
2. Re: Can Jboss.xml be Externalised ?
shetty_ritesh Nov 20, 2008 2:17 PM (in response to shetty_ritesh)Thanks Jai Kiran, this is exactly what i was expecting.
But i have one concern. There may be many such configurations that need to be externalised. Can we have something like a properties file from which the jboss picks up the key value pair ? -
3. Re: Can Jboss.xml be Externalised ?
jaikiran Nov 21, 2008 1:15 AM (in response to shetty_ritesh)"shetty_ritesh" wrote:
Can we have something like a properties file from which the jboss picks up the key value pair ?
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=145915#4190838 something that i learnt just yesterday :-)