12:54 p.m.
Support for pluggable JPA providers
-----------------------------------
Key: JBAS-9040
URL: https://issues.jboss.org/browse/JBAS-9040
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.0.0.CR1
Issue to track support for pluggable persistence providers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:05 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-9040) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/JBAS-9040?page=com.atlassian.jira.plugin....
]
Scott Marlow updated JBAS-9040:
-------------------------------
Parent: JBAS-8959
Issue Type: Sub-task (was: Task)
Support for pluggable JPA providers
-----------------------------------
Key: JBAS-9040
URL: https://issues.jboss.org/browse/JBAS-9040
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.0.0.CR1
Issue to track support for pluggable persistence providers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:35 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-9040) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/JBAS-9040?page=com.atlassian.jira.plugin....
]
Scott Marlow updated JBAS-9040:
-------------------------------
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
was:Issue to track support for pluggable persistence providers.
Support for pluggable JPA providers
-----------------------------------
Key: JBAS-9040
URL: https://issues.jboss.org/browse/JBAS-9040
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.0.0.CR1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:09 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-9040) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/JBAS-9040?page=com.atlassian.jira.plugin....
]
Scott Marlow edited comment on JBAS-9040 at 3/19/11 11:08 AM:
--------------------------------------------------------------
JBAS-9066 is is a possible dependency.
was (Author: smarlow):
This is a possible dependency at this point.
Support for pluggable JPA providers
-----------------------------------
Key: JBAS-9040
URL: https://issues.jboss.org/browse/JBAS-9040
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.0.0.CR1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:09 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-9040) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/JBAS-9040?page=com.atlassian.jira.plugin....
]
Scott Marlow edited comment on JBAS-9040 at 3/19/11 11:08 AM:
--------------------------------------------------------------
JBAS-9066 is a possible dependency.
was (Author: smarlow):
JBAS-9066 is is a possible dependency.
Support for pluggable JPA providers
-----------------------------------
Key: JBAS-9040
URL: https://issues.jboss.org/browse/JBAS-9040
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.0.0.CR1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:37 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-9040) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/JBAS-9040?page=com.atlassian.jira.plugin....
]
Scott Marlow updated JBAS-9040:
-------------------------------
Component/s: JPA / Hibernate
Support for pluggable JPA providers
-----------------------------------
Key: JBAS-9040
URL: https://issues.jboss.org/browse/JBAS-9040
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.0.0.CR1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-9040) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/JBAS-9040?page=com.atlassian.jira.plugin....
]
Scott Marlow updated JBAS-9040:
-------------------------------
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.
Support for pluggable JPA providers
-----------------------------------
Key: JBAS-9040
URL: https://issues.jboss.org/browse/JBAS-9040
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.0.0.CR1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:03 a.m.
New subject: [JBoss JIRA] Updated: (AS7-566) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow updated AS7-566:
-----------------------------
Fix Version/s: 7.1.0.Alpha1
(was: 7.0.0.CR1)
Support for pluggable JPA providers
-----------------------------------
Key: AS7-566
URL: https://issues.jboss.org/browse/AS7-566
Project: Application Server 7
Issue Type: Sub-task
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.1.0.Alpha1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:46 p.m.
New subject: [JBoss JIRA] Commented: (AS7-566) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on AS7-566:
----------------------------------
Committed some changes here
https://github.com/scottmarlow/jboss-as/commit/18633d5c1f7dcb8e6e7f135b17...
and
https://github.com/scottmarlow/jboss-as/commit/6b9aef5eac3c1c97db6d8cff66...
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. :-)
Support for pluggable JPA providers
-----------------------------------
Key: AS7-566
URL: https://issues.jboss.org/browse/AS7-566
Project: Application Server 7
Issue Type: Sub-task
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.1.0.Alpha1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:54 p.m.
New subject: [JBoss JIRA] Commented: (AS7-566) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on AS7-566:
----------------------------------
Will need a jboss-deployment-structure.xml rather than MANIFEST.MF entries. Also need one
more change for locating PersistenceProviderAdaptor implementations (the integration
classes). Will need a META-INF/services entry in each of the integration modules.
services/org.jboss.as.jpa.spi.PersistenceProviderAdaptor
org.jboss.as.jpa.hibernate3.HibernatePersistenceProviderAdaptor
<jboss-deployment-structure>
<deployment>
<exclusions>
<module name="org.hibernate"/>
</exclusions>
<dependencies>
<module name="org.jboss.as.jpa.hibernate3"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
Support for pluggable JPA providers
-----------------------------------
Key: AS7-566
URL: https://issues.jboss.org/browse/AS7-566
Project: Application Server 7
Issue Type: Sub-task
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.1.0.Alpha1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:58 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (AS7-566) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow edited comment on AS7-566 at 7/16/11 12:57 AM:
------------------------------------------------------------
Will need a jboss-deployment-structure.xml rather than MANIFEST.MF entries. Also need one
more change for locating PersistenceProviderAdaptor implementations (the integration
classes). Will need a META-INF/services entry in each of the integration modules.
jboss-as-jpa-hibernate3.jar/META-INF/services/org.jboss.as.jpa.spi.PersistenceProviderAdaptor
will contain:
{quote}
org.jboss.as.jpa.hibernate3.HibernatePersistenceProviderAdaptor
{quote}
jboss-deployment-structure.xml will contain:
{code}
<jboss-deployment-structure>
<deployment>
<exclusions>
<module name="org.hibernate"/>
</exclusions>
<dependencies>
<module name="org.jboss.as.jpa.hibernate3"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
{code}
was (Author: smarlow):
Will need a jboss-deployment-structure.xml rather than MANIFEST.MF entries. Also need
one more change for locating PersistenceProviderAdaptor implementations (the integration
classes). Will need a META-INF/services entry in each of the integration modules.
services/org.jboss.as.jpa.spi.PersistenceProviderAdaptor
org.jboss.as.jpa.hibernate3.HibernatePersistenceProviderAdaptor
<jboss-deployment-structure>
<deployment>
<exclusions>
<module name="org.hibernate"/>
</exclusions>
<dependencies>
<module name="org.jboss.as.jpa.hibernate3"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
Support for pluggable JPA providers
-----------------------------------
Key: AS7-566
URL: https://issues.jboss.org/browse/AS7-566
Project: Application Server 7
Issue Type: Sub-task
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.1.0.Alpha1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:31 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (AS7-566) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow edited comment on AS7-566 at 7/27/11 3:30 PM:
-----------------------------------------------------------
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).
was (Author: smarlow):
Will need a jboss-deployment-structure.xml rather than MANIFEST.MF entries. Also need
one more change for locating PersistenceProviderAdaptor implementations (the integration
classes). Will need a META-INF/services entry in each of the integration modules.
jboss-as-jpa-hibernate3.jar/META-INF/services/org.jboss.as.jpa.spi.PersistenceProviderAdaptor
will contain:
{quote}
org.jboss.as.jpa.hibernate3.HibernatePersistenceProviderAdaptor
{quote}
jboss-deployment-structure.xml will contain:
{code}
<jboss-deployment-structure>
<deployment>
<exclusions>
<module name="org.hibernate"/>
</exclusions>
<dependencies>
<module name="org.jboss.as.jpa.hibernate3"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
{code}
Support for pluggable JPA providers
-----------------------------------
Key: AS7-566
URL: https://issues.jboss.org/browse/AS7-566
Project: Application Server 7
Issue Type: Sub-task
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.1.0.Alpha1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:35 p.m.
New subject: [JBoss JIRA] Commented: (AS7-566) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on AS7-566:
----------------------------------
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.
Support for pluggable JPA providers
-----------------------------------
Key: AS7-566
URL: https://issues.jboss.org/browse/AS7-566
Project: Application Server 7
Issue Type: Sub-task
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.1.0.Alpha1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 a.m.
New subject: [JBoss JIRA] Resolved: (AS7-566) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow resolved AS7-566.
------------------------------
Resolution: Done
Support for pluggable JPA providers
-----------------------------------
Key: AS7-566
URL: https://issues.jboss.org/browse/AS7-566
Project: Application Server 7
Issue Type: Sub-task
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.1.0.Alpha1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 a.m.
New subject: [JBoss JIRA] Commented: (AS7-566) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on AS7-566:
----------------------------------
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"/>
Support for pluggable JPA providers
-----------------------------------
Key: AS7-566
URL: https://issues.jboss.org/browse/AS7-566
Project: Application Server 7
Issue Type: Sub-task
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.1.0.Alpha1
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:39 a.m.
New subject: [JBoss JIRA] Updated: (AS7-566) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow updated AS7-566:
-----------------------------
Fix Version/s: 7.0.1.Final
(was: 7.1.0.Alpha1)
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)?
was:
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.
We could have an optional property "org.jboss.jpa.provider.versionSpecifier"
that matches a specific version of the provider.
Is this the best way to allow different versions of persistence provider?
3. How could we best dynamically build a ModuleDependency on a persistence provider jar
that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
Support for pluggable JPA providers
-----------------------------------
Key: AS7-566
URL: https://issues.jboss.org/browse/AS7-566
Project: Application Server 7
Issue Type: Sub-task
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.0.1.Final
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)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:41 a.m.
New subject: [JBoss JIRA] Closed: (AS7-566) Support for pluggable JPA providers
[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow closed AS7-566.
----------------------------
Support for pluggable JPA providers
-----------------------------------
Key: AS7-566
URL: https://issues.jboss.org/browse/AS7-566
Project: Application Server 7
Issue Type: Sub-task
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.0.1.Final
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)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4914
days inactive
5048
days old
16 comments
2 participants
participants (2)
-
David Lloyd (JIRA) -
Scott Marlow (JIRA)