CXF’s HTTP Binding not RESTy enough for Sanjiva?

December 3rd, 2006

The other day Sanjiva made a few comments about the CXF REST support. Glad to see its getting noticed! But I’d also like to add a few corrections:

What Dan is working on for CXF is what Axis2 has: support for the WSDL 2.0 HTTP binding. (That in itself is kinda interesting since he previously claimed that what Axis2 had was “ugly”.)

AFAIK Axis2 does not support the full WSDL 2.0 HTTP binding concepts, which is part of the reason I called it ugly. First, it doesn’t handle PUT and DELETE, it only supports GET and POST operations. Second, and more importantly, it doesn’t support using URI templates. Both those concepts are core parts of the WSDL2 HTTP binding, so I’m not sure how he can state that Axis2 has implemented it.

Further on:

Adding a few annotations to a Java class does not suddenly make that class which was offering a service into a resource: Its just a service with a nice HTTP binding. 

Not true. I would phrase things this way: CXF lets you design your resources however you want. Those resources can the be backed by an operation - just like they might be backed by a file system. We also allow you to map to different verbs for adding, deleting, and updating. The annotations don’t make your service RESTy, but they do enable you to create a REST style architecture with HTTP.

Comments are closed.