Databases
StackOverflow2013
Postsdbo
POSpring-WS: Automatic wsdl fault generation/association
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpring-WS: Automatic wsdl fault generation/association
    primarykey
    data
    text
    <p>I am using DynamicWsdl11Definition in spring-ws to generate my wsdl spec. Eventually, I am getting a spec without wsdl faults attached to wsdl operations as I don't know how to associate particular wsdl/soap operations with particular wsdl faults automatically. How can I do that? Is there any way to associate wsdl faults with wsdl operations in the XSD schema?</p> <p>Here is a portion from my XSD:</p> <pre><code> &lt;xs:element name="setContextRequest"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element minOccurs="0" name="usageContext" nillable="true" type="xs:string"/&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;xs:element name="setContextResponse"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; </code></pre> <p>Here is my exception:</p> <pre><code> &lt;xs:element name="InvalidSessionException"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element minOccurs="0" name="InvalidSessionException" nillable="true" type="fault:InvalidSession"/&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; </code></pre> <p>Here is WSDL spec:</p> <pre><code> &lt;wsdl:operation name="setContext"&gt; &lt;soap:operation soapAction=""/&gt; &lt;wsdl:input name="setContextRequest"&gt; &lt;soap:body use="literal"/&gt; &lt;/wsdl:input&gt; &lt;wsdl:output name="setContextResponse"&gt; &lt;soap:body use="literal"/&gt; &lt;/wsdl:output&gt; &lt;/wsdl:operation&gt; </code></pre> <p>My question is on how to associate teh fault with that operation eventually to end up with:</p> <pre><code> &lt;wsdl:operation name="setContext"&gt; &lt;soap:operation soapAction=""/&gt; &lt;wsdl:input name="setContextRequest"&gt; &lt;soap:body use="literal"/&gt; &lt;/wsdl:input&gt; &lt;wsdl:output name="setContextResponse"&gt; &lt;soap:body use="literal"/&gt; &lt;/wsdl:output&gt; &lt;wsdl:fault name="invalidSession" type="InvalidSession"/&gt; &lt;/wsdl:operation&gt; </code></pre> <p>Thanks.</p> <p>ps: I'm setting requestSuffix, responseSuffix and faultSuffix, thus able to generate wsdl fault messages too.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAleyna
    1. USAleyna
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSpring-WS: Automatic wsdl fault generation/association
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSpring-WS: Automatic wsdl fault generation/association
      1. USlearning_bee
      1. VTFavorite
    1. COFaults are part of the WSDL contract. And I personally think it is better to have them listed in the contract. Please find a sample method above. Thanks!
      singulars
      1. POSpring-WS: Automatic wsdl fault generation/association
      1. USAleyna
    2. COSpring does not care about the code Mark so adding throws statement would not do anything if I am getting it right here. I guess I need to do some changes on the schema itself so that it will generate wsdl faults just like the way it does for wsdl operations I do not know how to do that. I do not even know if Spring supports that
      singulars
      1. POSpring-WS: Automatic wsdl fault generation/association
      1. USAleyna
 

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