Hi,

I don't think we have the camel-hessina component, and we love contribution, 
please share the idea with us :)

I think you can take a look at the camel-xmlrpc[1] component
I just have quick question of the methodName option. What's the prepose of 
methodName? If you need to specify the methodName, you may also need to provide 
a Interface class for camel-hassina endpoint to use.


--  
Willem Jiang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) 
(English)
          http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem





On Wednesday, July 17, 2013 at 3:54 PM, flangel wrote:

> Hi,
>  
> what is the current state of hessian support. I like to use Hessian as a
> "from" endpoint, i.e. start the route by exposing an http endpoint and
> decoding the payload. Something along the line of from ("hessian:\\uri).
>  
> Currently, i am using an http endpoint and add a processor that decodes the
> hessian wire protocol/payload.
>  
> Question:
>  
> 1. Does a Hessian component that provides a consumer (From) endpoint already
> exist. I could not find any source code/examples.
>  
> 2. If not, and if you are experienced with Hessian, what would a good api be
> for the hessian "from" endpoint. What about from
> ("hessian:\\uri\<Service>?methodName=method1). This would create an endpoint
> waiting for the invocation of method1 through a client. The client created a
> factory connection to \\uri\<Service> previously to invoking the method.
>  
> 3. the "to" case would be rather simple
> to("hessian:\\<uri>\service?methodName=method1) with the parameters in the
> header  
>  
> Your feedback is appreciated
> Best
> Frank
>  
>  
>  
>  
>  
>  
>  
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Hessian-support-from-to-endpoints-tp5735774.html
> Sent from the Camel - Users mailing list archive at Nabble.com 
> (http://Nabble.com).



Reply via email to