2013-03-21 99 views
0

我在Jboss As 7.1服务器上部署了一个名为SessionServiceBean的会话bean。在部署我得到在控制台下面的输出监听的bean,正确的JNDI标识符:JNDI:未找到EJB

JNDI bindings for session bean named SessionServiceBean in deployment unit subdeployment "account-ejb.jar" of deployment "replay-ear.ear" are as follows: 

java:global/replay-ear/account-ejb/SessionServiceBean!de.replay.account.SessionService 
java:app/account-ejb/SessionServiceBean!de.replay.account.SessionService 
java:module/SessionServiceBean!de.replay.account.SessionService 
java:jboss/exported/replay-ear/account-ejb/SessionServiceBean!de.replay.account.SessionService 
java:global/replay-ear/account-ejb/SessionServiceBean 
java:app/account-ejb/SessionServiceBean 
java:module/SessionServiceBean 

现在,如果我尝试在我的JUnit测试案例来查找豆:

service = (SessionService) jndiCtx.lookup("java:global/replay-ear/account-ejb/SessionServiceBean!de.replay.account.SessionService"); 

我得到一个例外告诉我,服务器无法找到这个bean:

javax.naming.NameNotFoundException: global/replay-ear/account-ejb/SessionServiceBean!de.replay.account.SessionService -- service jboss.naming.context.java.jboss.exported.global.replay-ear.account-ejb."SessionServiceBean!de.replay.account.SessionService" 
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) 
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) 
    at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127) 
    at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 
    at java.lang.Thread.run(Unknown Source) 

我不明白这个错误作为JNDI标识符配衬在日志中输出的一个和我的客户是肯定的连接正确的服务器。

难道是用户Im用于身份验证没有jndi查找所需的权限?我其实不知道为什么这不起作用。那是我第一次使用远程ejbs。

回答

0

显然,错误是将java:global保留在JNDI标识符中。

工作查找现在看起来是这样的:

service = (SessionService) jndiCtx.lookup("/replay-ear/account-ejb/SessionServiceBean!de.replay.account.SessionService");