Errors creating a Web Service Proxy using Microsoft WSDL.exe tool

I have deployed a BPEL process using JDeveloper. This process can be invoked from the BPEL console and completes as expected. I am trying to create a Web Service Proxy using the Microsoft WSDL.exe tool so that the process can be invoked from a Microsoft Word document. This process is based on the AutoLoan example in the Developer's Guide for Microsoft Office Interoperability B25781-01.
WSDL.exe returns the following error message
Error: There was an error processing 'http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0/HonorariumSmartDoc?wsdl'.
- The document at the url http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0/HonorariumSmartDoc?wsdl was not recognized as a known document type. The error message from each known type may help you fix the problem:
- Report from 'WSDL Document' is 'There is an error in XML document (19, 7).'.
- A schema with the namespace '' has already been added.
- Report from 'DISCO Document' is 'Discovery document at the URL http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0/HonorariumSmartDoc?wsdl could not be found.'.
- The document format is not recognized.
- Report from 'XML Schema' is 'Expected Schema root. Make sure that the root element is <schema> and the namespace is 'http://www.w3.org/2001/XMLSchema' for an XSD schema or 'urn:schemas-microsoft-com:xml-data' for an XDR schema. An error occurred at , (2, 2).'.
How do I resolve this error?

The WSDL file is below.
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions name="HonorariumSmartDoc" targetNamespace="http://xmlns.oracle.com/HonorariumSmartDoc" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.oracle.com/HonorariumSmartDoc" xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:client="http://xmlns.oracle.com/HonorariumSmartDoc">
- <types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/HonorariumSmartDoc" schemaLocation="HonorariumSmartDoc.xsd" />
</schema>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://erp.template.co.uk:8889/orabpel/xmllib/ws-addressing.xsd" />
</schema>
</types>
- <message name="HonorariumSmartDocResponseMessage">
<part name="payload" element="tns:HonorariumSmartDocProcessResponse" />
</message>
- <message name="HonorariumSmartDocRequestMessage">
<part name="payload" element="tns:HonorariumSmartDocProcessRequest" />
</message>
- <message name="WSARelatesToHeader">
<part name="RelatesTo" element="wsa:RelatesTo" />
</message>
- <message name="WSAReplyToHeader">
<part name="ReplyTo" element="wsa:ReplyTo" />
</message>
- <message name="WSAMessageIDHeader">
<part name="MessageID" element="wsa:MessageID" />
</message>
- <portType name="HonorariumSmartDocCallback">
- <operation name="onResult">
<input message="tns:HonorariumSmartDocResponseMessage" />
</operation>
</portType>
- <portType name="HonorariumSmartDoc">
- <operation name="initiate">
<input message="tns:HonorariumSmartDocRequestMessage" />
</operation>
</portType>
- <binding name="HonorariumSmartDocBinding" type="tns:HonorariumSmartDoc">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="initiate">
<soap:operation style="document" soapAction="initiate" />
- <input>
<soap:header message="tns:WSAReplyToHeader" part="ReplyTo" use="literal" encodingStyle="" />
<soap:header message="tns:WSAMessageIDHeader" part="MessageID" use="literal" encodingStyle="" />
<soap:body use="literal" />
</input>
</operation>
</binding>
- <binding name="HonorariumSmartDocCallbackBinding" type="tns:HonorariumSmartDocCallback">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="onResult">
<soap:operation style="document" soapAction="onResult" />
- <input>
<soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle="" />
<soap:body use="literal" />
</input>
</operation>
</binding>
- <service name="HonorariumSmartDocCallbackService">
- <port name="HonorariumSmartDocCallbackPort" binding="tns:HonorariumSmartDocCallbackBinding">
<soap:address location="http://set.by.caller" />
</port>
</service>
- <service name="HonorariumSmartDoc">
- <port name="HonorariumSmartDocPort" binding="tns:HonorariumSmartDocBinding">
<soap:address location="http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0" />
</port>
</service>
- <plnk:partnerLinkType name="HonorariumSmartDoc">
- <plnk:role name="HonorariumSmartDocProvider">
<plnk:portType name="tns:HonorariumSmartDoc" />
</plnk:role>
- <plnk:role name="HonorariumSmartDocRequester">
<plnk:portType name="tns:HonorariumSmartDocCallback" />
</plnk:role>
</plnk:partnerLinkType>
</definitions>

Similar Messages

  • 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>

  • Error creating a web service client from th WSDL document (soamanager)

    Hello everyone,
    we have generate with the wizard a web-service using the function module BAPI_CONTROL_RECIPE_GET_LIST. Then we have generated with SOAMANAGER the end point. As test, we have used a web-service explorer of Eclispe and we can retrieve without problems the data.
    Then we wanted to generate the web-servcie client with Eclipse Galileo (3.5.0) wiith the server GlassFish v2.1 Java EE 5 we first installed the WSIT jars, in order to support WS-RM protocol
    We have started the generation based on the document obtainend within the soamanager under the "Open WSDL document for selected binding" link.
    We have tried it several times and we always got the following error is:
    IWAB0399E Error in generating Java from WSDL: WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy):
    faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.: <br>
        WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
    at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
    at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
    at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
    at java.lang.Thread.run(Unknown Source)
    Do you know if we took the right document in order to generate the web-service client? Do we need to have some specifics settings in the configurations of th endpoint? (provider security, transport settings, etc...?)
    If needed, or if someone would be nice enough to try to generate it on its side, I can post here the whole wsdl document, but due to its length, I first wait your comments.
    Thanks a lot in advance for your feed-back
    best regards
    Pierre-André
    addtions:
    maybe this should have been better posted within the forum Service-Oriented Architecture than standards?
    I forgot to mention the following threads, which seems to me to be somehow in this direction. But I do not get really how I could use them, or how is is releated.
    Edited by: Pierre-andre Jacquod on Sep 23, 2009 4:02 PM

    Hi,
    I am facing the same issue while generating the client java class from IBM RAD 6.0.
    Here is the error I am getting.
    WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
         [java] at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
         [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
         [java] at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
         [java] at java.lang.Thread.run(Thread.java:571)
    Please guide me to resolve this issue.
    Thanks & Regards,
    Vijay

  • Problem creating a web service PROXY from a wsdl file/URL

    Hi,
    I am experiencing problems when I want to import a WSDL file for creating a proxy object.
    When I import the WSDL file from URL I get an error like this: <b>404   Not Found
    The requested resource does not exist.</b>
    Then, I  try to create it from a file, but I get other error:
    <b>Document not found (path o:\BCS.WSDL, error code 7</b>
    The error code 7 indicates <b>unknown error</b>
    Any help?.
    thanks in advance.
    Eduardo.

    Hi,
    I've done the same from other ECC6.0 System and everything was working perfetly, why all this can happen?
    I've ckecked the activation of the proxy objects, traces, etc... and it's the same in both systems, what more should i check?
    Thanks in adavance.

  • Create a Web Service to connect a third party tool using ABAP.

    Hi Guru's,
    I wanted to create a web service to access a third party tool for fetching data from it. Can anyone guide me on how to do that and what are the basic needs that we should have to use Web services? To execute a web service, do we need a J2EE engine?
    Thanks & Regards,
    Veerabhadra Rao A.

    Hi Rich,
    Thanks for your immediate response.
    Can you please explain me the technical point of view for fetching the data from a third party application using web service? Which method would be correct for this (i.e., BAPI/FM/FG/Message Interface)? What is the step by step process to fetch data? If I use a function module, how do I pass the data to the web service? Can you give me some more inputs to it?
    Please help.
    Thanks & Regards,
    Veera.

  • Help: Creating web service proxy using JAXB generated domains

    Hi,
    I'm currently doing some investigation considering the use of web services (BPEL) as a complete application backend.
    The application should contain a pojo facade which communicates with some web service proxies. By making a datacontrol
    of the pojo facade, I'm able to expose methods to the client layer.
    I generated my domain objects by using the JAXB Compilation option in JDeveloper. By using that, a java class can be generated
    based on an XSD. Disadvantage of this use, seems to be the fact that the ObjectFactory class, generated by JAXB, is overwritten
    each time I create java classes from an XSD.
    Q1: Is there a solution to prevent the ObjectFactory class to be overwritten? I also could decide not to use it.
    After the domain objects are created, I want to call the actual webservice and receive the response by using the JAXB marshaller
    and unmarshaller. Problem here is:
    Q2: How do I (manually?) create a proxy which calls the web service, by using the domain objects generated by JAXB?
    Q3: An important requirement is that it needs to be simple to switch from several environments (eg from development to test). How
    can I fulfill this requirement in a nice, solid solution?
    Any tips working with web services as the backend layer are welcome!
    JDeveloper 10.1.3.4
    ADF Faces/JSF
    BPEL
    Thanks,
    Koen Verhulst

    repost.

  • 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....

  • 11G - XDB Native Web Services - how to create a web service proxy

    Hi,
    I am working on XDB Native web Services (http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28369/xdb_web_services.htm#CHDDBCHB). I want to create a proxy web service for orawsv service (http://server:port/orawsv?wsdl), which is protected by an user/password
    In Jdeveloper 10133:
    + copy orawsv wsdl (http://server:port/orawsv?wsdl) in local file
    + create a proxy web service form the local wsdl (from the wizard)
    + implement the client (http://www.oracle.com/technology/obe/11gr1_db/datamgmt/xmldb2_b/xmldb2_b.htm)
    ==> OK
    In Jdeveloper 11g
    + copy orawsv wsdl (http://server:port/orawsv?wsdl) in local file
    + create a proxy web service form the local wsdl (from the wizard)
    + how to implement the client : there is no method to set a password
    any ideas?
    Thanks for your help,
    Cyryl
    Edited by: cbalmati on Oct 21, 2008 6:26 AM

    I'm working on getting a proxy web service working in 11g and the contents of this thread is close to answering my question.
    The web service proxy is accessing a service that requires a SOAP Security header.
    In looking at the previous post, I thought that by using the BindingProvider API I could add the security settings. But when I invoke the proxy I consistently get the following error response from the (PeopleSoft) web service: "com.sun.xml.ws.client.ClientTransportException: request requires HTTP authentication: Unauthorized'
    In contrast to that error, when I use JDeveloper's HTTP Analyzer, I get a successful response from the web service. Below is what the raw HTTP looks like:
    POST https://isiswebdev.services.wisc.edu:7002/PSIGW/PeopleSoftServiceListeningConnector HTTP/1.1
    Content-Type: text/xml; charset=UTF-8
    Host: isiswebdev.services.wisc.edu:7002
    SOAPAction: "CI_U_FA_CSA_STDTA_CI_G.V2"
    Content-Length: 548
    X-HTTPAnalyzer-Rules: 1
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:ns2="http://xmlns.oracle.com/Enterprise/Tools/schemas/M183895.V1">
    <env:Header>
    <ns1:Security>
    <ns1:UsernameToken>
    <ns1:Username>UserName</ns1:Username>
    <ns1:Password>XXXXXXX</ns1:Password>
    </ns1:UsernameToken>
    </ns1:Security>
    </env:Header>
    <env:Body>
    <ns2:Get__CompIntfc__U_FA_CSA_STDTA_CI>
    <ns2:EMPLID>012345678912</ns2:EMPLID>
    </ns2:Get__CompIntfc__U_FA_CSA_STDTA_CI>
    </env:Body>
    </env:Envelope>
    Here's the Java code that I'm using to try to make the same call:
    public void callIWebservice(String emplId){
    cSA_STDNT_DATA = new CSA_STDNT_DATA();
    CI_U_FA_CSA_STDTA_CI_PortType port = cSA_STDNT_DATA.getCI_U_FA_CSA_STDTA_CI_Port();
    Map<String, Object> requestContext = ((BindingProvider)port).getRequestContext();
    requestContext.put(BindingProvider.USERNAME_PROPERTY, "UserName");
    requestContext.put(BindingProvider.PASSWORD_PROPERTY,"XXXXXXX");
    GetCompIntfcUFACSASTDTACITypeShape CiType = new GetCompIntfcUFACSASTDTACITypeShape();
    EMPLIDTypeShape emplIDType = new EMPLIDTypeShape();
    emplIDType.setValue(emplId);
    CiType.setEMPLID(emplIDType);
    try {
    GetCompIntfcUFACSASTDTACIResponseTypeShape response = port.getDATA(CiType);
    System.out.println(response.getCUMGPA());
    } catch (M464939V1 e) {
    System.out.println(e.getFaultInfo());
    But, alas, I just get the ClientTransportException.
    Is the Bindingprovider interface the correct way to add the soap security headers? Or am I following the wrong path?
    Any help will be greatly appreciated.

  • Error when running Web Service Proxy from JDev (running publisher report)

    Hello.
    I would like to call publisher report from forms, so i was using this instructions:
    http://www.oracle.com/technology/products/xml-publisher/docs/Forms_BIP_v21.pdf
    When i test my Web Service Proxy, i get this warning:
    WARNING: The received SOAP fault contains non standard fault element: "{http://xml.apache.org/axis/}hostname". This element will be ignored.
    javax.xml.rpc.soap.SOAPFaultException: oracle.apps.xdo.webservice.exception.OperationFailedException: PublicReportService::generateReport failed: due to oracle.apps.xdo.servlet.CreateException: Report definition not found:/Path/Employees.xdo
    at oracle.j2ee.ws.client.StreamingSender._raiseFault(StreamingSender.java:555)
    at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:396)
    at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
    at bip_webservice.proxy.runtime.PublicReportServiceSoapBinding_Stub.runReport(PublicReportServiceSoapBinding_Stub.java:290)
    at bip_webservice.proxy.PublicReportServiceClient.runReport(PublicReportServiceClient.java:105)
    at bip_webservice.proxy.PublicReportServiceClient.main(PublicReportServiceClient.java:79)
    What is wrong? Did anyone try those instructions?
    Thanks.

    I am getting the same error. What was the solution that worked for you? Please help

  • Error creating a web service in NWDS SP18.

    Hello,
      I created a web service DC. It works fine when I test this with Web Services Navigator. I get the output as expected. But when I test it with Enterprise Portal Web Services Checker in NWDS, I get this error:
    "The SOAP Message returned is not well formed
    com.sap.engine.services.webservices.jaxm.soap.accessor.NestedSOAPException: Unable to create message from source"
    When I tried creating a web service using a simple J2EE-->EJB Module project, added to an EAR project and deployed, I see the same error. In both cases am able to successfully test on Web Services Navigator...
    Any body let me know how to create a web service in NWDS SP 18...
    Thanks
    Srinivas

    http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/f272e75d-0501-0010-1786-ab6ed3496bb1&language=en

  • Error creating a Web Service. Help!

    Hi, I'm triying to create a web service but when I try to test it or execute, it gives me this error:
    ORA-20001: The webservice was unreachable because either the URL you supplied was invalid, your environment requires a valid proxy server address for HTTP requests, or a wallet needs to be configured for HTTPS requests.
    Error testing service.
    The syntax is correct. The problem is that I can't create or config a Wallet, I read the tutorial to create a wallet but I can't upload it.
    Please I need help.

    Want to give it more than 3 minutes after asking before you expect an answer? No kidding it isn't answered yet!

  • Test web service proxy using EJB session bean client...

    Hello!
    I am following this blog /people/abdelmorhit.elrhazi/blog/2009/10/30/how-to-consume-an-inbound-backend-web-service-in-nwdsjboss-environment to create a EJB session bean client to access the web service proxy...
    The blog is not very clear. Where should I be deploying the web service proxy and the EJB session bean (web service client) ? on the PI 7.1 ?
    How to find out the URL for the wsdl ?
    Thanks

    > The blog is not very clear. Where should I be deploying the web service proxy and the EJB session bean (web service client) ? on the PI 7.1 ?
    "To deploy your web service proxy and session bean, right click on your JBoss server in the Servers view, and click on Add Remove Projects, add you ear file and click finish."
    You need a JBoss server.

  • Error creating a web service standalone proxy

    Hi all,
    I'm new with Sap Netweaver Developer Studio (SNDS), so sorry if the question is too easy.
    I wuold create a stand alone proxy for a web service created by a function module in R3.
    I follow the help of SNDS but the project doesn't compile. The error is
    This compilation unit indirectly references the missing type com.sap.engine.lib.xml.parser.tokenizer.XMLTokenReader (typically some required class file is referencing a type outside the classpath)     ZhrWsStrAnagInd2.java     AnagIndStandAloneProxy/src/com/capitalia/webservice/anagind/types/p1     line 0
    Where I can find this package? or the problem is another?
    thanks for any help,
    enzo

    Hi Enzo,
    Add <Install folder of Netweaver developer Studio>\SAP\JDT\eclipse\plugins\com.sap.tc.ap\comp\SAP_BUILDT\DCs\sap.com\tc\bi\xml\_comp\gen\default\public\def\lib\java\sapxmltoolkit.jar to classpath of your project (hope you know how to do it).
    Best regards, Maksim Rashchynski.

  • Creating a Web Service Proxy for a transaction with Microsoft Visual Studio

    Hi experts out there,
    I have created a simple transaction which I'd like to call as a webservice. Getting the WSDL from an authenticated browser (from which I started the xMII Workbench) works fine. But when I try to create a Web Reference within my Visual Studio project I only get the following output:
    "XacuteWS" Description
    Methods
    Xacute ( LoginName As string ,  LoginPassword As string ,  InputParams As InputParams ) As Rowset
    I think this is because my visual studio is not authenticated with the xMII server. So is there any way to achieve this? I have to find a way to generate a .NET proxy for out xMII web services because otherwise it would be too complicated to use the web services from within our .NET applications.
    Thanks in advance for any hint on this topic!
    Achim

    Two comments:
    1) The generated proxy looks correct.  If you explore the generated code for the InputParams object and the Rowset object, they should represent the incoming and outgoing data structures for your transaction.  If not, and if you are returning an XML property type from the transaction, be sure that you have used the "Assign Reference Document" technique to tell MII what the structure of your outgoing document is (there are a few other discussion threads on that topic).
    2) Personally, I find it much easier to consume MII services from .NET code using a URL-based technique instead of a SOAP based technique.  Invoke the "Runner" servlet (see the documentation) and you'll get an XML document back, that will always be in the MII Rowsets/Rowset/Row format.  Also, it is "self describing" because it includes Column metadata information.  It is very trivial to load this into a .NET XmlDocument object and parse/process it.  In fact, doing a similar approach, I've been able to make MII services appear as ADO.NET tables/stored procedures to .NET code.
    Rick

  • Internal error when downloading web service proxy jars

    Hi,
    I have a web service created from a stateless Java class in OC4J 10.1.2. I access the web page of the service and can download the WSDL and test the services, but if I try to download the compiled or source JAR files of the client proxy I get this:
    500 Internal Server Error
    java.lang.NullPointerException     at oracle.wsdl.toolkit.util.JarUtil.addFileEntry(JarUtil.java:105)     at oracle.wsdl.toolkit.util.JarUtil.createJar(JarUtil.java:34)     at oracle.j2ee.ws.BaseWebService.generateClientStubJar(BaseWebService.java:1555)     at oracle.j2ee.ws.BaseWebService.doGetClientJar(BaseWebService.java:1469)     at oracle.j2ee.ws.BaseWebService.doGet(BaseWebService.java:1142)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    I ccan find both the java and class files at %OC$J_HOME%\j2ee\home\application-deployments\myapp\myapp2006\temp\__java_stateless_rpc...(packages)...\proxy
    So I have the impression that the problem comes at packaging files into a JAR file.
    I've noticed the class names are very long because they include the full package route changing dots for underscores, which in my case results in class names of up to 64 characters (excluding extension and separator dot). Also the proxy directory where those files are created is very deep because after the __java_stateless_rpc directory the full package structure is repeated twice. I've detected that Windows Explorer does not allow me to delete, edit or view properties of those class and source files with names of 64 characters or more under the proxy directory, which for those cases means a complete path of over 256 characters.
    I'm not sure if this is the cause, but anyway I don't like those very long class names, is there any way of instructing the servlet to use other name generation scheme?
    Regards

    Hi,
    It seem that I was right and the length of the paths where in the heart of the problem. I've moved my oc4j directory to the root of my filesystem and the problem has dissapeared.
    Anyway, I find that name scheme very ugly and also ackward to use in the client, I could probably edit the sources myself but having to do so each time something changes...
    I'd propose that the servlett replicated the package structure under which the beans are originally, thus creating a more natural and logical structure with much shorter names.
    Maybe the path under __java_stateless_rpc could also be shortened.
    Regards

Maybe you are looking for