March 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-706) Typo's in reference manuals

by Geoffrey De Smet (JIRA)

Typo's in reference manuals --------------------------- Key: ANN-706 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-706 Project: Hibernate Annotations Issue Type: Patch Components: documentation Affects Versions: 3.3.0.ga Reporter: Geoffrey De Smet Priority: Trivial Just do a quick find on these sentences, and fix them (not really a patch but fixed just as fast :) hibernate annotations ===================== For netadata complete => metadata Hibernate Annotations will integrates in two ways => integrate can be as complex as you want avec even include subselects => want, even with hibernate validator =================== @Digits => duplicated in table -- 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

17 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2617) Warning on tables with inheritance when table defaults are set in entity-mappings

by Stephen Todd (JIRA)

Warning on tables with inheritance when table defaults are set in entity-mappings --------------------------------------------------------------------------------- Key: HHH-2617 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2617 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.2 Environment: Using Annotations Reporter: Stephen Todd Priority: Trivial Attachments: inheritance-orm.xml, TestSingleTableInheritanceWarnings.java The following warning message is logged when entity-mapping defaults are set and tables with inheritance are present: Illegal use of @Table in a subclass of a SINGLE_TABLE hierarchy: class.name.Here I attached a test case that recreates the problem. Basically, the error occurs when a resource contains persistence-unit-defaults. It appears that hibernate creates an @Table attribute for every registered entity when I think it should only do it for non-single table inheritance entities. Below is an example of the orm.xml <entity-mappings> <persistence-unit-metadata> <persistence-unit-defaults> <catalog>public</catalog> </persistence-unit-defaults> </persistence-unit-metadata> <entity class="hibernatebugs.TestAnnotationWarnings$ParentEntity"> <inheritance strategy="SINGLE_TABLE"/> </entity> </entity-mappings> Test requires EasyMock and Log4J. -- 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

17 years, 10 months

2
6
0 / 0

[Hibernate-JIRA] Created: (ANN-610) Copy/paste errors in reference docs

by Christian Bauer (JIRA)

Copy/paste errors in reference docs ----------------------------------- Key: ANN-610 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-610 Project: Hibernate Annotations Issue Type: Bug Components: documentation Reporter: Christian Bauer Priority: Minor The section on bidirectional indexed collections has copy/paste errors. Also, show a List example and drop the map-key example. -- 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

17 years, 10 months

2
4
0 / 0

[Hibernate-JIRA] Created: (ANN-696) @Type with Maps from Element to Element applies to both key to value type.

by Timon Hertli (JIRA)

@Type with Maps from Element to Element applies to both key to value type. -------------------------------------------------------------------------- Key: ANN-696 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-696 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Environment: Hibernate Annotations 3.3.0.ga, HSQLDB 1.8.0.7, JUnit 4.1 Reporter: Timon Hertli Attachments: test.zip Having a Hibernate map where key and value are both Elements, the @Type annotation seems to affect both key and value type: @CollectionOfElements @org.hibernate.annotations.MapKey @Type(type = "myEnumType") private Map<MyEnumType, String> enumKey = new HashMap<MyEnumType, String>(); @Test void testEnumKey () { MyPc pc = new MyPc(); pc.getEnumKey().put(MyEnumType.TYPE1, "str"); session.saveOrUpdate(pc); session.flush(); //flush throws an exception since it tries to persist the String as "myEnumType" } I think the following should be the expected behaviour: @Type should only affect the Map value type. There should be a seperate possibility to affect the key type with an @Type annotation, as it is the case with @Column now. This issue came from a forum entry: http://forum.hibernate.org/viewtopic.php?t=983577 -- 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

17 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-709) Express @Type on a Map key

by Emmanuel Bernard (JIRA)

Express @Type on a Map key -------------------------- Key: ANN-709 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-709 Project: Hibernate Annotations Issue Type: New Feature Components: binder Reporter: Emmanuel Bernard Fix For: 3.3.1 -- 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

17 years, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-707) Erroneous SQL goes to Oracle when using operator IN with composite key

by botWi (JIRA)

Erroneous SQL goes to Oracle when using operator IN with composite key ---------------------------------------------------------------------- Key: ANN-707 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-707 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.CR1 Environment: Hibernate 3.2.6 Hibernate Annotations 3.3.1.CR1 Hibernate EntityManager 3.3.2.CR1 Oracle 10g Reporter: botWi entity Footballer has composite primary key defined via @IdClass and @Id getters (see http://www.hibernate.org/hib_docs/annotations/reference/en/html_single/#e...) entity Goal has property 'footballer' defined via @ManyToOne query select g from Goal g where g.footballer in (select f from Footballer f where f.age=22) is translated to erroneous SQL select goal0_.id as col_0_0_ from tgoal goal0_ where (goal0_.fb_firstname, goal0_.fb_lastname) in (select (footballer1_.fb_firstname, footballer1_.fb_lastname) from tfootballer footballer1_ where footballer1_.age=22) it's strange, but the slightly modified query select g from Goal g where g.footballer.id in (select f.id from Footballer f where f.age=22) is translated to valid SQL select goal0_.id as col_0_0_ from tgoal goal0_ where (goal0_.fb_firstname, goal0_.fb_lastname) in (select footballer1_.fb_firstname, footballer1_.fb_lastname from tfootballer footballer1_ where footballer1_.age=22) -- 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

17 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Commented: (HBX-464) Quick access to cfg.xml and properties from the configuration node console

by Vitali Yemialyanchyk (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-464?page=co... ] Vitali Yemialyanchyk commented on HBX-464: ------------------------------------------ I did properties editor -> please look at patch for http://jira.jboss.com/jira/browse/JBIDE-1674. > Quick access to cfg.xml and properties from the configuration node console > -------------------------------------------------------------------------- > > Key: HBX-464 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-464 > Project: Hibernate Tools > Issue Type: New Feature > Components: consoleconfiguration > Affects Versions: 3.1beta1 > Reporter: Max Rydahl Andersen > > find a way (possibly just a popup menu) to go to the cfg.xml or hibernate.properties defined for the console... > maybe a "Related Files >" menu with quick access to every cfg.xml, properties and hbm.xml (limited to a certain number) -- 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

17 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2457) UnsupportedOperationException with WebSphereExtendedJTATransactionLookup

by Erik Post (JIRA)

UnsupportedOperationException with WebSphereExtendedJTATransactionLookup ------------------------------------------------------------------------ Key: HHH-2457 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2457 Project: Hibernate3 Type: Bug Versions: 3.2.2 Reporter: Erik Post Using the WebSphereExtendedJTATransactionLookup as transaction manager lookup class results in an UnsupportedOperationException being thrown by WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter.getStatus(). This method is called by JTATransactionFactory.isTransactionInProgress(). Would a solution be to have the TransactionManagerAdapter#getStatus method delegate to the TransactionAdapter#getStatus method? Also see http://forum.hibernate.org/viewtopic.php?t=966463 -- 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

17 years, 10 months

11
13
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-167) Prefix for embedded many-to-one indexing is not applied correctly

by Christian Bauer (JIRA)

Prefix for embedded many-to-one indexing is not applied correctly ----------------------------------------------------------------- Key: HSEARCH-167 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-167 Project: Hibernate Search Issue Type: Bug Components: mapping Reporter: Christian Bauer This is with the JAR from trunk I received from Emmanuel a few weeks ago: @ManyToOne(fetch = FetchType.LAZY) @org.hibernate.search.annotations.IndexedEmbedded(prefix = "createdBy_") protected User createdBy; @ManyToOne(fetch = FetchType.LAZY) @org.hibernate.search.annotations.IndexedEmbedded(prefix = "lastModifiedBy_") protected User lastModifiedBy; And on User class (by the way, it doesn't work with @Indexed on that class, contrary to documentation): @org.hibernate.search.annotations.Indexed public class User implements Serializable { @org.hibernate.search.annotations.DocumentId(name = "userId") private Long id = null; @org.hibernate.search.annotations.Field( index = org.hibernate.search.annotations.Index.UN_TOKENIZED, store = org.hibernate.search.annotations.Store.YES ) private String username; // Unique and immutable } In the index (checked with Luke) I get: <createdBy_userId> <createdBy_username> <createdBy_usernameusername> instead of the desired <createdBy_userId> <createdBy_username> <lastModifiedBy_username> -- 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

17 years, 10 months

1
2
0 / 0

[Hibernate-JIRA] Created: (EJB-342) event listener (prepersist, preinsert) not firing

by Adam Hardy (JIRA)

event listener (prepersist, preinsert) not firing -------------------------------------------------- Key: EJB-342 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-342 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA Environment: jdk1.5.0_12, linux 2.6 Reporter: Adam Hardy I have a superclass with several properties, including 'modified', a datetime field which a prepersistlistener should update. All my entities inherit this superclass. The superclass is mapped with the appropriate prepersist listener identifying the callback method to call. <mapped-superclass class="org.permacode.atomic.domain.AtomicEntity" access="FIELD"> <pre-persist method-name="prePersistCallBack" /> <attributes> <basic name="ownerId"> <column name="OWNER_ID" /> </basic> <basic name="created"> <column name="CREATED" /> <temporal>DATE</temporal> </basic> <basic name="modified"> <column name="MODIFIED" /> <temporal>DATE</temporal> </basic> <version name="version"> <column name="VERSION" /> </version> </attributes> </mapped-superclass> The method prePersistCallBack() is on the superclass: public void prePersistCallBack() { this.modified = new Date(); logger.info("doing prePersistCallBack() - " + this + " - modified=" + this.modified); } I see no logging and I see the SQL statement contains the untouched modified value. -- 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

17 years, 10 months

2
4
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 March 2008