Hello Ralph! Although Paul did answer your questions regarding the current status of the Hessian protocol support in Synapse, I'd like to add some comments - especially about reasons for the current "limitations".
> As far as I've seen, synapse 1.2 comes with a specific message formatter > and a message builder support for hessian. > I'm unsure what possibilites arise from these components. Currently Hessian messages are "wrapped" insight SOAP messages while the content stream (the byte message) will stay untouched. Of course this limits possible use cases, but also involves the smallest possible performance impact. > Is there a possibility to expose a hessian-based service as a SOAP-based > proxy service with the help of synapse? No, not yet as Paul already mentioned. > How is type mapping achieved in that case? As incomming Hessian message are not deserialized to form some "normalized" message format, there is no type mapping at the moment. > Is there a possibility to expose a SOAP-based web service as binary > hessian-based proxy service (e.g. for performance reasons)? No, such a solution currently does not exist. To be honest, I would not expect any performance improvements over a good SOAP stack. While converting between binary hessian messages and SOAP messages would offer flexibility and could solve some integration issues, I don't see a value from a performance perspective. Why? Synapse would need to deserialize incoming Hessian messages and transform them into a SOAP request which would be forwarded to the service. The SOAP-service reply again would need to be read and serialized to a binary Hessian stream. How shall this help performance? > Unfortunately, there is no further documentation and no example on how to > use synapse with hessian binary protocol. The uswe is totally transparent for a user. You send the Hessian message to the ESB instead of the Hessian service and the ESB forwards the request to the service. The same applies for the response. The only parameters which would need some documentation are the ones in synapse.properties to configure the in memory buffer for responses before synapse starts to stream data to disc. Regards, Eric
