Hi,
I have designed a test.wsdl and mine.xsd.
A part of my wsdl and xsd
doc is as below
xsd:schema targetNamespace="http://www.example.org/test/" xmlns:Q1="http://www.example.org/resource/Iternary">
<xsd:import schemaLocation="mine.xsd" namespace="http://www.example.org/resource/Iternary"></xsd:import>
<xsd:element name="OperationResponse"
type="Q1:booking_request">
</xsd:element>
<xsd:element name="OperationResponse"
type="Q1:reply_details">
</xsd:element>
</xsd:schema>
============================================================
A part of my .xsd document is..
<element name="booking_request" type="c:booking_request"></element>
<complexType name="booking_request">
<sequence>
<element name="card_details type="c:credit_card"></element>
.......
.......
.......
//There are some more complex types here
</sequence>
</complexType>
=====================================================================
When I used this to generate the client code
SOAPImpl.java has the request as
public void newOperation(org.example.www.resource.Iternary.Credit_card card_details,
.....
.....
org.example.www.resource.Iternary.holders.Flight_iternaryHolderflight2, org.example.www.resource.Iternary.holders.Personal_descriptionHolder newElement) throws java.rmi.RemoteException {
flight2.value = new org.example.www.resource.Iternary.Flight_iternary();
newElement.value = new org.example.www.resource.Iternary.Personal_description();
}
What are these new holder parameters generated?
Shouldnt I get a interface like
public void newOperation(org.example.www.resource.Iternary.booking_request)
since I have specified only one complex element as the input
Cheers,
Sam
