| Modeling and generating simple interface operation messaging style [message #563241] |
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
|
|
|
Powered by
FUDForum. Page generated in 0.01905 seconds
] 
Search
Help
Register
Login
Home
