[
https://issues.jboss.org/browse/WFLY-8868?page=com.atlassian.jira.plugin....
]
Juergen Weber commented on WFLY-8868:
-------------------------------------
META-INF/jboss.properties is an interesting mechanism, but it still requires individual
patching of an ear or deployment overlays (which do only work for CLI).
Concerning ease of deployment it makes no difference if I write the queue name into
ear/ejb/ejb-jar.xml/<activation-config-property-value>
or into ear/META-INF/jboss.properties, for both I have to patch the application on
deployment.
An alternative to my suggested <application-properties>
would be a jboss-application.properties in the server config dir with entries like
myMDB_DEV_QUEUE_1.ear.queuename=DEV_QUEUE_1
which should resolve via
<activation-config-property-value>${this:queuename}
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)