November 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2201) session.iterate() does not exist

by Andres Gonzalez (JIRA)

session.iterate() does not exist -------------------------------- Key: HHH-2201 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2201 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.0.ga Reporter: Andres Gonzalez Priority: Minor In Section "14.15. Tips & Tricks": You can count the number of query results without actually returning them: ( (Integer) session.iterate("select count(*) from ....").next() ).intValue() I don't find any session.iterate() method... Maybe it should read: ( (Integer) session.createQuery("select count(*) from ....").iterate().next() ).intValue() -- 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, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2267) A copy/paste mistake in the documentation for <schemavalidator> ant task

by Finn Bock (JIRA)

A copy/paste mistake in the documentation for <schemavalidator> ant task ------------------------------------------------------------------------ Key: HHH-2267 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2267 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.0.ga Reporter: Finn Bock Priority: Trivial A copy/paste mistake in the documentation for <schemavalidator> start ant tag has a </schemaupdate> as the end tag. http://www.hibernate.org/hib_docs/v3/reference/en/html/toolsetguide.html#... -- 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, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2180) minordocumentation error in hbm xml

by Craig Baker (JIRA)

minordocumentation error in hbm xml ----------------------------------- Key: HHH-2180 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2180 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.0.ga Reporter: Craig Baker Priority: Trivial search for <one-to-one name"employee" class="Employee" property-ref="person"/> missing "=" after name -- 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, 3 months

3
4
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, 3 months

2
1
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, 3 months

2
1
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, 3 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, 3 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-1995) NPE on evict after update

by Nelis Bijl (JIRA)

NPE on evict after update ------------------------- Key: HHH-1995 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1995 Project: Hibernate3 Type: Bug Versions: 3.1.3 Environment: Hibernate 3.1, SQL Server 9.0.1399 Reporter: Nelis Bijl Attachments: A.hbm.xml I am a newby and investigating the dom4j feature (XML <-> DB). When I try to evict after an update I get a NullPointerException at org.hibernate.event.def.EvictVisitor.evictCollection(EvictVisitor.java:50) This is caused by the fact that the update did not call addCollectionHolder whereas the error location tries to use the result of removeCollectionHolder. Attached you will find the used hbm.xml. The collectionholder is root node A. -- 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, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2235) Support for null map-keys in <map> mappings

by Igor Lobanov (JIRA)

Support for null map-keys in <map> mappings ------------------------------------------- Key: HHH-2235 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2235 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Reporter: Igor Lobanov Priority: Minor I'm not sure if I should file it as a bug. Hibernate requires index column for <map> mappings to be not null. This is required by the code in AbstractCollectionPersister#readIndex(...), which raises exception if index column is null. However, when I override collection persister and force readIndex method to return null, everything seems to work fine. Hibernate allows me to work with maps using null value as a key. Though I havn't tested it extensivly yet. What is the reason for disallowing null values as a keys? If there are possible complicated error conditions, then this issue is a feature request for null-values support for <map> mappings. If there are no errors possible, then constraining such behavior is probably wrong. -- 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, 4 months

4
21
0 / 0

[Hibernate-JIRA] Created: (HHH-2019) Provide a way to unset properties, and/or provide a 'none' option for hbm2ddl.auto

by Dave E Martin (JIRA)

Provide a way to unset properties, and/or provide a 'none' option for hbm2ddl.auto ---------------------------------------------------------------------------------- Key: HHH-2019 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2019 Project: Hibernate3 Type: Improvement Environment: hibernate / annotations / hibernate.properties Reporter: Dave E Martin Priority: Minor It may occasionally be desirable to programmatically get rid of or override a property value, this is generally allowed for by the .setProperty method, however: Once hbm2ddl.auto is set to something, there is no way to unset it, or set it to a value which would be equivalent to its being unset (or its undocumented). There is no remove or unset, or deleteProperty, and also setting it to null does not work. Due to issues such as HHH-2018, it may be necessary to programmatically 'get rid of' hbm2ddl.auto even if the end user (or some other mechanism) has specified a value for it in an external hibernate.properties file (or other method of setting hibernate properties). -- 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, 4 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2006