Bug 779601 (SOA-1971)

Summary:	JBPM-2812: Timer does not take leaving transition defined at super-state
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Martin Weiler <mweiler>
Component:	JBPM - within SOA, JBPM - standalone	Assignee:	trev <tkirby>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 CP02	CC:	dlesage
Target Milestone:	---
Target Release:	4.3 CP04 ER1
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1971
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-25 10:20:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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