Hi, yes, this stripping is really annoying but required - otherwise downstream users would have to deal with the details of JCR. Are these two events triggered by the same observation call, so maybe we could combine them into a single event?
Regards Carsten 2012/5/15 Justin Edelson <[email protected]>: > In JcrResourceListener, there's some code which strips off the > "jcr:content" path segment. This results in two events being produced with > the same path event property, but with different attributes, when, for > example, a file is uploaded. It seems like we should have some way (another > event property?) to differentiate between these two events. WDYT? > > Justin -- Carsten Ziegeler [email protected]
