You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Mark Brouwer (JIRA)" <ji...@apache.org> on 2007/03/28 09:52:32 UTC
[jira] Created: (RIVER-18) Order of discovery providers not
maintained
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/%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.
[jira] Closed: (RIVER-18) Order of discovery providers not
maintained
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer closed RIVER-18.
-----------------------------
Resolution: Fixed
Fixed, reviewed by Vinod.
> 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
>
>
> 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.
[jira] Updated: (RIVER-18) Order of discovery providers not
maintained
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-18:
------------------------------
Component/s: other
Affects Version/s: jtsk_2.1
> 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
>
> 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.
[jira] Resolved: (RIVER-18) Order of discovery providers not
maintained
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (RIVER-18) Order of discovery providers not
maintained
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-18:
------------------------------
Fix Version/s: AR2
> 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
>
>
> 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.
[jira] Updated: (RIVER-18) Order of discovery providers not
maintained
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-18:
------------------------------
Attachment: RIVER-18.patch
> 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.
[jira] Work started: (RIVER-18) Order of discovery providers not
maintained
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ 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/%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.
[jira] Reopened: (RIVER-18) Order of discovery providers not
maintained
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer reopened RIVER-18:
-------------------------------
Forgot to include the change for {{com.sun.jini.resource.Service}} that maintains the order of the defined service providers and that brings it on par with the Java SE 6 {{java.util.ServiceLoader}}.
> 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
>
>
> 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.
[jira] Closed: (RIVER-18) Order of discovery providers not
maintained
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer closed RIVER-18.
-----------------------------
> 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.