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

  • AXIOM and JAXB

    I am receiving errors when using AxiomSoapMessageFactory as my messageFactory along with JAXB. The same code works great when using SAAJ as my factory, but do to other issues AXIOM must be used. The error I am receiving is:

    Code:
    org.springframework.oxm.jaxb.JaxbUnmarshallingFailureException: JAXB unmarshalling exception: null; nested exception is javax.xml.bind.UnmarshalException
     - with linked exception:
    [javax.xml.stream.XMLStreamException]
    Caused by: javax.xml.bind.UnmarshalException
     - with linked exception:
    [javax.xml.stream.XMLStreamException]
    	at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.handleStreamException(UnmarshallerImpl.java:422)
    	at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:360)
    	at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:330)
    	at org.springframework.oxm.jaxb.Jaxb2Marshaller.unmarshalStaxSource(Jaxb2Marshaller.java:322)
    	at org.springframework.oxm.jaxb.Jaxb2Marshaller.unmarshal(Jaxb2Marshaller.java:309)
    	at org.springframework.ws.support.MarshallingUtils.unmarshal(MarshallingUtils.java:54)
    	at org.springframework.ws.client.core.WebServiceTemplate$2.extractData(WebServiceTemplate.java:267)
    	at org.springframework.ws.client.core.WebServiceTemplate.sendAndReceive(WebServiceTemplate.java:408)
    	at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:256)
    My messageFactory statement is:
    Code:
    	<bean id="messageFactory" class="org.springframework.ws.soap.axiom.AxiomSoapMessageFactory">
    		<property name="payloadCaching" value="true"/> 
    	</bean>
    My Marshaller/Unmarshaller is org.springframework.oxm.jaxb.Jaxb2Marshaller

    Any thoughts on this one?

    Thanks in advance,

    Keith

  • #2
    This is probably fixed in 1.0.2, to be released this week.

    Comment

    Working...
    X