maxOccurs issue

I have the below WSDL . The problem here is that WSDL2java does not bother about the MaxOccur .Which means for any value of maxoccur more than 1,it considers as unbound. Is this an error ?

For example in the below WSDL empSkills elelement has a maxOccur ="2" ,but WSDL2java converts this as maxOccur=unbound . After deploying the application ,when i try to hit the end point URI i get the WSDL with empSkills element representing maxOccurs=unbound.

ENVIRONMENT: Axis 1.4,Weblogic 8.1

<?xml version="1.0" encoding="UTF-8"?>

<wsdl:definitions name="EmployeeSearch" targetNamespace="http://myroots.employee.com.in" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ama="http://myroots.employee.com.in">
  <wsdl:types>
      <xsd:schema targetNamespace="http://myroots.employee.com.in">
      <xsd:complexType name="EmployeeInput">
       <xsd:sequence>
            <xsd:element maxOccurs="1" minOccurs="1" name="empId" type="xsd:string" ></xsd:element>
</xsd:sequence>
          </xsd:complexType>
     <xsd:complexType name="EmployeeDetails">
      <xsd:sequence>
            <xsd:element maxOccurs="1" minOccurs="1" name="empId" type="xsd:string" ></xsd:element>
            <xsd:element maxOccurs="1" minOccurs="1" name="empName" type="xsd:string" ></xsd:element>
            <xsd:element maxOccurs="1" minOccurs="1" name="empDesig" type="xsd:string" ></xsd:element>
            <xsd:element maxOccurs="1" minOccurs="1" name="empOccupation" type="xsd:string" ></xsd:element>
<xsd:element maxOccurs="2" minOccurs="0" name="empSkills" type="xsd:string" ></xsd:element>
</xsd:sequence>
      </xsd:complexType>
     </xsd:schema>
  </wsdl:types>
  <wsdl:message name="EmployeeInput">
    <wsdl:part name="EmployeeInput" type="ama:EmployeeInput"/>
  </wsdl:message>
  <wsdl:message name="EmployeeDetails">
    <wsdl:part name="EmployeeDetails" type="ama:EmployeeDetails"/>
  </wsdl:message>
  <wsdl:portType name="EmployeePortType">
    <wsdl:operation name="getEmployeeDetails">
      <wsdl:input message="ama:EmployeeInput"/>
      <wsdl:output message="ama:EmployeeDetails"/>
    </wsdl:operation>
  </wsdl:portType>
  <wsdl:binding name="EmployeeBinding" type="ama:EmployeePortType">
    <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="getEmployeeDetails">
      <wsdlsoap:operation soapAction="http://localhost:7001/test/services/EmployeeSearch/GetEmployeeDetails" style="rpc">
        <wsdl:input>
          <wsdlsoap:body parts="EmployeeInput" use="literal"/>
        </wsdl:input>
        <wsdl:output>
          <wsdlsoap:body parts="EmployeeDetails" use="literal"/>
        </wsdl:output>
      </wsdlsoap:operation>
    </wsdl:operation>
  </wsdl:binding>
  <wsdl:service name="EmployeeSearch">
    <wsdl:port binding="ama:EmployeeBinding" name="EmployeeBinding">
      <wsdlsoap:address location="http://localhost:7001/test/services/EmployeeBinding"/>
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>

Hi!

Bala'J'i Rags wrote:I have the below WSDL . The problem here is that WSDL2java does not bother about the MaxOccur .Which means for any value of maxoccur more than 1,it considers as unbound. Is this an error ?

No. So far, I haven't seen any utility program like WSDL2Java that generates code for boundary checking.
If you want total control of the WSDL, you should deploy your own WSDL, instead of letting the server generate one. In your Java code, you specify the presence of an existing WSDL by using the wsdlLocation attribute in the @WebService or @WebServiceProvider annotations.
Best wishes!

Thanks for the quick reply Ivan.

Actually Axis1.4 comes with utility -Wsdl2Java which autogenerates stub/skeleton given a WSDL file. Since i am using a Top down approach and iam using jdk1.4..iam

handicapped with this issue.

Where should i give the wsdl location in the program.Can you suggest some sample code snippet

Thanks for your time..