[webbeans-dev] Injection over Lookup

[Pete Muir]

On 24 Jan 2009, at 09:07, Ales Justin wrote:

> Injecting it how?
>
> Currently the entry point is ServletContext,
> which holds MC's Kernel and DeploymentUnit as its attribute.
>
> The WB pieces that reside in WB app are not (yet) 'connected' to MC  
> directly.
> Only the custom WB deployers are.
> See wb-int/jbossas/ and its vdf package for more details.
>
> WRT to autowiring, I agree, there is no need to do lookup by name,

I was just following ALR's example when I did this :-p

> a class would be enough - as long as there is only one matching  
> instance.

I don't know the class names to use, tell me, or make the change :-)

>
>
> Andrew Lee Rubinger wrote:
>> Hey guys:
>> Is there a reason we're doing stuff like:
>> JBossEjb 
>> .lookupEjbReferenceResolver 
>> (controller).resolveEjb(topLevelDeploymentUnit, new  
>> EjbReference(beanName, beanInterface, mappedName))
>> ...instead of injecting the reference resolver?
>> http://anonsvn.jboss.org/repos/jbossas/projects/webbeans-ri-int/trunk/ejb/src/main/java/org/jboss/webbeans/integration/ejb/JBossEjbResolver.java 
>>  There are a few other examples where this type of lookup is used.   
>> Given only one implementing class per interface, you can even rely  
>> upon MC to do the autowiring.
>> S,
>> ALR
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev