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

Similar Messages

Error when creating Web Service Proxy

Hi',
I am creating a web service proxy to call a web service (OSB) "http://st-curriculum.oracle.com/obe/jdev/obe11jdev/ps1/webservices/ws.html#t5", I am making a client to call a OSB proxy and I am able to see the WSDL in the IE, however when I try to create a client using Jdev I get below error.
Please advice me.
Thanks
Yatan
oracle.jdeveloper.webservices.model.WebServiceException: Error creating model from wsdl "http://localhost:8001/xx/som/contracts/CustomerContract?wsdl": A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.TaskCompletionMessage" is already in use. Use a class customization to resolve this conflict.(Relevant to above error) another "TaskCompletionMessage" is generated from here.(Relevant to above error) another "SOMMessage" is generated from here.A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.SOMMessage" is already in use. Use a class customization to resolve this conflict.Two declarations cause a collision in the ObjectFactory class.(Related to above error) This is the other declaration.
     at oracle.jdeveloper.webservices.model.java.JavaWebService.createPortTypes(JavaWebService.java:1635)
     at oracle.jdeveloper.webservices.model.WebService.createServiceFromWSDL(WebService.java:2846)
     at oracle.jdeveloper.webservices.model.WebService.createServiceFromWSDL(WebService.java:2611)
     at oracle.jdeveloper.webservices.model.java.JavaWebService.<init>(JavaWebService.java:509)
     at oracle.jdeveloper.webservices.model.java.JavaWebService.<init>(JavaWebService.java:461)
     at oracle.jdeveloper.webservices.model.proxy.WebServiceProxy$ProxyJavaWebService.<init>(WebServiceProxy.java:2268)
     at oracle.jdeveloper.webservices.model.proxy.WebServiceProxy.updateServiceModel(WebServiceProxy.java:1701)
     at oracle.jdeveloper.webservices.model.proxy.WebServiceProxy.setDescription(WebServiceProxy.java:525)
     at oracle.jdevimpl.webservices.wizard.jaxrpc.proxy.ProxyJaxWsSpecifyWSDLPanel.setDescription(ProxyJaxWsSpecifyWSDLPanel.java:238)
     at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel.buildModel(SpecifyWsdlPanel.java:1109)
     at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel$5.run(SpecifyWsdlPanel.java:661)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
     at java.lang.Thread.run(Thread.java:619)
Caused by: oracle.jdeveloper.webservices.tools.WsdlValidationException: Error creating model from wsdl "http://localhost:8001/xx/som/contracts/CustomerContract?wsdl": A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.TaskCompletionMessage" is already in use. Use a class customization to resolve this conflict.(Relevant to above error) another "TaskCompletionMessage" is generated from here.(Relevant to above error) another "SOMMessage" is generated from here.A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.SOMMessage" is already in use. Use a class customization to resolve this conflict.Two declarations cause a collision in the ObjectFactory class.(Related to above error) This is the other declaration.
     at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.newWsdlValidationException(WsaAdaptor.java:825)
     at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.getSeiInfo(WsaAdaptor.java:515)
     at oracle.jdeveloper.webservices.tools.WebServiceTools.getSeiInfo(WebServiceTools.java:523)
     at oracle.jdeveloper.webservices.model.java.JavaWebService.getSeiInfo(JavaWebService.java:1741)
     at oracle.jdeveloper.webservices.model.java.JavaWebService.createPortTypes(JavaWebService.java:1496)
     ... 12 more
Caused by: oracle.j2ee.ws.common.tools.api.ValidationException: Error creating model from wsdl "http://localhost:8001/xx/som/contracts/CustomerContract?wsdl": A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.TaskCompletionMessage" is already in use. Use a class customization to resolve this conflict.(Relevant to above error) another "TaskCompletionMessage" is generated from here.(Relevant to above error) another "SOMMessage" is generated from here.A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.SOMMessage" is already in use. Use a class customization to resolve this conflict.Two declarations cause a collision in the ObjectFactory class.(Related to above error) This is the other declaration.
     at oracle.j2ee.ws.tools.wsa.jaxws.JaxwsWsdlToJavaTool.getJAXWSModel(JaxwsWsdlToJavaTool.java:664)
     at oracle.j2ee.ws.tools.wsa.WsdlToJavaTool.createJAXWSModel(WsdlToJavaTool.java:475)
     at oracle.j2ee.ws.tools.wsa.Util.getJaxWsSeiInfo(Util.java:1357)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at oracle.jdevimpl.webservices.tools.wsa.Assembler$2$1.invoke(Assembler.java:218)
     at $Proxy50.getJaxWsSeiInfo(Unknown Source)
     at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.getSeiInfo(WsaAdaptor.java:505)
     ... 15 more
Caused by: oracle.j2ee.ws.common.tools.api.ValidationException: A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.TaskCompletionMessage" is already in use. Use a class customization to resolve this conflict.(Relevant to above error) another "TaskCompletionMessage" is generated from here.(Relevant to above error) another "SOMMessage" is generated from here.A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.SOMMessage" is already in use. Use a class customization to resolve this conflict.Two declarations cause a collision in the ObjectFactory class.(Related to above error) This is the other declaration.
     at oracle.j2ee.ws.tools.wsa.SchemaTool.genValueTypes(SchemaTool.java:188)
     at oracle.j2ee.ws.tools.wsa.jaxws.JaxwsWsdlToJavaTool.getJAXWSModel(JaxwsWsdlToJavaTool.java:647)
     ... 24 more
Caused by: oracle.j2ee.ws.common.databinding.common.spi.DatabindingException: A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.TaskCompletionMessage" is already in use. Use a class customization to resolve this conflict.(Relevant to above error) another "TaskCompletionMessage" is generated from here.(Relevant to above error) another "SOMMessage" is generated from here.A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.SOMMessage" is already in use. Use a class customization to resolve this conflict.Two declarations cause a collision in the ObjectFactory class.(Related to above error) This is the other declaration.
     at oracle.j2ee.ws.common.tools.databinding.jaxb20.JAXB20TypeGenerator.generateJavaTypes(JAXB20TypeGenerator.java:120)
     at oracle.j2ee.ws.tools.wsa.SchemaTool.genValueTypes(SchemaTool.java:186)
     ... 25 more

Hi Yatan
The error is mostly there may be some Duplicate variable/schema element decalared in the wsdl or the xsd referred in the wsdl. Like in WSDL for any Operations, most of the times, we use input and outputs as complex xsd element. We declare these xsd in the same file or in another file and import that in the .wsdl file. So check or validate your XSD file for any Duplicates.
In JDeveloper itself, I think, you can open XSD or WSDL and validate it from right click menu options like that.
Thanks
Ravi Jegga

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

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

Error while creating web services proxy in Jdev. 10.1.3

Hello,
I created a web service using jdev.10.1.2 and created successfully a ws proxy with the the same version.
However when I try to generate a ws proxy using 10.1.3, I am getting error:
The WSDL document is invalid for the following reason:
the wsdl contains a mixture of uses- "literal" and "encoded" Only literal OR encoded is supported in a wsdl, not both.
What is the problem and how can I resolve this?
Thanks in advance.

I followed like what is mentioned in the document, however my return type is still object.
Below is my message part. Pasted at the bottom is my complete wsdl.
<message name="getEmpInfoXML0Response">
<part name="result" type="xsd:anyType" />
</message>
****************************** WSDL**************************************
<?xml version="1.0" encoding="UTF-8" ?>
- 
- 
- <definitions name="Portalws" targetNamespace="http://ws/bs/ew/EmpInfo.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://ws/bs/ew/EmpInfo.wsdl" xmlns:ns1="http://ws.bs.ew/IPortalws.xsd">
- <types>
<schema targetNamespace="http://ws.bs.ew/IPortalws.xsd" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://www.w3.org/2001/XMLSchema" />
</types>
- <message name="getEmpInfoXML0Request">
<part name="empno" type="xsd:string" />
</message>
- <message name="getEmpInfoXML0Response">
<part name="result" type="xsd:anyType" />
</message>
- <portType name="EmpInfoPortType">
- <operation name="getEmpInfoXML">
<input name="getEmpInfoXML0Request" message="tns:getEmpInfoXML0Request" />
<output name="getEmpInfoXML0Response" message="tns:getEmpInfoXML0Response" />
</operation>
</portType>
- <binding name="EmpInfoBinding" type="tns:EmpInfoPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="getEmpInfoXML">
<soap:operation soapAction="" style="rpc" />
- <input name="getEmpInfoXML0Request">
<soap:body use="encoded" namespace="Portalws" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
- <output name="getEmpInfoXML0Response">
<soap:body use="encoded" namespace="Portalws" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
- <service name="Portalws">
- <port name="EmpInfoPort" binding="tns:EmpInfoBinding">
<soap:address location="http://host:portt/WebService-PortalWS-context-root/Portalws" />
</port>
</service>
</definitions>

