OpenEngSB
  1. OpenEngSB
  2. OPENENGSB-1966

Remove ConfigPersistenceBackend which uses default PersistenceService

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: framework-2.5.0
    • Fix Version/s: openengsb-3.0.0.M1
    • Component/s: framework
    • Labels:
    • Changelog:
      Hide
      Reason: The general ConfigPersistenceBackend uses the default PersistenceServcie which has various shortcomings like synchronisation errors, in memory storage, ... With the planned removal of the general PersistenceService there is also no use for this general ConfigPersistenceBackend anymore.

      Migration path: It is no longer possible to use the ConfigPersistenceBackend with the backend.id=persistence-service. Therefor please check your features.xml and/or your config file setup that none reference this backend.id. Instead you should use one of the specialized backends which use JPA, Files or any other form of persistence.

      Example
      From:
          <config name="org.openengsb.persistence.config-rule">
            backend.id=persistenceService
            configuration.id=RULEBASE
          </config>
      to:
          <config name="org.openengsb.persistence.config-rule">
            backend.id=ruleBaseJPAService
            configuration.id=RULEBASE
          </config>
      Show
      Reason: The general ConfigPersistenceBackend uses the default PersistenceServcie which has various shortcomings like synchronisation errors, in memory storage, ... With the planned removal of the general PersistenceService there is also no use for this general ConfigPersistenceBackend anymore. Migration path: It is no longer possible to use the ConfigPersistenceBackend with the backend.id=persistence-service. Therefor please check your features.xml and/or your config file setup that none reference this backend.id. Instead you should use one of the specialized backends which use JPA, Files or any other form of persistence. Example From:     <config name="org.openengsb.persistence.config-rule">       backend.id=persistenceService       configuration.id=RULEBASE     </config> to:     <config name="org.openengsb.persistence.config-rule">       backend.id=ruleBaseJPAService       configuration.id=RULEBASE     </config>
    • Sprint:
      Sprint 1, Sprint 2

      Description

      Once we have specific JPA Backends for the various objects, this backend is no longer needed.

        Gliffy Diagrams

          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

            Hide
            Lukas Stampf added a comment -

            This was once an issue, because we wanted to get rid of neodatis. Now that neodatis got replaced with a simple object storage, do we really want to get rid of it? As just an option to use it does no harm, does it?

            Show
            Lukas Stampf added a comment - This was once an issue, because we wanted to get rid of neodatis. Now that neodatis got replaced with a simple object storage, do we really want to get rid of it? As just an option to use it does no harm, does it?
            Hide
            Andreas Pieber added a comment -

            TBH I don't like this simple persistence. its just something too similar to e.g. JPA but with ways more limitations and more possibly hidden problems. So I'm definitely more in favor that users use the JPA instead of this mystically persistence interface.

            Show
            Andreas Pieber added a comment - TBH I don't like this simple persistence. its just something too similar to e.g. JPA but with ways more limitations and more possibly hidden problems. So I'm definitely more in favor that users use the JPA instead of this mystically persistence interface.
            Hide
            Andreas Pieber added a comment -

            please fill out the changelog field for this issue; in addition I think there should be two issues: one improvement for 3.x and one deprication for 2.x.y

            Show
            Andreas Pieber added a comment - please fill out the changelog field for this issue; in addition I think there should be two issues: one improvement for 3.x and one deprication for 2.x.y
            Hide
            Lukas Stampf added a comment -

            There is already an issue for the Deprecation: OPENENGSB-2185

            Show
            Lukas Stampf added a comment - There is already an issue for the Deprecation: OPENENGSB-2185

              People

              • Assignee:
                Lukas Stampf
                Reporter:
                Lukas Stampf
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Agile