2012/5/16 Felix Meschberger <[email protected]>: > Hi, > > Am 16.05.2012 um 08:44 schrieb Carsten Ziegeler: > >> 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? > > Aren't they combined already ? If not, we should try to do it. > > On a related note: I wonder, whether we should not split the > JcrResourceListener into a separate JCR2OSGi Event bridge bundle ?
As we're splitting the resource resolver/factory from the jcr bundle, I think we can leave it in the pure jcr resource bundle then. Carsten > > Regards > Felix > >> >> 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] > -- Carsten Ziegeler [email protected]
