Bug 812002 - Document usage of jboss.as.jpa.managed property for Spring users
Document usage of jboss.as.jpa.managed property for Spring users
Status: CLOSED INSUFFICIENT_DATA
Product: JBoss Enterprise WFK Platform 2
Classification: JBoss
Component: doc-Spring-Developer-Guide (Show other bugs)
2.0.0.ER3
Unspecified Unspecified
high Severity high
: GA
: 2.3.0
Assigned To: Tejas Mehta
Tomas Repel
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-12 09:56 EDT by Karel Piwko
Modified: 2013-08-11 21:31 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-22 23:42:51 EDT
Type: Task
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker WFK2-81 Minor Closed Document usage of jboss.as.jpa.managed property for Spring users 2017-06-27 06:00 EDT

  None (edit)
Description Karel Piwko 2012-04-12 09:56:00 EDT
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Karel Piwko 2012-04-12 09:59:02 EDT
Document a new AS7 feature [1] which allows you to use JPA managed by Spring without moving default persistence.xml file.


https://docs.jboss.org/author/display/AS71/JPA+Reference+Guide

jboss.as.jpa.managed description:

can be set to false to disable container managed JPA access to the persistence unit.  The default is true, which enables container managed JPA access to the persistence unit.  This is typically set to false for Seam 2.x + Spring applications.
Comment 2 Marius Bogoevici 2012-04-12 16:25:52 EDT
Will wait for clarifications on this functionality, as the behaviour WRT this flag does not seem to be final. In the current state, it only solves part of the problem (duplicate deployment), however, the JPA/Hibernate libraries are still included.
Comment 4 Marius Bogoevici 2012-07-10 19:27:12 EDT
I suggest we move this to WFK 2.1 when the functionality will be hopefully 
clarified in EAP6.
Comment 8 Marek Novotny 2013-01-17 09:27:49 EST
Marius, could you update what we can do with this issue?
Comment 10 Joshua Wilson 2013-07-22 23:42:51 EDT
Migrated to JIRA. https://issues.jboss.org/browse/WFK2-81

Note You need to log in before you can comment on or make changes to this bug.