|
| Re: Sequence Diagram - return value on message [message #473012 is a reply to message #473011] |
Sun, 27 May 2007 15:53  |
 james bruck
Messages: 1724
Registered: July 2009 |
Senior Member |
|
|
Hi Andrew,
From a previous posting.... entitled "Messages with return value, local
variables"
After the OccurrencesSpecification of the return Message, you
could create another ExecutionOccurrenceSpecification on the return
lifeline.
That ExecutionOccurrenceSpecification could refer to an
ActionExecutionSpecification. That ActionExecutionSpecification would
refer to an AddStructuralFeatureValueAction. The StructuralFeature that
the
AddStructuralFeatureValueAction would refer to is the attribute owned
either by the Classifier that types the return lifeline or the classifier
that owns the interaction. To make the inputPin of the action correspond to
the return value of the operation,
create a ValuePin to refer to the valueSpecification. Also,
you could create an InstanceSpecification that corresponds to the
ValueSpecification of the argument corresponding to the return parameter.
That InstanceSpecification would stay around for the lifetime of the
interaction.
Regards,
- James
"Andrew Carton" <cartona@cs.tcd.ie> wrote in message
news:f3a1kf$lk0$1@build.eclipse.org...
> Hi,
>
> I was just wondering, is there any formal way of associating a return
> value of a return message with a previously sent synchronous message? The
> standard doesn't fully demonstrate how this is achieved. I know you can do
> it like..
> value := myOp(param1=whatever, param2=whatever)
> if you don't want to illustrate another return message. I would however
> like to associate the return message with a previous. Is it just the case
> that the next MessageOccurrenceSpecification with a Receive event is the
> actual return?
>
> Thanks,
> Andrew.
|
|
|
| Re: Sequence Diagram - return value on message [message #618152 is a reply to message #473011] |
Sun, 27 May 2007 15:53 |
james bruck
Messages: 1724
Registered: July 2009 |
Senior Member |
|
|
Hi Andrew,
From a previous posting.... entitled "Messages with return value, local
variables"
After the OccurrencesSpecification of the return Message, you
could create another ExecutionOccurrenceSpecification on the return
lifeline.
That ExecutionOccurrenceSpecification could refer to an
ActionExecutionSpecification. That ActionExecutionSpecification would
refer to an AddStructuralFeatureValueAction. The StructuralFeature that
the
AddStructuralFeatureValueAction would refer to is the attribute owned
either by the Classifier that types the return lifeline or the classifier
that owns the interaction. To make the inputPin of the action correspond to
the return value of the operation,
create a ValuePin to refer to the valueSpecification. Also,
you could create an InstanceSpecification that corresponds to the
ValueSpecification of the argument corresponding to the return parameter.
That InstanceSpecification would stay around for the lifetime of the
interaction.
Regards,
- James
"Andrew Carton" <cartona@cs.tcd.ie> wrote in message
news:f3a1kf$lk0$1@build.eclipse.org...
> Hi,
>
> I was just wondering, is there any formal way of associating a return
> value of a return message with a previously sent synchronous message? The
> standard doesn't fully demonstrate how this is achieved. I know you can do
> it like..
> value := myOp(param1=whatever, param2=whatever)
> if you don't want to illustrate another return message. I would however
> like to associate the return message with a previous. Is it just the case
> that the next MessageOccurrenceSpecification with a Receive event is the
> actual return?
>
> Thanks,
> Andrew.
|
|
|
Powered by
FUDForum. Page generated in 0.03671 seconds
] 
Search
Help
Register
Login
Home
