WSDL documents can use the <types> element as a container for datatype definitions that are relevant for exchanged Web services messages. For maximum interoperability and platform neutrality, WSDL uses the XML Schema Definition (XSD) language for datatype definitions. For example:
<definitions .... > <types> <xsd:schema .... />* </types> </definitions>
Before Enterprise Portal version 6.0, when you created Web service portlets or elements, the portal could not process WSDL files that used the complexType datatype format in the schema definition, resulting in the unsuccessful invocation of the Web service.
Enterprise Portal 6.0 and later can parse all WSDL files that use the complexType data type and other compound datatypes using the format that complies with WC3 XML Schema specification.
Parsing of Web services WSDL takes longer the first
time the WSDL is accessed.
You can define these datatypes within the <types> element to represent all or part of input or output messages. When you create Web services portlets and elements, you must provide inputs to these fields to generate input messages for the Web service’s invocation.
Verify that you can execute the Java compiler command
(javac) at the command line
from anywhere on the local machine.
| Copyright © 2004. Sybase Inc. All rights reserved. |
|
|
