The background servlets support makes use of SlingRequestProcessor for out-of-request execution. See BackgroundServletStarterFilter.java[0] for the starting point. The javadocs[1] may also help.
Regards Julian [0] http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/bgservlets/src/main/java/org/apache/sling/bgservlets/impl/BackgroundServletStarterFilter.java [1] http://sling.apache.org/apidocs/sling6/org/apache/sling/engine/SlingRequestProcessor.html On Mon, May 9, 2011 at 10:12 AM, JCR <[email protected]> wrote: > I tried to find the some information about (in the context of OSGi), but > frankly, was not really successful in it. > Do you have more precise pointers? > Would be highly appreciated. > > On 09.05.2011 00:41, Justin Edelson wrote: >> >> Did you try using the SlingRequestProcessor service as I suggested? >> >> On Sun, May 8, 2011 at 6:01 PM, JCR<[email protected]> wrote: >>> >>> Hi all, >>> >>> I'm looking for a pattern to call a sling resource from within an OSGi >>> bundle. >>> >>> My idea would be something with sling.include("/some/path.html"), but >>> this >>> does not seem to be possible, as it is not a service. >>> So, another option would be to do a full-sized HTTP GET call, which >>> sounds >>> like a lot of overhead. >>> >>> Thanks for any ideas. >>> Juerg >>> > >
