Details

      Description

      i didn't look at the details just realized that all EventJournalTest of the TCK fail in the setup
      jcr2spi - spi2dav(ex) - jcr-server.
      i assume that this is due to missing implementation (the corresponding SPI method throws UnsupportedRepositoryOperationException).

      1. 2541.diff
        42 kB
        Julian Reschke
      2. JCR-2541.diff
        50 kB
        Julian Reschke

        Issue Links

          Activity

          angela created issue -
          angela made changes -
          Field Original Value New Value
          Summary spi2dav : EventJournal not (properly) implemented spi2dav : EventJournal not implemented
          Description i didn't look at the details just realized that all EventJournalTest of the TCK fail in the setup
          jcr2spi - spi2dav(ex) - jcr-server.
          i assume that this is due to missing or incomplete implementation.
          i didn't look at the details just realized that all EventJournalTest of the TCK fail in the setup
          jcr2spi - spi2dav(ex) - jcr-server.
          i assume that this is due to missing implementation (the corresponding SPI method throws UnsupportedRepositoryOperationException).
          angela made changes -
          Component/s observation [ 11613 ]
          angela made changes -
          Link This issue is duplicated by JCR-2794 [ JCR-2794 ]
          Hide
          Julian Reschke added a comment -

          If I understand correctly, we'll need a new variant of SUBSCRIBE/POLL/UNSUBSCRIBE for this, right?

          Show
          Julian Reschke added a comment - If I understand correctly, we'll need a new variant of SUBSCRIBE/POLL/UNSUBSCRIBE for this, right?
          Hide
          Julian Reschke added a comment -

          I discussed this with Marcel last week, summary:

          • implement the EventJournal as a "feed" resource
          • filtering happens client-side, same as for observation
          • feed format would be Atom (RFC 4287) unless there's a strong reason not to
          • getting events "since" can be implemented using the If-None-Match/Vary, using the timestamp as etag

          To be discussed: discovery of the feed URI

          Show
          Julian Reschke added a comment - I discussed this with Marcel last week, summary: implement the EventJournal as a "feed" resource filtering happens client-side, same as for observation feed format would be Atom (RFC 4287) unless there's a strong reason not to getting events "since" can be implemented using the If-None-Match/Vary, using the timestamp as etag To be discussed: discovery of the feed URI
          Julian Reschke made changes -
          Assignee Julian Reschke [ reschke ]
          Julian Reschke made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Hide
          Julian Reschke added a comment -

          Work in progress: implementation of EventJournal as Atom feed. Entry details missing; consumer side missing as well.

          Show
          Julian Reschke added a comment - Work in progress: implementation of EventJournal as Atom feed. Entry details missing; consumer side missing as well.
          Julian Reschke made changes -
          Attachment ejpatch.diff [ 12506143 ]
          Hide
          Julian Reschke added a comment -

          Proposed patch.

          Show
          Julian Reschke added a comment - Proposed patch.
          Julian Reschke made changes -
          Attachment ejpatch6.diff [ 12506447 ]
          Hide
          Julian Reschke added a comment -

          Updated patch (cleaned up and somewhat prepared for PERSIST events)

          Show
          Julian Reschke added a comment - Updated patch (cleaned up and somewhat prepared for PERSIST events)
          Julian Reschke made changes -
          Attachment ejpatch8.diff [ 12506606 ]
          Hide
          Julian Reschke added a comment -

          Proposed patch, compatible with PERSIST events, but not taking advantage of them yet

          Show
          Julian Reschke added a comment - Proposed patch, compatible with PERSIST events, but not taking advantage of them yet
          Julian Reschke made changes -
          Attachment JCR-2541.diff [ 12506621 ]
          Julian Reschke made changes -
          Attachment ejpatch.diff [ 12506143 ]
          Julian Reschke made changes -
          Attachment ejpatch6.diff [ 12506447 ]
          Julian Reschke made changes -
          Attachment ejpatch8.diff [ 12506606 ]
          Julian Reschke made changes -
          Link This issue is related to JCR-3179 [ JCR-3179 ]
          Hide
          Julian Reschke added a comment -

          Proposed patch.

          Show
          Julian Reschke added a comment - Proposed patch.
          Julian Reschke made changes -
          Attachment 2541.diff [ 12507000 ]
          Julian Reschke made changes -
          Attachment JCR-2541.diff [ 12506621 ]
          Hide
          Julian Reschke added a comment -

          Updated patch, incl. more documentation, and enhanced DomUtil functionality in order to reduce namespace noise.

          Show
          Julian Reschke added a comment - Updated patch, incl. more documentation, and enhanced DomUtil functionality in order to reduce namespace noise.
          Julian Reschke made changes -
          Attachment JCR-2541.diff [ 12507190 ]
          Julian Reschke made changes -
          Status In Progress [ 3 ] Resolved [ 5 ]
          Fix Version/s 2.4 [ 12318241 ]
          Resolution Fixed [ 1 ]
          Jukka Zitting made changes -
          Fix Version/s 2.3.6 [ 12319192 ]
          Fix Version/s 2.4 [ 12318241 ]
          Jukka Zitting made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            • Assignee:
              Julian Reschke
              Reporter:
              angela
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development