[
https://issues.apache.org/jira/browse/QPID-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220013#comment-15220013
]
Rob Godfrey commented on QPID-7176:
-----------------------------------
So there's actually two cases here...
# on creation of the new object where the only context available is the
parent(s) of the object to be created
# updating an existing object where the context is the object itself.
I suppose these two cases could be generalise to a single case of a path to a
configured object which might be a parent or the object itself... but that is
also potentially tricky.
As an aside I think from the examples given in the description
"{{#clientCertRecorder}} should be restricted to the
ManagedPeerCertificateTrustStores that are defined at that moment" you could
actually solve that with a valid values function using the existing
infrastructure (presuming you aren't caching valid values).
> Support valid values that are context sensitive
> -----------------------------------------------
>
> Key: QPID-7176
> URL: https://issues.apache.org/jira/browse/QPID-7176
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
>
> The model already has the ability to publish valid value information for the
> attributes of a category. This information is static.
> We need an analogous mechanism for instances or instances that are about to
> be. For example, when creating or updating a Queue, the choice for
> {{#alternateExchange}} should be restricted to Exchanges belonging to the
> enclosing virtualhost, or when creating or editing a AMQPPort,
> {{#clientCertRecorder}} should be restricted to the
> ManagedPeerCertificateTrustStores that are defined at that moment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
