Web reference WSDL not conforming to SOAP standard

I built a web service based on the BAPI_FLIGHT_GETLIST function module using the "create web service" wizard. The generated web service endpoint is active in SOAMANAGER transaction.
When I try to generate a proxy class in Visual Studio 2005 using the "Add web reference" tool the service method is shown as expected in the preview window. However, when I click the "Add Reference" button I get the following error message:
Custom tool warning: DiscoCodeGenerator unable to initialize code generator.
No code generated.
The Solution Explorer window shows the Web Reference object generated with components Reference.map, Reference.cs and a WSDL file; however the Reference.cs proxy class has no code in it and there are no objects for the method parameters.
When running the WSDL.exe program from the command line, the following error message is generated:
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Warning: This web reference does not conform to WS-I Basic Profile v1.1.
SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of implementation guidelines that recommend how a set of core Web services specifications should be used together to develop interoperable Web services. For the 1.1 Profile, those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
For more details on the WS-I Basic Profile v1.1, see the specification at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
Warning: no classes were generated.
Warnings were encountered. Review generated source comments for more details.
I've seen several documents that step through this process that work fine. Has anyone seen this issue before and found a solution?
I'm running NW2004s with SP14 on Windows Server 2003 R2. Clients are VS2005 on both XP & Vista - same result on both client environments.
Thanks,
Dorian.

Hi,
I'm not familiar with the tools you described to create the Web Service aboved SAP BAPI's, but i have 2 ideas which you can start with.
I am part of the team developed the "ESE for .NET" and on the last step of our tool we are using VS API to "Add Web Reference".
We have noticed 2 ocaasions that might interest you:
1. Can you please verify that the WSDL contains the "wsdl:binding" part ?
   according to the error message you described you are missing the binding part.
   As you know WSDL of .NET Web Service combined of 5 major sections: "wsdl:types, "wsdl:message, "wsdl:portType, "wsdl:binding" & "wsdl:service".
   .NET proxy generation can't be executed on a WSDL based on a Service Definition only, it must have the "wsdl:binding" part which always comes only with
   the End Points WSDL from SAP services.
2. Can you send me the WSDL file by email ? [email protected]
3. Another important issue for Runtime of the Services - SAP Web Service schema is a little different than MS schema, you should look for "parameters" inside the WSDL and change it to "paramter".
Hope this information will help you,
Nadav

Similar Messages

Amazon S3 Web Service WSDL not working

I trying to create a shared reference to the new Amazon S3 web service using the following WSDL
http://s3.amazonaws.com/doc/2006-03-01/AmazonS3.wsdl
.. but the wizard isn't recognising any input or output parameters , is this a fault of Amazon's WSDL or a problem with the wizard ?
The same wsdl file can be used successfully by the Microsoft Office 2003 Web Services tool so I guess it's unlikely to be a wsdl fault.

Maybe a REST based approach might be a better option see my problems with the Microsoft Office Toolkit and S3 http://developer.amazonwebservices.com/connect/thread.jspa?threadID=10120&tstart=0
Update: Got it working using a REST approach under Ruby on Rails via Rail3. Open source V closed source , SOAP V REST you just got to wonder where the future lies ?

Possible Bug? autotype + wsdl2service generates implementation that does not conform to the WSDL

Hey folks,
I've got some hand crafted, valid, WS-I compliant WSDL + imported XSD that I've
been using for awhile now to generate an Apache Axis 1.2 beta Document Literal
Web Service implementation. I'm now trying to use the same WSDL to generate a
BEA WL 8.1 SP2 Document Literal Web Service implementation and I'm running into
problems.
I've attached the WSDL, XSD, and build script that I'm using to generate the implementation.
It deploys fine, but notice that the autogenerated WSDL that is returned from
the deployed BEA Web Service contains two <xs:schema> sections: one for the imported
WSDL (as expected) and one for several new elements that seem to get substituted
for the elements used in the orignal WSDL message parts.
The results of this are two fold:
1) the autogenerated WSDL appears to be invalid when loaded into both XMLSpy and
SOAPscope
2) the SOAP requests to invoke the operations on the service do not conform to
the hand crafted original WSDL. I've attached examples of both a BEA generated
SOAP request and an EXPECTED SOAP request.
I've poured over both the types.xml and the web-services.xml, and I'll be damned
if I can see the problem. I'm wondering if the way I import schemas and reference
elements declared therein is somehow not supported by BEA's ant tasks?
Any advice or pointers at all would be appreciated.
Regards,
-Jonathan Anderson
Booz Allen Hamilton
[BankService2.zip]

I don't know if you already now this but if you are using <autotype> to generate
the types.xml from the XML Schema then you should first
1) autotype the imported schema first.
2) Then for the actual achema (that uses the imported xsd) <autotype> but with
the
typeMappingFile="importedSchemas/types.xml"
option set to the types.xml output from 1)
The types.xml will then contain all types from both Schemas. You can then pass
this final types.xml from 2) to <source2wsdd> via
typesInfo="types.xml"
Any help ?
Pete
"Jonathan Anderson" <[email protected]> wrote:
>
Definitely seems as if BEA monitors these newsgroups. Lot's of developers
talking
to themselves, it seems.
<sigh>
"Jonathan Anderson" <[email protected]> wrote:
Hey folks,
I've got some hand crafted, valid, WS-I compliant WSDL + imported XSD
that I've
been using for awhile now to generate an Apache Axis 1.2 beta Document
Literal
Web Service implementation. I'm now trying to use the same WSDL togenerate
a
BEA WL 8.1 SP2 Document Literal Web Service implementation and I'm running
into
problems.
I've attached the WSDL, XSD, and build script that I'm using to generate
the implementation.
It deploys fine, but notice that the autogenerated WSDL that is returned
from
the deployed BEA Web Service contains two <xs:schema> sections: onefor
the imported
WSDL (as expected) and one for several new elements that seem to get
substituted
for the elements used in the orignal WSDL message parts.
The results of this are two fold:
1) the autogenerated WSDL appears to be invalid when loaded into both
XMLSpy and
SOAPscope
2) the SOAP requests to invoke the operations on the service do notconform
to
the hand crafted original WSDL. I've attached examples of both a BEA
generated
SOAP request and an EXPECTED SOAP request.
I've poured over both the types.xml and the web-services.xml, and I'll
be damned
if I can see the problem. I'm wondering if the way I import schemas
and reference
elements declared therein is somehow not supported by BEA's ant tasks?
Any advice or pointers at all would be appreciated.
Regards,
-Jonathan Anderson
Booz Allen Hamilton

Cannot add wsdl as web reference

Hi,
I am trying to add wsdl file as web reference to a visual studio project. But when I am trying to add the url, I am getting following message on right side : The HTML document does not contain Web service discovery information.
And following result is getting in out put.
"xx-yyy.serviceagent" Description
Methods
OpI ( As , As , As , As )
OpQ ( As , As )
When I am typing the wsdl url in browser, I can get the xml file. And also when I am using this wsdl in
SOAP UI, I can get the functions and I can call the services also.

Hi,
Thank you for posting in the MSDN forum. It seems that it is not the correct forum for this issue, since
this forum is to discuss Visual Studio IDE. I am moving your question to the moderator forum ("Where is the forum for..?"). The owner of the forum will direct you to a right forum.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Web Reference inside Script Task causes Binary code for script not found error

I am attempting to access a SOAP web API (sales force) from a SSIS package. To do this I created a script task.
Inside the script task I went to Add Service Reference. Then I click advanced to make it a web reference. Then I point it to the WSDL file and give it a name SFEnterprise. It successfully finds and adds the Web Reference to the script task.
I leave scriptMain.cs alone and I have no warnrings and no errors. Now in the solution explorer I right-click the script task and hit BUILD. I see the message from Output that BUILD succeeded.
I close the VSTA script editor and now I am back on the control flow window. However I have a red X on the script task with the following message. "The Binary code for the script is not found. Please open the script in the designer by clicking EditScript
button and make sure it builds successfully"
But it does build successfully! And I have not even added any custom code except for the web reference using the WSDL file.
I am using SSIS 2012 and Visual Studio 2012. I have been reading about this binary code error message on Google searches and suggestions about delay validation and turning off pre-compile do not apply to SSIS 2012.
Is SSIS not capable of doing this?

I was wanting to use the 2.0 coding style of accessing the soap service which is supported by adding the web reference vs. adding a service reference. But using a service reference instead of web reference actually allows the script task to compile. This
is really odd behavior. I wonder why one works and not the other.
Changing my C# code over to service reference coding style to access the SOAP service was still returning an error. When I added a break point I found the error message "Could not find default endpoint element that references contract in the ServiceModel
client configuration section"when calling new SoapClient();
I found this page http://www.sqlis.com/sqlis/post/Where-is-my-appconfig-for-SSIS.aspx and after I copied the System.ServiceModel app settings from the script task app.config to the DTSDebugHost.exe.config it was able to successfully login to the endpoint
during package debug mode.
This means I will have to edit the SQL Server DTS config files on the prod SSIS server to get the package to actually run in the job agent.
So for now I am good I think just plugging away at coding what the script task is actually supposed to do now that is can actually login.

The value in flexfield context reference web bean does not match with the value in the context of the Descriptive flexfield web bean BranchDescFlex. If this in not intended, please go back to correct the data or contact your Systems Administrator for assi

Hi ,
We have enabled context sensitive DFF in Bank Branch Page for HZ_PARTIES DFF , We have created Flex Map so that only bank branch context fields are only displayed in the bank branch page and as we know party information DFF is shared by supplier and Customer Page so we dint want to see any Bank Branch fields or context information in those pages.
We have achieved the requirement but when open existing branches bank branch update is throwing below error message :
"The value in flexfield context reference web bean does not match with the value in the context of the Descriptive flexfield web bean BranchDescFlex. If this in not intended, please go back to correct the data or contact your Systems Administrator for assistance."
this error is thrown only when we open existing branches, if we save existing branch and open then it is not throwing any error message.
Please let us know reason behind this error message.
Thanks,
Mruduala

You are kidding? It took me about 3 minutes to scroll down on my tab to get to the triplex button!
Habe you read the error message?
Quote:
java.sql.SQLSyntaxErrorException: ORA-04098: trigger 'PMS.PROJECT_SEQ' is invalid and failed re-validation
Check the trigger and it should work again.
Timo

Adobe 11.0.03 does not conform to standard open parameters. Have they been updated

Adobe 11.0.03 does not conform to standard open parameters. Have they been updated?

Copied from what I posted in many other topics; three possibilities
Using Windows Explorer navigate to C:\Program Files (x86)\Adobe\Reader 11.0\Reader, then double-click on Eula.exe and accept the license agreement
Can you open Adobe Reader by itself? If so, try disabling Protected Mode [Edit | Preferences | Security (Enhanced)].
It could even be a malware issue; see http://helpx.adobe.com/acrobat/kb/reader-core-dll-error.html

Methods do not conform to the restrictions imposed by the web service impl

Anyone know what this message means?
Im using JDev 903 and OC4J 903
Error:
These methods do not conform to the
restrictions imposed by the web service implementation
Offending methods:
public abstract com.bayer.cropscience.nafta.uscrop.hierarchymaint.HierarchyLevel[] com.bayer.cropscience.nafta.uscrop.hierarchymaint.IHierarchyPersistenceWS.getHierarchyLevelsForHeaderGK(double)
Ive checked all I can. Im using JDev to generate web services from an existing class. Other methods work fine, but I dont know how to handle this error.
Thanks,
Mark

Anyone know what this message means?
Im using JDev 903 and OC4J 903
Error:
These methods do not conform to the
restrictions imposed by the web service implementation
Offending methods:
public abstract com.bayer.cropscience.nafta.uscrop.hierarchymaint.HierarchyLevel[] com.bayer.cropscience.nafta.uscrop.hierarchymaint.IHierarchyPersistenceWS.getHierarchyLevelsForHeaderGK(double)
Ive checked all I can. Im using JDev to generate web services from an existing class. Other methods work fine, but I dont know how to handle this error.
Thanks,
Mark

Getting "museJSAssert: Error calling selector function: Reference Error: Web Pro is not defined".

First off, I am not a coding person. I decided to use Muse becuse I am good with Illustrator and Photoshop.
The sight I built: www.speedcinch.com is now getting a bunch of errors when it initially was working fine. I am using godaddy for a host and using their ftp.
This is the error I am getting now: museJSAssert: Error calling selector function: Reference Error: Web Pro is not defined
You can see how my sight is supposed to work at http://speedcinchcom.businesscatalyst.com/index.html
I have no idea what to do. Please help.

Well, if nothing else I've ascertained that it's not GoDaddy's connectivity issue, as the issue continues late into today, and it does vary a bit per the other error reports. Using FileZilla there are just a few timeouts in the log, enough to give some pause but not necessarily (according to GD) disruptive. I've checked the list of uploaded files against the Muse Export folder contents and everything is there. In fact, the site looks good, buttons work, rollovers, etc, but there are no images. Like everyone else, this has cost me time and money in the last 24 hours.
Let's see what the good people at Adobe live chat have to say, and I'll share it with you.

Web Services - WSDL doubt.

Hi all,
Im sorry to repeat this subject again, but I continue with some doubts
I read almost SDN web logs about web services. All they teach, how to configure and develop a simple web services but the steps to create a web service connection between XI, continues a little bit confused to me
To clarify my objective, look at this scenario: With an iview with an upload form, I want to upload an xml file to XI trough web service (soap adapter). NW Portal <-> (web services) <-> XI.
I dont have sure what I need to do to configure a scenario like that. Tell me if Im correct: First I need to create an outbound interface to connect Portal via web services to XI, with a soap adapter?
In the web logs that Im read, (/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi) I need to download wsdl files but who make these wsdl files? I need to make it before configure my soap adapter?
I dont understand what is the propose of wsdl files and what is used for!!! I never worked with web services Im come from ABAP programming and Im trying to do the first steps in web technologies. So, Im sorry if said some mistakes
Please, can anybody clarify my doubts? Documentation to help is appreciated.
Thanks in advance,
Ricardo.

Hi Ricardo,
>>>I dont have sure what I need to do to configure a scenario like that. Tell me if Im correct: First I need to create an outbound interface to connect Portal via web services to XI, with a soap adapter?
yes that's what you have to do:
1. create an outbound interface
2. publish a web service based on this interface (sender SOAP adapter)
>>>In the web logs that Im read, (/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi) I need to download wsdl files but who make these wsdl files? I need to make it before configure my soap adapter?
you need to download wsld file if you want to call
a web service from XI, since you only want to do Portal -> xi and not XI -> web service then you don't need any
wsld files
>>>but who make these wsdl files?
you will, once you'll define your web service
on the XI - your Portal iview will use this file
Regards,
michal

Process as a Web Service WSDL client

Hi,
I am using the Process as a Web Service Option inside of BPM . I launch the deployed webservices webapps and I get the WSDL out of it.. The WSDL works fine with SOAP UI..But when I try to create a web service client out of that WSDL it gives me the following error:-
com.bea.albpm.TestProject.SampleProject.OperationException cannot be resolved as type and the web service client does not work..
how do I resolve this error.. Is there a jar file that I need to import?

Did you use PAPI code inside your web service or did u just use PAPI Web Services ( like did u just pressed the button Launch PAPI Web Services ) and it created the WSDL for you and u used it to create the client?
I am using the latest version of OBPM..
Oracle 10.3.10
Can you let me know what do u mean by PAPI interface.. Is it the PAPI code of is the PAPI Web Service which is built by BPM automatically and could be used?
Edited by: user8707382 on Sep 10, 2009 9:00 AM

Web-Service WSDL contains no messages in External Definations

Hi All,
I am working on IDOC->XI->Web-method scenatio.
Web-method team has given me attached WSDL. this WSDL is not showing any message in Message Tab while uploading WSDL in External Definations Tab in IR.
Is it possible to send data to this type of Web-method with receiver SOAP Adapter?
Because in /people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2 weblog we can see messages in message tab while uploading message.
Please help.
Regards
**********WSDL***********************
<?xml version="1.0" encoding="UTF-8"?>
 <wsdl:definitions name="GE_OC_SalesOrder_Source_Services" targetNamespace="http://3.209.120.84/"
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
 xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
 xmlns:tns="http://3.209.120.84/">
 <wsdl:types>
 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://localhost/GE_OC_SalesOrder_Source/Services/publishSalesOrderCanonical" xmlns:tns="http://localhost/GE_OC_SalesOrder_Source/Services/publishSalesOrderCanonical">
 <xsd:complexType name="__publishSalesOrderCanonicalInput">
 <xsd:sequence>
 <xsd:element name="_x0078_mlString" nillable="true" type="xsd:string"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="__publishSalesOrderCanonicalOutput">
 <xsd:sequence>
 <xsd:element name="status" nillable="true" type="xsd:string"/>
 <xsd:element name="status_message" nillable="true" type="xsd:string"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:schema>
 </wsdl:types>
 <wsdl:message name="publishSalesOrderCanonicalInput">
 <wsdl:part name="_x0078_mlString" type="xsd:string"/>
 </wsdl:message>
 <wsdl:message name="publishSalesOrderCanonicalOutput">
 <wsdl:part name="status" type="xsd:string"/>
 <wsdl:part name="status_message" type="xsd:string"/>
 </wsdl:message>
 <wsdl:portType name="GE_OC_SalesOrder_Source_ServicesPortType">
 <wsdl:operation name="publishSalesOrderCanonical">
 <wsdl:input message="tns:publishSalesOrderCanonicalInput"/>
 <wsdl:output message="tns:publishSalesOrderCanonicalOutput"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="GE_OC_SalesOrder_Source_ServicesBinding" type="tns:GE_OC_SalesOrder_Source_ServicesPortType">
 <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
 <wsdl:operation name="publishSalesOrderCanonical">
 <soap:operation soapAction=""/>
 <wsdl:input>
 <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://3.209.120.84/GE_OC_SalesOrder_Source.Services" use="encoded"/>
 </wsdl:input>
 <wsdl:output>
 <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://3.209.120.84/GE_OC_SalesOrder_Source.Services" use="encoded"/>
 </wsdl:output>
 </wsdl:operation>
 </wsdl:binding>
 <wsdl:service name="GE_OC_SalesOrder_Source_ServicesService">
 <wsdl:port name="GE_OC_SalesOrder_Source_ServicesPort0" binding="tns:GE_OC_SalesOrder_Source_ServicesBinding">
 <soap:address location="http://3.209.120.84:5555/soap/rpc"/>
 </wsdl:port>
 </wsdl:service>
 </wsdl:definitions>

Hi Stefan,
Thanks for reply. You are true WSDL is RPC style.
But if you Observe My WebService WSDL following lines
<wsdl:message name="publishSalesOrderCanonicalInput">
<wsdl:part name="_x0078_mlString" type="xsd:string"/>
</wsdl:message>
There is only one part(field) but we wants to send 50 field XML.
If you see Note:856597 & attached WSDL in Note getQuote_rpc.wsdl following lines
<message name="GetTradePriceInput">
<part name="tickerSymbol" type="xsd:string"/>
<part name="time" type="xsd:dateTime"/>
</message>
There are two part(fields) for two XML fields as in Note.
Is it possible to Pass XML message in this type of web-service?
If possible then How can I send?
Please help....
Best Regards

WSSE usename token not in the SOAP Header

Background:
Webservice with four methods; OpGet, OpCreate, OpGetList, OpSet. Setup a jcx with this webservice URL, generate a test harness from workshop, and running this test harness and looking at the SOAP messages being send and received to verify that the web services are working. The OpGet is working since it doesn't require user credentials. But the OpCreate is currently not working. Remedy is rejecting it because of access control.
Problem #1:
Need to pass the user credential in the SOAP header. Here's the required information in WSDL regarding Authentication.
<wsdl:operation name="OpCreate">
<soap:operation soapAction="urn:SimpleWebService/OpCreate" style="document"/>
<wsdl:input>
<soap:header message="s:ARAuthenticate" part="parameters" use="literal">
</soap:header>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
Solution that I have implemented so far:
I have setup a WSSE file with the simple username/password in the <wsSecurityOut> element and was expecting to see this in the SOAP Header element in the WSDL message. When I look at the SOAP message in the test harness that I have generated in Workshop, I don't see this credential information. I have set the "ws-security-service property to the wsse file. I know that the harness has seen the wsse file since it gives me warning about having the password in simple text without encryption.
Shouldn't I be seeing this userNameToken information in the SOAP Header when I run the test harness (jws) from workshop? As you can see below (Problem #2) no SOAP header is being generated.
Problem #2:
I see that in the SOAP message that test harness is sending wrong "xsi:type" information. It seems to be sending the "StatusType" for all the parameters except the one "Status" where it needs to?
SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<ns:OpCreate xmlns:ns="urn:SimpleWebService">
<ns:Assigned_To xsi:type="ns:StatusType">donnab</ns:Assigned_To>
<ns:Short_Description xsi:type="ns:StatusType">testing from weblogic 8.1 SP3 Workshop</ns:Short_Description>
<ns:Status>New</ns:Status>
<ns:Submitter xsi:type="ns:StatusType">donnab</ns:Submitter>
</ns:OpCreate>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Here's the WSDL where the OpCreate is defined:
<xsd:element name="OpCreate" type="s:CreateInputMap"/>
<xsd:complexType name="CreateInputMap">
<xsd:sequence>
<xsd:element name="Assigned_To" type="xsd:string"/>
<xsd:element name="Short_Description" type="xsd:string"/>
<xsd:element name="Status" type="s:StatusType"/>
<xsd:element name="Submitter" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>

I've never been able to see that information because I assume Weblogic server strips it out the minute it receives it and uses it to authenticate the user against a principal in the server.
You can get ahold of this info, though. In your .jws file, in workshop, add this as a context:
/** @common:context */
JwsContext context;
In your web services method, access the context to get the username:
context.getCallerPrincipal().getName();
That will return a String w/ the username passed in the username token.
-Becky

Call web service (WSDL) from apex

Hi all,
I have web service (WSDL) as (http://localhost:8080/merlin-service/services/ContraIndicationService?wsdl) from example.
and I want to call this service from Apex, how can i do that , any idea?
I tried web service reference found in apex but it is failed.
So please any idea about this.
Thanks and regards.
Mohd.
Edited by: Ajeeb on Aug 26, 2010 10:23 AM

Hi,
I used web service refences to create call this web service and when I tested the web service in the test area in web service refences
it is working fine and it is giving the foloowing
In the request:
<?xml version='1.0' encoding='UTF-8'?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body><ns1:searchByCommonNameGroupIdAndCim10Ids xmlns:ns1="http://contraindication.api.vidal.com"><ns1:commonNameGroupId>4835</ns1:commonNameGroupId><ns1:cim10Ids><ns1:int>4399</ns1:int></ns1:cim10Ids></ns1:searchByCommonNameGroupIdAndCim10Ids></SOAP-ENV:Body>
</SOAP-ENV:Envelope>
and it is returning this response
(<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soap:Body><ns1:searchByCommonNameGroupIdAndCim10IdsResponse xmlns:ns1="urn:Vidal"><ns1:contraIndicationCim10List><contraIndications xmlns="urn:Vidal"><contraIndicationTypeCim10Tuple><cim10><code>J45</code><id>4398</id><name> </name></cim10><contraIndication><id>16241</id><name>History of asthma attack related to taking aspirin</name></contraIndication><type>ABSOLUTE</type></contraIndicationTypeCim10Tuple><contraIndicationTypeCim10Tuple><cim10><code>J45</code><id>4398</id><name> </name></cim10><contraIndication><id>16251</id><name>History of asthma attack related to taking non-steroidal anti-inflammatory drugs</name></contraIndication><type>ABSOLUTE</type></contraIndicationTypeCim10Tuple></contraIndications><homogeneous xmlns="urn:Vidal">true</homogeneous></ns1:contraIndicationCim10List></ns1:searchByCommonNameGroupIdAndCim10IdsResponse></soap:Body></soap:Envelope>
But when I created form and report for this service it is giving me no data found>
How can I get the output of this service, if it is XML data also no problem for me.
Best Regards.
Mohd.

UTL_DBWS accessing web service gives 'not contain port' error

Hello
I am trying to call a web service from https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl
In the WSDL xml, i get the targetNamespace (http://PlanonWebServices.ws),
the service name (PlanonSession),
the wsdl URL (https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl),
the portType name (PlanonSessionHttpEndpoint),
the operation name (login).
When i call the web service, i get an error about the port :
-29532 - ORA-29532: Java call terminated by uncaught Java exception: service:
{http://PlanonWebServices.ws}PlanonSession does not contain port:
{http://PlanonWebServices.ws}PlanonSessionHttpEndpoint
The code is :
CREATE OR REPLACE PROCEDURE planon_Login AS
planon_username VARCHAR2(50):= 'XXXXXX'; --- removed for security
planon_passwd VARCHAR2(50):= 'XXXXX'; --- removed for security
service_ sys.utl_dbws.SERVICE;
call_ sys.utl_dbws.CALL;
service_qname sys.utl_dbws.QNAME;
port_qname sys.utl_dbws.QNAME;
operation_qname sys.utl_dbws.QNAME;
string_type_qname sys.utl_dbws.QNAME;
username sys.utl_dbws.QNAME;
password sys.utl_dbws.QNAME;
--retx ANYDATA;
retx_string VARCHAR2(1000);
l_namespace VARCHAR2(1000);
l_wsdl_url VARCHAR2(1000);
l_input_params sys.utl_dbws.ANYDATA_LIST;
outputs sys.utl_dbws.ANYDATA_LIST;
output_retx VARCHAR2(1000);
xml_string sys.xmltype;
retx sys.xmltype;
qname_list_ sys.utl_dbws.QNAME_LIST;
qname_list_string sys.utl_dbws.QNAME_LIST;
BEGIN
dbms_output.put_line('Step 1');
dbms_output.put_line('Step 1 : Set l_wsdl_url');
l_wsdl_url := 'https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl';
dbms_output.put_line('Step 1 : Set l_namespace');
l_namespace := 'http://PlanonWebServices.ws';
dbms_output.put_line('Step 1 : Set service_');
service_qname := sys.utl_dbws.to_qname(l_namespace,'PlanonSession');
service_ := sys.utl_dbws.create_service (URIFACTORY.getURI(l_wsdl_url), service_qname);
dbms_output.put_line('Step 1 : Set port_qname_');
port_qname := sys.utl_dbws.to_qname(l_namespace,'PlanonSessionHttpEndpoint');
dbms_output.put_line('Step 1 : Set operation_qname');
operation_qname := sys.utl_dbws.to_qname(l_namespace, 'login');
dbms_output.put_line('Step 1 : Set call_');
call_ := sys.utl_dbws.create_call(service_,port_qname,operation_qname);
dbms_output.put_line('Step 2');
sys.utl_dbws.set_property(call_,'USERNAME', planon_username);
sys.utl_dbws.set_property(call_,'PASSWORD', planon_passwd);
sys.utl_dbws.set_property(call_,'SOAPACTION_USE','TRUE');
sys.utl_dbws.set_property(call_,'SOAPACTION_URI','https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession');
sys.utl_dbws.set_property(call_,'ENCODINGSTYLE_URI', 'https://schemas.xmlsoap.org/soap/encoding/');
sys.utl_dbws.set_property(call_,'OPERATION_STYLE','document');
dbms_output.put_line('Step 3');
string_type_qname := sys.utl_dbws.to_qname('https://www.w3.org/2001/XMLSchema', 'string');
/* first return parameter in the WSDL should not be specified in the parameter list or errors occur
sys.utl_dbws.add_parameter(call_, 'loginResponse', string_type_qname, 'ParameterMode.OUT');
sys.utl_dbws.set_return_type(call_,string_type_qname);
xml_string := xmltype('<PlanonSession xmlns="https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services">'
|| '</PlanonSession>');
retx := sys.utl_dbws.invoke(call_,xml_string);
dbms_output.put_line('Step 6');
dbms_output.put_line('Step 7');
dbms_output.put_line('Call Web Service:services:PlanonSession: ' || retx.getStringVal());
dbms_output.put_line('Step 10');
sys.utl_dbws.release_call(call_);
sys.utl_dbws.release_service(service_);
dbms_output.put_line('Step 11');
EXCEPTION
when others then
dbms_output.put_line(SQLCODE || ' - ' || SQLERRM);
END;
The WSDL document is :
?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:ns="http://PlanonWebServices.ws" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" targetNamespace="http://PlanonWebServices.ws">
<wsdl:documentation>PlanonSession</wsdl:documentation>
<wsdl:types>
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://PlanonWebServices.ws">
<xs:complexType name="Exception">
<xs:sequence>
<xs:element minOccurs="0" name="Exception" nillable="true" type="xs:anyType"/>
</xs:sequence>
</xs:complexType>
<xs:element name="logout">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="logoutResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setReferenceDate">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="param1" nillable="true" type="xs:dateTime"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setReferenceDateResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setSessionDataSection">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="param1" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setSessionDataSectionResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="login">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="param1" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="loginResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>
<wsdl:message name="logoutRequest">
<wsdl:part name="parameters" element="ns:logout"/>
</wsdl:message>
<wsdl:message name="logoutResponse">
<wsdl:part name="parameters" element="ns:logoutResponse"/>
</wsdl:message>
<wsdl:message name="loginRequest">
<wsdl:part name="parameters" element="ns:login"/>
</wsdl:message>
<wsdl:message name="loginResponse">
<wsdl:part name="parameters" element="ns:loginResponse"/>
</wsdl:message>
<wsdl:message name="setSessionDataSectionRequest">
<wsdl:part name="parameters" element="ns:setSessionDataSection"/>
</wsdl:message>
<wsdl:message name="setSessionDataSectionResponse">
<wsdl:part name="parameters" element="ns:setSessionDataSectionResponse"/>
</wsdl:message>
<wsdl:message name="setReferenceDateRequest">
<wsdl:part name="parameters" element="ns:setReferenceDate"/>
</wsdl:message>
<wsdl:message name="setReferenceDateResponse">
<wsdl:part name="parameters" element="ns:setReferenceDateResponse"/>
</wsdl:message>
<wsdl:portType name="PlanonSessionPortType">
<wsdl:operation name="logout">
<wsdl:input message="ns:logoutRequest" wsaw:Action="urn:logout"/>
<wsdl:output message="ns:logoutResponse" wsaw:Action="urn:logoutResponse"/>
</wsdl:operation>
<wsdl:operation name="login">
<wsdl:input message="ns:loginRequest" wsaw:Action="urn:login"/>
<wsdl:output message="ns:loginResponse" wsaw:Action="urn:loginResponse"/>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<wsdl:input message="ns:setSessionDataSectionRequest" wsaw:Action="urn:setSessionDataSection"/>
<wsdl:output message="ns:setSessionDataSectionResponse" wsaw:Action="urn:setSessionDataSectionResponse"/>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<wsdl:input message="ns:setReferenceDateRequest" wsaw:Action="urn:setReferenceDate"/>
<wsdl:output message="ns:setReferenceDateResponse" wsaw:Action="urn:setReferenceDateResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="PlanonSessionSoap11Binding" type="ns:PlanonSessionPortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="logout">
<soap:operation soapAction="urn:logout" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="login">
<soap:operation soapAction="urn:login" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<soap:operation soapAction="urn:setSessionDataSection" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<soap:operation soapAction="urn:setReferenceDate" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="PlanonSessionSoap12Binding" type="ns:PlanonSessionPortType">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="logout">
<soap12:operation soapAction="urn:logout" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="login">
<soap12:operation soapAction="urn:login" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<soap12:operation soapAction="urn:setSessionDataSection" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<soap12:operation soapAction="urn:setReferenceDate" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="PlanonSessionHttpBinding" type="ns:PlanonSessionPortType">
<http:binding verb="POST"/>
<wsdl:operation name="logout">
<http:operation location="PlanonSession/logout"/>
<wsdl:input>
<mime:content type="text/xml" part="logout"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="logout"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="login">
<http:operation location="PlanonSession/login"/>
<wsdl:input>
<mime:content type="text/xml" part="login"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="login"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<http:operation location="PlanonSession/setSessionDataSection"/>
<wsdl:input>
<mime:content type="text/xml" part="setSessionDataSection"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="setSessionDataSection"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<http:operation location="PlanonSession/setReferenceDate"/>
<wsdl:input>
<mime:content type="text/xml" part="setReferenceDate"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="setReferenceDate"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="PlanonSession">
<wsdl:port name="PlanonSessionHttpSoap11Endpoint" binding="ns:PlanonSessionSoap11Binding">
<soap:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpSoap11Endpoint/"/>
</wsdl:port>
<wsdl:port name="PlanonSessionHttpSoap12Endpoint" binding="ns:PlanonSessionSoap12Binding">
<soap12:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpSoap12Endpoint/"/>
</wsdl:port>
<wsdl:port name="PlanonSessionHttpEndpoint" binding="ns:PlanonSessionHttpBinding">
<http:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpEndpoint/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Any help is greatly appreciated.
Thanks in advance

I got the same error... did you find a solution?
tks
Mário Cardia

Web reference WSDL not conforming to SOAP standard

Similar Messages

Maybe you are looking for