[
https://issues.apache.org/jira/browse/QPID-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226741#comment-14226741
]
Rob Godfrey commented on QPID-6246:
-----------------------------------
The purpose of @ManagedAnnotation is to denote semantically defined aspects of
a configured object type (aspects which might apply across more than one type
or even category). As such it doesn't make sense for these to be applied to
Java classes (rather than interfaces) nor should the annotation be inherited
(just because a given interface is semantically meaningful to management
tooling, doesn't mean that all interfaces that extend it should automatically
also be interesting to tooling).
I've made changes to this effect, also added a processor to validate that the
annotation is only applied to interfaces which extend ManagedInterface. I've
also changed around ConfiguredTypeRegistry a bit to make the processing of
ManagedInterfaces work more like the other properties of a configured object.
> Refactor authentication provider UIs to uses dedicated dialogues
> ----------------------------------------------------------------
>
> Key: QPID-6246
> URL: https://issues.apache.org/jira/browse/QPID-6246
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.30
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Fix For: 0.31
>
> Attachments:
> 0001-QPID-6246-WIP-change-authentication-provider-UI.patch
>
>
> Refactor all authentication provider UIs to have independent,
> provider-specific UIs. This will allow the UI experience to improved and will
> facilitate the introduction of field level help etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
