I think I see what you mean. In my head I'm trying to think of the benefits of using CXFRS or Restlet instead of straight HTTP... but in truth I'm not coming up with many. I'm ultimately just going to take the resulting XML and unmarshal it via JAXB, then throw non-HTTP 200 response codes as an exception.
Am I grossly oversimplifying things? Or are the benefits of Restlet/CXFRS just limited to helper methods and URI templates? willem.jiang wrote: > > After doing some research work on the HTTP authentication and cookies, I > found it could be better to choice camel-http component[1] to do the job. > It provides you more easy way to set the cookies from the Http header. > > Willem Jiang wrote: >> I just checked the Restlet Request Object , it supports to set the >> Cookies on the Request Object. It should be easy to support it in >> camel-restlet. Please feel free to create a JIRA[1] for it. > -- View this message in context: http://old.nabble.com/Setting-Cookie-Header-in-Restlet-Request-tp27839785p27855022.html Sent from the Camel - Users mailing list archive at Nabble.com.
