Up until now, I use Alfresco out of the box Webscripts based „tooling“ for REST service exploration. It feels a bit outdated and cumbersome – especially after playing with Nuxeo API playground last year – which made me jealous.
A few days ago, Alfresco announced that its new REST API Explorer product is live. The introductory post is mostly about how Alfresco plans to build APIs (Contract first, documentation, Swagger based). I think pretty much everybody agrees that it is a good idea to build on top of Swagger. However, I was missing details and did not get the motivation for some directions taken (Happens pretty frequently to me ?). I decided to give it a spin. My expectations were it being pretty similar to Nuxeo API playground.
Looking at the live version, I was missing functionality to enter an entry endpoint for an arbitrary (recent) Alfresco installation reachable from my browser. I was expecting it to allow CORS based usage just as the Nuxeo Playground does. Grabbed the source from github and had a closer look. Turns out the application indeed supports an endpoint URL from the query string. Unfortunately, it seems there is no dynamic repository endpoint available today, so the tool relies on a static file describing the APIs.
Time may tell. In the meantime, I hope they will introduce the dynamic repo endpoint. Will keep it around for playing with the „frequently used“ APIs it covers.
Getting CORS based access to work turns out to be really easy. Download the file below, drop it in
alfresco/WEB-INF/lib, restart the server, go here and run it against your local repository (or any other). Works for me using the 2016-GA releases.