Hi Richard

Thanks for the quick reply. I copied the xmlBean url twice and now changed
the URL to Spring web service ticket. The xmlBean ticket mentioned in the
spring web service one so I paste it here.

Anyway, please correct me if I am wrong. I don't think adding prefix mapper
will fix my problem. In my case I am only use camel spring-ws and jaxb as
web service client. What returned from the server is out of my control. I
only want the unmarshaller to pick up the namespace prefix from the soap
Envelope.

example,
*xmlns:n2="http://www.ben_rr.com"* in the soap response

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:n2="http://www.ben_rr.com";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
   <soap:Body>
      <n:loginResponse xmlns:n="http://www.ben_rr.com/";>
         <n:Result xsi:type="n2:LoginResp">
            <header xsi:type="n2:APIResponseHeader">
               <errorCode xsi:type="n2:APIErrorEnum">OK</errorCode>
               <timestamp
xsi:type="xsd:dateTime">2012-05-16T03:57:03.782Z</timestamp>
            </header>
            <errorCode xsi:type="n2:LoginErrorEnum">OK</errorCode>
            <minorErrorCode xsi:nil="1"/>
            <validUntil
xsi:type="xsd:dateTime">0001-01-01T00:00:00.000Z</validUntil>
         </n:Result>
      </n:loginResponse>
   </soap:Body>
</soap:Envelope>


--
View this message in context: 
http://camel.465427.n5.nabble.com/spring-ws-component-unmarshall-Jaxb-problem-when-Payload-namespace-prefix-in-attribute-value-tp5710538p5710568.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to