Over at FamilySearch, I've been involved in supporting Flash application development that consumes a public POX API. It's not a REST API, but like REST, we provide a set of resources that are accessible at a given URI. Up to this point, our Flash developers have been stuck with parsing the resources as XML.
So you've got your JAX-WS or JAX-RS endpoints defined and implemented, and they're compiling, building and running smooth on your server. All is well, right? You've been diligent in documenting and testing your code, and the consumers of your API seem to be happy.
Well, that's just because they don't know what they're missing.
As of version 1.10, Enunciate will generate elegant client-side C# code and supply an AMF provider for your REST endpoints.
Enunciate 1.9 provides support for JAX-WS RI and CXF and generates a lightweight JAX-WS client-side library for accessing the endpoints.
For more information on how to use CXF with Enunciate:
Enunciate 1.8 was recently released with support for JAX-RS annotations. This means that Enunciate will now be able to process your Web service API as defined by JAX-WS (for SOAP endpoints) and JAX-RS (for REST endpoints).
OAuth for Spring Security was released this week, and I thought
I'd take a stab at why you might be interested.
What is OAuth?
I like to explain OAuth by describing the problem it is trying to solve. So here goes.
Enunciate 1.7 has been released!
The first part of this tutorial walked through the development of a Web service API that exposes its endpoints via SOAP, REST/XML, JSON, GWT-RPC, and AMF. In this second part of the tutorial, we intend to prove out this API.
So you've got a web application that needs to expose a Web service API. Maybe you're going to be writing a
href="http://en.wikipedia.org/wiki/Rich_Internet_application">Rich Internet Application (RIA) using
href="http://en.wikipedia.org/wiki/Adobe_Flex">Flex or some
If you haven't checked out the Enunciate project recently, you may want to give it another look to see how it can improve the development, deployment, and consumption of your Web service API.