Startup classes cannot lookup Session Beans

[dgriffin]

I am moving from JBoss 4.0.5 / Seam 1.2.1  to 5.0.0.CR1 / Seam 2.0.3.CR1

I have made this unexpected discovery:

Lookup of session beans fails in Seam components annotated with @Startup in the @Create or @PostConstruct method.  This worked fine in the older versions I mentioned above. 

Can anyone confirm my findings?  Maybe I am overlooking something required in these new versions.

I want to do some application initialization.  I use @Startup with an @Create method.  This was working great unit I went to the new versions.

[dgriffin]

I did some things to move these lookups outside of @Startup components.   Lookup still fail.

I see the exact jndi name I am trying to lookup in the log file when the SLSB was installed.  Makes no sense.  I see it but the top level lookup key is reported as not bound.

As in lookup(ec20/b/c)   returns javax.naming.NameNotFoundException: ec20 not bound

ideas?

[pmuir]

Please post code and a full stack trace.

[alrubinger]

Please confirm in JNDIView that the SLSB is getting placed at ec20/b/c, like the logs report?

Wiki for Displaying JNDIView

S,
ALR

[dgriffin]

I have since determined this is not a Seam issue.  It seems to be a 5.0.0RC1 issue.  I moved the startup code into a servlet configured with load-on-startup and the problem still occurs.  It looks like the app server is executing startup methods that need to use EJBs before the EJBs are bound in jndi. This is now posted in the JBoss EJB3 forum. 

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165901#4165901