Re: ResourceBundleProvider(s) design

2016-08-08 Thread Mandy Chung
Hi Peter, Sorry for the delay in reply. Still catching up on mails from vacation. > On Aug 4, 2016, at 3:26 AM, Peter Levart wrote: > > > On 08/04/2016 11:21 AM, Peter Levart wrote: >> If the providing module declares the service type, then the consuming module >> will have an explicit depen

Re: ResourceBundleProvider(s) design

2016-08-04 Thread Peter Levart
On 08/04/2016 11:21 AM, Peter Levart wrote: If the providing module declares the service type, then the consuming module will have an explicit dependency on the providing module, which also defeats the purpose of service provider's implicit coupling. I take this back. The service type is reso

ResourceBundleProvider(s) design

2016-08-04 Thread Peter Levart
Hi, I would like to ask about why java.util.spi.ResourceBundleProvider is designed they way it is. I'm questioning the design of the following part of specification: "The provider service type is determined by {@code basename+"Provider"}." Why is that necessary? It requires that provid