[
https://issues.apache.org/jira/browse/QPID-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177570#comment-14177570
]
ASF subversion and git services commented on QPID-6168:
-------------------------------------------------------
Commit 1633244 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1633244 ]
QPID-6168: [Java Broker] Move valid value check into the create/change
validation logic
* avoid the possibility that a failing many attribute update leaves an object
part updated.
> On create or change, validate an object's attributes against its valid values
> -----------------------------------------------------------------------------
>
> Key: QPID-6168
> URL: https://issues.apache.org/jira/browse/QPID-6168
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: 0.31
>
>
> In the Java Broker's model, attributes can be annotated with valid values.
> These are a set of possible values which it is legal for the attribute to be.
> This metadata is already exposed to clients (like the Web Mangement UI) in
> order to allow them to auto-populate drop downs (etc) with legal values
> without needless duplication of logic on the client side.
> Currently, the CO tier on the Broker side does not enforce that the
> attributes have a value from the valid value set. We have some per instance
> style validation that could be replaced with common code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
