Hi Eric
Sure, if you only want to route on the "To" address (Hessian does not
seem to use any specific transport headers like SOAPAction etc),
What do you mean by the "To" address? Just the URL?
Yes, this means the scheme, hostname, port and path, from what I found
out looking briefly into Hessian, the Hessian payload is transported
over http (and https?).. but I did not come across any custom transport
(i.e. http) headers used by Hessian.. can you point me to any if they do
exist?
I'm thinking of the usage of a Hessian Envelope with any custom header
information.
The spec states the following:
"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."
So my thought was to use custom headers within the Hessian Envelope and
"expose" only this information to the ESB.
What do you think?
Sure, but a sample message with the custom headers etc. that you have in
mind and the sample routing decision you want to make with the ESB would
be really useful at this point in time. I believe encryption,
compression and signatures etc are all within the Hessian payload, and
thus hidden from the ESB use case scenarios you have in mind - am I right?
We only need to specify and access some custom header information and use these
as a
source for CBR and logging.
Are these http/s headers?
asankha
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
