Bug 303783 - connecting message flow to pool causes stack overflow
Summary: connecting message flow to pool causes stack overflow
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BPMN (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-24 11:36 EST by Kachel_Bac CLA
Modified: 2012-01-06 13:57 EST (History)
0 users

See Also:

Attachments
the Stacktrace (93.11 KB, text/plain)
2010-03-16 05:49 EDT, Kachel_Bac CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kachel_Bac CLA 2010-02-24 11:36:26 EST 
Build Identifier: 20090920-1017

Connecting a task with another pool via a message flow results in a stack overflow and eclipse crashes.

Problem is not only related to Black-Box pools. The error will occur whether there are activities in the second pool or not. All you have to do for a crash is  to connect the task with the pool itself.


Speculation: The Problem may be caused by an inconsistence in the model. Pool does inherit from MessageVertex in the ecore but not in the xsd.

Reproducible: Always

Steps to Reproduce:
1.Create a new diagramm and open it with the diagramm-editor.
2.Create a new pool.
3.Klick on "Message Connection" in the palette.
4.Klick on the task in the first Pool and connect it with the second pool (the pool itself not a task in it).
Comment 1 Kachel_Bac CLA 2010-03-16 05:49:48 EDT 
Created attachment 162147 [details]
the Stacktrace

Added an Attachment with the ErrorLog of such an error