5:39 p.m.
https://sourceforge.net/apps/mediawiki/hibernate/index.php?title=Category...
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
2:47 a.m.
Nice.
One comment, I think ServiceInitiator.getServiceInitiated() is a little
confusing. Just by then name I thought
it would be the method which initiates the service, but it rather just
gives me the service type/name.
Why not ServiceInitiator.getServiceType?
--Hardy
On Sun, 03 Oct 2010 00:39:59 +0200, Steve Ebersole <steve(a)hibernate.org>
wrote:
6:59 a.m.
I wanted to make it explicit that this is not the initiator's type/role. Its
the role/type of the service being initiated. I do not follow how you infer
"get me the service initiated" to mean a method for doing the initiation.
Given the vocabulary that has sort of grown, I'm ok with saying
getServiceRoleInitiated() if thats "better".
On Monday, October 04, 2010 02:47:40 am Hardy Ferentschik wrote:
Nice.
One comment, I think ServiceInitiator.getServiceInitiated() is a little
confusing. Just by then name I thought
it would be the method which initiates the service, but it rather just
gives me the service type/name.
Why not ServiceInitiator.getServiceType?
--Hardy
On Sun, 03 Oct 2010 00:39:59 +0200, Steve Ebersole <steve(a)hibernate.org>
wrote:
> https://sourceforge.net/apps/mediawiki/hibernate/index.php?title=Category
> :Services
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
8:13 a.m.
On 10/02/2010 06:39 PM, Steve Ebersole wrote:
Isn't there a service-lifecycle-and-dependency-injection library in our
arsenal we can use?
-CB
8:28 a.m.
Not a simple one I am aware of. There is seam/weld/cdi which is more than we
need. And I have been unable to find "real life" microcontainer use guides for
something like this. Bear in mind that my bootstrap class is simply one
choice/option to this. The services at the end of the day are just pojos...
On Monday, October 04, 2010 08:13:09 am Chris Bredesen wrote:
On 10/02/2010 06:39 PM, Steve Ebersole wrote:
> https://sourceforge.net/apps/mediawiki/hibernate/index.php?title=Category
> :Services
Isn't there a service-lifecycle-and-dependency-injection library in our
arsenal we can use?
-CB
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
10:37 a.m.
I remember Mark P. mentioning they (drools) have some basic bootstrap for their core which
is simplistic and then if containers want it can use another DI to set it up for user
visibile customization (i.e. spring, cdi etc.)
Not sure how they did it though - but might be worth a look ?
/max
On Oct 4, 2010, at 15:28, Steve Ebersole wrote:
Not a simple one I am aware of. There is seam/weld/cdi which is more
than we
need. And I have been unable to find "real life" microcontainer use guides for
something like this. Bear in mind that my bootstrap class is simply one
choice/option to this. The services at the end of the day are just pojos...
On Monday, October 04, 2010 08:13:09 am Chris Bredesen wrote:
> On 10/02/2010 06:39 PM, Steve Ebersole wrote:
>> https://sourceforge.net/apps/mediawiki/hibernate/index.php?title=Category
>> :Services
>
> Isn't there a service-lifecycle-and-dependency-injection library in our
> arsenal we can use?
>
> -CB
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
9:59 a.m.
Not commenting on the idea of an Hibernate specific registry, here are a few comments on
the design:
Map should be Map<String, Object> or whatever types will end up being used.
public Class serviceRole() default InjectService.class;
should probably be
public Class<?> serviceRole() default Void.class;
Void.class is kind of a defacto default in the annotation land for Class<?>
@InjectService
Why not JSR-303's @Inject with a qualifier if you really need some additional
metadata?
On 3 oct. 2010, at 00:39, Steve Ebersole wrote:
https://sourceforge.net/apps/mediawiki/hibernate/index.php?title=Category...
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
10:43 a.m.
Ah, I had tried void and voic.class. Did not know about Void.class. Good to
know. I will change that
On Monday, October 04, 2010 09:59:14 am Emmanuel Bernard wrote:
Not commenting on the idea of an Hibernate specific registry, here
are a
few comments on the design:
Map should be Map<String, Object> or whatever types will end up being
used.
public Class serviceRole() default InjectService.class;
should probably be
public Class<?> serviceRole() default Void.class;
Void.class is kind of a defacto default in the annotation land for Class<?>
@InjectService
Why not JSR-303's @Inject with a qualifier if you really need some
additional metadata?
On 3 oct. 2010, at 00:39, Steve Ebersole wrote:
> https://sourceforge.net/apps/mediawiki/hibernate/index.php?title=Category
> :Services
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
7:26 p.m.
On Monday, October 04, 2010 09:59:14 am Emmanuel Bernard wrote:
@InjectService
Why not JSR-303's @Inject with a qualifier if you really need some
additional metadata?
I am not against the idea so much. The problems I had were twofold:
1) Personally I have no idea how to define these "qualifiers" in the way I need
and no one I ask seems to be able to tell me how to either. I need to be able
to say:
(a) that an injection is optional
(b) the service role to inject (the default is the type where @Inject is
applied).
So how can I do that?
2) @Inject, iiuc, can be applied in numerous contexts and is really quite
broad. In my little injector code I don't want to have to support all this.
My main focus is
a) services that are able to be "managed" by other means (spring, jboss-mc,
weld, etc)
b) a dead simple built in manager for managing the services, really this is a
legacy requirement for "property based bootstrapping" like we have before.
Personally I think y'all are getting a little too hung up the on injection of
dependent services here. It is a quite limited scope and the implementation
is both dead simple and already done (its not like this is going to drag on
for years like we have seen elsewhere).
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
6:33 a.m.
Personally I think y'all are getting a little too hung up the on injection of
dependent services here. It is a quite limited scope and the implementation
is both dead simple and already done (its not like this is going to drag on
for years like we have seen elsewhere).
It is not the problem on how complex or simple the service will be; it is about
exposing a dependency injection mechanism to the users of Hibernate that is
different.
That is my only concern, but I also don't have any good solution on how to avoid
it without introducing major complexity or non-wanted 3rd party dependencies.
If we could just somehow limit us to simply have a a service lookup and not have
to add annotation based injections into this.
/max
7:34 p.m.
On Monday, October 04, 2010 09:59:14 am Emmanuel Bernard wrote:
Not commenting on the idea of an Hibernate specific registry
Good because the time for that was almost a year ago when I asked y'all to
review the designs I was working on for 4 :)
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
5194
days inactive
5200
days old
10 comments
5 participants
participants (5)
-
Chris Bredesen -
Emmanuel Bernard -
Hardy Ferentschik -
Max Rydahl Andersen -
Steve Ebersole