ServiceLoader.load* take 2

[David M. Lloyd]

On 06/12/2012 04:16 PM, Jesse Glick wrote:
> On 06/12/2012 05:01 PM, David M. Lloyd wrote:
>> It seems like a specific behavior is the goal, but what is the purpose
>> of the behavior?
>
> That the customary invocation of ServiceLoader load service provider
> classes from all eligible modules in the current configuration, whether
> or not the caller's module and/or the "main module" happen to have a
> direct or indirect dependency on that provider module.

What defines "eligible"?  Is there an expectation that a configuration 
will exist per-application, so that applications do not tend to have 
overlapping modules?  Does this mean that the opinion of Oracle is that 
service implementations should generally be global per installation?

-- 
- DML