On Aug 26, 2010, at 12:42 PM, Alexander Klimetschek <[email protected]> wrote:
> On Thu, Aug 26, 2010 at 18:38, Alexander Klimetschek <[email protected]> wrote: >> On Thu, Aug 26, 2010 at 16:52, Felix Meschberger <[email protected]> wrote: >>> You might also want to consider providing a SlingPostProcessor. >> >> No, I want to use the ModifyOperation in my context, not the other way >> around. Apart from doing an internal forward (I find this awkward, >> also not sure if this properly works for new nodes/resources created >> in the request's session), there is no way to "call" this useful, >> existing logic. > > An important part of my use case is that I first create a node using a > service that already exists and then want to run the modify operation > on the newly created node. This is difficult to do with another > SlingPostOperation... also that operation should not be used outside > of what my servlet defines (the operation namespace is kind of > "global"). > > Regards, > Alex > > -- > Alexander Klimetschek > [email protected] I agree with Alex that forwarding doesn't seem right. If one was to use an existing SlingPostOperation to create a composite (which is what this looks like), you would probably want to use a transaction and only commit the transaction at the end of the composite. It isn't directly related, but looking at the dependency between the two jackrabbit bundles and servlets.post (and some of my own code) along with this thread makes me think we do need to expose more of the post servlet innards to other bundles. There's good stuff in there which is of general use. As this means new APIs, let's be thoughtful about it. In the interim... Alex - can you use Embed-Dependency like jackrabbit-accessmanager does? It's not pretty, but works. Justin
