> The only thing > which is not nice is that the way to detect the Hessian message is making > assumptions on the transport used (content-type of http transport header as > a decision criteria). But there are obviously other alternatives to > implement the isHessianMessage() method (e.g. letting the builder write an > info about the application protocol used in a defined place within the > message context or even something smarter?).
Normally, the message formatter is selected based on the "messageType" (Constants.Configuration.MESSAGE_TYPE) property of the MessageContext. This is transport independent, so you should use this information. Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
