Looking closer, things make even less sense. Both times the event is called the jcr:content sub node also exists.
I don't know if this is a problem in sling's webdav implementation or if it's a problem in our webdav client. Rob On Apr 17, 2013, at 5:08 PM, Robert A. Decker wrote: > Hi, > > We're sharing a node over webdav and monitoring added, removed, changed > events. > > When we remove a node we see two events with the path like we'd expect: > topic:org/apache/sling/api/resource/Resource/REMOVED > path:/content/bmn/iarpa/metaphor/drives/outbox/1366206196.meta/jcr:content > topic:org/apache/sling/api/resource/Resource/REMOVED > path:/content/bmn/iarpa/metaphor/drives/outbox/1366206196.meta > > But when we add a node we see two events like we'd expect, but we don't see > the jcr:content added event. Instead we see two events for the filename node: > topic:org/apache/sling/api/resource/Resource/ADDED > path:/content/bmn/iarpa/metaphor/drives/outbox/1366206196-1.complete > topic:org/apache/sling/api/resource/Resource/ADDED > path:/content/bmn/iarpa/metaphor/drives/outbox/1366206196-1.complete > > I would expect the second one to look like: > topic:org/apache/sling/api/resource/Resource/ADDED > path:/content/bmn/iarpa/metaphor/drives/outbox/1366206196-1.complete/jcr:content > > I've tried it with files with and without content and it gives the same > results. > > Rob
