Announcement Announcement Module
Collapse
No announcement yet.
JAXB unmarshalling exception Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • JAXB unmarshalling exception

    I am trying to test my custom fault message resolver against new api. I do see that my fault resolver works just fine against the old api. I have created jaxb objects for this new api (using XJCTask) and when I make a request that should fail (which it does) but it never get intercepted by my custom fault resolver. I see following exception in the log. Did i miss options while creating jaxb objects?

    I am using spring ws 1.5.2

    Any help appreciated.

    org.springframework.oxm.jaxb.JaxbUnmarshallingFail ureException: JAXB unmarshalling exception: unexpected element (uri:"http://schemas.xmlsoap.org/soap/envelope/", local:"Fault"). Expected elements are <{https://adwords.google.com/api/adwords/cm/v200909}ApiExceptionFault>.......

  • #2
    I figured out why spring is throwing exception. The google webservice is actually sending back soap fault with Http status code of 200. And obviously spring ws template thinks there is nothing wrong with response and tries to unmarshal regular response and thats where it barfs.

    According soap spec the soap fault should have http status code of 500 (which is what spring code also expects).

    Comment

    Working...
    X