Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Tigerstripe » Modeling and generating simple interface operation messaging style
Modeling and generating simple interface operation messaging style [message #563241] Thu, 29 May 2008 02:49
Jerome Magnet is currently offline Jerome MagnetFriend
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
Previous Topic:Several questions as starting to use Tigerstripe
Next Topic:Several questions as starting to use Tigerstripe
Goto Forum:
  


Current Time: Sun Nov 23 10:00:46 GMT 2014

Powered by FUDForum. Page generated in 0.01631 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software