NonStop SOAP 4.1 User's Manual

[options] include the following:
-o<output location>
specifies the output location where the service skeleton files must be generated.
-g
generates the client stubs and the service skeleton files. This option can be used only
if the –ss option is specified.
-f
flattens the generated files.
-or
overwrites the existing files.
-wv <version>
specifies the WSDL file version.
-d <databinding_option>
specifies that the databinding option must be used. NonStop SOAP 4 provides the
axisdatabinding (adb) databinding option to generate the service skeleton files
in the C programming language. If you do not want to use the databinding option,
use the -d none option.
NOTE: Databinding is an option provided by NonStop SOAP 4 that helps the XML
schema parsing process. By default, the WSDL2C tool develops services with the
databinding option set to axisdatabinding (adb).
-ss
generates the service skeleton files.
-uri <wsdl_path>
specifies the location of the WSDL file.
For example, use the following commands to generate the service skeleton files:
OSS> export NSSOAP_HOME=/usr/tandem/nssoap/t0865h01
OSS> WSDL2C –o "/home/nssoap/test/client" –ss –d adb
–uri "/home/nssoap/test/services/test_service/SoapPW_test.wsdl"
where,
/home/nssoap/test/client
is the output location.
-uri /home/nssoap/test/services/test_service/SoapPW_test.wsdl
specifies the WSDL Web address provided to the WSDL2C tool.
5. On successful execution, the following service skeleton files are generated under the src
directory in the location specified in the -o option of the WSDL2PWY command:
• Service skeleton source file to implement your application business logic.
• Header file that holds the declarations for the functions generated in the service skeleton
source file.
• Data binding header files that hold declarations for the data structures present in the
WSDL schema.
NOTE: If the -o option is not specified, the files are generated in the src directory under
the current directory.
214 NonStop SOAP Tools