You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2015/06/17 15:07:00 UTC
[jira] [Updated] (QPID-6595) Allow ConfiguredObject context
variables to be resolved in terms of their ancestor's attributes
[ https://issues.apache.org/jira/browse/QPID-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-6595:
-----------------------------
Summary: Allow ConfiguredObject context variables to be resolved in terms of their ancestor's attributes (was: Allow ConfiguredObject defaults to be resolved in terms of their ancestor's attributes)
> Allow ConfiguredObject context variables to be resolved in terms of their ancestor's attributes
> -----------------------------------------------------------------------------------------------
>
> Key: QPID-6595
> URL: https://issues.apache.org/jira/browse/QPID-6595
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: 6.0 [Java]
>
>
> We currently have the ability to express a context variable using a notation ${this:attributeName} which when resolved for a particular object, results in an expansion based on the Configured Object's attributes.
> We want to extend this mechanism so that the expansion is performed using an ancestor of the object. The syntax will be ${ancestor:<categoryname>:attributeName} when category name corresponds to a name of the category within the model.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org