Eclipse Community Forums: Tigerstripe » Modeling and generating simple interface operation messaging style

Help

Home

Home » Archived » Tigerstripe » Modeling and generating simple interface operation messaging style

Show: Today's Messages :: Show Polls :: Message Navigator

Modeling and generating simple interface operation messaging style [message #10079]

Thu, 29 May 2008 02:49

Jerome Magnet

Messages: 14
Registered: July 2009

Junior Member

Hi,

I am trying to figure out the best approach to model the two most common
operation patterns (or MEP);
- one-way (In-only)
- request-response (In-Out)

The following is a simplified representation of these two operations:

One-way: void operation(input1, input2, inputN)
Request-response: void operation(input1, input2, inputN, output1, output2,
outputN)

Return is always void. The parameters can be a sequence of; Inputs, Ouputs
or both at the same time.
In the case of the One-way, a single request message is defined using the
input parameters
In the case of the Request-response, two messages are defined based on
appropriately identified parameters (In, Out, both/InOut).

Based on the Tigerstripe current capabilities I see the following
limitations:
- Editing a method of an interface (Session Facade) is limited; lack of
visibility of the parameters type and name (In, Out, InOut)
- Assigning stereotypes to each individual parameters
- Assigning various exceptions to a request-response operation

Let me know if I am correct in the above evaluation. It seems the best
approach would be to extend Tigerstripe with a special artifact type
(primary operation?), the same way as Query and UpdateProcedure are already
defined.

Thanks,
Jerome

Report message to a moderator

Re: Modeling and generating simple interface operation messaging style [message #10126 is a reply to message #10079]

Thu, 29 May 2008 09:26

Richard Craddock

Messages: 31
Registered: July 2009

Member

Hi Jerome,

not sure I fully understand your assessment of limitations:

> Based on the Tigerstripe current capabilities I see the following
> limitations:
> - Editing a method of an interface (Session Facade) is limited;
lack of visibility of the parameters type and name (In, Out, InOut)

From your next comment, I am assuming that you are adding a Stereotype to
each parameter to identify if it is In, Out, Inout ? If so is the issue
that you cannot see those Stereotypes when looking at the list of
parameters? We may be able to do someting with the display to improve this.

> - Assigning stereotypes to each individual parameters

This should be possible - is there something that doesn't work - or is it
just "fiddly"?

> - Assigning various exceptions to a request-response operation

Again this should be straightforward You should just need to select
exceptions that exist in your model. Can you expand on the problem?

Regards,

Richard

Report message to a moderator

Re: Modeling and generating simple interface operation messaging style [message #563289 is a reply to message #10079]

Thu, 29 May 2008 09:26

Richard Craddock

Messages: 31
Registered: July 2009

Member

Report message to a moderator

Previous Topic:	Several questions as starting to use Tigerstripe
Next Topic:	Generate XMI instead of UML

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 20:48:26 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter