Databases
StackOverflow2013
Postsdbo
POHow can I handle Castor unmarshaling of SOAP messages when the namespace is defined inside the operation tag?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I handle Castor unmarshaling of SOAP messages when the namespace is defined inside the operation tag?
    primarykey
    data
    text
    <p>I am developing a contract-first web service based on Spring-WS. I'm relying on Castor marshaling, and I have run into the following issue. </p> <p>Requests are being accepted when the "xmlns" namespace is defined in the Envelope tag, such as:</p> <pre><code>&lt;soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://www.mycompany.com/MyService/schemas"&gt; &lt;soap:Header/&gt; &lt;soap:Body&gt; &lt;doPlaceHoldRequest&gt; &lt;hold&gt; &lt;accountInfo&gt; &lt;accountNumber&gt;123456789&lt;/accountNumber&gt; &lt;/accountInfo&gt; &lt;extended&gt;false&lt;/extended&gt; &lt;afterHours&gt;false&lt;/afterHours&gt; &lt;amountSavings&gt;1.00&lt;/amountSavings&gt; &lt;amountChecking&gt;0.00&lt;/amountChecking&gt; &lt;/hold&gt; &lt;/doPlaceHoldRequest&gt; &lt;/soap:Body&gt; &lt;/soap:Envelope&gt; </code></pre> <p>However, both .NET and Java clients generated from the .wsdl provided by Spring-WS (which was generated from a XSD), form their requests in the following manner:</p> <pre><code>&lt;soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"&gt; &lt;soap:Header/&gt; &lt;soap:Body&gt; &lt;doPlaceHoldRequest xmlns="http://www.mycompany.com/MyService/schemas"&gt; &lt;hold&gt; &lt;accountInfo&gt; &lt;accountNumber&gt;123456789&lt;/accountNumber&gt; &lt;/accountInfo&gt; &lt;extended&gt;false&lt;/extended&gt; &lt;afterHours&gt;false&lt;/afterHours&gt; &lt;amountSavings&gt;1.00&lt;/amountSavings&gt; &lt;amountChecking&gt;0.00&lt;/amountChecking&gt; &lt;/hold&gt; &lt;/doPlaceHoldRequest&gt; &lt;/soap:Body&gt; &lt;/soap:Envelope&gt; </code></pre> <p>Which results in an Unmarshalling Exception being thrown by Castor. How do I get Castor to recognize these messages as valid? Could my WSDL (or the XSD I used to autogenerate it) be wrong?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USHéctor Ramos
    1. USHéctor Ramos
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow can I handle Castor unmarshaling of SOAP messages when the namespace is defined inside the operation tag?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo far I've switched to plain old Jax-WS and it is working like a charm. Never again I will touch Spring-WS and Castor... such a headache!
      singulars
      1. POHow can I handle Castor unmarshaling of SOAP messages when the namespace is defined inside the operation tag?
      1. USHéctor Ramos
    2. COThose two XML documents are semantically identical, despite the difference in the namespace declaration positions. If Castor doesn't like one of them but likes the other, then Castor is broken. Spring-WS is the best option, in my experience, JAX-WS is too clunky.
      singulars
      1. POHow can I handle Castor unmarshaling of SOAP messages when the namespace is defined inside the operation tag?
      1. USskaffman
 

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