You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2016/02/17 13:13:18 UTC
[jira] [Resolved] (QPID-7068) Drive
AbstractConfiguredObject#validationChange from reflection rather than
attribute metadata
[ https://issues.apache.org/jira/browse/QPID-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy resolved QPID-7068.
------------------------------
Resolution: Fixed
The fix was back-ported into 6.0.x branch and committed under revision [https://svn.apache.org/r1730697]
> Drive AbstractConfiguredObject#validationChange from reflection rather than attribute metadata
> ----------------------------------------------------------------------------------------------
>
> Key: QPID-7068
> URL: https://issues.apache.org/jira/browse/QPID-7068
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-6.0.1, qpid-java-6.1
>
>
> A defect came to light where a {{org.apache.qpid.server.model.AbstractConfiguredObject#validateChange}} failed internally with an UnsupportedMethodException from AbstractConfiguredObject.java:2902.
> The particular problem was caused by the overriding of {{ACO#getName}} in an implementation's interface. This was hiding the attribute's annotation and prevented AttributeGettingHandler from locating the validation proxy method.
> This highlighted the need to change AttributeGettingHandler to drive the validation using reflected metadata, rather the the attribute metadata.
--
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