The mock implementations in o.a.s.servlet-helpers are actually quite complete for common use cases. What do you have in mind that might be missing?
Kind regards, Dirk On Tue, 2 Jun 2020 at 08:58, Konrad Windszus <[email protected]> wrote: > If you don’t have a request at hand it will be impossible to implement > fully. If you have a request just use regular request dispatching. > Konrad > > > > Am 02.06.2020 um 08:21 schrieb Carsten Ziegeler <[email protected]>: > > > > So you want to make an HTTP request from within Sling to itself? > > I wouldn't recommend doing this, but I see no problem of having this as > a new separate module, maybe starting in the whiteboard. > > > > Regards > > Carsten > > > >> Am 02.06.2020 um 06:10 schrieb Andreas Schaefer: > >> Hi > >> As of know - and place correct me if I am wrong - there is no way for a > service to call Sling internally as a request in a full fledged manner. > >> Even though one can call Sling internally through SlingRequestProcessor > usable Request and Response objects are only available as Mock objects and > therefore limited In their abilities. > >> So I am wondering if you guys would mind for me to build a service > providing the means to make internal Sling calls through the HTTP stack > with an official internal Sling Request / Response object that provides all > features applicable internally and removing most of the Unsupported > Operation Exceptions? > >> Cheers - Andy > > > > -- > > -- > > Carsten Ziegeler > > Adobe Research Switzerland > > [email protected] > > -- Dirk Rudolph | Senior Software Engineer Netcentric AG M: +41 79 642 37 11 D: +49 174 966 84 34 [email protected] | www.netcentric.biz
