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 200805120001) 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) If one customizing existing element with type referenced from other project then BPEL became uncompilable. Steps to reproduce from our spec: 1. Create SynchronousSample sample project in IDE. 2. Create a new BPEL Module BpelModule. 3. Create a new XML Schema file newXmlSchema.xsd under BpelModule. 4. Add a new complex type "newComplexType", just like the "simpleProcess" defined in SynchronousSample.xsd (use simple build-in "string" for example). 5. Set SynchronousSample BPEL Process reference to BpelModule. 6. Open SynchronousSample.xsd in Schema Editor. Import "newXmlSchema.xsd" as its Referenced Schema. 7. Customize the existing element "typeA". Change its type from "simpleProcess" to "newComplexType", which is defined at the Referenced Schema newXmlSchema.xsd. 8. Open SynchronousSample.bpel in BPEL Editor. Double-click Assign1 to open the bpel mapper. 9. In BPEL Mapper, drag "inputType" under "inputVar" in the left pane of Source tree pane to "resultType" under "outputVar" in the Destination pane (the right pane) if the connection is missing. 10. Save all changes. 11. Deploy (actually build is enough) SynchronousSampleApplication. After step 9 code looks like at screenshot attached. Build log attached as well.
Created attachment 61241 [details] screenshot
Created attachment 61242 [details] build log
I think it's not a bug at all. The described behavior is absolutely predictable. Actually the error appears in the BPEL not on the 9 step, but on the 7 step. The BPEL Editor doesn't prohibit crating invalid BPEL code. The problem is that the XML structure is changed, but the XPath expression isn't corrected. It's impossible to do an automatic correction of an XPath expression after an arbitrary change in an XML Schema. The only thing which seems confusing is that the BPEL mapper not clear enough informs about a problem. It's not good that the BPEL mapper doesn't show invalid assignments. Now it only complains with the help of a dialog with an error message. But such solution was approved as acceptable for now.
tested and verified using \\thumper\50builds\gfesb-sync\v2\nightly\20090105-0707 and the correct error dialog pops up.