Creating a message flow instead of having a sequence flow

[GoogleCodeExporter]

What is the problem?
Out of the shape menu, create a new Task which relies to another pool. It
would create a sequenceflow between the two tasks. 

What should be done alternatively?
This is not correct, the right way would be creating a message flow between
the two tasks. To be independent from the stencil set, the 'can connect'
callback has be reimplement (this mtime maybe a little more performant than
last time).

Original issue reported on code.google.com by W.Tsches...@gmail.com on 21 Jul 2009 at 7:48

[GoogleCodeExporter]

Hi,

isn't the problem, that the semantic checker doesn't recognize that sequence 
flows between to pool aren't 
allowed?
The same problem is the sematic check of message flows between two tasks in 
only one pool.

Regards,
Thomas

Original comment by Thomas2...@gmail.com on 3 Dec 2009 at 5:25