배포 단계의 PARSE를 처리하지 못했습니다.

Question

warfly 파일을 서버의 배포 폴더에 넣은 다음 서버를 시작하고 다음 예외를 제외하면 LBatch.war을 wildfly-8에 배포하려고합니다.

14:39:53,810 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC000001: Failed to start service jboss.deployment.unit."LBatch.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."LBatch.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "LBatch.war" 
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] 
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final] 
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final] 
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40] 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40] 
    at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] 
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS015599: Apache CXF library (cxf-bundle-2.6.6.jar) detected in ws endpoint deployment; either provide a proper deployment replacing embedded libraries with container module dependencies or disable the webservices subsystem for the current deployment adding a proper jboss-deployment-structure.xml descriptor to it. The former approach is recommended, as the latter approach causes most of the webservices Java EE and any JBossWS specific functionality to be disabled. 
    at org.jboss.as.webservices.deployers.WSLibraryFilterProcessor.deploy(WSLibraryFilterProcessor.java:71) 
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] 
    ... 5 more 

14:39:53,815 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "LBatch.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"LBatch.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"LBatch.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"LBatch.war\" 
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS015599: Apache CXF library (cxf-bundle-2.6.6.jar) detected in ws endpoint deployment; either provide a proper deployment replacing embedded libraries with container module dependencies or disable the webservices subsystem for the current deployment adding a proper jboss-deployment-structure.xml descriptor to it. The former approach is recommended, as the latter approach causes most of the webservices Java EE and any JBossWS specific functionality to be disabled."}} 
14:39:53,856 INFO [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "LBatch.war" (runtime-name : "LBatch.war") 
14:39:53,858 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report 
JBAS014777: Services which failed to start:  service jboss.deployment.unit."LBatch.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."LBatch.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "LBatch.war" 

14:39:53,891 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 
14:39:53,891 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 
14:39:53,892 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.0.Final "WildFly" started (with errors) in 5084ms - Started 218 of 267 services (1 services failed or missing dependencies, 89 services are lazy, passive or on-demand) 
14:39:54,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment LBatch.war (runtime-name: LBatch.war) in 146ms 
14:39:54,287 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "LBatch.war" (runtime-name: "LBatch.war") 
14:39:54,287 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report 
JBAS014777: Services which failed to start:  service jboss.deployment.unit."LBatch.war".PARSE 

Answer 1

어떤 이유로 인해 CXF 종속성을 프로젝트에 추가하면 Wildfly가 만족스럽지 않습니다.

약 cxf-bundle-2.6.6.jar에 대해 불평하고 있습니다.

프로젝트에 해당 JAR이 포함되어 있지 않은지 확인하십시오. Maven을 사용하고 있다면 직접 포함시키지 않더라도 사용중인 다른 프로젝트에 포함되어 있기 때문에 종속성 계층 구조를 확인하십시오.

Wildfly가 왜 그것에 대해 불만하는지 잘 모릅니다. 아마 그것은 이미 그것의 자신의 세트를 가지고 있고 그것을 삽입 할 필요가 없을 것입니다.

Answer 2

이것은 기본적으로 WSDL based webservices on Wildfly에서 동일한 문제입니다. JBossWS 문서를 참조하여 JBoss Module 종속성을 정의하고 배포시 CXF가 번들되지 않도록해야합니다.