OER: Generate Web Service Proxy REX in JDeveloper

Hi,
I want to generate a Web Service Proxy for REX (OER version 11.1.1.5.0) using JDeveloper 11.1.1.5.0. I am using JAX-RPC Weblogic Style. When I start the Web Service Proxy Generator it fails with the following error:
"The WSDL document contains the following errors:
Operation "assetTypeTabsRead" and "assetTabApprove" have conflicting SOAPAction avlues. Do not overload any operation or given unique SOAPAction value to each operation binding.
And many more (42481) ...."
I am looking for the correct way to generate a Service Proxy foor REX and JDeveloper. Any help is appreciated.
Best regards,
Sjoerd
Edited by: Sjoerd Aalbers on Dec 11, 2011 2:18 PM

'Generate Web Service Stub/Skeleton' option in 10.1.2, was replaced by 'Generate Web Service Proxy' in 10.1.3

Similar Messages

Error when generating Web Services Proxy for SCA Application Module

Hello,
I'm trying to create Web Services for a simple Application Module with JDeveloper 11g (11.1.1.3.0).
I start a new ADF Project, I create an Application Module as simple as possible : it contains only a simple View Object on the DEPT Entity.
On my Application Module, I choose "Service Interface" and I add my View Object in the service interface.
I test my Web Service in the Embedded Weblogic Server, it works well. (I succeed in using the Get operation, for example).
But when I try to generate a Web Service proxy (right-click on the WSDL File -> Generate Web Service Proxy), It always fail with such errors :
oracle.jdeveloper.webservices.tools.WsdlValidationException: Error creating model from wsdl "file:/C:/JDeveloper/mywork/ApplicationAppelServiceSCA/Model/src/model/common/AppModuleService.wsdl": 'unset' is already defined'Bytes' is already defined'ref' is already defined'Duration' is already defined'Types' is already defined'Character' is already defined'type' is already defined'Day' is already defined'nestedInterfaces' is already defined'Date' is already defined'datagraph' is already defined'Type' is already defined'Integer' is already defined'ModelsType' is already defined'ChangeSummaryType' is already defined'instanceClass' is already defined'Month' is already defined'DataObject' is already defined'javaClass' is already defined'LongObject' is already defined'DateTime' is already defined'dataObject' is already defined'YearMonth' is already defined'ShortObject' is already defined'Long' is already defined'types' is already defined'JavaInfo' is already defined'IntObject' is already defined'Boolean' is already defined'DoubleObject' is already defi...
Can someone help me to understand this error ?
i never manually edited the WSDL File, so I don't understand why the generated WSDL or XSD files might contain errors.
Thanks for your Help,
Laurent

We have the same problem, and the problem was in the xsd import:
The wdsl import a schema that import other schema, the second import use a relative path, that was wrong.
So check the xsd import sequence....

Is it possible to rename a property when generate web service proxy?

We have issue to generate client proxy because of following schema:
<xs:complexType name="Provider">
<xs:sequence>
<xs:element minOccurs="0" name="SSN" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="Ssn" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
This is from our vendor's wsdl file. Two "ssn" with different case are intentionally kept for backward compatibility. Is there a way to get around the issue? Here is the error message:
Caused by: java.lang.IllegalArgumentException: trying to create the same field twice: ssn
     at com.sun.codemodel.JDefinedClass.field(JDefinedClass.java:419)
     at com.sun.codemodel.JDefinedClass.field(JDefinedClass.java:390)
     at com.sun.tools.xjc.generator.bean.field.AbstractFieldWithVar.createField(AbstractFieldWithVar.java:72)
     at com.sun.tools.xjc.generator.bean.field.SingleField.<init>(SingleField.java:89)
     at com.sun.tools.xjc.generator.bean.field.SingleField.<init>(SingleField.java:76)
     at sun.reflect.GeneratedConstructorAccessor175.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at com.sun.tools.xjc.generator.bean.field.GenericFieldRenderer.generate(GenericFieldRenderer.java:64)
     at com.sun.tools.xjc.generator.bean.field.DefaultFieldRenderer.generate(DefaultFieldRenderer.java:79)
     at com.sun.tools.xjc.generator.bean.BeanGenerator.generateFieldDecl(BeanGenerator.java:754)
     at com.sun.tools.xjc.generator.bean.BeanGenerator.generateClassBody(BeanGenerator.java:542)
     at com.sun.tools.xjc.generator.bean.BeanGenerator.<init>(BeanGenerator.java:242)
     at com.sun.tools.xjc.generator.bean.BeanGenerator.generate(BeanGenerator.java:182)
     at com.sun.tools.xjc.model.Model.generateCode(Model.java:286)
     at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:252)
     at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:85)
     at com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.bind(JAXBModelBuilder.java:134)
     at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildJAXBModel(WSDLModeler.java:2255)
     at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:194)
     at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:140)
     at com.sun.tools.ws.wscompile.WsimportTool.buildWsdlModel(WsimportTool.java:261)
     at oracle.jdevimpl.webservices.tools.weblogic.JDevWsimportTool.buildWsdlModel(JDevWsimportTool.java:381)
     at oracle.jdevimpl.webservices.tools.weblogic.JDevWsimportTool.buildWsdlModel(JDevWsimportTool.java:344)
     at oracle.jdevimpl.webservices.tools.weblogic.JDevWsimportTool.access$000(JDevWsimportTool.java:91)
     at oracle.jdevimpl.webservices.tools.weblogic.JDevWsimportTool$1.derrive(JDevWsimportTool.java:161)
     at oracle.jdevimpl.webservices.tools.weblogic.JDevWsimportTool$1.derrive(JDevWsimportTool.java:157)
     at oracle.javatools.util.deferred.DerivedCache$CachedResource.get(DerivedCache.java:144)

