SoaML 1.0 FTF Avatar
  1. OMG Issue

SOAML — SoaML Issue - Service Interface applied to class and interface

  • Key: SOAML-23
  • Legacy Issue Number: 13818
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Cory Casanave)
  • Summary:

    SoaML specifies the use of the <<ServiceInterface>> stereotype on both classes and interfaces. In the case of ServiceInterface applied to a class there is a specific and potentially complex set of model elements that are required to complete the service interface specification (the class will, at minimum, realize and use UML interfaces and may have parts). When ServiceInterface is applied to a UML interface there is a different set of model elements (operations and receptions) – as a result there is a different structure and expectation of how each is specified. The unifying point is that they can both be used as the type of a ServicePoint or RequestPort. These two “flavors” of ServiceInterface are confusing to the user and inconsistently specified in the documentation. The documentation does not differentiate how to specify each flavor of ServiceInterface and is inconsistent about the base class for <<ServiceInterface>>.

    Either different stereotypes should be used (perhaps <<Provider>> & <<Consumer>> on interfaces per other issues) or the documentation should clearly distinguish <<ServiceInterface>>Class and <<ServiceInterface>>Interface.

  • Reported: SoaML 1.0b1 — Sat, 21 Mar 2009 04:00 GMT
  • Disposition: Resolved — SoaML 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT