Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-647 pluggable JPA providers
  3. AS7-566

Support for pluggable JPA providers

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • 7.0.1.Final
    • None
    • JPA / Hibernate
    • None

    Description

      Maybe we could have a service per persistence provider that is based on a configuration settings.

      Questions:

      1. Where do the persistent provider jars go in the system? Should we deploy them somehow?

      2. Each persistence.xml specifies the javax.persistence.spi.PersistenceProvider class name (via provider element) that it will use (defaults to whatever the AS7 default persistence provider). The persistence.xml also allows vendor properties to be specified.

      3. How could we best dynamically build a ModuleDependency on a persistence provider jar that
      could be injected into a deployment (perhaps from JPADependencyProcessor)?

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. AS7-388 Detect, filter, and act upon system APIs found in deployments

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. AS7-413 Rename "jboss-structure.xml" to "jboss-deployment-structure.xml"

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Sub-task - The sub-task of the issue AS7-560 restructure use of JPA persistence provider specific details

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Sub-task - The sub-task of the issue AS7-574 Deploy compatible versions of the Hibernate persistence provider with application deployments

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              smarlow1@redhat.com Scott Marlow
              dlloyd@redhat.com David Lloyd
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: