Unexpected behaviour when binding to java:comp and @Startup beans

[marius.bogoevici]

So, for Weld-int  we bind a BeanManager to java:comp/BeanManager. In order to make it accessible to EJBs, the binding procedure works like this:

1) Obtain the JavaEEComponent which corresponds to the EJBs DU

2) From the JavaEEComponent, obtain the Context (which represents java:comp for said component)

3) Bind the BeanManager

As a bit of background, one of the interceptors that are applied to CDI-enabled EJBs is injected with a @Resource("java:comp/BeanManager")

This works fine, as long as the EJB is not a @Startup  bean. For the latter, the lookup that is performed during EJBContainer.startup() seems to miss the JavaEEComponent (debugging ComponentObjectFactory shows that CurrentComponent.get() returns null and thus JavaEEComponent is ignored - so that the BeanManager that is bound to JavaEEComponent's context is not found).

So, I'm looking forward to some clarifications concerning this - mainly to discuss what's the best way to move forward:

a) open a JIRA, fix the issue, or

b) use the SwitchBoard

Thanks,

Marius

Message was edited by: Marius Bogoevici, typo in title

[jaikiran]

This should have worked, because when EJBContainer.start() is invoked, it's expected that the java:comp is setup correctly. Let me see what's wrong.

(If you have app which can reproduce this, please mail it to me or attach it here. That will help )

[marius.bogoevici]

Yes, that's what puzzles me.

I'll try to think of a way to reproduce the issue per se - the problem becomes obvious with the Weld JNDI Binding.

Meanwhile, here is a very simple example which does not quite reproduce the issue, but helps explaining what I mean.

while postconstructing the ejb, we're looking for java:comp - now if you're looking at ComponentObjectFactory, you can see that CurrentComponent.get() returns null, so the application is using the legacy branch. A "java:comp" is found during lookup, but for some reason, it does not seem to be the same as the one accessed via JavaEEComponent.getContext().

So, thanks Jaikiran for looking into this, and please let me know what you think.

[jaikiran]

I think, I figured out what's wrong. I have a small patch in EJB3 code which you can test. But I want to make sure that I create this patch against the correct base. So where are you testing this currently? Against AS 6.0.0.M3 or latest AS trunk?

[pmuir]

We're testing against AS trunk.