This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
This is the loanprocessor app from scratch: create an EJB module. Create a Webservice Create a BPEL Proj. Create a BPEL process. Finish the business logic part. Build the BPEL project works fine. Create a Composite App and add the BPEL module. Deploy the ca and it fails. Deployment is looking for the LoanProcessorService_schema1.xsd in: arash.sfbay.sun.com_8080\LoanProcessorService\LoanProcessor\__container_publishing_subctx\META-INF\wsdl\LoanProcessorService_schema1.xsd But the schema is located in: http://arash.sfbay.sun.com:8080/LoanProcessorService/LoanProcessor/__container$publishing$subctx/META-INF/wsdl/LoanProcessorService_schema1.xsd. The "$" is missing from the path. The deployment gives the following err: [deploy-service-assembly] Deploying a service assembly... host=localhost port=4848 file=D:\sherrydev\SOA\del2\CompositeApp3/dist/CompositeApp3.zip Deploy service assembly failed. (partial success) MESSAGE: () Exception thrown in operation createLocalDeploymentRoot MESSAGE: (UNKNOWN) C:\Sun\AppServer\domains\domain1\jbi\system\deployment\CompositeApp3\com.sun.httpsoapbc-1.0-2_CompositeApp3-com.sun.httpsoapbc-1.0-2\META-INF\src\arash.sfbay.sun.com_8080\LoanProcessorService\LoanProcessor\__container_publishing_subctx\META-INF\wsdl\LoanProcessorService_schema1.xsd (The system cannot find the path specified) MESSAGE: (UNKNOWN) C:\Sun\AppServer\domains\domain1\jbi\system\deployment\CompositeApp3\com.sun.httpsoapbc-1.0-2_CompositeApp3-com.sun.httpsoapbc-1.0-2\META-INF\src\arash.sfbay.sun.com_8080\LoanProcessorService\LoanProcessor\__container_publishing_subctx\META-INF\wsdl\LoanProcessorService_schema1.xsd (The system cannot find the path specified) MESSAGE: (UNKNOWN) C:\Sun\AppServer\domains\domain1\jbi\system\deployment\CompositeApp3\com.sun.httpsoapbc-1.0-2_CompositeApp3-com.sun.httpsoapbc-1.0-2\META-INF\src\arash.sfbay.sun.com_8080\LoanProcessorService\LoanProcessor\__container_publishing_subctx\META-INF\wsdl\LoanProcessorService_schema1.xsd (The system cannot find the path specified) D:\sherrydev\SOA\del2\CompositeApp3\nbproject\build-impl.xml:207: Service assembly deployment failed. at org.netbeans.modules.compapp.projects.jbi.anttasks.DeployServiceAssembly.execute(DeployServiceAssembly.java:442) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:240) at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:293) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131) BUILD FAILED (total time: 3 seconds)
Created attachment 33974 [details] loanapp.zip is attached
Sherry, Can you tell the steps used to create the bpel project? I like to know a few things, e.g., - how did you copy the ejb wsdl and xsd files over - did you use the drag-n-drop method or file copy - did you invoke the "populate catalog" action Thanks, -- Tientien Li
Created attachment 34043 [details] exception when clicked finish on wsdl wizard
At this level I cannot reproduce this bug because I am not able to create the wsdl. However, I used the drag-n-drop method I invoked the "populate catalog" action I try it again on Monday with a new build.
The deployment error was caused by the httpsoap binding component in the JBI run-time. We will notify the soap bc team and asking them to fix the code.
Bugster bug 6472707 opened to track this.
his was an issue with earlier versions of JDK 1.5 (like before 1.5.0_06). We are shipping a version of the AppServer iwth 1.5.0_09, so this is no longer a problem with the latest JDK version. The Glashfish folks originally had a check for this issue when they were running with a JDK version less than 1.5.0_06, but they removed it after moving up to a version later than 1.5.0_06. (see http://bt2ws.central.sun.com/CrPrint?id=6182812). Please use a later version of the Appserver that has a JDK > than 1.5.0_06.
As per the developers comments ,changing the status to verified status
Primary verification which I did for this bug is based on the steps to reproduce, no longer can reproduce with latest builds and even reporter,developer claims the same Secondary Verification i,e the Based on the developer comments i,e deployment fails in JDK 1.5.0_04 and works with the latest jdk which is bundles netbeans installer.I did verified found that things are correct ,For FCS releasing criteria is using the 1.5.0_09 Hence I change the status to changing the status to verified as per the developer comments