[jboss-dev-forums] [JBoss AS 7 Development] - Variable Expansion Environment Specific

jmighion do-not-reply at jboss.com
Wed Aug 15 11:36:30 EDT 2012


jmighion [https://community.jboss.org/people/jmighion] created the discussion

"Variable Expansion Environment Specific"

To view the discussion, visit: https://community.jboss.org/message/753832#753832

--------------------------------------------------------------
The variable expansion with ${foo} works locally on a Win 32 and 64, jdk 1.6.0_26, EAP 6.0, but on Win Server 2003 with the same jdk and EAP 6.0 the variable expansion doesn't work.

I have system properties set in standalone.xml like : 
<system-properties>
        <property name="queueManager" value="some.queue.manager"/>
</system-properties>

Through the cli I can see the variable is set with /system-property=queueManager:read-resource.  When I try to deploy a .war with a reference to ${queueManager} in ejb-jar.xml I get an exception saying it can't find "${queueManager}" instead of "some.queue.manager".  

It also works locally when setting the variable in standalone.conf.bat with -DqueueManager=some.queue.manager, but not on the Win Server 2003 environment.

Are there any environment specific constraints I should know of or might this be a bug?
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/753832#753832]

Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2225]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20120815/5a6a2609/attachment.html 


More information about the jboss-dev-forums mailing list