Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support for DAV:status code and DAV:location, plus sync-collection fix #230

Closed
wants to merge 11 commits into from

Conversation

dankarp
Copy link
Collaborator

@dankarp dankarp commented Oct 19, 2015

  • expose DavResource's optional DAV:status value

    DAV resources may contain a DAV:status instead of a DAV:propstat.
    We parse these optional status lines and expose the status code
    (or 200 when absent) via DavResource.getStatusCode.

    A small code reorg moves the propstat properties as final members
    of an inner class.

  • complete DAV:response by including DAV:location element

    RFC 4918 includes a "location" element in a DAV:response:

       <!ELEMENT response (href, ((href*, status)|(propstat+)),
                           error?, responsedescription? , location?) >

       <!ELEMENT location (href)>
Add support for an optional <DAV:location> element in a
<DAV:response> by updating webdav.xsd and generating new
Response and Location JAXB model classes.  (We also update the
ObjectFactory, which is not currently auto-generated.)

Note that the location value is not currently exposed by
DavResource.
  • minor fixes for the sync-collection report

    Fix DAV:sync-collection in webdav.xsd by straightening out the
    property order, the allowable DAV:sync-limit values, and the
    syntax of the DAV:limit element. Update the JAXB model classes
    and our SyncCollectionReport object as appopriate.

dankarp and others added 11 commits September 22, 2015 16:34
Fix <DAV:sync-collection> in webdav.xsd by straightening out the
property order, the allowable <DAV:sync-limit> values, and the
syntax of the <DAV:limit> element.  Update the JAXB model classes
and our SyncCollectionReport object as appopriate.
RFC 4918 includes a "location" element in a <DAV:response>:

   <!ELEMENT response (href, ((href*, status)|(propstat+)),
                       error?, responsedescription? , location?) >

   <!ELEMENT location (href)>

Add support for an optional <DAV:location> element in a
<DAV:response> by updating webdav.xsd and generating new
Response and Location JAXB model classes.  (We also update the
ObjectFactory, which is not currently auto-generated.)

Note that the location value is not currently exposed by
DavResource.
DAV resources may contain a <DAV:status> instead of a <DAV:propstat>.
We parse these optional status lines and expose the status code
(or 200 when absent) via DavResource.getStatusCode.

A small code reorg moves the propstat properties as final members
of an inner class.
@dkocher
Copy link
Collaborator

dkocher commented Feb 19, 2016

Can you please rebase with the master branch which will also make the tests green.

@dkocher
Copy link
Collaborator

dkocher commented Feb 22, 2016

Replaced by pull request #241.

@dkocher dkocher closed this Feb 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants