@EJB not working for managed beans in adfc-config

Question

using adf 11.1.1.3
We have an application that uses EJB (deployed on the same WLS as our application). We notice that when we create managed beans in the adfc-config and use the @EJB annotation to get an instance of the sessionbean, it is not working.
The error we get is a simple nullPointerexception pointing to the EJB.
When we register the bean in faces-config.xml instead of adfc-config.xml, we do get an instance of the EJB.
I also get a nullpointerException when i add the managed bean to a taskflow instead of the adfc-config.
This is an example of the bean:
public class HomeTest {
    @EJB
    MyService service;
    public HomeTest() {
    public List getData(){
      return service.getSomedata();
}When i register this bean in adfc-config i get a nullpointer on service.
When i register the same bean in the faces-config, it is working.

Answer 1

Frank,
Thanks! I think i managed to implement the workaround:
This is my bean that has been registered in the faces-config:
public class BeanHelper {
    @EJB
    private MyEJB myEjB;
    public BeanHelper() {
        super();
    public MyEJB getMyEJB()
          return myEJB;
}In my adfc managed bean i use
MyEJB myEJB = (MyEJB)JSFUtils.get("#{BeanHelper.myEJB}");This is working fine.
This way i no longer need to use a direct lookup and i don't need to know the exact path and so on for the EJB.
Thanks Frank!
Is there a way to let Oracle update the bug with this workaround so if other people find the bug, they know how to implement a workaround?