I think the externally visible aspect of a message exchange ends (by
definition) when messages are no longer being exchanged. The "exit" activity
seems to refer to a private aspect of the process's life-cycle, as there
does not seem to be a message exchange directly associated with this
activity. It seems to me that the rule of thumb should be that any activity
that does not directly involve message exchanges should not be considered
externally visible.
- Jim Clune
----- Original Message -----
From: "Yaron Y. Goland" <>
To: <>
Cc: <>; <>;
<>
Sent: Friday, May 20, 2005 10:43 AM
Subject: Re: [wsbpel] Issue 99 - Updated proposal for vote
My understanding of the purpose of the 'external behavior' profile is to
describe all actions that a process will undertake that can be viewed
externally to the process. The goal being to describe the order in which
a process expects to send and receive messages. A key part of describing
such a sequence is knowing when the sequence ends. Without the use of
the <exit> activity it is significantly more difficult to describe end
states, especially ones that represent an exception to the 'expected'
execution path.
Yaron
wrote:
