• Post Reply Bookmark Topic Watch Topic
  • New Topic

Castor unmarshalling exception - Configure DefaultMethodEndpointAdapter Issue

 
Mat Anthony
Ranch Hand
Posts: 261
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
I'm trying to configure DefaultMethodEndpointAdapter to handle two different MarshallingPayloadMethodProcessor.
Each of the MarshallingPayloadMethodProcessor uses Castor Marshaller to configure different mapping files.
I'm trying to keep the mapping files seprate for each client. Calling the web service with the configuration below I get a Castor unmarshalling exception.

Castor unmarshalling exception; nested exception is org.exolab.castor.xml.MarshalException:
The class for the root element 'halfordSearchRequest' could not be found.

It looks as if halfords mapping file is not being used hence the request cannot find the class to Unmarshall to.






Not sure why this is not working since methodArgumentResolvers takes a list.

Mat
 
Mat Anthony
Ranch Hand
Posts: 261
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
if I remove any ref to curry-PayloadMethodProcessor within DefaultMethodEndpointAdapter methodArgumentResolvers & methodReturnValueHandlers it finds the class to unmarshel to.
Note sure what is going on here .


Any help or hints would be appreciated.

Mat
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!