sca-assembly message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: ISSUE 47:Operation element for Interface
- From: Bryan Aupperle <aupperle@us.ibm.com>
- To: sca-assembly@lists.oasis-open.org
- Date: Mon, 2 Jun 2008 13:24:30 -0400
Upon further reflection o this issues,
the original proposal is not sufficient.
Suppose a service is bidirectional and
both the forward and callback interfaces have a cancel method that
need to be denoted as endsConversation in the SCDL. A single operation
child element is not sufficient to handle this case. We need operation
and callbackOperation child elements; each with the name, oneWay and endsConversatioon
attributes described in the original proposal.
Note that I am not suggesting
a complete replication of the interface definition, Only those operations
that need the SCA attributes would need to be listed in the SCDL.
When we discussed opening this issues,
the question was raised if we could extend the existing operation child
element of service and reference instead of adding an operation element
to interface. It seems more natural to me to have operations belong
to interfaces. However, if we go that direction, we still have to
address the callback problem above.
Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
Master Inventor
Research Triangle Park, NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]