Last week I was getting a response from a service which returned a record. I was simply using xpath function and assigning each record into a destination message. Then I used a transformation shape to map 3 source messages to the response message. One of the messages was assigned a record from the response and the message was being constructed successfully as I was logging the message and saw it in the Orchestration Debugger. But after the Transformation, the values were NULL.
All that was missing was the namespace in the message and my message type wasn't correct. If the message types are not correct, you will get the following exceptions if you are sending a message to a port. But in my case, I wasn't.
Inner exception: Received unexpected message type does not match expected type http://Namespace#RootNode. Exception type: UnexpectedMessageTypeException
Well just give your message the appropriate type and you are done. Well it was simple and it wasted 2 hours of mine.
Posted in Tips & Tricks Tagged: Message Debatching - Values not being mapped in a Transformation - Null Values in Destination Schema