[
https://issues.jboss.org/browse/JBIDE-8042?page=com.atlassian.jira.plugin...
]
Robert (Bob) Brodt updated JBIDE-8042:
--------------------------------------
Fix Version/s: 3.2.0.CR1
Priority: Critical (was: Major)
This is a critical bug and has exposed other problems with variables that are considered
by the BPEL spec to be "implicit". That is, variables that are not explicitly
defined by a BPEL <variable> element, but rather as attributes of other BPEL
elements, which are: <forEach>, <onEvent> and <catch>
BPEL validator does not recognize counter variable inside forEach.
------------------------------------------------------------------
Key: JBIDE-8042
URL:
https://issues.jboss.org/browse/JBIDE-8042
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.2.0.Beta2, 3.2.0.CR1
Reporter: Marek Baluch
Assignee: Robert (Bob) Brodt
Priority: Critical
Fix For: 3.2.0.CR1
Attachments: Screen.png
The declared counter variable in the following code snippet is marked by the validator
red (see attached image).
CODE
...
<bpel:variable name="number" type="xsd:int"/>
...
<bpel:forEach parallel="no" counterName="counter"
name="ForEach">
<bpel:startCounterValue><![CDATA[1]]></bpel:startCounterValue>
<bpel:finalCounterValue><![CDATA[10]]></bpel:finalCounterValue>
<bpel:scope name="Scope">
<bpel:assign validate="no" name="Assign">
<bpel:copy>
<bpel:from variable="counter"/>
<bpel:to variable="number"/>
</bpel:copy>
</bpel:assign>
</bpel:scope>
</bpel:forEach>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira