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.
Build: \\thumper\50builds\gfesb\v2.1\main\nightly\20090413-0723 When an XSLT project use another WSDL from another project (i.e. BPEL) using Project Reference, it failed at deploy time. The error was that the application is trying to refer to the WSDL file in a location that does not exist. In this scenario, it is trying to reference the invokedbpel.wsdl file under a path with extra ‘src’ in the path: ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU "rpXSLT2BPEL_wsdl_ref_JBI-rpXSLT2BPEL_wsdl_ref": TRANSL-6001: Failed to parse transformmap descriptor: TRANSL-6009: Imported WSDL document does not exist at: C:\GlassFishESBV2.1\glassfish\domains\domain1\jbi\service- assemblies\rpXSLT2BPEL_wsdl_ref_JBI\rpXSLT2BPEL_wsdl_ref_JBI- rpXSLT2BPEL_wsdl_ref\sun-xslt-engine\..\..\InvokedBpel\src\invokedbpel.wsdl Where the actual location for the WSDL file are under: ..\..\ InvokedBpel\invokedbpel.wsdl (without the ‘src’). To reproduce: 1)Open the attached projects 2)Open the XSLT project’s properties, and make sure the referenced project (to BPEL project) is still valid. If not, remove it and add the BPEL project to the XSLT reference project again. 3)Save All. 4)Re-build all projects. 5)Deploy the JBI project The problem will then occur. (see attached projects and log file)
Created attachment 80287 [details] Project and log files
Vitaly, please take a look.
Richard from design point of view this issue is a duplicate of the issues: http://www.netbeans.org/issues/show_bug.cgi?id=153469 (fixed on 14th of April) and http://www.netbeans.org/issues/show_bug.cgi?id=157072 (fixed on 16th of April). I've gone through the your project to verify it. Some changes have to be done: First of all you don't include 4th project rp_BPEL_synchronous with Synchronous.xsd in result rpXSLT2BPEL_wsdl_ref\src\XSLT_WSDL.wsdl is not valid. Another point - because of 153469 - the import of the referenced resources has wrong location that is why it is required to recreate these imports (in our case it is invokedbpel.wsdl) Resulted jar is fine and contains all required artifacts and referenced resources are registered as expected in catalog.xml. But it is was observed that XSLT SE runtime doesn't support catalog.xml for the referenced resources. I've filled an issue against XSLT SE: https://open-esb.dev.java.net/issues/show_bug.cgi?id=1760. I'll stay this issue open until it will be fixed on runtime or special fix will done for the design side.
Issue depends on P2 enhancement on xslt runtime which is beyond the scope for GlassFishESB 2.1 release
Since runtime issue 1760 had been fixed. I've checked this with updated project. All works for me.
Created attachment 82465 [details] updated project
Fix does not make it to GFESB 2.1 release (build: 20090515-1455) - will be verified with future (2.1.1) release. This ticket has dependency on RT ticket 1760 which is moved to release 2.1.1.
Verified with build: 20091028-0719 Tested with the attached projects that contains resource to be referenced, and a newly created XSLT project that make references to both XSD and WSDL from the projects. Able to successfully build, deploy and run end-to-end with XSLT project.