Modeling Legacy Web Service Classes in Rational Software Architect

A web service class can be created by creating a WebService class (stereotype: <<webservice>>) via the Rational Software Architect user interface. For more information on working with the model in Rational Software Architect see the Working with the Cram Model in Rational Software Architect document.

A WebService class will:

• Generate DDL that causes the methods of the class to become callable by user ' WEBSVCS '.
• Generate an Axis 1.4 configuration file that makes the class available as a web service.

To add an inbound web service class to a package, select Add Class, WebService from the right-click context menu and name the class.

A WebService class can support one of the two styles of web services supported by specifying the Document_Type property on the Curam property tab for the class:

• RPC - specify the Document_Type property value as 2 - no (which is the default when 0 - unspecified is the value)
• Document-oriented web service (DOWS) - specify the Document_Type property value as 1 - yes

When creating a DOWS you control the processing of operation arguments and return values by specifying the property XML_Document:

• "Method parameters" - specify the XML_Document property value as 2 - no (which is the default when 0 - unspecified is the value)
• "XML document" - specify the XML_Document property value as 1 - yes

Since the above properties apply uniformly to all operations of that class you will need to model different classes when you have web services with different style requirements.