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.
Bpel model do not process wsdl imported using XML cross-project references correctly. This problem prevented elements from imported wsdl, e.g., partnerlinktype to be used within bpel. Steps to reproduce this error: - create a Sync sample project - create a bpel project, BpelModule1 - open bpel project reference and add sync sample's bpel project - in BpelModule1, create a new empty WSDL, newWSDL.wsdl - open it in wsdl editor - right click on Imports to add WSDL import - select ByFile/SynchronousSample/ProcessFiles/SynchronousSample.wsdl - after the import, all child elements from SynchronousSample.wsdl are accessible in newWSDL.wsdl - in BpelModule1, create a new empty BPEL, newProcess.bpel - open it in bpel editor - right click on newProcess (in Navigator) to add Partner Link.. - it only see the local wsdl (newWSDL.wsdl) not SynchronousSample.wsdl from referenced project - if select newWSDL.wsdl, bpel do not process import to get partnerlinktype (see attached image) - right click on Imports (in Navigator) to add WSDL import - select ByFile/SynchronousSample/ProcessFiles/SynchronousSample.wsdl - after the import, elements from SynchronousSample.wsdl are NOT accessible in newProcess.bpel In general, the bpel editor do not process wsdl imported from XML cross-project reference correctly. The bpel editor does not process wsdl imported using XML cross-project references correctly. This problem causes elements from imported wsdl, e.g., partnerlinktype to be inaccessible within bpel. Steps to reproduce this error: 1. create a project reference - create a Sync sample project - create a bpel project, BpelModule1 - open bpel project reference and add sync sample's bpel project 2. test cross-project reference in WSDL - in BpelModule1, create a new empty WSDL, newWSDL.wsdl - open it in wsdl editor - right click on Imports to add WSDL import - select ByFile/SynchronousSample/ProcessFiles/SynchronousSample.wsdl - after the import, all child elements from SynchronousSample.wsdl are accessible in newWSDL.wsdl 3. test cross-project reference in BPEL - in BpelModule1, create a new empty BPEL, newProcess.bpel - open it in bpel editor - right click on newProcess (in Navigator) to add Partner Link.. - it only see the local wsdl (newWSDL.wsdl) not SynchronousSample.wsdl from referenced project - if select newWSDL.wsdl, bpel does not process import to get partnerlinktype (see attached image) 4. another way to add cross-project reference in BPEL - right click on Imports (in Navigator) to add WSDL import - select ByFile/SynchronousSample/ProcessFiles/SynchronousSample.wsdl - after the import, elements from SynchronousSample.wsdl are NOT accessible in newProcess.bpel In general, the bpel editor does not process wsdl imported from XML cross-project reference correctly.
Created attachment 48335 [details] partnerlinktype not accessible
Created attachment 48336 [details] test projects
Oops.. the first half of the problem description was a draft version..
Vladimir, I'll explain you more when I come back to the office.
Complete and aligned over all SOA modules solution of the problem requires deep analysis and more investigation. Now only partial solution can be implemented and it can cause other bugs. Will be addressed in Sierra timeframes. Marked as ENHANCEMENT.
fixed in sierra.