[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=13415168#comment-13415168 ] 

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

Something along these lines is already supported -- see my comment on https://issues.jboss.org/browse/WFLY-3977 A META-INF/jboss.properties file in the deployment, or added as a deployment-overlay, will let you add properties to the expression resolution.

I'm not sure if that's described anywhere in WildFly documentation.  A bit of googling didn't show anything. :(

The https://docs.jboss.org/author/display/WFLY10/Expressions page is a child page of the docs on developing subsystems, so it's focused on expression resolution during handling of management operations or during standalone.xml etc config file processing during boot. In that context, the META-INF/jboss.properties mechanism is not available.

> 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)