Hi,
This style of REST is supported. There are 2 options, probably more,
assuming that you have written your Api implementing using servlets. Mount
the servlets at a hard coded path using the sling servlet annotation, but
this won't allow you to acl the end point, or give the Api a resource type,
On Apr 10, 2014, at 11:26 PM, Ian Boston i...@tfd.co.uk wrote:
Hi,
This style of REST is supported. There are 2 options, probably more,
assuming that you have written your Api implementing using servlets. Mount
the servlets at a hard coded path using the sling servlet annotation, but
On Friday, April 11, 2014, Tyson Norris tnor...@adobe.com wrote:
On Apr 10, 2014, at 11:26 PM, Ian Boston i...@tfd.co.uk javascript:;
wrote:
Hi,
This style of REST is supported. There are 2 options, probably more,
assuming that you have written your Api implementing using servlets.
Hi Tyson
Am 11.04.2014 um 00:35 schrieb Tyson Norris tnor...@adobe.com:
along the lines of supporting REST-ful APIs, is there any way (mapping? etc)
to support an api like :
GET /api/v1/foo/bar
First and foremost: don't do the v1 thing since it is just wrong. An URL
addresses a resource
Konrad Windszus created SLING-3499:
--
Summary: Support custom annotations with Sling Models
Key: SLING-3499
URL: https://issues.apache.org/jira/browse/SLING-3499
Project: Sling
Issue Type:
