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

[Juergen Weber (JIRA)]

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

Juergen Weber updated WFLY-8868:
--------------------------------
    Description: 
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

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