jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1917) Report Info appends properties after content
Date Mon, 29 Dec 2008 17:14:44 GMT

    [ https://issues.apache.org/jira/browse/JCR-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659587#action_12659587
] 

Julian Reschke commented on JCR-1917:
-------------------------------------

DTD fragments in WebDAV specs aren't normative with respect to ordering (essentially because
that would break the extensibility model). See RFC 4918, Section 17.

So if you have a client that relies on specific ordering, that client essentially is broken.

> Report Info appends properties after content
> --------------------------------------------
>
>                 Key: JCR-1917
>                 URL: https://issues.apache.org/jira/browse/JCR-1917
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-webdav
>    Affects Versions: 1.5.0
>         Environment: N/A
>            Reporter: Philip Borlin
>
> RFC 3253 does not specify any ordering for reports, but RFC 4791 (CalDAV specification
which is built on top of WebDAV) contains DTD sequences that define the order the <prop>
elements occur within a report.
> Examples are from section 9.5:
> <!ELEMENT calendar-query ((DAV:allprop |
>                                     DAV:propname |
>                                     DAV:prop)?, filter, timezone?)>
> and from section 9.10
> <!ELEMENT calendar-multiget ((DAV:allprop |
>                                       DAV:propname |
>                                       DAV:prop)?, DAV:href+)>
> As of 1.5.0 org.apache.jackrabbit.webdav.version.report.ReportInfo the toXML(Document)
method specifically puts the content before the properties.  I request that we reverse the
order and put the properties first before the content.
> This fix should have no impact on WebDAV servers since ordering is not specified and
will allow CalDAV extensions to be built on top of jackrabbit's WebDAV.
> Failing to make this fix makes it impossible to add CalDAV extensions on top of jackrabbit's
WebDAV.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message