You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "Marcel Offermans (Commented) (JIRA)" <ji...@apache.org> on 2012/03/15 08:09:43 UTC

[jira] [Commented] (ACE-223) Undefined order of UIExtensionFactories

    [ https://issues.apache.org/jira/browse/ACE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229946#comment-13229946 ] 

Marcel Offermans commented on ACE-223:
--------------------------------------

Whilst I agree that having a well defined order is a lot better than having no order (which turned out to be a pretty random order) I am not convinced we should use the service ranking for that, so in the end I would like to have some more sophisticated system. However, compared to the current situation I think this is an improvement, so I'm applying the patch.
                
> Undefined order of UIExtensionFactories 
> ----------------------------------------
>
>                 Key: ACE-223
>                 URL: https://issues.apache.org/jira/browse/ACE-223
>             Project: ACE
>          Issue Type: Bug
>          Components: Web UI
>    Affects Versions: 0.8.0
>            Reporter: J.W. Janssen
>         Attachments: ACE-223-service_ranking.patch
>
>
> You can register multiple UIExtensionFactories for a NamedObject's editor. However, their order isn't defined and changes continuously. Needless to say that this is annoying to the end user/administrator.
> We should provide a default ordering (for example on the service.id of registered UIExtensionFactory), but also allow custom ordering to be defined explicitly, for example by adding a service-property.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira