Hello hessian experts,

we are using the hessian Java implementation (currently 3.0.20) for some
of our services with high performance requirements. 
In order to get more control about our services, have a centralized
service logging and so on we plan to use the WSO2 ESB.
Right now we are discussing with the WSO2 guys some ways to implement a
content based routing with minimal impact to the overall performance.
We only need to specify some custom header information like version
(major.minor), a unique client identification, a request-context
information and maybe one or two others.
So de-serializing and normalizing the whole message to an internal
XML-representation doesn't seem to be the best way to go, if
transformation and other features which would demand to convert the
whole message are not needed.
>From my point of view using custom http-headers doesn't seem to be the
right solution as well. This should be independent from low transport
protocols.

Reading the Hessian spec I found the following statements:

"Envelopes may have headers that specify routing or other special
processing information." [...] " The envelope syntax enables
compression, encryption, signatures, and any routing or context headers
to wrap a Hessian message."

But unfortunately I did not find an example of a hessian message with an
envelope and custom header information I could use for dynamic routing
decisions. So the questions are:

1) How would such a message look like? Could you please provide an
example!

2) How to create such a message with the Hessian Java API? Currently we
don't use any headers and simply do something like:

[...]
final AbstractHessianOutput hessianOut = factory.getHessianOutput(os);
hessianOut.call(methodName, args);
hessianOut.flush();
[...]

3) Do you have any hints to efficiently de-serialize only this header
information?

Thank you very much for your assistance!


Regards,
   Eric

--
Eric Hubert
Software Architect
Associate Director Research & Development
Jamba! GmbH

_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev

Reply via email to