Using XSL Transformations for Web Service Component Tables
When performing a query on a component table that represents a web service method, the following steps are executed:
SELECT <column 1>[,...<column n>]
FROM <Web service component table name>
WHERE <column> = <value>
•You can define this XSL transformation in the Input XSL field in the last page of the New Web Service Component Wizard. This can be an URL, a location on the disk, or just a plain XSL string.
If you have simple type input parameters for an RPC-oriented method, then you do not need the Input XSL and steps 2) and 3) are skipped.
If you do not want to transform the input and no input XSL is provided, then steps 2) and 3) are skipped.
Suppose an external (non-USoft) Translation web service provides a Translate method that translates a text from one language to another language by using a LanguageMode parameter, for example: EnglishTOFrench.
Once you have defined a web service component table that represents the Translate (query) method of this web service, the following diagram shows the process described above.
In the example, the text "Hello World" is translated from English to French.
The important thing is that you must define the Input and Output XSL transformations, the other steps are carried out by USoft.
For more detailed examples of using XSL transformations for web service component tables, refer to the See Also topics.