Occasional SOAP errors when making web service calls from C#

We have a C# application making web service calls to RFCs (non-NCO, SAP 4.7, WAS 6.40) and occasionally getting the following error:
The 'SOAP-ENV:Envelope' start tag on line '1' does not match the end tag of 'SOAP-ENV:Envel'. Line 1, position 34560.
This error happens randomly and can occur, not occur, and occur again for the exact same call (same data, same web service call). I anticipate that we might have a missing configuration on one of our application servers, but don't know where to tell BASIS to look. Any ideas or other help would be appreciated.

That's going to be difficult. The random nature of the error makes it impossible to reproduce (so far) in our Development and Test environments. Since the error is coming from the SAP side, I believe I would need a sniffer on each production application server in order to try to catch this and that would result in some very large log files. Is there any log file or other SAP transaction that might already be capturing these failures?

Compile error when using Web Services Proxy

I used the wizard and kept all default settings then I edited the <Port>.java class to make the actual invocation.
When I tried to compile the generated code I got 2 errors in the FaultMessage class about 2 missing Constructors:
Error(17,5): cannot find constructor Exception(java.lang.String)
Error(25,5): cannot find constructor Exception(java.lang.String,java.lang.Throwable)
Looking at the class hierarchy I noticed that FaultMessage extends from a Exception class which was generated by the Wizard so I decided to add the constructors there.
Once the .ctors are created it works as expected.
I'm posting this message anyway so it helps others if facing the same issue and to raise the question about why is this happening? Perhaps some wrong jars in my system? Aren't Jdeveloper generated classes supposed to work 'out of the box'?
Thanks,
MV

Are you sure that you have posted your question to the correct forum? This forum is only for Oracle Enterprise Manager related issues.

ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http

I am getting error message ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http PL/SQL package,
when browsed through some of the messages they point to setting Oracle Wallet Manager.
I am trying to connect
Any idea on how to resolve this issue ?
your input is appreciated.
Thanks
Ravi

Duplicate post ... please ignore.

Errors when processing web service call

Hello Experts,
Based on a requirement, I got a URL based on WSDL, using which I created a Consumer Proxy in SAP.
I created a Logical Port in SOA Manager with type selected as 'WSDL'.
When I'm trying to execute the proxy class to call the webservice using the logical port through SE80 it is throwing an error log as stated below.
1) SOAP:14 Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
2)Error when processing Web service call
3)Error when calling SOAP Runtime functions: Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
Kindly help me out.
Thanks,
Vamshi

Hi,
Check Anton's reply in this thread: External WS Consumption Issue
Also refer the below doc which may help you: Consume an External Web Service in a Nutshell with Good Old ABAP
Calling WebServices from ABAP via HTTPS
Regards,
Kiran

Serialization error when calling web service method

Hi,
In JDeveloper 10.1.3.1, I'm working on an EJB that will be deployed as a web service. There is a method in the EJB that is defined to return a generic Object, but in the implementation, it really returns one of several possible specialized bean objects. I can deploy the EJB successfully to IAS 10.1.3.1.
I created a web service proxy from the wsdl that was generated from deploying the EJB. Using the proxy, I try to call the EJB method and cast the method's return value to the bean object I know should be returned. However, I get an error like this:
java.rmi.ServerException:
start fault message:
Internal Server Error (serialization error: no serializer is registered for (class com.test.TestBean, null))
:end fault message
Does anyone know how this serialization error can be resolved? If I change the web service method signature to return the bean object that is actually being returned (instead of Object), then it works fine. But I want to be able to define the method to return a generic Object because I plan to make the method flexible enough to return several different types of bean objects. Whenever the client calls the method, it will know what is the actual object being returned and I had planned to cast the return value to its actual class.
Thanks for any ideas.

Well, I think so... I've followed all the steps, and my merged WSDL file seems like the one in page 12...
Any suggestion, please?
Thank you,

Creating Web Service Proxy From WSDL - Error SPRX046

We are attempting to create some Web Service proxy objects from some WSDL files. Some of the WSDL files contain message definitions with multiple parts such as
<i><wsdl:message name="GetNewSubmissionsResponse">
      <wsdl:part element="impl:Count" name="Count"/>
      <wsdl:part element="impl:MoreAvailable"       name="MoreAvailable"/>
      <wsdl:part element="impl:IRSData" name="IRSData"/>
      <wsdl:part element="impl:StateSubmissions" name="StateSubmissions"/>
   </wsdl:message></i>
This always generates the error message <b>SPRX046 - "
Msg Proxy generation terminated: Message must have exactly one part".</b>
Is this just a limitation with SAP Web AS? Has anyone dealt with this before? These WSDLs work in other environments (AXIS Java, XML Spy etc).
Thanks

It seems ABAP proxy only supports Document-Literal style WSDL. Document-literal style is supported by most Web services platforms, and is supposed to be most interoperable.
Per WS-I Basic Profile 1.0 (see [1])which provides interoperability guidance of using WSDL1.1, when the message part is defined using the @element attribute, the message can only be bound to so-called "document-Literal" style which in turn requires that the message contains only one part.The WSDL you provided violated the document-literal rules.
Have you tried to change the message definition a bit so it's BP conformant? Try defining a complex type for the subelements, then define an wrapper element to use that complex type, and finally let the message part to refer to the wrapper element. Something like,
<wsdl:message name="GetNewSubmissionsResponse">
<wsdl:part element="impl:GetNewSubmissionsResponseWrapper" name="myResponse"/>
</wsdl:message>

Validation error while creating Web Service Proxy.

Hi,
I'm trying to create Web Service Proxy. But I'm stuck with a Validation error
model error: type
+"{http://xmlns.oracle.com/2001/XMLSchema/DOM}+
+org.w3c.dom.Document" not found.+
I'm using "Create Web Service Proxy" wizard. There are 6 steps in creating proxy through JDev. wizard.
First step itself displaying the above validation error when I click on "Next" button.
Few points
We have created web service using "oracle.j2ee.ws.StatelessJavaRpcWebService" servlet
Thanks in advance.
-Sukumar

Hi,
It might be that the .net service which you have is not WS-I compliant. Can you first run WS-I Analyzer on the wsdl to see it the test passes.
Thanks,
Vishal

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>

Error when processing web service call

Hello Experts,
Based on a requirement, I got a URL based on WSDL, using which I created a Consumer Proxy in SAP.
I created a Logical Port in SOA Manager with type selected as 'WSDL', and didnot gave any authentication id or password in it.
When I'm trying to execute the proxy class to call the webservice using the logical port, it is asking me a prompt for Userid and Password, and when I press enter, it is throwing an error log as stated below.
SOAP:1,007 SRT: Unsupported xstream found: ("HTTP Code 401 : Unauthorized")
(Error when calling SOAP Runtime functions).
I think I configured the Logical port incorrectly. Is there any specific setting that I missed, I dont know.
Kindly help me out.
Thanks,
Mallik

Unsupported xstream found: ("HTTP Code 401 : Unauthorized")
Unsupported xstream means response received from service provider (host) is NOT in valid xml format (usually HTML). You will see this type of error when host or service you are trying to call return HTML (error pages etc).
HTTP Code 401 : Unauthorized : Clearly means that user/password for service provider is incorrect
[Click here|http://en.wikipedia.org/wiki/List_of_HTTP_status_codes] to understand all HTTP code
I am closing this thread, if you have any question post new question in forum.
Regards,
Gourav

Validation Failed when creating Web Service Proxy

Hi
I am having trouble creating a web service proxy in JDeveloper (11.1.1.3). When I enter the endpoint URL (which is a https WSDL file). I get the following error:
No WSDL document could be found at https://host:port/.../.././...wsdl.
I can open the WSDL in SOAP UI and it accesses it fine and I can call the service within.
When I put it in a browser I need to enter the authentication details before I can view the WSDL.
But I can't get to the next step in the Web Service Proxy wizard, I've had a look in the threads before an couldn't find any help.
Is there anyone who can help me with this?
Regards
Saheem

Thanks John but unfortunatly that didn't help.
I removed the proxy but the WSDL was still not found I also added the host to the Proxy exceptions list and switched the proxy back on but this did not work either.
I also tried the method in the link you provided. But I get an error when attempting to create a Web Service Dasta Control too. The error I get here is:
DCA-40002: The WSDL document is invalid due to the following reason: WSDl Exception: faultCode=PARSER_ERROR: Failed to read wsdl file at: "https://../../..wsdl", caused by javax.net.ssl.SSLHandshakeException. :...........

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

Similar Messages

Maybe you are looking for