[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148952#comment-16148952
]
Julian Reschke commented on JCR-4173:
-------------------------------------
Turns out we have a set of problems in remoting:
1) Server: {{SubscriptionImpl}} attempts to serialize keys as XML elements in
no namespace, causing the XML to break when the name contains ":". Values are
always sent as plain strings.
2) Client: {{EventImpl.getEventInfo()}} actually assumes keys are Names
(namespace, localName), and values follow JCR Path syntax (again,
prefix-sensitive).
Even if the key handling would work, we'd still be fragile when the values
contain prefixes, as their mapping information isn't part of the XML.
The current code sort-of works for the keys defined in JCR 2.0 (as they are not
prefixed), but might fail if the path values contain elements in namespaces.
> Unable to receive observation events when connecting via DavEx
> --------------------------------------------------------------
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
> Project: Jackrabbit Content Repository
> Issue Type: Test
> Reporter: Robert Munteanu
> Assignee: Julian Reschke
> Attachments: OAK-6583.zip
>
>
> When connecting to an Oak repository by DavEx remoting ( via Sling ) event
> listeners are not notified of events they are registered for.
> Tracing down the problem I saw that the returned XML for {{POLL}} calls is
> invalid: {{::::1:529:-1:The prefix "jcr" for element "jcr:primaryType" is not
> bound.}}
> The raw XML returned is
> {noformat}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?><dcr:eventdiscovery
> xmlns:dcr="http://www.day.com/jcr/webdav/1.0";><dcr:eventbundle><dcr:event><D:href
>
> xmlns:D="DAV:">http://localhost:8888/server/default/jcr%3aroot/123d9c7a-9b14-4cc2-8436-3c2ca04e64ac/</D:href><dcr:eventtype><dcr:nodeadded/></dcr:eventtype><dcr:eventuserid>admin</dcr:eventuserid><dcr:eventuserdata/><dcr:eventdate>1503526390002</dcr:eventdate><dcr:eventidentifier>/123d9c7a-9b14-4cc2-8436-3c2ca04e64ac</dcr:eventidentifier><dcr:eventinfo><jcr:primaryType>nt:unstructured</jcr:primaryType></dcr:eventinfo></dcr:event><dcr:event><D:href
>
> xmlns:D="DAV:">http://localhost:8888/server/default/jcr%3aroot/123d9c7a-9b14-4cc2-8436-3c2ca04e64ac/jcr%3aprimaryType</D:href><dcr:eventtype><dcr:propertyadded/></dcr:eventtype><dcr:eventuserid>admin</dcr:eventuserid><dcr:eventuserdata/><dcr:eventdate>1503526390002</dcr:eventdate><dcr:eventidentifier>/123d9c7a-9b14-4cc2-8436-3c2ca04e64ac</dcr:eventidentifier><dcr:eventinfo><jcr:primaryType>nt:unstructured</jcr:primaryType><afterValue>nt:unstructured</afterValue></dcr:eventinfo></dcr:event></dcr:eventbundle></dcr:eventdiscovery>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
