Good morning folks! This is more of a approach/design question rather than an Axis2/C question.
The project I am working on requires that I provide both SOAP and REST interface to my webservice. With Axis2/C SOAP is no big deal. But REST is something I am not too sure about. As it says in the API documentation itself, Axis2/C is a SOAP toolkit and REST is not supported that well. These 2 issues in particular 1) There is no support for PUT and DELETE 2) Also the way Axis2/C requires the operation name and the operation parameters in the url, is a shift away from REST as there is no resource representation. So the solution looks like writing an Apache module (I have never written one before) which receives the REST request, translates the request to a SOAP request and then forwards it on to Axis2/c. But this is exactly what Axis2/C is also doing. I want to start looking in to improving REST support in Axis2/C. Is it doable? Am I missing something very obvious which would prevent us from implementing such support in Axis2? If not please let me know as to where I should start looking in the Axis2 source. If the above approach is not feasible, I will have to look at other ways of supporting REST. One way would be to write my own apache module. I would love to hear any comments/suggestions. Thanks a lot for all the help! Subra
