[hibernate-dev] Fwd: ServiceLoader and @ProviderFor

[Hardy Ferentschik]

Accidentally only replied to Steve

> On Fri 05 Oct 2012 03:14:57 PM CDT, Hardy Ferentschik wrote:
>> No strong opinion to be honest. I have not had any problems with managing the service files and since refactoring in Idea consider text files as well it is not such a big issues IMO. Using any annotation processor always adds also a bit of pixie dust. Someone new to the source/ build needs to put several pieces together to understand how things fit together.
>> 
>> On the other hand, we have already several APs in the build what does one more matter ;-) If others things it makes there live easier ...
>> 
>> --hardy
>> 
>> 
>> 
>> On 5 Oct 2012, at 21:23, Steve Ebersole <steve at hibernate.org> wrote:
>> 
>>> https://code.google.com/p/spi/
>>> 
>>> ^^ defines an annotation and processor for helping with services in the
>>> JDK ServiceLoader sense.
>>> 
>>> For example, if you wanted to implement Integrator:
>>> 
>>> @ProviderFor(Integrator.class)
>>> public void class MyIntegrator implements Integrator {
>>>     ...
>>> }
>>> 
>>> The AP then:
>>> 1) validates your defined services (not really sure what this means
>>> behind making sure you define a no-arg ctor).
>>> 2) manages your
>>> META-INF/services/org.hibernate.integrator.spi.Integrator file for you
>>> 
>>> Just wanted to see what y'all thought of including this for building.
>>> It is not a runtime dependency at all!  More I am just wondering if
>>> y'all thought this made it easier/better to manage the META-INF/services
>>> provider file.
>>> 
>>> 
>>> --
>>> steve at hibernate.org
>>> http://hibernate.org
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> 
> --
> steve at hibernate.org
> http://hibernate.org