> >> 1. Message formatters should be protocol independent (even if they > >> have access to the full MessageContext). > > > > This is currently not the case. Whereas the rest of Synapse is totally > > unaware of any Hessian specifics, the Hessian Builder/Formatter pair is > > actually the protocol dependent implementation. It is only used for > > Hessian Messages and has to be configured (activated) in axis2.xml for > > the specific content type. > > My statement was not precise enough. What I wanted to say is that > message formatters should be _transport_ protocol independent. On the > other hand, as you point out, they implement a specific _application_ > protocol. BTW, is Hessian used on other transport protocols, such as > JMS? Ah, sorry that I didn't get your point at first. This makes sense. I haven't seen some other transport protocol than http for Hessian so far as it is RPC oriented, but it should be possible to use other transports.
Regards, Eric
