[jboss-jira] [JBoss JIRA] Updated: (BPEL-256) First activity of a flow has to have a defined target even if the containing flow element has a target

First activity of a flow has to have a defined target even if the containing flow element has a target ------------------------------------------------------------------------------------------------------ Key: BPEL-256 URL: http://jira.jboss.com/jira/browse/BPEL-256 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public(Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Santiago Erquicia Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA The first activity of a flow is forced to have targets even if the flow definition has targets already defined. This does not happen with the last activity of a flow, which doesn't have a source defined because the flow definition has a source defined. For example: <bpel:flow name="Flow1"> <bpel:targets> <bpel:target linkName="Link20"/> </bpel:targets> <bpel:sources> <bpel:source linkName="Link25"/> </bpel:sources> <bpel:links> <bpel:link name="Link21"/> <bpel:link name="Link27"/> <bpel:link name="Link28"/> </bpel:links> <bpel:assign name="InitializeCounter"> <!-- FIXTHIS --> <bpel:targets> <bpel:target linkName="Link20"/> </bpel:targets> <!-- ####### --> <bpel:sources> <bpel:source linkName="Link21"/> </bpel:sources> <bpel:copy> <bpel:from>0</bpel:from> <bpel:to part="count" variable="Count"/> </bpel:copy> </bpel:assign> ........... This extract of a bpel definition shouldn't require the target definition of InitializeCounter.