aspose file tools*
The moose likes Web Services and the fly likes Import Schmea vs elements in wsdl Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Import Schmea vs elements in wsdl" Watch "Import Schmea vs elements in wsdl" New topic
Author

Import Schmea vs elements in wsdl

Tom Boyce
Greenhorn

Joined: Jul 03, 2003
Posts: 24
I've seen two ways of doing this. You can import schema's and not have any element tags defined directly in the wsdl or you can define all your element tages between the schema tags. My questions is, do these cause different behaviors when the wsdl is used to build a cosuming client? In other words, if I have an operation called createForm defined in my wsdl, so I want an operation in the generated code to produce an operation method with a footprint like: createForm(String, String, String) Name, Address, Phone

To clairfy the two choices of wsdl construction, this is
<element name="resolveIncident">
<complexType>
<sequence>
<element name="name" type="xsd:String"/>
<element name="address" type="xsd:String"/>
<element name="phone" nillable="true" type="xsd:string"/>
</complexType>
</element>

or

<xsd:schema>
<!xsd:import namespace="http://www.forms.com" schemaLocation="http://10.1.1.1:80/formsweb/schema/service/NEWFORMService.xsd"/>
</xsd:schema>

where the schema would contain the elements above.

Ivan Krizsan
Ranch Hand

Joined: Oct 04, 2006
Posts: 2198
    
    1
Hi!
Extracting the type definitions to a separate XML schema document would be considered refactoring, as far as I know.
It should have no impact on the users of the WSDL document, as far as generation of client artifacts (code and interfaces etc) is concerned.
Best wishes!
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Import Schmea vs elements in wsdl