[cdi-dev] Summarize finding a BeanManager (for Java SE, integration with older Java EE and unit testing)

[Peter Muir]

Hi Rick,

We're all new to this group, the only person who has spent much time on CDI 1.1 so far is me, as I collated issues from CDI 1.0. Comments inline.

On 26 Apr 2011, at 00:24, Rick Hightower wrote:

> I am new to the group. Where is the source code for CDI 1.1?

The "source code" for CDI is the specification, which is in docbook format, and available at https://github.com/pmuir/cdi - this is the 1.0 spec with a few updates that Gavin had put in a while back. One task I still need to do is diff this spec to the 1.0 spec and see what issues he already addressed. At some point we may include a reference API (based on the one Weld distributed for 1.0) but I'm not sure yet.

> I can branch it, add this and solicit feedback.

Please do :-)

From previous experience I would suggest putting up a complete proposal on the JIRA issue for this, which walks through any algorithms, APIs and edge cases. This can then be discussed by the EG. I suggest doing this before diving in and editing the spec, as making spec document changes can be a large task if you don't know it well (as your change can impact on many sections!).

Eventually, I would suggest making changes, and then creating a github pull request where we can use the github code review features to comb through it.

> I think working code is much easier to talk about than bullet points.

I'm afraid most of the work here will be bullet points, very little (ok no) working code ;-)

> 
> 
> 
> On Mon, Apr 25, 2011 at 4:07 PM, Rick Hightower <richardhightower at gmail.com> wrote:
> We need a general purpose way of finding a BeanManager.
> +1 for me.
> 
> This way should include JNDI lookup to a fallback BeanManagerLocator that uses a ServiceLoader
> +1 for me.
> 
> I think the behavior should look like this:
> 
> Lookup BeanManager in JNDI
> If not found, try to load BeanManagerLocator from system property.
> If not found, try to load BeanManagerLocator from ServiceLoader.
> If more than one BeanManagerLocator found, sort by priority or die if there is more than one. (not sure about the sort, I think it should die, but can be convinced otherwise).
> Once the BeanManagerLocator is found, use it to return a BeanManager
> 
> In addition,
> 
> I think we need a simplified interface for BeanManager. 
> 
> https://github.com/CDISource/cdisource/blob/master/beancontainer/api/src/main/java/org/cdisource/beancontainer/BeanContainer.java
> 
> This could just be a utility class, but it should be included with CDI 1.1. I think the  BeanManager interface is too low level.
> 
> 
> 
> -- 
> Rick Hightower
> (415) 968-9037 
> Profile 
> 
> 
> 
> 
> -- 
> Rick Hightower
> (415) 968-9037 
> Profile 
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20110426/637523bf/attachment.html