Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltaspike-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gudnabrsam@gmail.com
 designates 209.85.160.47 as permitted sender)
MIME-Version: 1.0
Reply-To: gudnabrsam@gmail.com
In-Reply-To: <E9E45BF0-0D87-4A97-82DB-959B0BB96DA7@code-house.org>
References: <E9E45BF0-0D87-4A97-82DB-959B0BB96DA7@code-house.org>
Date: Tue, 10 Apr 2012 10:05:58 -0500
Message-ID: 
 <CAE9L6G1Zrm8iDNi6Ac-ju=ERX7HO8cZ9E5v4Wt4zxgmtKpAx8Q@mail.gmail.com>
Subject: Re: DELTASPIKE-151 Provide lookup method with Map result
From: Matt Benson <gudnabrsam@gmail.com>
To: deltaspike-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>From my perspective in the peanut gallery, it would seem that
providing mechanisms for not-necessarily-CDI-aware libraries to bridge
to CDI is as much a part of deltaspike's declared scope as e.g.
providing a Spring bridge.

$0.02,
Matt

2012/4/10 =C5=81ukasz Dywicki <luke@code-house.org>:
> Hi all,
> I would like to start discussion as sugested by Gerhard in his comment fo=
r my issue.
>
> I created an issue to include a new method in BeanProvider class. Purpose=
 of method is to find all named references and return them in Map where key=
 is name and value is bean instance. Just to give short introduction to Cam=
el - it is mediation library which allows to create complex integration log=
ic with various DSL variants. With Camel you can do transformations, evalua=
te different kind of expressions and so on. I think it is also worth to not=
e that Camel supports multiple Dependency Injection containers - starting f=
rom Spring and Guice up to Blueprint (OSGi specific). My goal is to provide=
 same level of support for CDI as Camel have for Spring. For example Camel =
allows to inject Interceptors, error handlers and so on. To find these elem=
ents Camel scans beans registry (which is customizable through SPI) for all=
 named references and use them.
>
> Most of you can identify the issue and path as Camel specific but I beliv=
e it is not. This method can be requested by any other project. We just sta=
rted to integrate our component with deltaspike before others. From proposa=
l I know that your goal is to create "industry standard" set of extensions =
for CDI. Previous version of camel-cdi had own BeanManagerProvider, BeanPro=
vider classes, own AnyLiteral class and so on. I've found similar classes i=
n your codebase so I wanted to use code written by you to simply avoid dupl=
ication between various Apache repos. Only one part which was missing in De=
ltaspike is named lookup result, which is not big deal to write and maintai=
n. There is no external dependencies necessary to implement this method and=
 it can be implemented on top of current BeanProvider API.
>
> I think that cooperation with other projects can bring lots of benefits f=
or deltaspike community with no cost from your side.
>
> Best regards,
> Lukasz