3.9The Web Services

3.9.1Web services modeling

Design items

Interface.

Operation.

Operation parameters and return type.

Applicable stereotypes and modeling rules

• ClientWebService

« ClientWebService » stereotyped interfaces must have only one operation.

• ServerWebService

« ServerWebService » stereotyped interfaces must have only one operation. Moreover the « implementation » stereotype tagged value must not be empty.

Tagged values

• ClientWebService

• targetNamespace. The XML namespace of the WSDL
• url. URL of the presented web service
• clientPathTypeRetour : List VO package on the customer side.
• serverPathTypeRetour : List VO package on the server side.
• typeRetour : VO type.

• ServerWebService

• implementation: Implementation class of the presented service.

3.9.2General rules

• Web services must be contained within a « PK_SERVICE » stereotyped package.
• A web service name ends with ’Service’.
• The « implementation » tagged value may not be empty.
• The « url » tagged value may not be empty.
• The « clientPathTypeRetour » tagged value may not be empty.
• The Bo parameter must not have any association
• The « serverPathTypeRetour » tagged value may not be empty.
• The « typeRetour » tagged value may not be empty.

3.9.3Examples

• ClientWebService  

Specifies a service for interacting with the presented web service..

Figure 1 «ClientWebService» Applied Stereotype example

Figure 2 «ClientWebService» Tag parameter example

• ServerWebService

Specifies a service for the presented web service

Figure 3 «ServerWebService» Applied Stereotype example

Figure 4 «ServerWebService» Tag Implementation example