Re: Services and Bindings - expected usage scenarios

2016-11-30 Thread Jochen Theodorou
On 30.11.2016 17:31, mark.reinh...@oracle.com wrote: [...] The SE Platform has ServiceLoader rather than a built-in DI mechanism because the former is more primitive and imposes less overhead, while the latter can be built on top of the former. (I don't really know, nor care, whether

Re: Services and Bindings - expected usage scenarios

2016-11-30 Thread mark . reinhold
2016/11/29 9:30:29 -0800, vitaliy.pisa...@hpe.com: > Thank you mark, this goes far to answer my question. > > I do want to ask you 3 follow-up questions: > > ... > > By promoting the SL pattern, aren’t you effectively taking a stand in > this debate? An SL proponent might say: "Look! The Java

RE: Services and Bindings - expected usage scenarios

2016-11-29 Thread Pisarev, Vitaliy
nvoyé: Mardi 29 Novembre 2016 18:30:29 > Objet: RE: Services and Bindings - expected usage scenarios > Thank you mark, this goes far to answer my question. > > I do want to ask you 3 follow-up questions: > > You mentioned that an Application that does not use DI (rare sight >

Re: Services and Bindings - expected usage scenarios

2016-11-29 Thread mark . reinhold
2016/11/29 6:54:35 -0800, vitaliy.pisa...@hpe.com: > ... > > I am looking at the great features in Java 9 and I know that we are > going to "jump" on the new module system with all the encapsulation it > gives us. But I and my fellow Architects are very unsure what to > think of the

Re: Services and Bindings - expected usage scenarios

2016-11-29 Thread Remi Forax
nternally. regards, Rémi - Mail original - > De: "Vitaliy Pisarev" <vitaliy.pisa...@hpe.com> > À: jigsaw-dev@openjdk.java.net > Envoyé: Mardi 29 Novembre 2016 12:35:54 > Objet: Services and Bindings - expected usage scenarios > Another best practices question

RE: Services and Bindings - expected usage scenarios

2016-11-29 Thread Pisarev, Vitaliy
נובמבר 2016 15:24 To: Pisarev, Vitaliy <vitaliy.pisa...@hpe.com>; jigsaw-dev@openjdk.java.net Subject: Re: Services and Bindings - expected usage scenarios On 29/11/2016 13:13, Pisarev, Vitaliy wrote: > What about the intent behind how are developers supposed to use this tool? > > For ex

Re: Services and Bindings - expected usage scenarios

2016-11-29 Thread Jochen Theodorou
isa...@hpe.com>; jigsaw-dev@openjdk.java.net Subject: Re: Services and Bindings - expected usage scenarios On 29/11/2016 11:35, Pisarev, Vitaliy wrote: Another best practices question. I am aware that the ServiceLoader API is not new to Java. What's new in Java 9 is that is has been put forward to the

Re: Services and Bindings - expected usage scenarios

2016-11-29 Thread Alan Bateman
On 29/11/2016 13:13, Pisarev, Vitaliy wrote: What about the intent behind how are developers supposed to use this tool? For example, when Optional was introduced in Java 8, it was specified that it is intended to be used as a methods return type. And people should not use it as class member

RE: Services and Bindings - expected usage scenarios

2016-11-29 Thread Pisarev, Vitaliy
to this). -Original Message- From: Alan Bateman [mailto:alan.bate...@oracle.com] Sent: יום ג 29 נובמבר 2016 14:06 To: Pisarev, Vitaliy <vitaliy.pisa...@hpe.com>; jigsaw-dev@openjdk.java.net Subject: Re: Services and Bindings - expected usage scenarios On 29/11/2016 11:35, Pisarev, Vitaliy

Re: Services and Bindings - expected usage scenarios

2016-11-29 Thread Alan Bateman
On 29/11/2016 11:35, Pisarev, Vitaliy wrote: Another best practices question. I am aware that the ServiceLoader API is not new to Java. What's new in Java 9 is that is has been put forward to the front of the stage and it is now very easy for a service provider to register a service. The

Services and Bindings - expected usage scenarios

2016-11-29 Thread Pisarev, Vitaliy
Another best practices question. I am aware that the ServiceLoader API is not new to Java. What's new in Java 9 is that is has been put forward to the front of the stage and it is now very easy for a service provider to register a service. The thing is that up until now, the ServiceLoader was