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 2017/02/01 09:27:51 UTC
[jira] [Resolved] (QPID-7601) [Java Broker] Allow annotations to
define ManagedAttributeValueTypes as abstract, some methods as derived
[ https://issues.apache.org/jira/browse/QPID-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy resolved QPID-7601.
------------------------------
Resolution: Fixed
> [Java Broker] Allow annotations to define ManagedAttributeValueTypes as abstract, some methods as derived
> ---------------------------------------------------------------------------------------------------------
>
> Key: QPID-7601
> URL: https://issues.apache.org/jira/browse/QPID-7601
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: qpid-java-7.0
>
>
> ManagedAttributeValueTypes may form a type hierarchy, however there is no way for a value to be resolved to a particular instance class.
> A type can be marked as abstract meaning that it cannot itself be instantiated from an input value (i.e. it cannot be used as a managed attribute, or the input to an operation). An abstract type can be used as an output value (e.g. as a return value from an operation, or as a derived attribute).
> Further we should allow ManagedAttributeTypes to themselves have derived attributes. These attributes should be returned from query methods, but not persisted, and values for these attributes should be ignored when present in input data.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org