[jboss-jira] [JBoss JIRA] (WFCORE-2908) Per application Expressions driven by the management model

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated WFCORE-2908:
-------------------------------------
    Description: 
This is the core side part of WFLY-8868. The overall request involves being able to include a properties attribute as part of a management model deployment resource, with those properties then being available to expression resolution, the same way env vars, system props, vault values and META-INF/jboss-properties values are. The core side aspect of this is to maintain the props in the model and make those values available to the DeploymentUnitProcessors. The WildFly full side part is to enhance the existing ee subsystem DUPs that deal with expression resolution to have them take advantage of this new source of resolution data.

This basically is an improvement on the existing META-INF/jboss-properties facility by allowing the admin to control the resolution without having to mess with the deployment content.

  was:
Wildfly supports Expression Substitution in descriptors [1]. These expressions are server global.

This should be enhanced to support application scoped expressions:
${this:aProperty}

It would be especially useful for Message Driven Beans, as an ActivationConfigProperty can only be set in a descriptor or via an annotation, but not in application code, so ActivationConfigProperties are effectively fixed.

Then you could deploy the same Message Driven Bean multiple times with a different name:

myMDB1.ear
myMDB2.ear

having 

<activation-config-property-value>${this:queuename}</activation-config-property-value>

and define

<application-properties>
<application name="myMDB_DEV_QUEUE_1.ear">
 <property name="queuename" value="DEV_QUEUE_1"/> 
</application>
<application name="myMDB_DEV_QUEUE_2.ear">
 <property name="queuename" value="DEV_QUEUE_2"/> 
</application>
</application-properties>

whereas for production the queuename properties would be different.

[1] https://docs.jboss.org/author/display/WFLY10/Expressions



> Per application Expressions driven by the management model
> ----------------------------------------------------------
>
>                 Key: WFCORE-2908
>                 URL: https://issues.jboss.org/browse/WFCORE-2908
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Juergen Weber
>
> This is the core side part of WFLY-8868. The overall request involves being able to include a properties attribute as part of a management model deployment resource, with those properties then being available to expression resolution, the same way env vars, system props, vault values and META-INF/jboss-properties values are. The core side aspect of this is to maintain the props in the model and make those values available to the DeploymentUnitProcessors. The WildFly full side part is to enhance the existing ee subsystem DUPs that deal with expression resolution to have them take advantage of this new source of resolution data.
> This basically is an improvement on the existing META-INF/jboss-properties facility by allowing the admin to control the resolution without having to mess with the deployment content.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)