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.
Product Version: NetBeans IDE Dev (Build 200802270005) Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) Steps to reproduce: 1. Create BluePrint1 sample. 2. Create BPEL module. 3. Add sample loan application schema into module. 4. Add reference from sample to module. 5. Add into purchaseOrder import of sample schema (3). 6. Add to composite application JBI module from module. 7. Deploy. Step 7 will failed. Look like all steps above are important because simple CA deploys without any problems. Reproduced on XP and Vista. Attached logs from AS startup and CA deploy.
Created attachment 57453 [details] as startup log
Created attachment 57454 [details] CA deploy log
This is likely to be caused by an issue in HTTP BC, which dos not use the XML catalog to resolve relative URIs. Can you please attach the project on which the issue can be reproduced?
This completely standard projects (sample and module) created as described.
I'll take this one.
Created attachment 57458 [details] Project for testing/verification
I'm resolving as INVALID in favor of a runtime issue -- https://open-jbi-components.dev.java.net/issues/show_bug.cgi?id=419
Ksorokin, Please don't close this issue. It is considered as a feature stopper. With this issue, cross project reference feature doesn't work. It needs to be listed in dashboard until it is fixed.
If this issue depends on another one, I would decrease the priority for now. once it's fixed in runtime, please update this issue as well.
I'm not sure I'm happy with idea to decrease priority for showstopper... Yes it depends on another issue but last filed even not in IZ, so current issue is the only one indicates problem for NB teams.
Product Version: NetBeans IDE Dev (Build 200803170003) Java: 1.6.0_05; Java HotSpot(TM) Client VM 10.0-b19 System: Linux version 2.6.20-15-generic running on i386; UTF-8; en_US (nb) Userdir: /export/home/tester/.netbeans/dev Successfully reproduced on Ubuntu. I believe this is P1 -- just no way to deploy even simple Composire Application without references.
Last part of output log, not too long to create standalone file so put it right here: Created dir: /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13/build Copying 6 files to /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13/build Building jar: /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13/build/SEDeployment.jar dist_se: Expanding: /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13/build/SEDeployment.jar into /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13Application/src/jbiServiceUnits/BluePrint13 Moving 1 file to /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13Application/src/jbiServiceUnits/BluePrint13 Moving 1 file to /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13Application/src/jbiServiceUnits/META-INF/BluePrint13 deps-javaee-jar: jbi-build: Copying 1 file to /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13Application/src/jbiServiceUnits Created dir: /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13Application/build/META-INF Building jar: /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13Application/build/BCDeployment.jar Validating CompApp project... Resolving connections... Writing connections out to connections.xml... Generating Service Assembly jbi.xml... Merging component projects' catalogs... Generating Binding Component Service Units... creating sun-http-binding.jar Creating/Updating CASA... Filtering Java EE Endpoints... Deleting: /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13Application/build/BCDeployment.jar Created dir: /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13Application/dist Building jar: /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13Application/dist/BluePrint13Application.zip run-jbi-deploy: /export/home/tester/NetBeansProjects/BluePrint13/BluePrint13Application/nbproject/build-impl.xml:213: null BUILD FAILED (total time: 26 seconds)
Just note: scenario to reproduce is very easy -- Create BluePrint1 sample then Deploy.
Used small hack to check this and found fix is not valid. Log here. Definitely this is log from newly added GF not GF shipped with NB due to path: file:/E:/pub/Orion/nbi/GF/... run-jbi-deploy: [deploy-service-assembly] Deploying a service assembly... host=localhost port=4848 file=C:\Work\Sun\SOA\crossing\BluePrint\BluePrintApplication/dist/BluePrintApplication.zip ERROR: Service assembly deployment failed (see error below). Cleaning up... [undeploy-service-assembly] Undeploying a service assembly... host=localhost port=4848 name=BluePrintApplication C:\Work\Sun\SOA\crossing\BluePrint\BluePrintApplication\nbproject\build-impl.xml:233: Successful execution of Deploy: C:\Work\Sun\SOA\crossing\BluePrint\BluePrintApplication/dist/BluePrintApplication.zip WARNING: (JBIMA0404) Deployment of service assembly BluePrintApplication succeeded partially; some service units failed to deploy. * Component: sun-http-binding ERROR: (SOAPBC_DEPLOY_2) HTTPBC-E00201: Deployment failed. javax.wsdl.WSDLException: WSDLException (at /definitions/types/xsd:schema/xs:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at ''BpelModule/newLoanApplication.xsd'', relative to ''file:/E:/pub/Orion/nbi/GF/domains/domain1/jbi/service-assemblies/BluePrintApplication/BluePrintApplication-sun-http-binding/sun-http-binding/BluePrint/purchaseOrder.xsd''.: java.io.FileNotFoundException: This file was not found: file:/E:/pub/Orion/nbi/GF/domains/domain1/jbi/service-assemblies/BluePrintApplication/BluePrintApplication-sun-http-binding/sun-http-binding/BluePrint/BpelModule/newLoanApplication.xsd BUILD FAILED (total time: 2 minutes 5 seconds)
Murali, looks we still experience some problems.
Sergey, It is failing in http-bc, NB build you are using does not have fix for http://www.netbeans.org/issues/show_bug.cgi?id=132267
Murali, looks like problem on our side. Kirill will look into this.
No such issue on mac or linux for me. With existing runtimes(shipped w/ netbeans) as well as building from snapshot. See attached logs.
Created attachment 59859 [details] log from mac with new runtimes
Created attachment 59860 [details] Log from linux on new runtimes
Both mac and linux test were done using netbeans build 200804060002 Java 1.6.0_04 for linux and java 1.5.0_13 on mac
Following steps in desc14 there was no issue, however, using the project attached to this issue, the problem is seen.
See notes for issue 132267.
Successfully reproduced with RC1 today. Was fix integrated or not yet? I'm gonna reopen issue again unfortunately... BTW looks like there are some changes -- sometimes Deploy passes successfully. I did not find reasons but one time of may be ten it says "BUILD SUCCESSFUL"
I've installed RC1 today -- I couldn't reproduce the issue. I tried it twice. I did it on Win. Please attach project you've experienced problem.
One more comment: firewall was switched off.
Okey I'll check without FW...
Well, if GF already started then deploy works fine. I think another issue should be filed.
Michael, may I ask you to attach the glassfish log file for case when deploy fails? I'm curious, whether we are trying to deploy the application before JBI is fully started.
Also, which JDK are you using for NetBeans and GlassFish?
Created attachment 59976 [details] build log
Created attachment 59977 [details] gf log
JDK 1.6.04 for both of them. Looks like failed is more possible while GF need to undeploy previous version of application but I'm not sure about...
I've filed a follow-up issue against composite application project -- issue 132544.
Michael, if the application can be deployed when GF is on and the app is undeloyed, this issue should be marked as verified.
Check issue 132544 now.
I am using NB61. RC1 from http://bits.netbeans.org/6.1/nightly/latest/zip/ 1. It is still generating invalid entries in catalog packaged with SU for http-bc <?xml version="1.0" encoding="UTF-8" standalone="no"?><catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog" prefer="system"> <system systemId="BpelModule1/newLoanApplication.xsd" uri="SynchronousSample/dependentProjectsFiles/BpelModule1/src/newLoanApplication.xsd"/> <system systemId="BpelModule1/newWSDL.wsdl" uri="SynchronousSample/dependentProjectsFiles/BpelModule1/src/newWSDL.wsdl"/> </catalog> 2. Sometimes it is generating duplicate catalog.xml outside META-INF folder Resulting in following error in deployment ------------------------------------------- C:\Documents and Settings\mpottlapelli\My Documents\NetBeansProjects\SynchronousSample\SynchronousSampleApplication\nbproject\build-impl.xml:213: Successful execution of Deploy: C:\Documents and Settings\mpottlapelli\My Documents\NetBeansProjects\SynchronousSample\SynchronousSampleApplication/dist/SynchronousSampleApplication.zip WARNING: (JBIMA0404) Deployment of service assembly SynchronousSampleApplication succeeded partially; some service units failed to deploy. * Component: sun-http-binding ERROR: (SOAPBC_DEPLOY_2) HTTPBC-E00201: Deployment failed. javax.wsdl.WSDLException: WSDLException (at /definitions/types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at ''BpelModule1/newLoanApplication.xsd'', relative to ''file:/C:/openEsb/glassfish/domains/domain1/jbi/service-assemblies/SynchronousSampleApplication/SynchronousSampleApplication-sun-http-binding/sun-http-binding/SynchronousSample/SynchronousSample.wsdl''.: java.io.FileNotFoundException: This file was not found: file:/C:/openEsb/glassfish/domains/domain1/jbi/service-assemblies/SynchronousSampleApplication/SynchronousSampleApplication-sun-http-binding/sun-http-binding/SynchronousSample/BpelModule1/newLoanApplication.xsd BUILD FAILED (total time: 1 second)
Murali, you used wrong link. I'll send you correct one via e-mail.
It works using the build http://bits.netbeans.org/6.1/rc1_hard_to_guess_dir/latest/zip/
Deployment fails for the attached project.Created the new projcet based on the steps mentioned above and the new project also failed to deploy. Used 20080421-1307 build to verify. The Netbeans version : 6.1 RC1 HTTP BC version: tried build number 080422 and 080311_4 BPEL engine: build 080421
vinathi, as we decided cause of this issue fixed but there is new one with very similar symptoms but other reason. Please check new issue and is it closer to your situation then this one. Issue number is 132544. Please note here so we'll close this or recheck aging according to your report.
The core problem is fixed. For non started AS there is another issue: 132544.
Please refer to attached project. It is synchronous sample project. SynchronousSample.wsdl imports wsdl and xsd from BpelModule1. BpelModule1's w1.wsdl imports wsdl and xsd from BpelModule2. In this scenario catalog packaged with the SA is not complete.
Created attachment 60593 [details] project to demonstrate the issue
Murali, in one of the comments Kirill mentioned that such scenario is not supported yet. It requires more complicated refactoring in catalog area. I'll close this issue and open another one. Murali, you've saved attachment in text/plain type. I couldn't read it.
I tested the attached project and a newly created project with vinathi together on her machine yesterday. If I remember correctly, even if the app server was previously started, deploying the project still failed. vinathi, could you please confirm/re-verify? However, on my own machine, I am able to deploy the project fine. I am using: NetBeans 6.1 RC2 BPEL SE 080408_1 HTTP BC 080311_4 I also tried the latest BPEL SE (080423) together with the latest sun-shared-util-library, the deployment still works fine.
verified using 20080429-0500 build. NetBeans 6.1 (Build 200804211638) BPEL SE 080429_1 HTTP BC 080428_1 I am able to deploy the project fine. However last time when I verified, the deployment failed.
Already verified by Vinathi