Bug 779601 (SOA-1971) - JBPM-2812: Timer does not take leaving transition defined at super-state
Summary: JBPM-2812: Timer does not take leaving transition defined at super-state
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1971
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBPM - within SOA, JBPM - standalone
Version: 4.3 CP02
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP04 ER1
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-03 13:23 UTC by Martin Weiler
Modified: 2010-03-25 10:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-25 10:20:10 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1971 0 None None None Never

Description Martin Weiler 2010-03-03 13:23:27 UTC 
Date of First Response: 2010-03-08 23:06:12
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/581483
project_key: SOA

Platform issue for JBPM-2812
Comment 1 Martin Weiler 2010-03-03 13:24:01 UTC 
Link: Added: This issue depends JBPM-2812
Comment 2 David Le Sage 2010-03-09 04:06:12 UTC 
The draft text for the Resolved Issues section of the Release Notes states:


https://jira.jboss.org/jira/browse/JBPM-2812

    The hasLeavingTransition(String pTransitionName) was not inspecting the
    superstate leaving transition. This meant that the leaving transitions were never found
    by the subnodes. Users were alerted to this by the WARN messages in the log that stated:

    State(state1) has no leaving transition with name: timeout

    This has now been rectified so that the method does inspect the transition. As a result, the timer
    now takes the timeout transition attached to the superstate correctly.
Comment 3 Jiri Pechanec 2010-03-25 10:20:10 UTC 
Verified in ER1
Note You need to log in before you can comment on or make changes to this bug.