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.
When deploying the attached project, got the following error message: .... Successful execution of Deploy WARNING: (JBIMA0404) Deployment of service assembly TestForNBReproComposite succeeded partially; some service units failed to deploy. * Component: sun-http-binding ERROR: (SOAPBC_DEPLOY_2) Failed to deploy: javax.wsdl.WSDLException: WSDLException (at /definitions/types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at ''http://localhost:8080/JavaEchoService/JavaEchoService?xsd=1'', relative to ''file:/C:/openesb/glassfish-v2-b50/domains/domain1/jbi/service-assemblies/TestForNBReproComposite/TestForNBReproComposite-sun-http-binding/sun-http-binding/TestForNBRepro/localhost_8080/JavaEchoService/JavaEchoService.wsdl''.: java.io.FileNotFoundException: This file was not found: http://localhost:8080/JavaEchoService/JavaEchoService?xsd=1 [start-service-assembly] Starting a service assembly... host=localhost port=4848 name=TestForNBReproComposite Failed execution of Start * Component: sun-bpel-engine ERROR: () The processing instruction target matching "[xX][mM][lL]" is not allowed. C:\Documents and Settings\jqian\Desktop\kini\TestForNBReproComposite\nbproject\build-impl.xml:238: Service assembly deployment failed.
Created attachment 44304 [details] projects
The problem is due to wrong catalog handling when generating BC SU jar.
In my local environment, I fixed the BC SU packaging problem to properly package the cached xml data along with the xml catalog, but I still got the same deployment error on HTTP SOAP BC. I think our HTTP SOAP BC might not support catalog. Can someone from the BC team confirm? I tried a project in our driver test suite that uses catalog. The project does deploy successfully. However, this doesn't prove anything because the remote XSD is available on the internet. After I disconnect from the internet, BPEL SE SU still deploys OK, proving that BPEL SE understands catalog, but HTTP SOAP BC has a deployment failure. [deploy-service-assembly] Deploying a service assembly... host=localhost port=4848 file=C:\public\SyncSampleEPRLiteralJBI/dist/SyncSampleEPRLiteralJBI.zip Successful execution of Deploy WARNING: (JBIMA0404) Deployment of service assembly SyncSampleEPRLiteralJBI succeeded partially; some service units failed to deploy. * Component: sun-http-binding ERROR: (SOAPBC_DEPLOY_2) Failed to deploy: javax.wsdl.WSDLException: WSDLException (at /definitions/types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at ''http://schemas.xmlsoap.org/ws/2004/08/addressing/'', relative to ''file:/C:/openesb/glassfish-v2-b50/domains/domain1/jbi/service-assemblies/SyncSampleEPRLiteralJBI/SyncSampleEPRLiteralJBI-sun-http-binding/sun-http-binding/SyncSampleEPRLiteral/SynchronousSample.wsdl''.: java.net.NoRouteToHostException: No route to host: connect [start-service-assembly]
There are two issues here: The first one is failing to deploy HTTP SOAP BC SU. There are two tasks for this one: (1) BC needs to support catalog; (2) BC SU generation in CompApp currently needs to provide supporting catalog data along with the catalog. The second one is failing to start BPEL SE SU: Failed execution of Start * Component: sun-bpel-engine ERROR: () The processing instruction target matching "[xX][mM][lL]" is not allowed. I looked at all the XML/WSDL/BPEL files in the BPEL SE SU and they are seem to be valid. There is nothing comes before the xml prolog. Murali mentioned that sometimes the error message could be misleading. Murali, could you or someone from the BPEL SE team take a look at this issue?
Problem 1.1: http://bt2ws.central.sun.com/CrPrint?id=6573809 Problem 1.2: Fixed in trunk. Problem 2: ?
Problem 1.1 in runtime is fixed now.
http://bt2ws.central.sun.com/CrPrint?id=6573809 is internal link. Its external link is the following http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6573809
Works for me on Build 200708080000
Does not work for me in build 200708150000. I attached a new java only test case. I'm not sure if this is triggering the same exact bug that using a .net test case did, but I figure this is a little more self-contained for the java crowd. In this example the problem is the BPEL editor does not include the second imported namespace from the java web service WSDL.
Created attachment 46684 [details] Java test for multiple schemas not working with BPEL editor/deployment
Reassigning to bpel editor for evaluation...
Am i right that bpel spec requires imports only for artifacts, referenced by bpel process DIRECTLY? In provided example case no bpel elements have a reference to elements from that schemas, only to wsdls which imports them. BPEL diagram editor automatically adds imports for all documents, containing definitions of elements used by bpel process. But as soon as no references to these schemas were found they remains unimported. We can change this behavior by enabling recursive imports. For example, when BPEL editor faces a need to import some WSDL, it also will add import for all other documents imported by this wsdl itself. This can help to solve this specific problem, but can cause some side-effects when some unused files will be added to deployment jars.
I added recursive import for schemas and wsdls.
Tested Jim Basilio's project on Netbeans/GlassFish nightly build 200709040000. Still cannot DEPLOY to glassfish WSDLs that import multiple schemas. When this issue is resolved, it would be very helpful if you could please provide the scenario you used to prove your results.
I disabled recursive schema imports because they caused P1 regression 114779. We should find another way to fix this problem.
Created attachment 51022 [details] project that fails deployment (BPEL SE problem)
Will not fix in NB 6.0, will address it in the next release.
Please look at this.
jim_basilio, I took a look @ the example you attached and came up with the following manual workaround. You need to edit the imported NewWebServiceService.wsdl file, adding namespace declaration for 'http://myothernamespace' to <definitions>; and edit the <xsd:import>'s schemaLocation attribute values, setting them to the local URIs of the corresponding schemes, that is 'NewWebServiceService.xsd_1.xsd' and 'NewWebServiceService.xsd_2.xsd'. This said, to fix the erroneous situation in this case, two steps need to be performed: 1) add the missing namespace declarations for imported schemes 2) correct the schema locations, setting them to local URIs After these steps I was able to successfully deploy and run the project.
The issue has been fixed by BPEL SE model change check-in. Sun internal INF=110351.
Make sure you deploy TestJavaWebservicec before deploying the composite app.
This issue is not fixed for 6.0, as older runtime version will be used for this release. Also, the integration does not seem to fix the namespaces issue, mentioned in the workaround I had suggested.
Changed target milestone from Sierra to 6.1 in order to display correct info on NB 6.1 dashboard
The build process for BPEL projects has been overhauled, more proper catalog support was one of the changes. The issue should be fixed now.
Tested attached projects using Build 200810130101 and the compapp failed to deploy with following error. pre-init: init-private: init-userdir: init-user: init-project: do-init: post-init: init-check: init: init-deploy: deps-jar: init: Building jar: C:\bpprojects\deploy\BPELMissionControl\build\SEDeployment.jar dist_se: Expanding: C:\bpprojects\deploy\BPELMissionControl\build\SEDeployment.jar into C:\Users\ggenipudi\Documents\NetBeansProjects\CompositeApp1\src\jbiServiceUnits\BPELMissionControl Moving 1 file to C:\Users\ggenipudi\Documents\NetBeansProjects\CompositeApp1\src\jbiServiceUnits\BPELMissionControl Moving 1 file to C:\Users\ggenipudi\Documents\NetBeansProjects\CompositeApp1\src\jbiServiceUnits\META-INF\BPELMissionControl deps-javaee-jar: jbi-build: Building jar: C:\Users\ggenipudi\Documents\NetBeansProjects\CompositeApp1\build\BCDeployment.jar Validating CompApp project... Generating Service Engine Service Units... Resolving connections... Writing connections out to connections.xml... Generating Service Assembly jbi.xml... Merging component projects' catalogs... [Fatal Error] catalog.xml:1:1: Premature end of file. Exception: A processing error occurred; org.xml.sax.SAXParseException: Premature end of file. Generating Binding Component Service Units... creating sun-http-binding.jar Creating/Updating CASA... Operation aborted due to : java.io.FileNotFoundException: C:\Users\ggenipudi\Documents\NetBeansProjects\CompositeApp1\src\jbiServiceUnits\catalog.xml (The system cannot find the file specified) Filtering Java EE Endpoints... Deleting: C:\Users\ggenipudi\Documents\NetBeansProjects\CompositeApp1\build\BCDeployment.jar Building jar: C:\Users\ggenipudi\Documents\NetBeansProjects\CompositeApp1\dist\CompositeApp1.zip Building jar: C:\Users\ggenipudi\Documents\NetBeansProjects\CompositeApp1\dist\CompositeApp1.zip run-jbi-deploy: [deploy-service-assembly] Deploying a service assembly... host=localhost port=4848 file=C:\Users\ggenipudi\Documents\NetBeansProjects\CompositeApp1/dist/CompositeApp1.zip [start-service-assembly] Starting a service assembly... host=localhost port=4848 name=CompositeApp1 ERROR: Successful execution of Start: CompositeApp1 WARNING: (JBIMA0405) Start of service assembly CompositeApp1 succeeded partially; some service units failed to start. * Component: sun-bpel-engine ERROR: (BPJBI-4001:BPELSE) BPJBI-7004:Service unit CompositeApp1-BPELMissionControl failed to load deployment C:\GlassFishESB\glassfish\domains\domain1\jbi\service-assemblies\CompositeApp1.1\CompositeApp1-BPELMissionControl\sun-bpel-engine : BPJBI-6024:Error while loading BPEL file C:\GlassFishESB\glassfish\domains\domain1\jbi\service-assemblies\CompositeApp1.1\CompositeApp1-BPELMissionControl\sun-bpel-engine\newProcess.bpel, Exception details are BPMOD-7001:Parsing error encountered in file :C:\GlassFishESB\glassfish\domains\domain1\jbi\service-assemblies\CompositeApp1.1\CompositeApp1-BPELMissionControl\sun-bpel-engine\META-INF\catalog.xml, message :Premature end of file. * Component: sun-http-binding INFO: (JBIMA0409) Lifecycle operation start succeeded for Service Unit CompositeApp1-sun-http-binding. Cleaning up... [stop-service-assembly] Stopping a service assembly... host=localhost port=4848 name=CompositeApp1 [shutdown-service-assembly] Shutting down a service assembly... host=localhost port=4848 name=CompositeApp1 [undeploy-service-assembly] Undeploying a service assembly... host=localhost port=4848 name=CompositeApp1 C:\Users\ggenipudi\Documents\NetBeansProjects\CompositeApp1\nbproject\build-impl.xml:213: Start failure. BUILD FAILED (total time: 4 seconds)
The error message suggests that the cause of the failure is the same as in issue 150164, which was fixed earlier today. Please verify that the fix helps here as well.
tested and verified using NetBeans IDE 6.1 (Build 200810140114) I am getting following error message during deploy [start-service-assembly] Starting a service assembly... host=localhost port=4848 name=TestForNBReproComposite ERROR: Successful execution of Start: TestForNBReproComposite WARNING: (JBIMA0405) Start of service assembly TestForNBReproComposite succeeded partially; some service units failed to start. * Component: sun-http-binding ERROR: (SOAPBC_INIT_1) HTTPBC-E00203: Initialization failed. java.lang.Exception: HTTPBC-E00142: Endpoint ''http://j2ee.netbeans.org/wsdl/testExternalWSDL,testExternalWSDLService,testExternalWSDLPort,Consumer'' cannot be activated because: an active endpoint deployed in composite application ''TestForNBReproComposite'', WSDL ''testExternalWSDL.wsdl'' is already using the same address ''http://GGenipudi-TM9.stc.com:18181/testExternalWSDLService/testExternalWSDLPort''. * Component: sun-bpel-engine INFO: (JBIMA0409) Lifecycle operation start succeeded for Service Unit TestForNBReproComposite-TestForNBRepro. Cleaning up... [stop-service-assembly] Stopping a service assembly... host=localhost port=4848 name=TestForNBReproComposite [shutdown-service-assembly] Shutting down a service assembly... host=localhost port=4848 name=TestForNBReproComposite [undeploy-service-assembly] Undeploying a service assembly... host=localhost port=4848 name=TestForNBReproComposite C:\bpprojects\INVALIDCATALOG\TestForNBReproComposite\nbproject\build-impl.xml:213: Start failure. BUILD FAILED (total time: 4 seconds)
Geetha, fix for 150164 (which cover this issue) was committed by Oct 16. You tested with build 200810140114. Please verify on later build.
Tested and verified using NetBeans IDE 6.1 (Build 200810140114) and gfesb\v2\nightly\20081022-0703 and was able to deploy the projects successfully.