On 27 Jan 2009, at 07:43, Andrew Lee Rubinger wrote:
Pete Muir wrote:
> 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
My example had no lookup code; all was injected/installed via MC ;)
For instance, I'd been expecting JBossEjbResolver to itself be an MC
bean, where the EjbReferenceResolver would be an injected instance
Like I do in ejb3-mc-int:
...declares the EjbReferenceResolver impl:
...injects the EjbReferenceResolver into something that uses it.
<parameter><inject bean="org.jboss.ejb3.EjbReferenceResolver" /
This is probably a good idea...
I bring this up as a general point as I'd been looking things
If you can get JBossEjbResolver from MC injected into
ServletJBossEjbResolver, then you can avoid lookups altogether.
I don't think so, but this would depend on Ales as he wrote the bridge
>> a class would be enough - as long as there is only one matching
> 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:
>>> (controller).resolveEjb(topLevelDeploymentUnit, new
>>> EjbReference(beanName, beanInterface, mappedName))
>>> ...instead of injecting the reference resolver?
>>> 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.
>> webbeans-dev mailing list
Andrew Lee Rubinger
Sr. Software Engineer
JBoss, a division of Red Hat, Inc.
webbeans-dev mailing list