Bug 845410 - Bug in Administration and Configuration Guide
Summary: Bug in Administration and Configuration Guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 5
Classification: JBoss
Component: doc-Admin_and_Config_Guide
Version: 5.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Scott Mumford
QA Contact: Rajesh Rajasekaran
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-03 02:04 UTC by Joshua Wilson
Modified: 2014-05-15 04:41 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-15 04:41:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joshua Wilson 2012-08-03 02:04:05 UTC
Description of problem: Reference to OLD Hibernate Defaults.


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


How reproducible: Go to 4.2.3. Default Hibernate options: 

http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/Administration_And_Configuration_Guide/ch04s02s03.html

At first I thought that the reference to JBoss AS 4.2 was a typo but now I think the whole section is old.  "JBOSS_DIST/server/default/deploy/ejb3.deployer/MEAT-INF/persistence.properties" does not exist in the installation of EAP 5.1.2.  If I search for "persistence.properties" I can only find it in "/usr/share/jboss-seam2/bootstrap/META-INF/persistence.properties".  

I think you may be looking for: "/var/lib/jbossas/server/default/deployers/ejb3.deployer/META-INF/jpa-deployers-jboss-beans.xml".  The format is different as it is xml instead of a properties file.  Please note that it is in the "deployers" directory instead of the "deploy" directory.

Also there is an example of all possible Hibernate settings at: "/usr/share/hibernate3-3.3.2/etc/hibernate.properties"


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


Expected results:


Additional info:

Comment 2 Jan Martiska 2014-04-15 09:25:43 UTC
Looks good.


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