Note that there are some explanatory texts on larger screens.

plurals
  1. POglassfish can't find my wsdl when WAR is deployed
    primarykey
    data
    text
    <p>I have a CXF service service that I created WSDL first and when I deploy the WAR into glassfish app server 2.1.1, I get the following exception:</p> <pre><code>java.io.FileNotFoundException: C:\Sun\AppServer\domains\domain1\config\TestService.wsdl </code></pre> <p>If I put the WSDL in that location, everything works fine. How do I setup my WAR so that the TestService.wsdl gets put into the config folder?</p> <p>Thanks!</p> <p>UPDATE: I am still having problems deploying this service to Glassfish. As is it deploys and runs fine in Tomcat.</p> <p>I set the -wsdlLocation property during the build to "WEB-INF/wsdl/TestService.wsdl" but now when I deploy the application in glassifish I get the following exceptions in the server.log</p> <pre><code>[#|2010-02-01T10:47:06.164-0500|SEVERE|sun- appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=23;_ThreadName=Thread- 501;_RequestID=d3a3f49b-9329-477d-b6fc-24e0f4e4f3fa;|wsdl file file:/C:/development/wexlink/FileUploadService/wsdl/FileUploadService.wsdl does not exist for web service FileUploadService|#] [#|2010-02-01T10:47:06.977-0500|SEVERE|sun appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=23;_ThreadName=Thread- 501;_RequestID=d3a3f49b-9329-477d-b6fc-24e0f4e4f3fa;|Exception occured in J2EEC Phasejava.lang.RuntimeException: wsdl file file:/C:/development/wexlink/FileUploadService/wsdl/FileUploadService.wsdl does not exist for web service FileUploadService com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [FileUploadService] -- wsdl file file:/C:/development/wexlink/FileUploadService/wsdl/FileUploadService.wsdl does not exist for web service FileUploadService at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:406) at com.sun.enterprise.deployment.backend.ModuleDeployer.loadDescriptors(ModuleDeployer.java:426) at com.sun.enterprise.deployment.backend.WebModuleDeployer.deploy(WebModuleDeployer.java:160) at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:182) at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:208) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:966) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:283) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:835) at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187) at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:225) </code></pre> <p>Caused by: java.lang.RuntimeException: wsdl file file:/C:/development/wexlink/FileUploadService/wsdl/FileUploadService.wsdl does not exist for web service FileUploadService at com.sun.enterprise.deployment.util.ModuleContentValidator.accept(ModuleContentValidator.java:187) at com.sun.enterprise.deployment.WebBundleDescriptor.visit(WebBundleDescriptor.java:1410) at com.sun.enterprise.deployment.archivist.WebArchivist.postOpen(WebArchivist.java:171) at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:215) at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:813) at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:794) at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:365) ... 10 more |#]</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload