Enhance the GWS server application to be WS-I compliant (recommended)

Important: You must be able to change all the Client applications that access your migrated Genero Web Services (GWS) Server.

If you use the Literal styles now available in GWS 2.x for your Web Service, your application will be WS-I compliant. However, the migration techniques still use the RPC/Encoded style (Only RPC/Encoded was supported in GWS 1.3x.). If you can change all the client applications that access your migrated GWS Server, we recommend that you enhance the GWS Server application to be WS-I compliant.

Replace the publishing functions in the GWS Server application, but omit the setInputEncoded and setOutputEncoded lines. The resulting style will be Literal.
The enhanced GWS Server will have a new RPC/Literal WSDL that must be used to regenerate the client stub with the fglwsdl tool:
```
fglwsdl -o NewClientstub http://localhost:8090/MyCalculator?WSDL
```
Compile that new client stub, and re-link it with the GWS Client application. This operation must be repeated for each Client application accessing that service.
Third party Client applications must also be changed to use the new WSDL.