Hi John,
I had a look and I could reproduce. I have used this module to hide
existing nodes (denies), that's why I've never run into it.
The root cause is that for the create case, not only [1] but also [2]
gets called (since there is no tree available). ResourceTypePattern [3]
always
Hi Marc,
On Sat, 2019-03-02 at 13:58 -0800, Marc Davenport wrote:
> Hello all,
> In our previous application based on Sling6 we used a maven assembly
> to build our application war. In the assembly we placed some classes
> into WEB-INF/lib and made felix provide these. I'm trying to shift
> us
On Mon, 2019-02-25 at 18:53 -0500, marc.davenp...@oracle.com wrote:
> I've been trying to rationalize the hit or miss nature of this
> problem.
> In my mind, I'm looking for a race condition. I'm going to bet that
> this is a configuration issue on our end, but I'm not sure how this
> would
Thanks Robert. I didn't see anything that indicated I could do this in the
code, but I was also open to the idea that I was reading the wrong part of the
model parsing. I think the person put things in WEB-INF because they were jars
that were not OSGI bundles. I have seen people wrapping jars
Thanks, Georg, for root causing the restriction problem. I've filed
https://jira.apache.org/jira/browse/SLING-8302 to document the problem. In the
meantime, I'll look into reformulating our access control policies as deny
restrictions.
Sorry for creating a new thread from a different email;
