river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Brouwer (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (RIVER-18) Order of discovery providers not maintained
Date Sun, 10 Feb 2008 12:19:08 GMT

     [ https://issues.apache.org/jira/browse/RIVER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Brouwer resolved RIVER-18.
-------------------------------

    Resolution: Fixed

This time all code related to this fix should be in.

> Order of discovery providers not maintained
> -------------------------------------------
>
>                 Key: RIVER-18
>                 URL: https://issues.apache.org/jira/browse/RIVER-18
>             Project: River
>          Issue Type: Bug
>          Components: other
>    Affects Versions: jtsk_2.1
>            Reporter: Mark Brouwer
>            Assignee: Mark Brouwer
>             Fix For: AR2
>
>         Attachments: RIVER-18.patch
>
>
> 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/%3c4608D561.407@cheiron.org%3e]
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.


Mime
View raw message