Details

    • Similar Issues:
      Show 10 results 

      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)?

        Issue Links

          Activity

          Hide
          Scott Marlow
          added a comment - - edited

          JBAS-9066 is a possible dependency.

          Show
          Scott Marlow
          added a comment - - edited JBAS-9066 is a possible dependency.
          Hide
          Scott Marlow
          added a comment -

          This isn't a high priority for this release. The effort will continue on the https://github.com/scottmarlow/jboss-as/tree/multipleproviders_2 branch until its ready.

          Show
          Scott Marlow
          added a comment - This isn't a high priority for this release. The effort will continue on the https://github.com/scottmarlow/jboss-as/tree/multipleproviders_2 branch until its ready.
          Hide
          Scott Marlow
          added a comment -

          Committed some changes here https://github.com/scottmarlow/jboss-as/commit/18633d5c1f7dcb8e6e7f135b171eddacbbe659a2 and https://github.com/scottmarlow/jboss-as/commit/6b9aef5eac3c1c97db6d8cff66b735cf6d2f0821

          Am currently working on the Hibernate3 module for AS7. If everything goes as planned, JPA applications that include a copy of Hibernate 3 jars, will need to add a dependency on the "org.jboss.as.jpa.hibernate3" module (as described in https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7). This could be done by adding a MANIFEST.MF entry:
          Dependencies: org.jboss.as.jpa.hibernate3

          Or something like the above, depending on how this effort goes.

          Show
          Scott Marlow
          added a comment - Committed some changes here https://github.com/scottmarlow/jboss-as/commit/18633d5c1f7dcb8e6e7f135b171eddacbbe659a2 and https://github.com/scottmarlow/jboss-as/commit/6b9aef5eac3c1c97db6d8cff66b735cf6d2f0821 Am currently working on the Hibernate3 module for AS7. If everything goes as planned, JPA applications that include a copy of Hibernate 3 jars, will need to add a dependency on the "org.jboss.as.jpa.hibernate3" module (as described in https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7 ). This could be done by adding a MANIFEST.MF entry: Dependencies: org.jboss.as.jpa.hibernate3 Or something like the above, depending on how this effort goes.
          Hide
          Scott Marlow
          added a comment - - edited

          Comment deleted. I'll instead describe the changes in https://docs.jboss.org/author/display/AS7/JPA+Reference+Guide (after the code change is merged to as7).

          Show
          Scott Marlow
          added a comment - - edited Comment deleted. I'll instead describe the changes in https://docs.jboss.org/author/display/AS7/JPA+Reference+Guide (after the code change is merged to as7).
          Hide
          Scott Marlow
          added a comment -

          Integration support for Hibernate 4, will continue to be built in (Hibernate 4 jars are included with AS7). For Hibernate 3, the integration code will be in AS7 but the Hibernate 3 jars either need to be copied in or packaged with the application deployment.

          Show
          Scott Marlow
          added a comment - Integration support for Hibernate 4, will continue to be built in (Hibernate 4 jars are included with AS7). For Hibernate 3, the integration code will be in AS7 but the Hibernate 3 jars either need to be copied in or packaged with the application deployment.
          Hide
          Scott Marlow
          added a comment -

          Documentation explaining how to package Hibernate3 jars for JPA use, will be added to above mentioned doc link.

          http://community.jboss.org/thread/167590 describes how you can download a build with these changes.

          Although, I would rather see you download the AS7 source and build it yourself. Test, fix problems that you run into (the AS7 code is easy/fun to play with). More about this process is described in http://community.jboss.org/wiki/HackingOnAS7

          If you want to try the code changes for this jira, before the doc is written, just add hibernate3 jars to your deployment and set the following property in your persistence unit (persistence.xml file):
          <property name="jboss.as.jpa.providerModule" value="hibernate3-bundled"/>

          Show
          Scott Marlow
          added a comment - Documentation explaining how to package Hibernate3 jars for JPA use, will be added to above mentioned doc link. http://community.jboss.org/thread/167590 describes how you can download a build with these changes. Although, I would rather see you download the AS7 source and build it yourself. Test, fix problems that you run into (the AS7 code is easy/fun to play with). More about this process is described in http://community.jboss.org/wiki/HackingOnAS7 If you want to try the code changes for this jira, before the doc is written, just add hibernate3 jars to your deployment and set the following property in your persistence unit (persistence.xml file): <property name="jboss.as.jpa.providerModule" value="hibernate3-bundled"/>

            People

            • Assignee:
              Scott Marlow
              Reporter:
              David Lloyd
            • Votes:
              4 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: