Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2
    • Component/s: config, jackrabbit-core
    • Labels:
      None

      Description

      Bundle persistence has been the recommended default since Jackrabbit 1.3, and there is little reason for anyone to be using non-bundle persistence anymore. Thus I'd like to deprecate all non-bundle PMs in Jackrabbit 2.2 and target for their removal in Jackrabbit 3.0.

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Resolved Resolved
          5d 10h 59m 1 Jukka Zitting 08/Nov/10 23:52
          Resolved Resolved Closed Closed
          364d 15h 59m 1 Jukka Zitting 08/Nov/11 15:52
          Bart van der Schans made changes -
          Link This issue relates to JCR-3183 [ JCR-3183 ]
          Jukka Zitting made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Hide
          karan singh malhi added a comment -

          What about the InMemPersistenceManager? I do not see a replacement for it in the o.a.j.c.persistence.bundle package.

          Show
          karan singh malhi added a comment - What about the InMemPersistenceManager? I do not see a replacement for it in the o.a.j.c.persistence.bundle package.
          Jukka Zitting made changes -
          Field Original Value New Value
          Status Open [ 1 ] Resolved [ 5 ]
          Assignee Jukka Zitting [ jukkaz ]
          Resolution Fixed [ 1 ]
          Hide
          Jukka Zitting added a comment -

          I deprecated all the non-bundle persistence managers in revision 1032784.

          In revision 1032787 I added a generic mechanism that logs warnings for all kinds of deprecated configuration entries.

          Show
          Jukka Zitting added a comment - I deprecated all the non-bundle persistence managers in revision 1032784. In revision 1032787 I added a generic mechanism that logs warnings for all kinds of deprecated configuration entries.
          Hide
          Claus Köll added a comment -

          +1

          Show
          Claus Köll added a comment - +1
          Hide
          Felix Meschberger added a comment -

          +1

          Show
          Felix Meschberger added a comment - +1
          Hide
          Alexander Klimetschek added a comment -

          +1

          Show
          Alexander Klimetschek added a comment - +1
          Hide
          Stefan Guggisberg added a comment -

          +1

          Show
          Stefan Guggisberg added a comment - +1
          Hide
          Jukka Zitting added a comment -

          I was thinking of deprecating them in the source code (and any relevant documentation) and mentioning this in the 2.2 release notes. A log warning would be a nice extra.

          Show
          Jukka Zitting added a comment - I was thinking of deprecating them in the source code (and any relevant documentation) and mentioning this in the 2.2 release notes. A log warning would be a nice extra.
          Hide
          Marcel Reutegger added a comment -

          +1

          Would that just be in the source code or do you intend to also log some kind of warning when a non-bundle PM is still in use in 2.2?

          Show
          Marcel Reutegger added a comment - +1 Would that just be in the source code or do you intend to also log some kind of warning when a non-bundle PM is still in use in 2.2?
          Jukka Zitting created issue -

            People

            • Assignee:
              Jukka Zitting
              Reporter:
              Jukka Zitting
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development