Hi Carsten, sorry, I was not very specific about "scripting", indeed. IIUC one needs to supply an OSGi bundle in order to be able to tweak the POST behavior. What I would like to do is adjust the POST behavior without having to resort to deploying an OSGi bundle i.e. directly from a JSP. For example, if one could write a POST.jsp that executes the default behavior and passes back the change list (additionally to the mechanism proposed by you): <% changes = Sling.defaultPOSTBehaviour(); // do some more %> (this code is an illustration of what I mean rather than an actual suggestion) The use cases in the back of my mind are a) adding mixins to newly created nodes and b) comment spam prevention on a blog.
Cheers Michael On Tue, Jul 22, 2008 at 11:12 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > Michael Marth wrote: > >> Carsten, >> in your proposal how would available processors be discovered? Would they >> explicitly register or be discovered by OSGi mechanisms? I also wonder if >> the functionality would be available from scripts? >> thanks for explaining >> > > The processors are OSGi services that use the osgi service registry, so the > post servlet would fetch all registered processors and apply them. > > This scripting stuff is mentioned all the time here :) Can you elaborate > how you would like to use these processors from scripting? Btw, you can get > all registered processors in a script through the "sling" object. > > Carsten > > -- > Carsten Ziegeler > [EMAIL PROTECTED] > -- Michael Marth | Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/
