CAS-1360: Implementation of the REST API with Spring @RestController

Contains all the changes from the review of earlier PR and also the GH pages REST documentation is updated with a pending PR. No unit tests yet (although tested fully manually locally), but could work on that and create a separate PR. Please note that the original restlet module does not contain unitit tests, so I personally think that this PR/module does not 'violate' it in this regard ;-)

Best,
D.
No, the default entry is the core idea here - it enables users to simply add the jar dependency to the pom in order to enable the REST support and not tinker with anything else! If no rest support jar is available on the classpath, the attempts to call /v1/* URIs would go through CAS' DispatcherServlet, not find any concrete handler mappings (it would if @RestController implementation is loaded via the rest support jar contributed bean) and redirect to the /login anyway. A win-win situation.—
Sent from Mailbox

On Thu, Jul 10, 2014 at 5:07 AM, LELEU Jérôme <notifications@github.com>
wrote:

>> @@ -169,6 +172,12 @@
>>      <url-pattern>/authorizationFailure.html</url-pattern>
>>    </servlet-mapping>
>>  
>> +  <!-- REST support if cas-server-extension-rest is included -->
> I don't think it should be here by default, it should be added when necessary, shouldn't it?
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/Jasig/cas/pull/458/files#r14755653