April 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2418) Refer HSQL DB website in chapter 1.2.3

by Diego Pires Plentz (JIRA)

Refer HSQL DB website in chapter 1.2.3 -------------------------------------- Key: HHH-2418 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2418 Project: Hibernate3 Type: Improvement Components: documentation Versions: 3.2.2 Reporter: Diego Pires Plentz "1.2.3. Hibernate configuration We now have a persistent class and its mapping file in place. It is time to configure Hibernate. Before we do this, we will need a database. HSQL DB, a java-based SQL DBMS, can be downloaded from the HSQL DB website. Actually, you only need the hsqldb.jar from this download. Place this file in the lib/ directory of the development folder. " to "1.2.3. Hibernate configuration We now have a persistent class and its mapping file in place. It is time to configure Hibernate. Before we do this, we will need a database. HSQL DB, a java-based SQL DBMS, can be downloaded from the HSQL DB website(http://hsqldb.org/). Actually, you only need the hsqldb.jar from this download. Place this file in the lib/ directory of the development folder. " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2420) Error in 2.5. Contextual Sessions

by Diego Pires Plentz (JIRA)

Error in 2.5. Contextual Sessions --------------------------------- Key: HHH-2420 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2420 Project: Hibernate3 Type: Improvement Components: documentation Reporter: Diego Pires Plentz "Typically, the value of this parameter would just name the implementation class to use; for the three out-of-the-box implementations, however, there are **two** corresponding short names, "jta", "thread", and "managed"." should be "Typically, the value of this parameter would just name the implementation class to use; for the three out-of-the-box implementations, however, there are three corresponding short names, "jta", "thread", and "managed"." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2567) Update reference to use FlushMode.MANUAL

by Diego Pires Plentz (JIRA)

Update reference to use FlushMode.MANUAL ---------------------------------------- Key: HHH-2567 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2567 Project: Hibernate3 Issue Type: Task Components: documentation Reporter: Diego Pires Plentz Attachments: transactions.xml.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2409) Oracle incorrect SQL causes ORA-00907: missing right parenthesis

by Greg Till (JIRA)

Oracle incorrect SQL causes ORA-00907: missing right parenthesis ---------------------------------------------------------------- Key: HHH-2409 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2409 Project: Hibernate3 Type: Bug Versions: 3.2.2 Environment: Hibernate version 3.2.2ga (also reproduced in 3.2.1ga and 3.2.0ga) Database: Oracle Database 10.2 XE Reporter: Greg Till Priority: Critical Hibernate incorrectly inserts the "AS" keyword when aliasing a table name on Oracle. Oracle reports this as a missing parenthesis error. See forum post http://forum.hibernate.org/viewtopic.php?p=2340268#2340268 for more details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2160) JTATransactionFactory.isTransactionInProgress fails with WebSphereExtendedJTATransactionLookup

by Timothy Folks (JIRA)

JTATransactionFactory.isTransactionInProgress fails with WebSphereExtendedJTATransactionLookup ---------------------------------------------------------------------------------------------- Key: HHH-2160 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2160 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: Hibernate 3.2.0 ga WebSphere Application Server 6.0.2.15 DB2 9.1 Reporter: Timothy Folks Configurating Hibernate with the following settings: hibernate.transaction.factory_class=org.hibernate.transaction.JTATransactionFactory hibernate.transaction.manager_lookup_class=org.hibernate.transaction.WebSphereExtendedJTATransactionLookup jta.UserTransaction=java:comp/UserTransaction hibernate.current_session_context_class=jta results in the following stack trace (irrelevant lines snipped) <snipped> Caused by: org.hibernate.TransactionException: could not register synchronization with JTA TransactionManager at org.hibernate.jdbc.JDBCContext.registerSynchronizationIfPossible(JDBCContext.java:181) at org.hibernate.jdbc.JDBCContext.<init>(JDBCContext.java:76) at org.hibernate.impl.SessionImpl.<init>(SessionImpl.java:213) at org.hibernate.impl.SessionFactoryImpl.openSession(SessionFactoryImpl.java:525) at org.hibernate.context.JTASessionContext.buildOrObtainSession(JTASessionContext.java:114) at org.hibernate.context.JTASessionContext.currentSession(JTASessionContext.java:80) at org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:542) <snipped> Caused by: java.lang.UnsupportedOperationException at org.hibernate.transaction.WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter.getStatus(WebSphereExtendedJTATransactionLookup.java:78) at org.hibernate.transaction.JTATransactionFactory.isTransactionInProgress(JTATransactionFactory.java:94) at org.hibernate.jdbc.JDBCContext.isTransactionInProgress(JDBCContext.java:187) at org.hibernate.jdbc.JDBCContext.registerSynchronizationIfPossible(JDBCContext.java:159) The workaround I've implemented is to change the following line in JTATransactionFactory.isTransactionInProgress: if ( jdbcContext.getFactory().getTransactionManager() != null ) { to: if ( jdbcContext.getFactory().getTransactionManager() != null && jdbcContext.getFactory().getTransactionManager() instanceof WebSphereExtendedJTATransactionLookup.TransactionManagerAdapter == false) { This results in the method falling back to looking up the UserTransaction in JNDI and calling getStatus on that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-601) OneToOne fails to update JoinTables

