Hi all The RequestPathInfo object (retrieved from SlingHttpServletRequest.getRequestPathInfo()) allows access to decomposed request path information. One piece of which is the request suffix which is the part of the URL path after the resource address (incl. selectors and extension).
Often times such a suffix is used as a secondary resource address, mostly in administrative console contexts. If would be helpful to be able to get a resource addressed by the suffix directly from the RequestPathInfo project to prevent error-prone template code all-over. For details see also SLING-2670 [1]. I have also attached a complete patch there including the API change, the implementation and the increment in the API export version. The consequence of this API change is, that all implementors of the org.apache.sling.api.request package have to be updated. Looking at the package this is mostly Sling core stuff plus implementors of the SlingRequestListener interface. WDYT ? Regards Felix [1] https://issues.apache.org/jira/browse/SLING-2670
