[
https://issues.apache.org/jira/browse/ACE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218374#comment-13218374
]
J.W. Janssen commented on ACE-223:
----------------------------------
Using the service ranking for that would work as well, I agree.
The service.id would be something of a last resort to get a predictable order
during the lifetime of the container, when nothing is specified for the service
ranking (or any other used service property).
> 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
>
> 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