by nhhockeyplayer (JIRA)

OneToOne fails to update JoinTables ----------------------------------- Key: ANN-601 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-601 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.2.1 Environment: XP Pro Reporter: nhhockeyplayer Attachments: Ownee.java, Owner.java OneToOne fails to update JoinTables -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-1999) DirtyCollectionSearchVisitor.processCollection fails on dom4j collection

by Nelis Bijl (JIRA)

DirtyCollectionSearchVisitor.processCollection fails on dom4j collection ------------------------------------------------------------------------ Key: HHH-1999 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1999 Project: Hibernate3 Type: Bug Versions: 3.1.3 Environment: SQL server 9.0.1399 Reporter: Nelis Bijl The test in above mentioned function: if ( type.isArrayType()) { is not correct in case of a document element being used as collection holder. I could temporary fix things by using 'type.isCollectionType()' but I am not sure whether that is appropriate. Perhaps '!(type instanceof PersistenCollection)' could be an option. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-284) Scanning for META-INF/orm.xml does not work in Windows environment due to different in path-separator

by Gary Ip (JIRA)

Scanning for META-INF/orm.xml does not work in Windows environment due to different in path-separator ----------------------------------------------------------------------------------------------------- Key: EJB-284 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-284 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA Environment: Windows XP SP2 Tomcat 5.2.23 Spring 2.0.3 Hibernate Core 3.2.2.GA Hibernate Annotations 3.3.0.GA Hibernate EntityManager 3.3.1.GA Reporter: Gary Ip In org.hibernate.ejb.Ejb3Configuration: line: 606, method scanForXmlFiles(...), Iterator it = ArchiveBrowser.getBrowser( jar, new ArchiveBrowser.Filter() { public boolean accept(String filename) { return (searchforHBMFiles && filename.endsWith( ".hbm.xml" ) ) || (searchforORMFiles && filename.endsWith( META_INF_ORM_XML ) ) ; } } filename passed in use "/" in *NIX environment, while "\" is used in Win32 environment. So orm.xml will be ignored in Win32 environment, as it will end with META-INF\orm.xml and won't be matched. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

3
13
0 / 0

[Hibernate-JIRA] Created: (EJB-233) Move from JBoss Archive browser to VFS

by Emmanuel Bernard (JIRA)

Move from JBoss Archive browser to VFS -------------------------------------- Key: EJB-233 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-233 Project: Hibernate Entity Manager Type: Task Components: EntityManager Reporter: Emmanuel Bernard HEM uses the JBoss ArchiveBrowser to scan a particular jar. This needs to be switched to the org.jboss.virtual.* set of interfaces as it is duplicating functionality. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-430) @ManyToOne results in default outer join eager fetch, should be lazy

by Christian Bauer (JIRA)

@ManyToOne results in default outer join eager fetch, should be lazy -------------------------------------------------------------------- Key: ANN-430 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-430 Project: Hibernate Annotations Type: Bug Components: documentation, binder Reporter: Christian Bauer Documentation says: <sect3> <title>Association fetching</title> <para>You have the ability to either eagerly or lazily fetch associated entities. The <literal>fetch</literal> parameter can be set to <literal>FetchType.LAZY</literal> or <literal>FetchType.EAGER</literal>. <literal>EAGER</literal> will try to use an outer join select to retrieve the associated object, while <literal>LAZY</literal> is the default and will only trigger a select when the associated object is accessed for the first time. EJBQL also has a <literal>fetch</literal> keyword that allows you to override laziness when doing a particular query. This is very useful to improve performance and is decided on a use case to use case basis.</para> </sect3> However, a simple @ManyToOne without any other attributes results in an eager join outer fetch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

3
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2007