[
https://jira.jboss.org/jira/browse/WBRI-329?page=com.atlassian.jira.plugi...
]
Ken Saks commented on WBRI-329:
-------------------------------
I'm still confused then. If the ejb container is delegating injection to web beans,
and web beans only processes fields that have annotations, then who would know to inject
bar2? I'm not so sure that having N different resolveXXX(InjectionPoint) calls in
the SPI is the best way to go. Why don't we just have a
"doEEstyleInjection(instance, <possibly-some-other-context>)" call that
WebBeans can use to ask the EE container to do all the EE style injection on an instance?
That will remove the need for a toggle, solve the ee-injection-defined-via-.xml case, and
simplify the SPI. The WebBeans code will no longer have to iterate over every EE-style
field/method, map it to a particular XXXService, and ask the individual service to resolve
it.
Move EJB injection to InjectionTarget
-------------------------------------
Key: WBRI-329
URL:
https://jira.jboss.org/jira/browse/WBRI-329
Project: Web Beans
Issue Type: Bug
Components: Enterprise Beans, Glassfish integration
Environment: 1.0.0.PREVIEW2.SP2 in 7/30/09 GlassFish V3 workspace
Reporter: Ken Saks
Fix For: 1.0.0.CR1
Currently we perform 299 style injection into EJBs via an interceptor, I would prefer to
move this to use the InjectionTarget SPI.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira