October 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-381) Provide a fail fast switch to stop processing constraints on first failure

by Emmanuel Bernard (JIRA)

Provide a fail fast switch to stop processing constraints on first failure -------------------------------------------------------------------------- Key: HV-381 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-381 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.1.0.Final Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard On first failure, HS should stop processing constraint failures and return straight. this should be both a ValidatorFactory setting and a Validator setting -- 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

13 years, 7 months

4
18
0 / 0

[Hibernate-JIRA] Created: (HHH-3123) NullPointerException on invalid HQL query with an extra brace

by Geoffrey De Smet (JIRA)

NullPointerException on invalid HQL query with an extra brace ------------------------------------------------------------- Key: HHH-3123 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3123 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Reporter: Geoffrey De Smet Priority: Trivial This query: "select p from IndividueleRekeningKasPO p left join fetch p.irTotalen inner join fetch p.toegangIndividueleRekeningKas tirkas where tirkas.authorityRef in (:authorityref)) and p.soort = :soort and p.id > 0" gives a NPE. The strange thing is that this query executes: "select p from IndividueleRekeningKasPO p left join fetch p.irTotalen inner join fetch p.toegangIndividueleRekeningKas tirkas where tirkas.authorityRef in (:authorityref)) and p.id > 0" both are invalid, because there is a closing brace to much in "(:authorityref))". -- 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

13 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5019) @TableGenerator throws Unsupported exception - error performing isolated work

by Rohini (JIRA)

@TableGenerator throws Unsupported exception - error performing isolated work ----------------------------------------------------------------------------- Key: HHH-5019 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5019 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1, 3.3.0.SP1, 3.3.0.GA, 3.3.0.CR2, 3.3.0.CR1, 3.2.7, 3.2.6, 3.2.5, 3.2.4.sp1, 3.2.4, 3.2.3, 3.2.2, 3.2.1 Environment: Hibernate Core 3.3.1, MySQL, Websphere 6.1 with EJB3.0 Feature pack Reporter: Rohini While implementing GenerationType.TABLE strategy with Hibernate as the persistence provider, id generation throws javax.persistence.PersistenceException: org.hibernate.HibernateException: error performing isolated work [3/18/10 14:40:41:533 IST] 0000002d SystemErr R at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614) -------------------------------------------------------------- 3/18/10 14:40:41:533 IST] 0000002d SystemErr R Caused by: org.hibernate.HibernateException: error performing isolated work at org.hibernate.engine.transaction.Isolater$JtaDelegate.delegateWork(Isolater.java:166) at org.hibernate.engine.transaction.Isolater.doIsolatedWork(Isolater.java:64) at org.hibernate.engine.TransactionHelper.doWorkInNewTransaction(TransactionHelper.java:74) at org.hibernate.id.MultipleHiLoPerTableGenerator.generate(MultipleHiLoPerTableGenerator.java:210) Looking at the Isolater.doIsolatedWork( work, session );, implementation try { // First we need to suspend any current JTA transaction and obtain // a JDBC connection surroundingTransaction = transactionManager.suspend(); if ( log.isDebugEnabled() ) { log.debug( "surrounding JTA transaction suspended [" + surroundingTransaction + "]" ); } This happnes only with WebsphereExtendedTransactionManagerLookup as the hibernate.transaction.manager_lookup_class. -- 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

13 years, 8 months

6
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3934) Problem with PDF doc

by Adam Warski (JIRA)

Problem with PDF doc -------------------- Key: HHH-3934 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3934 Project: Hibernate Core Issue Type: Improvement Components: envers Reporter: Adam Warski Priority: Minor there is a problem on p.8 of the PDF documentation, the table is all jumbled + overlapping itself. -- 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

13 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5566) Clob column are not getting updated, even if there is real updated in the Clob data, when we do merge operation

by Srinivasa Rao Yedluri (JIRA)

Clob column are not getting updated, even if there is real updated in the Clob data, when we do merge operation --------------------------------------------------------------------------------------------------------------- Key: HHH-5566 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5566 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: Spring2.5.6, Hibernate3.3.2, Weblogic10.3.1, Red Hat Linux, Oracle10G Reporter: Srinivasa Rao Yedluri Below is the hbm file snippet <hibernate-mapping> <class name="......OrderLineDTO" table="ORDER_LINES" dynamic-update="true"> <id name="lineId" type="long" column="LINE_ID" length="15"> <generator class="sequence"> <param name="sequence">xyz</param> </generator> </id> .................................. .................................. .................. <property name="installationDetailClob" type="clob" column="ORDER_LINE_ATTRIBUTES_MAP" not-null="false" lazy="true" /> <property name="attathmentMetadataClob" type="clob" column="ORDER_ATTACHMENT_METADATA" not-null="false" lazy="true"/>   <many-to-one name="orderHeader" class="......" fetch="select"> <column name="HEADER_ID" not-null="true" length="15" /> </many-to-one>  <set name="smartHands" inverse="true" lazy="false" cascade="all,delete-orphan"> <key> <column name="LINE_ID" /> </key> <one-to-many class="...................SmartHandDTO" /> </set> </class> </hibernate-mapping> DAO Code snippet: public void update(OrderHeaderDTO orderHeaderDTO) throws DataAccessException { getOrdersHibernateTemplate().merge(orderHeaderDTO); } 1. Create a table with clob column and have some other columns. Have one column with timestamp. 2. Insert a record in to it. 3. Now create detached object with new operator and populate all the information programatically including pk. Populate clob column and timestamp with different data than already persisted data. 3. Now do merg operation on this object, we find only timestamp column is part of update query but not clob column. Please let me know if you need any 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

13 years, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5648) Auto-increment IDs should be assigned upon commit (or hooks made available)

by Wallace Wadge (JIRA)

Auto-increment IDs should be assigned upon commit (or hooks made available) --------------------------------------------------------------------------- Key: HHH-5648 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5648 Project: Hibernate Core Issue Type: Bug Components: core Environment: v3.6, mysql Reporter: Wallace Wadge The connection pool BoneCP (http://jolbox.com) has support to automatically replay a transaction when a database/network goes down. Under hibernate, since objects get their IDs populated upon INSERTs, the following sequence of events is possible: BEGIN TRANSACTION INSERT STATEMENT (object gets the ID field populated) => network goes down, new connection is given and transaction is replayed beneath hibernate COMMIT TRANSACTION Now the database has given us a new ID but hibernate never had a chance to update the object properly. To fix: either assign the IDs upon a successful transaction commit or at least provide some kind of hooking mechanism so as to correct the problematic objects. -- 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

13 years, 8 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HV-376) validateValue() and validateProperty() are too restrictive regarding processable property names

by Gunnar Morling (JIRA)

validateValue() and validateProperty() are too restrictive regarding processable property names ----------------------------------------------------------------------------------------------- Key: HV-376 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-376 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.1.0.Final Reporter: Gunnar Morling Assignee: Hardy Ferentschik Priority: Minor The methods Validator#validateValue() and Validator#validateProperty() expect the name of a bean property, for which constraint validation should be performed. Currently not all valid Java property (field/method) identifiers are supported here, as the specified property name is processed in PathImpl with a regular expression, that matches only the word character class (A-Za-z0-9_), causing the evaluation of uncommon but yet valid property names such as the following ones to fail: * private String höchstBetrag; // German Umlaute such as "ö" are allowed in Java identifiers * private String €Amount; // some currency signs such as "€" are allowed, sigh * private String höchst\u00f6Betrag; // specifying letters such as "ö" using Unicode is allowed Trying to do so results in the following exception: {code:java} java.lang.IllegalArgumentException: Unable to parse property path ö at org.hibernate.validator.engine.PathImpl.parseProperty(PathImpl.java:216) at org.hibernate.validator.engine.PathImpl.createPathFromString(PathImpl.java:64) at org.hibernate.validator.engine.ValidatorImpl.validateValue(ValidatorImpl.java:152) {code} More information on the identifiers allowed in the Java language can be found in [JLS, chapter 3.8|http://java.sun.com/docs/books/jls/third_edition/html/lexical.html#3.8]. -- 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

13 years, 8 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5057) ScrollableResults does not fetch many-to-many collections

by Jérôme Van Der Linden (JIRA)

ScrollableResults does not fetch many-to-many collections --------------------------------------------------------- Key: HHH-5057 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5057 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Reporter: Jérôme Van Der Linden Priority: Blocker I have a many-to-many relation between two objects : {code:title=Project.java|borderStyle=solid} @Entity public class Project { private List<Viperson> managers; @ManyToMany(targetEntity = Viperson.class) @JoinTable(name = "PRJMANAGER", joinColumns = @JoinColumn(name = "PROJECTID", nullable = false), inverseJoinColumns = @JoinColumn(name = "VIPID", nullable = false)) public List<Viperson> getManagers() { return managers; } } {code} {code:title=Viperson.java|borderStyle=solid} @Entity public class Viperson { private List<Project> projects; @ManyToMany(mappedBy = "managers", targetEntity = Project.class) public List<Project> getProjects() { return projects; } } {code} And the following test (actually, it is a code from spring batch HibernateCursorItemReader I put in a testcase) : {code} @Test public void testSelectAll() { StatelessSession statelessSession = sessionFactory.openStatelessSession(); ScrollableResults cursor = statelessSession.createQuery("from Project").scroll(); Object[] data = null; if (cursor.next()) { data = cursor.get(); } } {code} data contains a {{Project}} but {{managers}} field is *null*, +even if I add eager fetching+. I have also a {{OneToMany}} in the {{Project}} class. This one is well loaded (i have a {{PersistentBag}}). Is there anything I miss ? I suspect a bug 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

13 years, 8 months

3
3
0 / 0

[Hibernate-JIRA] Created: (ANN-843) Version increment not triggered on @OneToOne property modification having inverse owner

by Guenther Demetz (JIRA)

Version increment not triggered on @OneToOne property modification having inverse owner --------------------------------------------------------------------------------------- Key: ANN-843 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-843 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate 3.3.1.GA , Microsoft SQL Server Reporter: Guenther Demetz Priority: Minor Attachments: Testcase.jar In the revised "Java Persistence with Hibernate" book by Christian Bauer and Gavin King on page 464 there's written following about versioning: "If you use Hibernate as JPA provider ... every value-typed property modification .. triggers a version increment." Now I saw that Version increment indeed is not triggered on @OneToOne properties having an inverse owner (= mappedBy setted). This allows several concurrent transactions to set the association from same object towards different targets without having a OptimistickLockException at commit. This violates the ToOne policy! (Hibernate detects the inconsistency later when loading the property from database: org.hibernate.HibernateException: More than one row with the given identifier was found) Please see attached junit-testcase for reproducing the problem. regards Guenther Demetz -- 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

13 years, 8 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4617) Using blobs with hibernate causes error

by Radosław Smogura (JIRA)

Using blobs with hibernate causes error --------------------------------------- Key: HHH-4617 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4617 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2 Environment: Hibernate 3.5-b2, Glassfish v3 promoted build 74, PostgreSQL 8.3.7 Reporter: Radosław Smogura Priority: Critical I have entity with byte[] property annotated as @Lob and lazy fetch type, when table is createad the created column is of type oid, but when the column is read in application, the Hibernate reads the OID value instead of bytes under given oid. It's behavior like to read / write bytea. If i remember well, auto-creating table with Hibernate creates oid column. The proper behavior for dealing in PostgreSQL (and this behavior is in Hibernate 3.4) is to use oids. -- 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

13 years, 8 months

4
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2010