[jboss-jira] [JBoss JIRA] (WFCORE-2908) Per application Expressions driven by the management model
Brian Stansberry (JIRA)
issues at jboss.org
Fri Jun 2 12:05:00 EDT 2017
[ https://issues.jboss.org/browse/WFCORE-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry moved WFLY-8883 to WFCORE-2908:
------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-2908 (was: WFLY-8883)
> 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
> Reporter: Juergen Weber
> Assignee: Jason Greene
>
> 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
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list