Hi Ean, when I last looked I coudn't find much documentation on using axis for exposing REST services. I think it is possible to do some form of REST from axis, but the functionality is limited. Bear in mind that it is possible to expose REST using a plain JSP or servlet, but it is cumbersome.
I have put some instructions together at http://cwiki.apache.org/confluence/x/rQPi of manually exporting a service using REST with apache wink. When I have documented more manual REST options (e.g. json, rss, etc), I will look at how an ofbiz service definition for REST could be implemented. On Mon, Mar 8, 2010 at 8:52 PM, Ean Schuessler <[email protected]> wrote: > chris snow wrote: > >> On my current project, we have manually added REST support to ofbiz using >> the jersey implementation. >> >> I've been toying with the idea of adding configurable REST support to >> ofbiz >> services (similar to SOAP support using export="true"). >> >> > Axis2 supports REST interfaces. We can probably just configure Axis2 a > little differently and get REST support for free when you do export="true". > > -- > Ean Schuessler, CTO > [email protected] > 214-720-0700 x 315 > Brainfood, Inc. > http://www.brainfood.com > >
