JBoss Web
  1. JBoss Web
  2. JBWEB-74

tomcat config files fail to support default sysprop values like other jboss-service.xml type configs

    Details

    • Type: Bug Bug
    • Status: Resolved (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Similar Issues:
      Show 9 results 

      Description

      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."

        Gliffy Diagrams

          Activity

          Hide
          Remy Maucherat added a comment -

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

          Show
          Remy Maucherat added a comment - This feature has been added in JBoss Web 2.1.1.CR1.

            People

            • Assignee:
              Remy Maucherat
              Reporter:
              John Mazzitelli
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development