2016-03-21 55 views
1

我有Java 8 &安裝了WildFly(JBoss)10.0。我在「遠程」服務器上部署了帶有遠程EJB的emsa.jar文件。WildFly 10使用JNDI的遠程EJB調用ClassNotFoundException javax.ejb.EJBException

我試圖通過運行在客戶端的主要方法爲Java應用程序在Eclipse中使用JNDI從單獨的客戶端應用程序中調用EJB中的一個方法,但我得到以下錯誤:

INFO: EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext[email protected], receiver=Remoting connection EJB receiver [connection=Remoting connection <545ebbdd>,channel=jboss.ejb,nodename=skb]} on channel Channel ID d234d46a (outbound) of Remoting connection 395b72b3 to localhost/127.0.0.1:8080 
Exception in thread "naming-client-message-receiver-1-thread-1" java.lang.NoClassDefFoundError: javax/ejb/EJBException 
    at org.jboss.ejb.client.SerializedEJBInvocationHandler.readResolve(SerializedEJBInvocationHandler.java:110) 
    at org.jboss.ejb.client.SerializedEJBInvocationHandler.readResolve(SerializedEJBInvocationHandler.java:106) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
    at java.lang.reflect.Method.invoke(Method.java:497) 
    at org.jboss.marshalling.reflect.SerializableClass.callReadResolve(SerializableClass.java:417) 
    at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1299) 
    at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:276) 
    at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:213) 
    at org.jboss.marshalling.river.RiverUnmarshaller.doReadNestedObject(RiverUnmarshaller.java:169) 
    at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1254) 
    at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:276) 
    at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:213) 
    at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:45) 
    at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:156) 
    at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:149) 
    at org.jboss.naming.remote.protocol.v1.BaseProtocolCommand.readResult(BaseProtocolCommand.java:59) 
    at org.jboss.naming.remote.protocol.v1.Protocol$1.handleClientMessage(Protocol.java:149) 
    at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1$MessageReceiver$1.run(RemoteNamingStoreV1.java:232) 
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
    at java.lang.Thread.run(Thread.java:745) 
Caused by: java.lang.ClassNotFoundException: javax.ejb.EJBException 
    at java.net.URLClassLoader.findClass(URLClassLoader.java:381) 
    at java.lang.ClassLoader.loadClass(ClassLoader.java:424) 
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) 
    at java.lang.ClassLoader.loadClass(ClassLoader.java:357) 
    ... 23 more 
javax.naming.NamingException: Unable to invoke lookup, status=WAITING 
    at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:98) 
    at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:95) 
    at org.jboss.naming.remote.client.HaRemoteNamingStore$1.operation(HaRemoteNamingStore.java:276) 
    at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:132) 
    at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272) 
    at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104) 
    at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93) 
    at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146) 
    at javax.naming.InitialContext.lookup(InitialContext.java:417) 
    at com.kelly_ann.employeemgmt.Main.main(Main.java:38) 

在客戶端的主類的代碼是:

package com.k_a.employeemgmt; 

import java.util.List; 
import java.util.Properties; 

import javax.naming.Context; 
import javax.naming.InitialContext; 
import javax.naming.NamingException; 

import com.k_a.employeemgmt.EmployeeMgmtService; 
import com.k_a.employeemgmt.domain.Employee; 

public class Main { 

    // this remotely invokes the server's EmployeeMgmtService.getAllEmployees() method. 
    public static void main(String[] args) { 
     try { 
      Properties jndiProperties = new Properties(); 
      jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); 
      jndiProperties.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); 
      jndiProperties.put("jboss.naming.client.ejb.context", true); 
      System.out.println("MYTESTjndiProperties: " + jndiProperties); // gets here 
      Context jndi = new InitialContext(jndiProperties); 
      System.out.println("MYTESTjndi: " + jndi); // gets here 

      EmployeeMgmtService service = (EmployeeMgmtService)jndi.lookup("emsa/EmployeeMgmtImpl!com.k_a.employeemgmt.EmployeeMgmtService"); 
      System.out.println("MYTESTservice: " + service); // doesn't get to here 
      List<Employee> employees = service.getAllEmployees(); 
      for(Employee employee : employees) { 
       System.out.println(employee); 
      } 
     } 

我的客戶端應用程序的搖籃構建文件(build.gradle)中有以下依賴性:

apply plugin: 'java' 

defaultTasks 'clean', 'compileJava', 'test', 'jar' 

jar { 
    archiveName = "emtc.jar" 
} 

test.useJUnit() 

repositories { 
    mavenCentral() 
} 

dependencies { 
    compile 'jboss:jboss-client:4.0.2' 
    compile 'org.jboss:jboss-remote-naming:2.0.4.Final' 
    compile 'org.jboss.xnio:xnio-nio:3.3.6.Final' 
    testCompile 'junit:junit:4.12' 
} 

我試過在WildFly/JBoss文檔here的最後一天,但沒有運氣。

任何想法?

回答

1

最終的解決方案:

的問題是我的搖籃的build.gradle文件,我需要申請上市here'application'插件並調用'run'任務。一旦完成,它就像一個魅力!在Gradle構建文件中使用Maven存儲庫物料清單(從here)結束,因爲這是確保正確的依賴關係管理的最佳方式。感謝所有的幫助!非常感激。 :-)

build.gradle文件

最終代碼如下:

apply plugin: 'java' 
apply plugin: 'application' 

defaultTasks 'clean', 'compileJava', 'test', 'jar', 'run' 

mainClassName = 'com.k_a.employeemgmt.Main' 

jar { 
    archiveName = "emtc.jar" 
} 

test.useJUnit() 

repositories { 
    mavenCentral() 
} 

dependencies { 
    compile 'org.wildfly:wildfly-ejb-client-bom:10.0.0.Final' 
    testCompile 'junit:junit:4.12' 
} 
2

我已經寫了一個小的tutorial關於Maven for Wildfly 9.0.2.Final的方法。所以我只是嘗試將它翻譯成Gradle方式(抱歉,我沒有使用Gradle的經驗),並且我調整了依賴關係以符合Wildfly 10.0.0.Final尊重您的需要,以便在出現任何錯誤版本時不會收到NoClassDefException組合:

dependencies { 
    org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:1.0.0.Final 
    org.jboss:jboss-remote-naming:2.0.4.Final 
    org.jboss:jboss-ejb-client:2.1.4.Final 
    org.jboss.xnio:xnio-nio:3.3.4.Final 
    org.jboss.marshalling:jboss-marshalling-river:1.4.10.Final 
    org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:1.0.0.Final 
} 

或者只是使用:

dependencies { 
    org.wildfly:wildfly-client-all:10.0.0.Final 
} 

但是在第二種情況下,你必須爲JMS等傳遞依賴...

順便說一句,在Maven的方式,我經常使用BOM依賴關係,這將暗示自動從根本上說是依賴關係的「正確」版本,但我不知道Gradle中是否有類似的東西。如果可以的話你可以使用這個BOM:

org.wildfly:wildfly-ejb-client-bom:10.0.0.Final 

然後你可以省略我上面提到的依賴的版本。

讓我反饋你的意見。

+0

感謝wildfly的EJB客戶端-BOM!這有很大幫助。 問題是我需要應用應用程序插件並調用'運行'任務的我的Gradle build.gradle文件。一旦完成,它就像一個魅力! – specialk1st