Java 无法在JBoss 7.x中查找远程EJB

我正在尝试连接到部署在JBoss7服务器中的远程EJB。我试图通过查看从JBoss CLI获得的JNDI转储来了解JNDI名称。
无论我尝试什么，我都无法查找EJB

我认为jndi名称应该是：java:global/XNet/api/ReceivingAPI_EJB！com.mycompany.receiving.api.ReceivingAPI_EJBRemote

以下是我正在使用的客户端：

package com.mycompany.mavenproject1;

import com.mycompany.receiving.api.ReceivingAPI_EJBRemote;
import com.mycompany.receiving.api.ReceivingAPI;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import java.util.Properties;
/**
 * Hello world!
 *
 */
public class App 
{
    public static void main( String[] args ) throws NamingException
    {
        System.out.println( "Hello World!" );


        //ReceivingAPI ejbRemote = DomainHelper.getHQApi(com.mycompany.receiving.api.ReceivingAPI.class);
        ReceivingAPI_EJBRemote ejbRemote = App.lookupRemoteStatelessCalculator();

        ejbRemote.getOpenRcvdocForSite(null, 7);
    }

//    private static ReceivingAPI_EJBRemote lookupRemoteStatelessReceiving() throws NamingException {
//        
//    }
//    
    private static ReceivingAPI_EJBRemote lookupRemoteStatelessCalculator() throws NamingException {
        final Properties jndiProperties = new Properties();
        jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
        jndiProperties.put(Context.PROVIDER_URL,"remote://someserver.xmx.com:1199");
        // username
        jndiProperties.put(Context.SECURITY_PRINCIPAL, "mycompany1");
        // password
        jndiProperties.put(Context.SECURITY_CREDENTIALS, "<removed>");
        //final Context context = new InitialContext(jndiProperties);


        jndiProperties.put("jboss.naming.client.ejb.context", true);

        InitialContext context = new InitialContext( jndiProperties );
        // The app name is the application name of the deployed EJBs. This is typically the ear name
        // without the .ear suffix. However, the application name could be overridden in the application.xml of the
        // EJB deployment on the server.
        // Since we haven't deployed the application as a .ear, the app name for us will be an empty string
        final String appName = "XNet";
        // This is the module name of the deployed EJBs on the server. This is typically the jar name of the
        // EJB deployment, without the .jar suffix, but can be overridden via the ejb-jar.xml
        // In this example, we have deployed the EJBs in a jboss-as-ejb-remote-app.jar, so the module name is
        // jboss-as-ejb-remote-app
        final String moduleName = "api";
        // AS7 allows each deployment to have an (optional) distinct name. We haven't specified a distinct name for
        // our EJB deployment, so this is an empty string
        final String distinctName = "hq";
        // The EJB name which by default is the simple class name of the bean implementation class
        final String beanName = com.mycompany.receiving.api.ReceivingAPI.class.getSimpleName();
        // the remote view fully qualified class name
        final String viewClassName = ReceivingAPI_EJBRemote.class.getName();
        // let's do the lookup

        try {
            ReceivingAPI test1 = (ReceivingAPI)context.lookup("java:global/XNet/api/" + beanName + "_EJB!" + viewClassName);
            System.out.println("Test1 = " + test1.getClass().getName());
        } catch(Throwable t) {
          System.out.println(t);  
        }

        try {
            ReceivingAPI test = (ReceivingAPI)context.lookup("java:global/XNet/api/hq/" + beanName + "_EJB!com.mycompany.receiving.api.ReceivingAPI_EJBRemote");
            System.out.println("Test = " + test.getClass().getName());
        } catch(Throwable t) {
            System.out.println(t);
        }

        try {
            ReceivingAPI test = (ReceivingAPI)context.lookup("ejb:XNet/api/hq/" + beanName + "_EJB!com.mycompany.receiving.api.ReceivingAPI_EJBRemote");
            System.out.println("Test = " + test.getClass().getName());
        } catch(Throwable t) {
            System.out.println(t);
        }
        return (ReceivingAPI_EJBRemote) context.lookup("ejb:" + appName + "/" + moduleName + "/" + distinctName + "/" + beanName + "_EJB!" + viewClassName);
    }

}

以下是JNDI CLI命令的转储：

[jboss1@hmudev01 bin]$ ./jboss-cli.sh --connect controller=localhost:10099
[standalone@localhost:10099 /] /subsystem=naming:jndi-view
{
    "outcome" => "success",
    "result" => {
        "java: contexts" => {
            "java:global" => {
                "XNet" => {
                    "class-name" => "javax.naming.Context",
                    "children" => {
                        "api" => {
                            "class-name" => "javax.naming.Context",
                            "children" => {
                                "ReceivingAPI_EJB!com.mycompany.receiving.api.ReceivingAPI_EJBLocal" => {
                                    "class-name" => "com.mycompany.receiving.api.ReceivingAPI_EJBLocal$$$view46",
                                    "value" => "Proxy for view class: com.mycompany.receiving.api.ReceivingAPI_EJBLocal of EJB: ReceivingAPI_EJB"
                                },
                                "ReceivingAPI_EJB!com.mycompany.receiving.api.ReceivingAPI_EJBRemote" => {
                                    "class-name" => "com.sun.proxy.$Proxy272",
                                    "value" => "Proxy for remote EJB StatelessEJBLocator{appName='XNet', moduleName='api', distinctName='hq', beanName='ReceivingAPI_EJB', view='interface com.mycompany.receiving.api.ReceivingAPI_EJBRemote'}"
                                },
                            }
                        }
                    }
                }
            }
        }

        ...
    }
}
[standalone@localhost:10099 /] 

任何my maven DEP如下所示：

 <dependencies>
    <dependency>
        <groupId>com.mycompany.receiving</groupId>
        <artifactId>xnet-domain-receiving-client</artifactId>
        <version>2.5.0-SNAPSHOT</version>
    </dependency>
    <dependency>
        <groupId>org.jboss.as</groupId>
        <artifactId>jboss-as-naming</artifactId>
        <version>7.1.3.Final</version>
    </dependency>
    <dependency>
        <groupId>org.jboss.marshalling</groupId>
        <artifactId>jboss-marshalling-river</artifactId>
        <version>1.4.0.Final</version>
    </dependency>
    <dependency>
        <groupId>org.jboss.client</groupId>
        <artifactId>jbossall-client</artifactId>
        <version>5.0.0.GA</version>
    </dependency>
    <dependency>
        <groupId>org.jboss.spec.javax.ejb</groupId>
        <artifactId>jboss-ejb-api_3.1_spec</artifactId>
        <version>1.0.2.Final</version>
    </dependency>
</dependencies>

com.mycompany.receiving
xnet域接收客户端
2.5.0-快照
org.jboss.as
jboss作为命名
7.1.3.最终版本
org.jboss.marshalling
jboss编组河
1.4.0.1最终版本
org.jboss.client
jbossall客户端
5.0.0.GA
org.jboss.spec.javax.ejb
jboss-ejb-api_3.1_规范
1.0.2.1最终版本

在上面的评论中，Rhys关于jndi字符串看起来“时髦”的说法是正确的。我想的都试过了。以下是对我的情况有效的方法

JNDI URL需要如下所示：

XNet/api/ReceivingAPI_EJB!com.mycompany.receiving.api.ReceivingAPI_EJBRemote

我还必须向问题中显示的其他项添加依赖项：

    <dependency>
        <groupId>javax</groupId>
        <artifactId>javaee-api</artifactId>
        <version>7.0</version>
    </dependency>

爪哇
JavaEEAPI
7

对于远程查找，我认为您可以删除任何与

global

相关的

ejb:

。话虽如此，我认为您的查找字符串有点古怪。它应该类似于

ejb:/。如果您部署在
.ear
中，这将略有变化，因此在您的情况下，我认为（假设RNet是您的.jar的名称）您所追求的字符串是
ejb:RNet/ReceivingAPI\u ejb！com.mycompany.receiving.api.ReceivingAPI_ejbloc
（注意缺少java:ejb）。看起来您也在将一些非标准端口推入jndi设置，假设这是有意的。如果这不起作用，我可能想看看jndiProps。Rhys你基本上是对的，但它让我有能力知道我需要做什么。我会把它贴在答案里。
    <dependency>
        <groupId>javax</groupId>
        <artifactId>javaee-api</artifactId>
        <version>7.0</version>
    </dependency>