[weld-issues] [JBoss JIRA] (WELD-734) Support @EJB injection in pre-Java EE 6 environments

[Ales Justin (JIRA)]

    [ https://issues.jboss.org/browse/WELD-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671867#comment-12671867 ] 

Ales Justin commented on WELD-734:
----------------------------------

Is this still relevant with JEE6 WebProfile?
e.g. I'd just say "take AS7 with WebProfile" if you need this


                
> Support @EJB injection in pre-Java EE 6 environments
> ----------------------------------------------------
>
>                 Key: WELD-734
>                 URL: https://issues.jboss.org/browse/WELD-734
>             Project: Weld
>          Issue Type: Feature Request
>          Components: Servlet Container Support
>    Affects Versions: 1.1.0.Beta1
>            Reporter: Dan Allen
>            Priority: Minor
>             Fix For: TBC
>
>
> Add support for the injection of EJBs into CDI beans (via the @EJB annotation) in Weld Servlet for use in pre-Java EE 6 environments. This feature would enable more developers to immeidately switch to CDI despite having to use an older platform.
> The best strategy to take to implement this feature would be to leverage Weld's EjbServices SPI interface (http://docs.jboss.org/weld/reference/latest/en-US/html/ri-spi.html) on a per container basis (in the same way Weld is integrated into the Java EE 6 containers).
> Currently, the Weld Listener doesn't provide any hooks to register services before it starts the container. We could redesign the Listener to support providing the EjbServices implementation (and perhaps other service implementations) in a listener subclass.
> It's unlikely we can fully implement EJB integration in pre EE6 environments as (at least in JBoss AS and GlassFish) as some of the hooks (specifically the hooks to remove EJBs on demand) are missing. However, basic injection would cover ~80% of the cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira