Application Server 7
  1. Application Server 7
  2. AS7-6120

Expand support for System Property substitution

    Details

    • Similar Issues:
      Show 10 results 

      Description

      Audit the core AS and all subsystems shipped in the AS distribution for suport for expression in management resource attributes.

      The basic philosophy toward expressions in previous releases was to only push devs to add support if there was a clear important use case. Devs could choose to add support beyond that, but we wouldn't push that. This JIRA and PRODMGT-195 from which it is derived reflects a change in philosophy. Now the philosophy is to support expressions unless the dev foresees a technical or future compatibility problem arising from doing so.

      This task DOES NOT advocate adding expression support to attributes that represent references to other model elements. Such references may prove problematic in the future and should not be added. We already have some model ref attributes that support expressions; this task DOES NOT advocate removing such support, unless the support has never been provided in a Final release (i.e. it was added during 7.2 development.)

      1. expressions.ods
        93 kB
        Brian Stansberry

        Issue Links

          Activity

          Hide
          Jeff Mesnil
          added a comment -

          the spreadsheet from 09/Jan/13 has red crosses for 2 messaging subsystem attributes: /profile=/subsystem=messaging/hornetq-server=/address-setting=* dead-letter-address & expiry-address. They're flagged as MR but the HornetQ addresses they reference are not part of the model, they are only runtime resources managed internally by HornetQ. I think it's ok to keep expression support for them.

          Show
          Jeff Mesnil
          added a comment - the spreadsheet from 09/Jan/13 has red crosses for 2 messaging subsystem attributes: /profile= /subsystem=messaging/hornetq-server= /address-setting=* dead-letter-address & expiry-address. They're flagged as MR but the HornetQ addresses they reference are not part of the model, they are only runtime resources managed internally by HornetQ. I think it's ok to keep expression support for them.
          Hide
          Brian Stansberry
          added a comment -

          I thought that was likely the case, but I flagged them to force myself to look or to ask you. Thanks for the input.

          Show
          Brian Stansberry
          added a comment - I thought that was likely the case, but I flagged them to force myself to look or to ask you. Thanks for the input.
          Hide
          Brian Stansberry
          added a comment -

          Updated the tracking file.

          Show
          Brian Stansberry
          added a comment - Updated the tracking file.
          Hide
          Brian Stansberry
          added a comment -

          Jeff, could you have a look at the various 'entries' attributes in messaging?

          In a standalone server it looks like those could support expressions (and we allow them from jndi names elsewhere in the AS). Biggest question is how big of a PITA it would be to add the transformation and testing thereof.

          Show
          Brian Stansberry
          added a comment - Jeff, could you have a look at the various 'entries' attributes in messaging? In a standalone server it looks like those could support expressions (and we allow them from jndi names elsewhere in the AS). Biggest question is how big of a PITA it would be to add the transformation and testing thereof.
          Hide
          Brian Stansberry
          added a comment -

          The /host=*/core-service=vault:vault-options attribute along with a few attributes in the datasource, mail, naming, security and web subsystems are type OBJECT where the object is basically a property map. Those should support expressions. (The web one is very low priority.)

          Show
          Brian Stansberry
          added a comment - The /host=*/core-service=vault:vault-options attribute along with a few attributes in the datasource, mail, naming, security and web subsystems are type OBJECT where the object is basically a property map. Those should support expressions. (The web one is very low priority.)

            People

            • Assignee:
              Brian Stansberry
              Reporter:
              Jimmy Wilson
            • Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: