Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Finally I solved this problem, a friend of mine helped me, apparently there were problems with the WSDL and the namespaces. C# generated the proxy wrong. Don't know if it's a c# problem or axis problem. But hope this answer helps anyone else. Take a look to all the namespaces on the methods of the WebService. C# Generated a method like this.</p> <pre><code>/// &lt;remarks/&gt; [System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://www.openuri.org/InformacionPoliza", RequestNamespace = "http://www.openuri.org/", ResponseNamespace = "http://www.openuri.org/", Use = System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle = System.Web.Services.Protocols.SoapParameterStyle.Wrapped)] [return: System.Xml.Serialization.XmlElementAttribute("Poliza")] public Poliza InformacionPoliza(CriteriosPoliza CriteriosPoliza) { object[] results = this.Invoke("InformacionPoliza", new object[] { CriteriosPoliza}); return ((Poliza)(results[0])); } </code></pre> <p>But in the WSDL had something like this..</p> <pre><code>&lt;wsdl:definitions xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://www.openuri.org/" xmlns:intf="http://www.openuri.org/" xmlns:tns1="http://www.example.org/PolizasBanorteSchemaCriterios" **xmlns:tns2="http://www.example.org/PolizasBanorteSchema"** xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.openuri.org/"&gt; &lt;!-- WSDL created by Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT) --&gt; &lt;wsdl:types&gt; &lt;schema xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://www.openuri.org/"&gt; &lt;import namespace="http://www.example.org/PolizasBanorteSchema"/&gt; &lt;import namespace="http://www.example.org/PolizasBanorteSchemaCriterios"/&gt; &lt;element name="InformacionPoliza"&gt; &lt;complexType&gt; &lt;sequence&gt; &lt;element name="CriteriosPoliza" type="tns1:CriteriosPoliza"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;/element&gt; &lt;element name="InformacionPolizaResponse"&gt; &lt;complexType&gt; &lt;sequence&gt; **&lt;element name="Poliza" type="tns2:Poliza"/&gt;** &lt;/sequence&gt; &lt;/complexType&gt; &lt;/element&gt; &lt;/schema&gt; </code></pre> <p>Look at the <code>&lt;element name="Poliza" type="tns2:Poliza"/&gt;</code> it refers to the <code>tns2</code> namespace and it says <code>xmlns:tns2="http://www.example.org/PolizasBanorteSchema"</code></p> <p>So the generated proxy by .NET was wrong it had to be like this</p> <pre><code>/// &lt;remarks/&gt; [System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://www.openuri.org/InformacionPoliza", RequestNamespace = "http://www.openuri.org/", ResponseNamespace = "http://www.openuri.org/", Use = System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle = System.Web.Services.Protocols.SoapParameterStyle.Wrapped)] [return: System.Xml.Serialization.XmlElementAttribute("Poliza", Namespace = "http://www.example.org/PolizasBanorteSchema")] public Poliza InformacionPoliza(CriteriosPoliza CriteriosPoliza) { object[] results = this.Invoke("InformacionPoliza", new object[] { CriteriosPoliza}); return ((Poliza)(results[0])); } </code></pre> <p>The namespace did the magic, </p> <pre><code> [return: System.Xml.Serialization.XmlElementAttribute("Poliza", Namespace = "http://www.example.org/PolizasBanorteSchema")] </code></pre> <p>Changed that line of code and everything worked like a charm So, be careful when using arrays and diferent namespaces in an axis service, you may have some problems generating a c# client.</p> <p><a href="http://www.primordialcode.com/blog/post/invoking-javaaxis-web-service-net-return-null-issue" rel="noreferrer">This post</a> was right :)</p>
    singulars
    1. This table or related slice is empty.
    1. POInvoking a Java/AXIS Web Service from .NET: the ‘return null’ issue
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMr.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POInvoking a Java/AXIS Web Service from .NET: the ‘return null’ issue
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the post, it answered exactly to an issue i had using OC4J based web services with document/literal services and a custom WSDL.
      singulars
      1. PO
      1. USEtienne
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload