Hi everyone, I just have a case where I have to split away some content from the original location and split parts in a dedicated subresource. I also have the constraint that access must work exactly the same (so the resourcetree should work like before while persistance splits the attributes up. This sounds like a case for ResourceDecorator but since this is just for a small content branch and ResourceDecorators are way to intrusive.
The option I found was to hook in a ResourceProvider, set a threadlocal flag for "internal Resolution", perform another resolve for the same path, return null for an internal resolve (therefore bubble to next ResourceProvider) reset the threadlocal and wrap the returned resource. But, thread locals always feel a bit hacky and I wonder if there is another option. I yet haven't seen a way to bubble through the resourceProviders or directly address specific ResourceProviders. Any idea how I could improve for that scenario? Cheers Dominik
