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.
Steps to reproduce: - create a new bpel module project - add If activity to the diagram - put Empty activity into the If - move Empty to the "else" branch then move it back Result: Diagram becomes invalid because of empty <else></else> content in source. No way to improve the diagram via designer.
I don't think this is a bug. Error reported by validator is: C:/Documents and Settings/Mike/AsynchronousSample2/AsynchronousSample2/src/AsynchronousSample.bpel:51,9 cvc-complex-type.2.4.a: Invalid content was found starting with element 'empty'. One of '{"http://schemas.xmlsoap.org/ws/2004/03/business-process/":documentation, WC[##other:"http://schemas.xmlsoap.org/ws/2004/03/business-process/"], "http://schemas.xmlsoap.org/ws/2004/03/business-process/":targets, "http://schemas.xmlsoap.org/ws/2004/03/business-process/":sources, "http://schemas.xmlsoap.org/ws/2004/03/business-process/":condition}' is expected. Of the possible children, the one most important is condition. If user adds a condiition the IF will become valid. <if name="If2"> <condition>$inputVar.inputType/paramA</condition> <empty name="Empty4"/> </if> <if name="If1"> <condition>$inputVar.inputType</condition> <sequence name="Sequence1"> <empty name="Empty3"/> <empty name="Empty1"/> </sequence> <else> <empty name="Empty2"/> </else> </if>
Ok, I was wrong. I was not following scenario exactly. Filer of bug wants to make the IF valid by removing the empty ELSE element. I was not following the scenario, because I was making it valid by adding child to the ELSE element. If you follow scenario, you will find that you cannot remove the empty ELSE element once it has been constructed. This is the bug. The empty ELSE is not selectable or deletable.
of course the workaround is that the empty else can be deleted from source.
Fixed
verified in build 060925_1
see above