[jboss-jira] [JBoss JIRA] (WFLY-8868) per application Expressions

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFLY-8868:
----------------------------------------

[~weberj] Thanks for the input about deployment overlays requiring CLI. That's an oversight in how we developed the feature, not ensuring HAL coverage. Now that [~claudio4j] is aware of it he's filing a JIRA to get that fixed.

In any case, your point about being able to associate properties with the deployment management resource instead of messing around with the deployment content is valid.

I'll clone this into WFCORE. Adding properties to the deployment management resources is something we do in core. But the actual enablement of expression resolution is turned on/off via the ee subsystem in full. So there would be two pieces / two issues. Hence the clone.

> per application Expressions
> ---------------------------
>
>                 Key: WFLY-8868
>                 URL: https://issues.jboss.org/browse/WFLY-8868
>             Project: WildFly
>          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)