1 Reply Latest reply on Oct 22, 2005 3:34 PM by spaquet

    2 Problems with AS4.0.3 und EJB3

    java.jago

      Hi, (I installed AS 4.0.3 with EJB3 support using the jar-installer)

      1. I have a problem with the IDETail of the Trailblazer demo. In the source-file there is a Annotation @Inject - but for me this Annotation doesn't exist - perhaps they changed the name ???

      2. EJB3-Error: When I deploy the EJB3Tail.ear it results in a lot of errors...strange, one should think that incompatibilities don't appear that fast...
      What is going on there ???

      Error Message: In the AS console...

      02:05:35,125 INFO [ProxyDeployer] no declared remote bindings for : trail.entit
      y.query.CalculatorBean
      02:05:35,140 INFO [ProxyDeployer] no declared remote bindings for : trail.entit
      y.update.CalculatorBean
      02:05:35,265 WARN [MDB] Could not find the queue destination-jndi-name=queue/in
      jection
      02:05:35,265 WARN [MDB] destination not found: queue/injection reason: javax.na
      ming.NameNotFoundException: injection not bound
      02:05:35,265 WARN [MDB] creating a new temporary destination: queue/injection
      02:05:35,281 INFO [injection] Bound to JNDI name: queue/injection
      02:05:35,281 INFO [MDB] JNDI Hashtable: null
      02:05:35,375 WARN [ServiceController] Problem starting service jboss.j2ee:servi
      ce=EJB3,name=trail.injection.RecordManagerBean
      javax.naming.NameNotFoundException: queue not bound
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:514)
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:522)
      at org.jnp.server.NamingServer.getObject(NamingServer.java:528)
      at org.jnp.server.NamingServer.lookup(NamingServer.java:281)
      at org.jnp.server.NamingServer.lookup(NamingServer.java:255)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
      at javax.naming.InitialContext.lookup(InitialContext.java:351)
      at org.jboss.ejb3.injection.ResourceHandler.loadFieldInjectors(ResourceH
      andler.java:182)
      at org.jboss.ejb3.injection.ResourceHandler.loadInjectors(ResourceHandle
      r.java:125)
      at org.jboss.ejb3.EJBContainer.resolveInjectors(EJBContainer.java:394)
      at org.jboss.ejb3.EJBContainer.initializePool(EJBContainer.java:330)
      at org.jboss.ejb3.EJBContainer.start(EJBContainer.java:283)
      at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:48)
      at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.
      java:63)
      at org.jboss.ejb3.stateless.StatelessManager.startService(StatelessManag
      er.java:93)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
      upport.java:274)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
      eanSupport.java:230)
      at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
      sorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch

        • 1. Re: 2 Problems with AS4.0.3 und EJB3
          spaquet

          Forget the @Inject it is depredated.
          There is a post relative to that point in this Forum.

          For the second point I'm facing the same issues and it does not seem to be trivial. Just wait another release (meanwhile extract the web part from the source and just load it. you will not access the live examples, but will have the doc part).