[jboss-jira] [JBoss JIRA] (WFCORE-179) Support nested expressions in management API and deployment descriptors

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012905#comment-13012905 ] 

Brian Stansberry commented on WFCORE-179:
-----------------------------------------

Quick notes on this:

org.jboss.as.controller.ExpressionResolverImpl handles the expressions in the management API. It already has repeated resolution thing going on to allow e.g. $[system.property.foo} to turn into ${VAULT:xxx:yyy} which ends up as "bar". (That can already support the use case in the description, just by having system property "me" include a full vault expression instead of just a single attribute.)

For deployment descriptors and annotations, org.jboss.metadata.property.CompositePropertyResolver is what is currently used. It doesn't do a recursive thing; it loops through other PropertyResolver impls (e.g. one for system props, one for props packaged in the deployment, one for vault) until if finds one that resolves.



> Support nested expressions in management API and deployment descriptors
> -----------------------------------------------------------------------
>
>                 Key: WFCORE-179
>                 URL: https://issues.jboss.org/browse/WFCORE-179
>             Project: WildFly Core
>          Issue Type: Feature Request
>            Reporter: Brian Stansberry
>
> Users have requested support for expressions such as:
> {code}
> ${VAULT::oracle::${me}::0}
> {code}
> where "me" is a system property.
> Allows externalization of the vault attribute name.
> This will likely require JBMETA changes as well, as the deployment level stuff is there.
> I want this to be a generic thing, not just a specific solution to the above example. So, something like, given a string, find the innermost expression, resolve it and then repeat until the input equals the output (i.e. there are no more expressions.)



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)