ML7: Ability to deploy Search API response transform

[peterskim12]

The Java and REST API in MarkLogic 7 will be updated to support specifying an XSLT or XQuery module to apply to the search results response as a transform.

It's not clear exactly how these are persisted in the database but it may be a useful feature for Roxy to be able to deploy these as a part of the 'deploy modules' process.

The Roxy project will need to have some directory where the user can put their search transforms, similar to how the rest-ext directory exists for the REST API extensions.

[dmcassel]

Transforms are used in the document endpoints now. I haven't used them enough to think about good ways to deploy, but yes, I agree this should get done.

[peterskim12]

Cool, I didn't realize that this already existed for document endpoints.
Looks like we just need to make a PUT request:

PUT /v1/config/transforms/{name}

We could have a directory called 'transforms' and the filename (without file extension) would be the name of the transform.

e.g. the transform at <roxy_dir>/transforms/my-search-result-transform.xqy
would be PUT to:
/v1/config/transforms/my-search-result-transform

[dmcassel]

Simple enough.

At the same time, I'm thinking of changing the default directories for rest-related stuff. Currently, there's rest-api/ for options and properties and rest-ext for extensions. I'm thinking this would be better:

rest-api/config
rest-api/ext
rest-api/transforms

The deployer keys off the locations in properties files, so the deploy process wouldn't change, just the initialization.