I tried to add a binding file to change one of the ssn to ssn1. Now The error message changed to "[ERROR] Two declarations cause a collision in the ObjectFactory class." We noticed if we generate the client proxy with default setting. It works fine (for other web services). Once we start to customize the generated code by changing package name or in this particular case change property name, Jdeveloper starts to complain the name collision. Does anyone know how to solve this? We prefer not to rename those names since there are too many name collisions. Besides the generated code will deviate from document too much if we try to rename those names with conflict.

Uniqueness Constraint Violation When Generating Web Service Proxy

JDeveloper 10.1.3.2 & 10.1.3.3
I'm receiving an error message that a class has already been gerated when attempting to use JDeveloper to create the stubs for a web service from the wsdl & xsd's. The problem seems to center on the declaration for the faults in one xsd file:
=========================
     
     <xs:element name="userLookupFault" type="tns:testFaultType"/>
     <xs:element name="testFault" type="tns:testFaultType">
          <xs:annotation>
               <xs:documentation>testFault should be the 'default' fault type for faults that are not categorized
                    into more specific faults.</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="testFaultType">
          <xs:sequence>
               <xs:element name="message" type="xs:string" nillable="true" minOccurs="0" maxOccurs="1"/>
               <xs:element name="timestamp" type="xs:dateTime" nillable="false" minOccurs="1" maxOccurs="1"/>
          </xs:sequence>
     </xs:complexType>
=========================
Apparently because the userLookupFault and testFault elements are both of type testFaultType JDeveloper attempts to create the testFaultType class twice. I've been able to get the proxy files to generate if I change one of the elements to a different type:
=========================
     <xs:element name="userLookupFault" type="tns:userLookupFaultType"/>
     <xs:complexType name="userLookupFaultType">
          <xs:sequence>
               <xs:element name="message" type="xs:string" nillable="true" minOccurs="0" maxOccurs="1"/>
               <xs:element name="timestamp" type="xs:dateTime" nillable="false" minOccurs="1" maxOccurs="1"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="testFault" type="tns:testFaultType" />
     <xs:complexType name="testFaultType">
          <xs:sequence>
               <xs:element name="message" type="xs:string" nillable="true" minOccurs="0" maxOccurs="1"/>
               <xs:element name="timestamp" type="xs:dateTime" nillable="false" minOccurs="1" maxOccurs="1"/>
          </xs:sequence>
     </xs:complexType>
=========================
Upon review I see that the wsdl files that fail to generate attempt to use both userLookupFault and testFault but those that use only one generate successfully.
Has anyone else experienced this issue?
Is there a reason two faults cannot be of the same type?

WSDLs were supplied by third party managing the web service I am attempting to generate the proxies for. I'm unsure of the method used to create the WSDL files.

Error While generating Web Service Proxy using Web Service Action in MII 12

Hi All,
We are using the Web Service action block in BLS transaction to call a web service from an external legacy system. When we provide the WSDL in the action block configuration and click Next we can see the Port and Operation of the web service which we have selected and finally clicked on Finish. On clicking Finish it is giving an error "[Fatal Error] :-1:-1: Premature end of file." and no web service request/response structures are being generated.
The WSDL file is attached herwith. Please check and provide the solution. We are using MII 12.2 SP02 with latest patch.
An error message is also added to the NetWeaver log as below:
XmlProxy Error: Premature end of file.
[EXCEPTION]
org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at com.sap.lhcommon.schema.XmlHelper.loadDocument(XmlHelper.java:38)
at com.sap.lhcommon.schema.XmlHelper.loadDocumentNS(XmlHelper.java:28)
at com.sap.lhcommon.webservice.SoapMessage.getExampleXmlAsBytes(SoapMessage.java:103)
at com.sap.xmii.servlet.XmlProxy.service(XmlProxy.java:204)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
The wsdl file is as follows:
<wsdl:definitions
targetNamespace="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://pod.service.server.mesassembly.cis.cat"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:intf="urn:cat.cis.mesassembly.server.service.pod"
xmlns:impl="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
>
<wsdl:types>
   <schema targetNamespace="http://pod.service.server.mesassembly.cis.cat"
   xmlns="http://www.w3.org/2001/XMLSchema">
   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
   <complexType name="ProductionOrderDetailsInput">
   <sequence>
     <element name="detailsString" type="xsd:base64Binary"/>
     <element name="productionOrderNumber" nillable ="true" type="xsd:string"/>
     <element name="fullExplosionFlag" type="xsd:string"/>
   </sequence>
   </complexType>
   <complexType name="ProductionOrderDetailsReceipt">
   <sequence>
     <element name="errorMessage" nillable="true" type="xsd:string"/>
     <element name="valid" type="xsd:boolean"/>
   </sequence>
   </complexType>
   </schema>
</wsdl:types>
<wsdl:message name="processOrderDetailsResponse">
<wsdl:part name="podReturn" type="tns:ProductionOrderDetailsReceipt" />
</wsdl:message>
<wsdl:message name="processOrderDetailsRequest">
<wsdl:part name="input" type="tns:ProductionOrderDetailsInput" />
</wsdl:message>
<wsdl:portType name="PodService">
    <wsdl:operation name="ProcessOrderDetails" parameterOrder="input">
      <wsdl:input message="impl:processOrderDetailsRequest"
      name="processOrderDetailsRequest"/>
      <wsdl:output message="impl:processOrderDetailsResponse"
      name="processOrderDetailsResponse"/>
    </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ProdOrderDetailsSoapBinding" type="impl:PodService">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="ProcessOrderDetails">
      <soap:operation soapAction="http://pod.service.server.mesassembly.cis.cat/NewOperation"/>
      <wsdl:input name="processOrderDetailsRequest">
        <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
      </wsdl:input>
      <wsdl:output name="processOrderDetailsResponse">
        <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:service name="PodService_Service">
    <wsdl:port binding="impl:ProdOrderDetailsSoapBinding" name="ProdOrderDetails">
      <soap:address location="http:/localhost:8080/MESAssembly/services/ProdOrderDetails"/>
    </wsdl:port>
</wsdl:service>
</wsdl:definitions>

The WSDL file is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
targetNamespace="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://pod.service.server.mesassembly.cis.cat"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:intf="urn:cat.cis.mesassembly.server.service.pod"
xmlns:impl="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
>
<wsdl:types>
   <schema targetNamespace="http://pod.service.server.mesassembly.cis.cat"
   xmlns="http://www.w3.org/2001/XMLSchema">
   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
   <complexType name="ProductionOrderDetailsInput">
   <sequence>
     <element name="detailsString" type="xsd:base64Binary"/>
     <element name="productionOrderNumber" nillable ="true" type="xsd:string"/>
     <element name="fullExplosionFlag" type="xsd:string"/>
   </sequence>
   </complexType>
   <complexType name="ProductionOrderDetailsReceipt">
   <sequence>
     <element name="errorMessage" nillable="true" type="xsd:string"/>
     <element name="valid" type="xsd:boolean"/>
   </sequence>
   </complexType>
   </schema>
</wsdl:types>
<wsdl:message name="processOrderDetailsResponse">
<wsdl:part name="podReturn" type="tns:ProductionOrderDetailsReceipt" />
</wsdl:message>
<wsdl:message name="processOrderDetailsRequest">
<wsdl:part name="input" type="tns:ProductionOrderDetailsInput" />
</wsdl:message>
<wsdl:portType name="PodService">
    <wsdl:operation name="ProcessOrderDetails" parameterOrder="input">
      <wsdl:input message="impl:processOrderDetailsRequest"
      name="processOrderDetailsRequest"/>
      <wsdl:output message="impl:processOrderDetailsResponse"
      name="processOrderDetailsResponse"/>
    </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ProdOrderDetailsSoapBinding" type="impl:PodService">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="ProcessOrderDetails">
      <soap:operation soapAction="http://pod.service.server.mesassembly.cis.cat/NewOperation"/>
      <wsdl:input name="processOrderDetailsRequest">
        <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
      </wsdl:input>
      <wsdl:output name="processOrderDetailsResponse">
        <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:service name="PodService_Service">
    <wsdl:port binding="impl:ProdOrderDetailsSoapBinding" name="ProdOrderDetails">
      <soap:address location="http:/localhost:8080/MESAssembly/services/ProdOrderDetails"/>
    </wsdl:port>
</wsdl:service>
</wsdl:definitions>

Generating WEB SErvice proxy client error: (type octet-stream)

HI,
I'm trying to generate a proxy client from a WSDL which has an element defined as "octet-stream" from http://xml.apache.org/xml-soap
But I'm getting this error: "model error: type {http://xml.apache.org/xml-soap} octet-stream not found"
Some suggestion...what can i do.
thanks

HI,
I'm trying to generate a proxy client from a WSDL which has an element defined as "octet-stream" from http://xml.apache.org/xml-soap
But I'm getting this error: "model error: type {http://xml.apache.org/xml-soap} octet-stream not found"
Some suggestion...what can i do.
thanks

Latest jdeveloper 11.1.2.1.0 doesn't have Web service Proxy at Business Tie

I have installed the latest Jdeveloper 11.1.2.1.o and tried to create a wsrp consumer but couldn't find the "Generate Web Service Proxy" under Business Tier -> Web service as suggested in developer's guide.
Did I miss anything? Should I installed any extention patches? Is there any other way to create a wsrp consumer to test the sample wsdl generated from wsrp producer for .net?
Thanks,
Judy

All right, It turns out I have to install jdeveloper 11.1.1.6 instead.

Web Service Proxy client to invoke a Web service on SSL (Jdev 10.1.3.1)

Hi,
I have to develope a Web Service proxy client to invoke a web service on SSL. First I'm testing with OC4J 10.1.3.1 and JDEV 10.1.3.1 and did this:
1) Developed a basic PL/SQL Web Service with JDEV and publish on my standalone OC4J.
2) Made a test with a browser, it worked OK
3) Generated a proxy client from JDev 10.1.3.1 to invoke web service, it worked OK
--- Now make it work on SSL----
4) Then, added SSL configuration to oc4j , generated a certificate with keytool (updated server.xml, secure-web-site.xml), and shutting down and starting the OC4j instance.
5) Import the certificate to JAVA_HOME/jre/lib/security/cacerts
6) Test web service from browser on https and worked OK.
7) When tried to modified proxy client (generated in step 3) to make it work on SSL, I realized that just changing the END_POINT to the new url (https) it worked!
Questions----
1.- By default the proxy client generated from JDEV 10.1.3.1 knows how to deal with SSL conections?
2.- If I dont have previously the server certificate to import it into JAVA keystore (cacerts) how could I ,from proxy client code, capture it and import it before the validation occurs... because if the certificate is not in keystore , the program fails.
Thanks in advance
J.

Hi,
Could you please provide me with the steps necessary to create a web service proxy client through JDeveloper or any other mechanism when 2 way SSL (requiring client authentication) is enabled.
Thanks a lot in advance
Nilesh

Web Service Proxy errors out

