GK >>The responsibility for associating the new object with the Context
GK>>should be in Bean.create() instead of in Context.get().

I think how to implement Bean and Context contract of the spec. is left to the implementations. This may not be required by the spec itself.

Gurkan
From: Gavin King <gavin@hibernate.org>
To: Scott Ferguson <ferg@caucho.com>
Cc: Michael Keith <michael.keith@oracle.com>; WebBeans <webbeans-dev@lists.jboss.org>; Java Community Process JSR #299 Expert List <JSR-299-EG@jcp.org>
Sent: Friday, January 2, 2009 6:42:39 AM
Subject: Re: [webbeans-dev] Re: Bean.getInjectionPoints()

On Fri, Jan 2, 2009 at 3:29 PM, Gavin King <gavin@hibernate.org> wrote:

> But what you're really saying is that it's better to handle circular
> references from Bean.create() than from Manager.getInstance().

I expressed myself badly here. What I mean is:

The responsibility for associating the new object with the Context
should be in Bean.create() instead of in Context.get().

This is not quite as simple as it sounds because it means adding a
Context.put() operation, with hard-to-define semantics, and some way
of ensuring that instances for which injection is not yet complete are
not visible to other threads executing in the same context.

Actually I think there is a better way to solve the problem, but I
need to talk it over with Pete.

--
Gavin King
gavin.king@gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
_______________________________________________
webbeans-dev mailing list
webbeans-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev