I have run into an issue when using the StaticRouter and having the message body not contain the object that I expected. Does the StaticRouter put another wrapper aroound the message body that would cause services down the line not to recognize the object that it should contain? My scenario is the following, I have a service that contains an action that takes in a message that I then add some properties too and then forward it to another service using the StaticRouter. In the receiving service the action tries to cast the message body to what it was set to in the forwarding service and it fails with a class cast exception. When I use the JMSRouter everything works fine and the service action has no problem casting the object to what is expected. Any help is much appreciated.