[
https://issues.apache.org/jira/browse/RIVER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on RIVER-18 started by Mark Brouwer.
> Order of discovery providers not maintained
> -------------------------------------------
>
> Key: RIVER-18
> URL: https://issues.apache.org/jira/browse/RIVER-18
> Project: River
> Issue Type: Bug
> Reporter: Mark Brouwer
> Assigned To: Mark Brouwer
>
> The order in which the discovery providers are obtained and utilized by
> {{com.sun.jini.discovery.DiscoveryV2}} is arbitrary, while the order in which
> they are 'defined' should be maintained. See this
> [posting|http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200703.mbox/[EMAIL
> PROTECTED] for the problems that can arise from an arbitrary order, also
> changing the semantics for {{com.sun.jini.resource.Service}} to the order in
> which they are defined would bring it on par with {{java.util.ServiceLoader}}
> introduced in Java SE 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
