History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: TAV-694
Type: Bug Bug
Status: Resolved Resolved
Resolution: By Design
Priority: Major Major
Assignee: Tom Oinn
Reporter: Stian Soiland-Reyes
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
myGrid

t2: Conditionals fire even on errors

Created: 2007-12-17 10:27   Updated: 2008-03-13 18:32
Component/s: t2 maelstrom
Affects Version/s: 1.7
Fix Version/s: 1.7.1

Time Tracking:
Not Specified


 Description  « Hide
The Conditional Branching example does not work, because both constants fire, and one of them is picked by semi-random as the result.

The reason is that the conditional fireing still fires even on an error. A dummy workflow with a string constants "Coordinated from" a beanshell script that does Thread.sleep(5000), shows that coordination works in principle.

However, if the beanshell is changed to throw an Exception, the string constant will still be produced.



 All   Comments   Work Log   Change History   Version Control      Sort Order: Ascending order - Click to sort in descending order
Tom Oinn - 2008-03-13 18:32
This is correct behaviour in T2 in terms of existing code. This is because errors at the moment get turned into error tokens and passed out in the data stream, the stream completes so the condition is satisfied. We need to implement the workflow / orchestration level failure mode but this particular behaviour is not a bug.