5 Replies Latest reply on Feb 14, 2006 2:29 AM by newlukai

    Problem since update to Seam 1.0 beta2 and JBoss 4.0.4 RC1

      Hi,

      my intention updating to the latest releases of Seam and JBoss AS was the need of @Factory. To use this annotation I had to upgrade. Since I updated both of them I don't get my app working again. Hopefully anybody has any idea.

      I have several stateless beans, some entitiy beans and, for now, one stateful bean. My ear file deploys without errors. But as soon as I point my browser to the app, I get this stacktrace:

      Caused by: javax.naming.NameNotFoundException: ReleaseSelection not bound
       at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
       at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
       at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
       at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
       at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
       at javax.naming.InitialContext.lookup(InitialContext.java:351)
       at org.jboss.seam.Component.instantiate(Component.java:651)


      This error causes a 'Could not instantiate Seam component' message.
      ReleaseSelection is a stateless bean. In the jmx-console I see that this bean is registered (StateString), and the name is 'ReleaseSelection'.
      I thought, that I made a mistake configuring the jndiPattern. But it's configured the same way as proposed in the examples myProg/#{ejbName}/local, where myProg is the ear file name without its suffix.

      Has anybody any hint or idea where to look for an error?

      Regards,
      Newlukai