[JBoss JIRA] (AS7-3423) Handle deployments with a persistence provider and javax.persistence classes
3:34 p.m.
Scott Marlow created AS7-3423:
---------------------------------
Summary: Handle deployments with a persistence provider and javax.persistence
classes
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
If an application deployment contains its own copy of a persistence provider and its own
of the javax.persistence classes, deploy it as an application managed JPA application (no
container managed JPA support feature are expected to be used).
1. initialize the application copy of the javax.persistence.Persistence class by setting
an application deployment level PersistenceProviderResolver (via
javax.persistence.spi.PersistenceProviderResolverHolder.PersistenceProviderResolver())
that would know about the persistence provider that is bundled.
2. don't inject the javax.persistence module into the deployment.
3. add a unit test that bundles a persistence provider, javax.persistence classes and
uses javax.persistence.Persistence.createEntityManagerFactory(String
persistenceUnitName).
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:59 p.m.
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-3423:
------------------------------
Fix Version/s: 7.1.1.Final
(was: 7.2.0.Alpha1)
Forum Reference: https://community.jboss.org/thread/195077
Handle deployments with a persistence provider and javax.persistence
classes
----------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.1.Final
If an application deployment contains its own copy of a persistence provider and its own
of the javax.persistence classes, deploy it as an application managed JPA application (no
container managed JPA support feature are expected to be used).
1. initialize the application copy of the javax.persistence.Persistence class by setting
an application deployment level PersistenceProviderResolver (via
javax.persistence.spi.PersistenceProviderResolverHolder.PersistenceProviderResolver())
that would know about the persistence provider that is bundled.
2. don't inject the javax.persistence module into the deployment.
3. add a unit test that bundles a persistence provider, javax.persistence classes and
uses javax.persistence.Persistence.createEntityManagerFactory(String
persistenceUnitName).
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:16 p.m.
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-3423:
-----------------------------------
Working on an alternative implementation that avoids having javax.persistence classes in
the deployment (since they conflict with the global javax.persistence classes that can
also be added to the deployment).
Handle deployments with a persistence provider and javax.persistence
classes
----------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.1.Final
If an application deployment contains its own copy of a persistence provider and its own
of the javax.persistence classes, deploy it as an application managed JPA application (no
container managed JPA support feature are expected to be used).
1. initialize the application copy of the javax.persistence.Persistence class by setting
an application deployment level PersistenceProviderResolver (via
javax.persistence.spi.PersistenceProviderResolverHolder.PersistenceProviderResolver())
that would know about the persistence provider that is bundled.
2. don't inject the javax.persistence module into the deployment.
3. add a unit test that bundles a persistence provider, javax.persistence classes and
uses javax.persistence.Persistence.createEntityManagerFactory(String
persistenceUnitName).
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:41 p.m.
New subject: [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-3423:
------------------------------
Summary: persistence providers deployed with applications should be available
via javax.persistence.Persistence api (was: Handle deployments with a persistence
provider and javax.persistence classes)
Forum Reference: https://community.jboss.org/thread/195077 (was:
https://community.jboss.org/thread/195077)
persistence providers deployed with applications should be available
via javax.persistence.Persistence api
----------------------------------------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.1.Final
If an application deployment contains its own copy of a persistence provider and its own
of the javax.persistence classes, deploy it as an application managed JPA application (no
container managed JPA support feature are expected to be used).
1. initialize the application copy of the javax.persistence.Persistence class by setting
an application deployment level PersistenceProviderResolver (via
javax.persistence.spi.PersistenceProviderResolverHolder.PersistenceProviderResolver())
that would know about the persistence provider that is bundled.
2. don't inject the javax.persistence module into the deployment.
3. add a unit test that bundles a persistence provider, javax.persistence classes and
uses javax.persistence.Persistence.createEntityManagerFactory(String
persistenceUnitName).
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:07 p.m.
New subject: [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-3423:
-----------------------------------
https://github.com/scottmarlow/jboss-as/tree/AS7-3423_deploymentWithJavaX... is
work in progress (seems to be working but needs some cleanup)
persistence providers deployed with applications should be available
via javax.persistence.Persistence api
----------------------------------------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.1.Final
If an application deployment contains its own copy of a persistence provider and its own
of the javax.persistence classes, deploy it as an application managed JPA application (no
container managed JPA support feature are expected to be used).
1. initialize the application copy of the javax.persistence.Persistence class by setting
an application deployment level PersistenceProviderResolver (via
javax.persistence.spi.PersistenceProviderResolverHolder.PersistenceProviderResolver())
that would know about the persistence provider that is bundled.
2. don't inject the javax.persistence module into the deployment.
3. add a unit test that bundles a persistence provider, javax.persistence classes and
uses javax.persistence.Persistence.createEntityManagerFactory(String
persistenceUnitName).
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:17 p.m.
New subject: [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-3423:
-----------------------------------
Switched to branch
https://github.com/scottmarlow/jboss-as/tree/AS7-3423_deploymentWithJavaX...
where I'm doing final testing/cleanup.
persistence providers deployed with applications should be available
via javax.persistence.Persistence api
----------------------------------------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.1.Final
If an application deployment contains its own copy of a persistence provider and its own
of the javax.persistence classes, deploy it as an application managed JPA application (no
container managed JPA support feature are expected to be used).
1. initialize the application copy of the javax.persistence.Persistence class by setting
an application deployment level PersistenceProviderResolver (via
javax.persistence.spi.PersistenceProviderResolverHolder.PersistenceProviderResolver())
that would know about the persistence provider that is bundled.
2. don't inject the javax.persistence module into the deployment.
3. add a unit test that bundles a persistence provider, javax.persistence classes and
uses javax.persistence.Persistence.createEntityManagerFactory(String
persistenceUnitName).
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:39 p.m.
New subject: [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-3423:
------------------------------
Description:
If an application deployment contains its own copy of a persistence provider, make it
possible for the application to access the persistence provider via the
javax.persistence.Persistence.
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
was:
If an application deployment contains its own copy of a persistence provider and its own
of the javax.persistence classes, deploy it as an application managed JPA application (no
container managed JPA support feature are expected to be used).
1. initialize the application copy of the javax.persistence.Persistence class by setting
an application deployment level PersistenceProviderResolver (via
javax.persistence.spi.PersistenceProviderResolverHolder.PersistenceProviderResolver())
that would know about the persistence provider that is bundled.
2. don't inject the javax.persistence module into the deployment.
3. add a unit test that bundles a persistence provider, javax.persistence classes and
uses javax.persistence.Persistence.createEntityManagerFactory(String
persistenceUnitName).
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
Forum Reference: https://community.jboss.org/thread/195077 (was:
https://community.jboss.org/thread/195077)
persistence providers deployed with applications should be available
via javax.persistence.Persistence api
----------------------------------------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.1.Final
If an application deployment contains its own copy of a persistence provider, make it
possible for the application to access the persistence provider via the
javax.persistence.Persistence.
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:36 a.m.
New subject: [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Bernard Labno commented on AS7-3423:
------------------------------------
Scott I've tested branch AS7-3423_deploymentWithJavaXPersistence_4 but it didn't
solve the problem to the end.
I'm running seam2 on as7 with hibernate3 bundled with app. If I add ehcache as
second-level cache i get this exception:
Caused by: net.sf.ehcache.CacheException: Another unnamed CacheManager already exists in
the same VM. Please provide unique names for each CacheManager in the config or do one of
following:1. Use one of the CacheManager.create() static factory methods to reuse same
CacheManager with same name or create one if necessary2. Shutdown the earlier cacheManager
before creating new one with same name.The source of the existing CacheManager is:
DefaultConfigurationSource [ ehcache.xml or ehcache-failsafe.xml ]
at
net.sf.ehcache.CacheManager.assertNoCacheManagerExistsWithSameName(CacheManager.java:457)
[ehcache-core-2.5.1.jar:]
at net.sf.ehcache.CacheManager.init(CacheManager.java:354) [ehcache-core-2.5.1.jar:]
at net.sf.ehcache.CacheManager.<init>(CacheManager.java:242)
[ehcache-core-2.5.1.jar:]
at net.sf.ehcache.hibernate.EhCacheRegionFactory.start(EhCacheRegionFactory.java:70)
[ehcache-core-2.5.1.jar:]
It looks like the persistence unit is being initialized twice. I'm attaching both my
server.log and sample project sources.
persistence providers deployed with applications should be available
via javax.persistence.Persistence api
----------------------------------------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Labels: eap6
Fix For: 7.1.1.Final
Attachments: sample.tar.bz2, server.log
If an application deployment contains its own copy of a persistence provider, make it
possible for the application to access the persistence provider via the
javax.persistence.Persistence.
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:36 a.m.
New subject: [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Bernard Labno updated AS7-3423:
-------------------------------
Attachment: server.log
persistence providers deployed with applications should be available
via javax.persistence.Persistence api
----------------------------------------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Labels: eap6
Fix For: 7.1.1.Final
Attachments: sample.tar.bz2, server.log
If an application deployment contains its own copy of a persistence provider, make it
possible for the application to access the persistence provider via the
javax.persistence.Persistence.
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:36 a.m.
New subject: [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Bernard Labno updated AS7-3423:
-------------------------------
Attachment: sample.tar.bz2
persistence providers deployed with applications should be available
via javax.persistence.Persistence api
----------------------------------------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Labels: eap6
Fix For: 7.1.1.Final
Attachments: sample.tar.bz2, server.log
If an application deployment contains its own copy of a persistence provider, make it
possible for the application to access the persistence provider via the
javax.persistence.Persistence.
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:04 p.m.
New subject: [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-3423:
-----------------------------------
Thanks for testing, I responded in the forum
[post|https://community.jboss.org/message/717678#717678].
Lets continue our discussion there instead of continuing here.
persistence providers deployed with applications should be available
via javax.persistence.Persistence api
----------------------------------------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Labels: eap6
Fix For: 7.1.1.Final
Attachments: sample.tar.bz2, server.log
If an application deployment contains its own copy of a persistence provider, make it
possible for the application to access the persistence provider via the
javax.persistence.Persistence.
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 p.m.
New subject: [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-3423:
-----------------------------------
I verified that adding the "<property name="jboss.as.jpa.managed"
value="false"/>", works around the issue (with the latest [source
changes|https://github.com/scottmarlow/jboss-as/tree/AS7-3423_deploymentW...]
(Bernard's test case deploys).
persistence providers deployed with applications should be available
via javax.persistence.Persistence api
----------------------------------------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Labels: eap6
Fix For: 7.1.1.Final
Attachments: sample.tar.bz2, server.log
If an application deployment contains its own copy of a persistence provider, make it
possible for the application to access the persistence provider via the
javax.persistence.Persistence.
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 a.m.
New subject: [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api
[
https://issues.jboss.org/browse/AS7-3423?page=com.atlassian.jira.plugin.s...
]
Scott Marlow closed AS7-3423.
-----------------------------
persistence providers deployed with applications should be available
via javax.persistence.Persistence api
----------------------------------------------------------------------------------------------------------
Key: AS7-3423
URL: https://issues.jboss.org/browse/AS7-3423
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Labels: eap6
Fix For: 7.1.1.Final
Attachments: sample.tar.bz2, server.log
If an application deployment contains its own copy of a persistence provider, make it
possible for the application to access the persistence provider via the
javax.persistence.Persistence.
https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might
be worth looking at when this jira is worked around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4698
days inactive
4736
days old
12 comments
2 participants
participants (2)
-
Bernard Labno (JIRA) -
Scott Marlow (JIRA)