Thanks, this got me through the deployment. Unfortunately, it just fails at
runtime with the following:
00:18:28,884 ERROR [STDERR] javax.naming.NamingException: Could not dereference
object [Root exception is javax.naming.NameNotFoundException:
ReplenishmentProcessorBean not bound]
I have
Did you try
| @EJB(mappedName=services.ejb.ReplenishmentProcessor)
|
Since in my app, I still have to call my MDB the old way though jndi (with
business interface class name).
I'm using JBossAS 4.0.4.CR2.
View the original post :
alesj wrote :
| I'm using JBossAS 4.0.4.CR2.
|
Installed through Installer with EJB3 configuration.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3941225#3941225
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3941225
Using:
@EJB(mappedName=services.ejb.ReplenishmentProcessor)
worked.
Thanks, very much. This does not match the behavior for everything else.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3941272#3941272
Reply to the post :
Add the mappedName parameter to the @EJB annotation. The mapped Name is the
jndi binding for the bean. For example,
@EJB(mappedName=ReplenishmentProcessorBean/local)
private ReplenishmentProcessor replenish;
View the original post :
