Hi Thanks for the reply.
Regarding the JCR Event (NODE_ADDED) I want to be able to listen to Nodes being added no matter if they are regular JCR nodes or Synthetic Nodes. This would enable to augment JCR Nodes with Synthetic Nodes. We want to use Synthetic Nodes to avoid boilerplate nodes that just refer to other nodes through Sling Resource Super Types. - Andy > On Mar 9, 2021, at 12:05 AM, Carsten Ziegeler <[email protected]> wrote: > > Hi, > > A resource provider can access its parent provider (which usually is the JCR > resource provider) through the ResolveContext which is passed to the resource > provider. > > Synthetic resources are not persisted and are usually only used during > resolving, but not during getResource. > > I'm wondering what the use case is to send out an event? > > Regards > Carsten > > Am 08.03.2021 um 20:09 schrieb Andreas Schaefer: >> Hi >> I have a few question regarding using Synthetic Resource and Resource >> Providers: >> 1. So far I was only able to create Synthetic Resources in a dedicated >> folder as the Resource Provider cannot use the Resource Resolver in >> getResource() to access the JCR repository as the RR always goes back to the >> Resource Provider creating an endless loop >> Is there a way to access the JCR Repository inside the >> ResourceProvider.getResource()? >> 2. Send an JCR Node Added Event when I create a Synthetic Resource >> Is there a way to send a JCR Event.NODE_ADDED event? >> Thanks - Andy > > -- > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected]
