> just keep in mind, that the scripts must be executed with the correct > (jcr) session. the jobs that are executed by the event handling might > to all run as 'admin'. where is the difference? you have to pass the correct session in both usecases, or did i miss something?
regards, philipp On 2/19/08, Tobias Bocanegra <[EMAIL PROTECTED]> wrote: > just keep in mind, that the scripts must be executed with the correct > (jcr) session. the jobs that are executed by the event handling might > to all run as 'admin'. > > regards, toby > > On 2/19/08, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > > On Feb 19, 2008 5:50 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > > > The question is which case is the special case? The one with the request > > > or the one without? Thinking of executing scripts as the task of the > > > script engine, this is foremost nothing to do with request. So, > > > personally, I see the request case as the special case :)... > > > > Ok, I might be off-base but in his post Alex says: > > > > > ...getting a ResourceResolver and executing a script without a request at > > > hand, > > > eg. within a thread that was triggered by an (job) event, would be cool > > > for > > > applications that goes beyond plain content delivery.... > > > > The ResourceResolver made me think that he needs a more complete > > environment than just executing a script. > > > > But yes you're right, if the use case can be simplified to not require > > a request, more power! > > > > -Bertrand > > > > > -- > -----------------------------------------< [EMAIL PROTECTED] >--- > Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel > T +41 61 226 98 98, F +41 61 226 98 97 > -----------------------------------------------< http://www.day.com >--- >
