Announcement Announcement Module
Collapse
No announcement yet.
Declaring xsi and xsd namespaces in both SOAP Envelope and Body content Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Declaring xsi and xsd namespaces in both SOAP Envelope and Body content

    Hi list!
    I'm really desperate after some days spent on a problem.
    Maybe someone can advise a way to the solution.

    I'm writing a SOAP web service, and the response I should send is required to have the following namespaces declared twice:
    Code:
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    Once in the SOAP Envelope:
    Code:
    <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">
    and once in the root element inside the body:
    Code:
      <soap:Body>
          <OTA_HotelResNotifRS
            xmlns="http://www.opentravel.org/OTA/2003/05"
            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <Errors>
                <Error Type="1">Found 1 valid reservations with CRS Confirmation Number=52690IC0000172, there should be none.</Error>
             </Errors>
          </OTA_HotelResNotifRS>
       </soap:Body>
    I think it's redundant, but the server I'm sending responses to claims to need both.

    My attempts to configure the JiBX mapping or to intercept the outgoing response and increment it have all failed.
    Any suggestion please?

    I'm using Spring WS and JiBX OXM, and I don't understand if the way to go is better configuring JiBX marshaller or better understand and apply the Axiom APIs in the interceptor.

    I'll post the same question on the JiBX Users ML.

    Cheers,
    Vito Meuli

  • #2
    Hi all!
    I've understood it's not a problem of marshalling.
    It's a problem of XML generation, so I've posted the next question on another thread:
    http://forum.springsource.org/showth...LOutputFactory

    Cheers,
    Vito Meuli

    Comment

    Working...
    X