[jboss-jira] [JBoss JIRA] Resolved: (JBWEB-74) tomcat config files fail to support default sysprop values like other jboss-service.xml type configs

[Remy Maucherat (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBWEB-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remy Maucherat resolved JBWEB-74.
---------------------------------

    Resolution: Done
      Assignee: Remy Maucherat  (was: Mladen Turk)


This feature has been added in JBoss Web 2.1.1.CR1.

> tomcat config files fail to support default sysprop values like other jboss-service.xml type configs
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBWEB-74
>                 URL: https://jira.jboss.org/jira/browse/JBWEB-74
>             Project: JBoss Web
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core
>            Reporter: John Mazzitelli
>            Assignee: Remy Maucherat
>
> From my JBoss forum post and Dimitris' reply:
> In jboss-service.xml, you can define values via properties like this:
> ${my.prop:123}
> where the value will be 123 if and only if my.prop property is not explictly set.
> However, this syntax does not seem to work on JBossAS 4.0.5 within the jbossweb-tomcat55.sar's server.xml.
> If I use ${my.prop} in server.xml, it works fine. But if I define a default value like ${my.prop:123}, it doesn't work - the value becomes literally ${my.prop}.
> Dimitris Andreadis reply: "JBoss uses org.jboss.util.StringPropertyReplacer for substituting variables. Tomcat/jboss-web must be using a different way to do this, so this is really a feature request for jboss-web."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira