This content has been marked as final.
Show 5 replies
-
1. Re: MDB external configuration
jaikiran May 21, 2009 10:38 AM (in response to cpslo1999)I'm hesitant to require that the person installing my consumer application(s) unzip the ear, change the selector's "myClientID" value, and rezip it. I would rather use a identical application package on our multiple production servers (and the test servers for that matter) and have other files, descriptors, or database settings outside of the ear tweaked to account for the environment.
I don't exactly remember which deployment descriptor file will contain the message selector - its either the ejb-jar.xml or the jboss.xml. In either case i guess you could specify some system property that gets substituted per system, dynamically. Something like this in the deployment descriptor:<message-selector>${someproperty}</message-selector>
Then, you can pass this property value as a JVM parameter through the server startup scripts:run.bat -Dsomeproperty=myClientID
You can edit the run.bat or run.conf to pass this property too. -
2. Re: MDB external configuration
anilit99 May 21, 2009 10:56 AM (in response to cpslo1999)I remember setting message selector in jboss.xml. A neat solution I should say !
-
3. Re: MDB external configuration
cpslo1999 May 21, 2009 11:00 AM (in response to cpslo1999)"jaikiran" wrote:
In either case i guess you could specify some system property that gets substituted per system, dynamically...
Then, you can pass this property value as a JVM parameter through the server startup scripts...
You can edit the run.bat or run.conf to pass this property too.
That's a slick trick. Is property substitution on deployment descriptors a standard JavaEE thing, or is that specific to JBoss? -
4. Re: MDB external configuration
anilit99 May 21, 2009 11:14 AM (in response to cpslo1999)I believe its a jboss specific thing.
-
5. Re: MDB external configuration
cpslo1999 May 21, 2009 12:08 PM (in response to cpslo1999)Alright. I'll give it a go.
Thanks guys for the tip!