2013-03-10 71 views
0

我們有一個使用CXF實現並在JBoss 5.1上運行的Web服務。 最近我們將CXF從2.3.1升級到了2.5.9。 我們還將WS-Policy添加到我們的服務中,以便來自客戶端的soap請求包含一個x509證書令牌。 但是,在處理請求時,框架在嘗試加載位於wss4j-1.6.9.jarorg.apache.ws.security.components.crypto.Merlin時拋出ClassNotFoundException。 這裏是異常的完整調用堆棧:在JBOSS上使用CXF處理SOAP請求時發生java.lang.ClassNotFoundException

java.lang.ClassNotFoundException: org.apache.ws.security.components.crypto.Merlin 
at java.net.URLClassLoader$1.run(URLClassLoader.java:200) 
at java.security.AccessController.doPrivileged(Native Method) 
at java.net.URLClassLoader.findClass(URLClassLoader.java:188) 
at java.lang.ClassLoader.loadClass(ClassLoader.java:303) 
at java.lang.ClassLoader.loadClass(ClassLoader.java:248) 
at org.apache.ws.security.util.Loader.loadClass(Loader.java:252) 
at org.apache.ws.security.util.Loader.loadClass(Loader.java:245) 
at org.apache.ws.security.util.Loader.loadClass(Loader.java:239) 
at org.apache.ws.security.components.crypto.CryptoFactory.getInstance(CryptoFactory.java:109) 
at org.apache.ws.security.components.crypto.CryptoFactory.getInstance(CryptoFactory.java:78) 
at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JInInterceptor.getSignatureCrypto(PolicyBasedWSS4JInInterceptor.java:383) 
at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JInInterceptor.checkAsymmetricBinding(PolicyBasedWSS4JInInterceptor.java:221) 
at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JInInterceptor.computeAction(PolicyBasedWSS4JInInterceptor.java:585) 
at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:238) 
at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:100) 
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) 
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:122) 
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:233) 
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:209) 
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:189) 
at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:129) 
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:223) 
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:143) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:199) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) 
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) 
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) 
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) 
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) 
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) 
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) 
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) 
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) 
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) 
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) 
at java.lang.Thread.run(Thread.java:619) 

有趣的是,從同一個JAR其他類成功加載。例如org.apache.ws.security.util.Loader,這可以在調用堆棧中看到。我試圖將JAR都放在我的WAR和JBoss lib文件夾中,但它沒有解決任何問題。

任何想法?

+0

檢查任何舊版本jar可能在lib – shola 2013-03-10 12:41:51

+0

@shola checked。服務器上只有一個wss4j jar,位於WEB-INF/lib內部。 – Aaron 2013-03-10 13:15:39

回答

1

找到解決方案:從屬性文件中取得的類名有一個尾隨空格。一旦刪除了空白,該類加載沒有問題。

相關問題