Error in building schema after publishing PL/SQLwebservice

Question

which return multiple rows. I am attaching the wsdl after generation please let me know if any wrong in wsdl. Procedure which is published is working fine in sql
<?xml version = '1.0' encoding = 'UTF-8'?>
<!--Generated by the Oracle JDeveloper Web Services WSDL Generator-->
<!--Date Created: Mon Feb 18 17:58:53 IST 2008-->
<definitions
name="EmployeeWebService"
targetNamespace="http://pimdb/EmployeeWebService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://pimdb/EmployeeWebService.wsdl"
xmlns:ns1="http://pimdb/EmployeeWebService.xsd">
<types>
<schema
targetNamespace="http://pimdb/EmployeeWebService.xsd"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="pimdb_EmployeeWebServiceImpl_getemplyeeTest_Out" jdev:packageName="pimdb" xmlns:jdev="http://xmlns.oracle.com/jdeveloper/webservices">
<all>
<element name="employeesdataOut" type="ns1:pimdb_EmployeewebserviceMytable"/>
</all>
</complexType>
<complexType name="pimdb_EmployeewebserviceMytable" jdev:packageName="pimdb" xmlns:jdev="http://xmlns.oracle.com/jdeveloper/webservices">
<all>
<element name="array" type="ns1:ArrayOfpimdb_GetemployeeMyrecordUser"/>
</all>
</complexType>
<complexType name="pimdb_GetemployeeMyrecordUser" jdev:packageName="pimdb" xmlns:jdev="http://xmlns.oracle.com/jdeveloper/webservices">
<all>
<element name="myIdNumber" type="decimal"/>
<element name="myName" type="string"/>
<element name="myHireDate" type="dateTime"/>
</all>
</complexType>
<complexType name="ArrayOfpimdb_GetemployeeMyrecordUser" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<complexContent>
<restriction base="SOAP-ENC:Array">
<attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="ns1:pimdb_GetemployeeMyrecordUser[]"/>
</restriction>
</complexContent>
</complexType>
</schema>
</types>
<message name="getemplyeeTest0Request">
<part name="inputName" type="xsd:string"/>
</message>
<message name="getemplyeeTest0Response">
<part name="return" type="ns1:pimdb_EmployeeWebServiceImpl_getemplyeeTest_Out"/>
</message>
<portType name="EmployeeWebServicePortType">
<operation name="getemplyeeTest">
<input name="getemplyeeTest0Request" message="tns:getemplyeeTest0Request"/>
<output name="getemplyeeTest0Response" message="tns:getemplyeeTest0Response"/>
</operation>
</portType>
<binding name="EmployeeWebServiceBinding" type="tns:EmployeeWebServicePortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getemplyeeTest">
<soap:operation soapAction="" style="rpc"/>
<input name="getemplyeeTest0Request">
<soap:body use="encoded" namespace="EmployeeWebService" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output name="getemplyeeTest0Response">
<soap:body use="encoded" namespace="EmployeeWebService" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
</binding>
<service name="EmployeeWebService">
<port name="EmployeeWebServicePort" binding="tns:EmployeeWebServiceBinding">
<soap:address location="http://kecoraclelab1.ad.infosys.com:7778/Phase2-WSDLInvoke-context-root/EmployeeWebService"/>
</port>
</service>
</definitions>

Answer 1

Hi Lokesh,
Iam not able to understand what you are trying to say. But my Input variable and Invoke Input variable are compatible, no problem on this. I got some clue from your reply.
Finally I got it worked by doing it in another way.
In my Invoking BPEL Process(ie. BPEL Process is trying to invoke the another BPEL Process using Partnerlink) wsdl I imported the partnerlink BPEL schema and it get solved my problem.
eg) <import namespace="http://xmlns.oracle.com/BpelProcessname" schemaLocation="ParnerLinkBPELSchema.xsd"/>
This can be usefull for others and I never did this to import the schema manually before, but it works without any errors.
Now only it causing this problem, whether it is any Jdeveloper issue.
And i tryed this using Jdev version 10.1.3.4.0, but still the same exception.
This workaround will usefull for others.
Thanks for your reply.
bye.....