Hi,
I have created web service proxy using Jdeveloper 10.1.3. My Jdeveloper is set to JDK 1.4.2_17. I can compile and run this web service proxy fine from Jdeveloper 10.1.3, but as soon as I deploy this to Oracle AS 10.1.2 on unix platform it errors out. This is the error message it gives. Why it doesn't find this class?
500 Internal Server Error
java.lang.NoClassDefFoundError: javax/xml/rpc/ServiceFactory
at aam.easproxy.proxy.InboundMsgSoap12Client.<init>(InboundMsgSoap12Client.java:17)
at index.jspService(_index.java:49)
[SRC:/index.jsp:13]
at com.orionserver[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Thanks,
AP

I think that the Web client proxy in JDeveloper 10.1.3 uses Java EE 1.4 libraries which you don't have on OAS 10.1.2.
You might want to look into hosting an OC4J 10.1.3 instance under OAS 10.1.2.

Distributing Oracle Web Services Proxy client?

Hi,
We built a web services client using Web Services Proxy tool in JDeveloper. We want to distribute it as a stand-alone application to our clients.
1. How can we determine the minimal set of JAR libraries required for the application to run?
2. Are there any licensing issues?
Thanks!
Simeon

If you are not using any ADF libraries there is no licensing concerns.

Problem while creating web service proxy in Jdeveloper 10.1.3

I am using Jdeveloper 10.1.3 to create a web service proxy so that I can track my request/response in HTTP Analyzer.
I am following the steps as mentioned in the follwoing uRL:
http://www.oracle.com/technology/obe/obe1013jdev/ws/wsandascontrol.htm
But I get the following warning while creating the web servcice proxy:
Generating proxy
WARNING: value type package prefix is ignored for the types defined in the schema that has same target namespace as the target namespace of wsdl: <my web service namepsace>
Proxy generation finished
After adding my code in the main methoad of proxy, I get the following error while compiling:
WARNING: Unable to connect to URL: <my web service proxy URL> due to java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
java.rmi.RemoteException: ; nested exception is:
HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
Please help as how to solve this.
Edited by: user11258855 on 02-Jul-2009 03:38

I am using Jdeveloper 10.1.3 to create a web service proxy so that I can track my request/response in HTTP Analyzer.
I am following the steps as mentioned in the follwoing uRL:
http://www.oracle.com/technology/obe/obe1013jdev/ws/wsandascontrol.htm
But I get the following warning while creating the web servcice proxy:
Generating proxy
WARNING: value type package prefix is ignored for the types defined in the schema that has same target namespace as the target namespace of wsdl: <my web service namepsace>
Proxy generation finished
After adding my code in the main methoad of proxy, I get the following error while compiling:
WARNING: Unable to connect to URL: <my web service proxy URL> due to java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
java.rmi.RemoteException: ; nested exception is:
HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
Please help as how to solve this.
Edited by: user11258855 on 02-Jul-2009 03:38

How to generate a Web Service Proxy for an ESB Routing Service?

Hi,
I have a SOAP service behind an ESB Routing Service. I am aware that i can call this ESB Service at the SOAP endpoint which can be found at the ESB Console after registration.
But, i want to invoke this service using a Web Service Proxy. My understanding is that, i need to use the WSDL generated for the ESB Routing Service to generate the proxy. The WSDL which can be seen in JDeveloper does not have any soap bindings and hence the tool does not allow me to generate any proxy.
Also, the two WSDLs whose URLs can be found at the ESB Console do not have the soap endpoint properties.
Can someone help me out on the same?
Thanks and regards,
Priya.

Priya,
Just take the SOAP endpoint and suffix it with a ?wsdl
Even the Concrete WSDL endpoint should be having a SOAP endpoint.
HTH
Uday

Can I load Java classes generated by the Web Service Proxy Wizard?

Hi gurus,
I am very new to Oracle JDeveloper and I have mainly used it to create and debug PL/SQL procedures. My client app is written in PowerBuilder 11 (Sybase), which claims that it will create a datawindow from a web service. Well, it turned out that PB can only handle simple stuff (it works with a very simple wsdl from the internet) but can't handle more complex ones that we need to use. So I am thinking about using JDev to create the web service proxy for the web service and then load it into Oracle as a Java stored procedure so that PowerBuilder can call the procedure. JDev succsfully generated the proxy and a few Java classes. My question is, do I need to load all the classes into the database? If yes, will the reference to the package work? For example, in a JDev generated class (the soap client class), it has package MyJdev.proxy; at the top. Or, will it work if I load all the classes included in package /MyJdev/proxy into the database?
Thank you very much for any help.
Ben

Thanks again, Bruce.
What I meant by SOAPElement is that one genereated Java class has this and this class also has the setter for this like this,
public void setSelection(javax.xml.soap.SOAPElement selection) {
this.selection = selection;
And here is the whole class,
public class CaseSearchByPartyRequest implements java.io.Serializable {
protected java.lang.String schemaVersion;
protected java.util.Calendar messageProducedDateTime;
protected javax.xml.soap.SOAPElement selection;
protected Restriction restriction;
public CaseSearchByPartyRequest() {
public java.lang.String getSchemaVersion() {
return schemaVersion;
public void setSchemaVersion(java.lang.String schemaVersion) {
this.schemaVersion = schemaVersion;
public java.util.Calendar getMessageProducedDateTime() {
return messageProducedDateTime;
public void setMessageProducedDateTime(java.util.Calendar messageProducedDateTime) {
this.messageProducedDateTime = messageProducedDateTime;
public javax.xml.soap.SOAPElement getSelection() {
return selection;
public void setSelection(javax.xml.soap.SOAPElement selection) {
this.selection = selection;
public Restriction getRestriction() {
return restriction;
public void setRestriction(Restriction restriction) {
this.restriction = restriction;
this.selection is the request that I think I need. And here is the static main method of the soap client class genereated.
public static void main(String[] args) {
try {
MyJdev.proxy.SoapClient myPort = new MyJdev.proxy.SoapClient();
System.out.println("calling " + myPort.getEndpoint());
// Add your own code here
} catch (Exception ex) {
ex.printStackTrace();
So, if I need to send the request to the web service, do I need to create the request, correct? I have done it through AQ and Messaging Gateway and works fine by manually creating the request xml in PL/SQL, but now I need to get it to work sychronously from the UI. I believe that I need the request (SOAPElement) because that is the only way that I can supply the parameters. I have not see any setters for the parameters other than some setters for user name and password.
Did I get something wrong here? If I don't supply the "selection", will JDev do it?
Thanks.
Ben

WEB SERVICE PROXY GENERATED USING 11.1.1.5.0 WSDL FAILS WITH 11.1.1.6.0

I have created a Web Service Proxy project in Jdev using BI Publisher 11.1.1.5.0 WSDL (ReportService). Generated ReportService_Service method uses following QName to get the port:
namespaceURI = "http://xmlns.oracle.com/oxp/service/v2"
localPart = "*v2/ReportService*"
Reports are generated successfully via Web Services when using BI Publisher 11.1.1.5.0 but when I use BI Publisher 11.1.1.6.x, it fails with this exception:
+'javax.el.ELException: javax.xml.ws.WebServiceException: {http://xmlns.oracle.com/oxp/service/v2}v2/ReportService is not a valid port. Valid ports are: {http://xmlns.oracle.com/oxp/service/v2}ReportService'+
I noticed that if the Web Service Proxy project is created using BI Publisher 1.1.1.1.6.0 WSDL (ReportService), the generated ReportService_Service method uses following QName to get the port:
namespaceURI = "http://xmlns.oracle.com/oxp/service/v2"
localPart = "*ReportService*"
We are supporting both 11.1.1.5.0 and 11.1.1.6.x, so is there a way to make it work with both.
FYI, I have tried removing v2 but then it only works with 11.1.1.6.0 and fails with 11.1.1.5.0.
+Caused By: javax.xml.ws.WebServiceException: {http://xmlns.oracle.com/oxp/service/v2}ReportService is not a valid port. Valid ports are: {http://xmlns.oracle.com/oxp/service/*v2}v2/*ReportService+

Dear,
found the solution (after trying last 1-2 days ...).
I was already using java 1.7 update 7.
I had to start java settings and to deselect Java 1.7.0_07.
Instead I selected latest Java version from Apple: 1.6.0_35-b10-428.
With these settings the installer finishes without crash.
Kind regards
Lorenz
Edited by: Lorenz on Oct 4, 2012 1:47 PM

Invoke Web Service Proxy in JDeveloper 11.1.2.3.0

Hello all,
I am using JDeveloper 11.1.2.3.0 to develop an android native application. For this purpose I was required to invoke a web service proxy in the application. I did so, but after the invocation process is complete, I am getting some errors in the "BPELProcess1.java" saying that "java.util.List is not a generic type". I am unable to find the cause of the errors. Please help.
Thanks in advance.

972388 wrote:
Thanks for your reply. I am getting the error in the code snippet "List<ProcessResponse.ArrayofObjects>". But if I change it to only "List", the error is resolved. But I am not quite sure I should change it, as because the former snippet is getting invoked automatically.I assume you problem occurs in on the mobile side? (ADF Mobile)
If so, are you using 'Web service client and proxy'? This is not supported in ADF Mobile.

OER: Generate Web Service Proxy REX in JDeveloper

Similar Messages

Maybe you are looking for