January 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-405) Be able to set Similarity per index in configuration properties

by Sanne Grinovero (JIRA)

Be able to set Similarity per index in configuration properties --------------------------------------------------------------- Key: HSEARCH-405 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-405 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Fix For: 3.3.0 -- 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

15 years, 5 months

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-668) Method in entity with return type of ArrayList<Object[]> causes failure to build session factory

by Clint Popetz (JIRA)

Method in entity with return type of ArrayList<Object[]> causes failure to build session factory ------------------------------------------------------------------------------------------------ Key: ANN-668 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-668 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate 3.2.X, no database needed (happens during factory build before connecting to db) Reporter: Clint Popetz Attachments: propertyTypeExtractorBug.tar.gz The following source: @javax.persistence.Entity public class TestEntity { @javax.persistence.Id public int Id; public java.util.ArrayList<Object[]> badMethod() { return null; } public static void main(String args[]) { new org.hibernate.cfg.AnnotationConfiguration().addAnnotatedClass(TestEntity .class).configure().buildSessionFactory(); } } will cause: java.lang.IllegalArgumentException: No PropertyTypeExtractor available for type void at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.toXType(JavaReflectionManager.java:164)^M at org.hibernate.annotations.common.reflection.java.JavaXMethod.create(JavaXMethod.java:18) at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.getXMethod(JavaReflectionManager.java:128) at org.hibernate.annotations.common.reflection.java.JavaXClass.getDeclaredMethods(JavaXClass.java:114) at org.hibernate.validator.ClassValidator.initValidator(ClassValidator.java:214) at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:133) at org.hibernate.validator.event.ValidateEventListener.initialize(ValidateEventListener.java:91) at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:356) at org.hibernate.cfg.Configuration.getInitializedEventListeners(Configuration.java:1304) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) Changing the return type to List<Object[]> avoids the bug. Attached is a tgz of an ant-buildable project; typing "ant run" will illustrate the bug. -- 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

15 years, 5 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3873) DB2Dialect.getLimitString raise DB2 error message when called with limit=0

by Julien Kronegg (JIRA)

DB2Dialect.getLimitString raise DB2 error message when called with limit=0 -------------------------------------------------------------------------- Key: HHH-3873 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3873 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: DB2, http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/core/branches/Branch... http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/core/branches/Branch... Reporter: Julien Kronegg Priority: Minor Executing a query called with setMaxResults(n) makes the underlying Hibernate code to call DB2Dialect.getLimitString. While this is working fine in general case, the following database error is raised when setting the maximum number of results to zero: SqlException: NUMBER 0 DIRECTLY SPECIFIED IN AN SQL STATEMENT IS OUTSIDE THE RANGE OF ALLOWABLE VALUES IN THIS CONTEXT (1, 2147483647) This is due to the getLimitString method in classes DB2400Dialect and DB2390Dialect : public String getLimitString(String sql, int offset, int limit) { return new StringBuffer(sql.length() + 40) .append(sql) .append(" fetch first ") .append(limit) .append(" rows only ") .toString(); } When the limit parameter is set to zero, the fetch limit is appended, which explains why the error message occur. Solution: ------------ When the limit is 0, there should be no "fetch first" instruction appended (as 0 is the general convention for "no limit"). The code would be: public String getLimitString(String sql, int offset, int limit) { + if (limit==0) return sql; return new StringBuffer(sql.length() + 40) .append(sql) .append(" fetch first ") .append(limit) .append(" rows only ") .toString(); } Workaround: ------------------ In order to avoid the error message, getLimitString(n) or setMaxResults(n) should be called with the 'newN' argument: int newN = (n==0?Integer.MAX_VALUE:n); Note: since the workaround is quite easy, I set the priority to "Minor" -- 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

15 years, 5 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3144) Final methods preclude some useful Hibernate extensions

by Ali Ibrahim (JIRA)

Final methods preclude some useful Hibernate extensions ------------------------------------------------------- Key: HHH-3144 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3144 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Ali Ibrahim Priority: Minor The following methods are final: AbstractPersistentCollection#read, AbstractPersistentCollection#write, AbstractLazyInitializer#initialize. It can be useful to override these methods. Fix is to make them protected. -- 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

15 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4074) Polymorphic queries avoid with polymorphism="explicit" in hbm.xml file doesn't work

by Radics Laszlo (JIRA)

Polymorphic queries avoid with polymorphism="explicit" in hbm.xml file doesn't work ----------------------------------------------------------------------------------- Key: HHH-4074 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4074 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: hibernate 3.3.2 Oracle 9i Reporter: Radics Laszlo hbm.xml: <hibernate-mapping default-cascade="none"> <class name="hu.raiffeisen.aps.soa.entity.collateral.AncestorImpl" table="ANCESTOR" dynamic-insert="false" dynamic-update="false" polymorphism="explicit"> <id name="id" type="java.lang.Long" unsaved-value="null"> <column name="ID" sql-type="NUMBER(19)"/> <generator class="sequence"> <param name="sequence">ANCESTOR_SEQ</param> </generator> </id> <property name="top" type="java.lang.Long"> <column name="TOP" not-null="true" unique="false" sql-type="NUMBER(19)"/> </property> <union-subclass name="hu.raiffeisen.aps.soa.entity.collateral.DescendantImpl" table="DESCENDANT" dynamic-insert="false" dynamic-update="false" abstract="false"> <property name="bottom" type="java.lang.Long"> <column name="BOTTOM" not-null="true" unique="false" sql-type="NUMBER(19)"/> </property> </union-subclass> </class> </hibernate-mapping> hql: "from AncestorImpl" fetch both ancestor and descendant rows -- 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

15 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-470) enrich UniqueConstraint with property name

by Johnny D. (JIRA)

enrich UniqueConstraint with property name ------------------------------------------ Key: ANN-470 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-470 Project: Hibernate Annotations Type: Improvement Reporter: Johnny D. To be able in annotation to give uniqueConstraint exact database name, there is need to add field java.lang.String name(); to annotation class UniqueConstraint in similar way like in index is. -- 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

15 years, 5 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-4042) StatelessSession does not flush when using jdbc batch_size > 1

by Gael Beaudoin (JIRA)

StatelessSession does not flush when using jdbc batch_size > 1 -------------------------------------------------------------- Key: HHH-4042 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4042 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: JBoss 4.2.3, Linux, java 1.6, hibernate 3.3.1, entityManager 3.4.0, jboss seam 2.1.2, postgresql 8.3 Reporter: Gael Beaudoin I'm using a StetelessSession to insert millions of rows : it works great and without using much memory. But I've just seen that with a jdbc batch size of 50 for example (<property name="hibernate.jdbc.batch_size" value="0"/> in my persistence.xml) the last round of inserts aren't flushed to the database. For example, with 70 insert, only the first 50 are sent to the database. I've searched a lot about this issues and on this thread (https://forum.hibernate.org/viewtopic.php?f=1&t=987882&start=0), the only solution found is to set the batch_size to 1, which is really a shame. I've tried to flush the session, close the jdbc connection, etc etc ... no luck. I'd be fine with a way to set the batch_size to 1 only for this method, pro grammatically, but I've not found any way to do that. If you don't pay attention, it's a easy way to lose data. -- 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

15 years, 5 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-424) Update to Lucene 3.0

by Sanne Grinovero (JIRA)

Update to Lucene 3.0 -------------------- Key: HSEARCH-424 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-424 Project: Hibernate Search Issue Type: Improvement Components: analyzer, directory provider, documentation, engine, mapping, query Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta2 Lucene 3.0 was released, update the dependencies and fix the code to work with the new APIs, to be able to make use of new features later. -- 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

15 years, 5 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2319) StatelessInterceptor

by Max Rydahl Andersen (JIRA)

StatelessInterceptor -------------------- Key: HHH-2319 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2319 Project: Hibernate3 Type: New Feature Components: core Versions: 3.2.1 Reporter: Max Rydahl Andersen It would make sense to have an Interceptor for StatelessSession to solve the following usecases: Log/adjust SQL: onPrepareStatement Proper entityname handling: instantiate/getEntity Maybe also tx interaction: afterTransationBegin/beforeTransactionCompletion/afterTransactionCompletion Technically it could be solved by just allowing to pass in a normal interceptor to a StatelessSession and just document that the state oriented callbacks will not be called. Alternatively we can create a StatelessInterceptor that only implement the releavant methods and wrap that instance into an internal Interceptor. -- 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

15 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4563) Maven repository uses proprietary JTA as transitive dependency

by Karel Piwko (JIRA)

Maven repository uses proprietary JTA as transitive dependency -------------------------------------------------------------- Key: HHH-4563 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4563 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Reporter: Karel Piwko Transitive dependency javax.transaction:jta:jar:1.0.1B was removed from jboss reposories and it is to be replaced with jboss-transaction-api. <dependency> <groupId>org.jboss.javaee</groupId> <artifactId>jboss-transaction-api</artifactId> </dependency> Logs: Missing: ---------- 1) javax.transaction:jta:jar:1.0.1B Try downloading the file manually from: http://java.sun.com/products/jta Then, install it using the command: mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jboss.weld.integration:weld-jboss-int-jboss-ejb:jar:5.2.0-SNAPSHOT 2) org.jboss.ejb3:jboss-ejb3-endpoint-deployer:jar:0.1.3 3) org.jboss.ejb3:jboss-ejb3-core:jar:1.1.5 4) org.hibernate:hibernate:jar:3.2.6.ga 5) javax.transaction:jta:jar:1.0.1B ---------- 1 required artifact is missing. for artifact: org.jboss.weld.integration:weld-jboss-int-jboss-ejb:jar:5.2.0-SNAPSHOT from the specified remote repositories: apiviz.release (http://apiviz.googlecode.com/svn/site/repo/mvn/release), snapshots.jboss.org (http://snapshots.jboss.org/maven2), oss.sonatype.org/jboss-snapshots (http://oss.sonatype.org/content/repositories/jboss-snapshots), central (http://repo1.maven.org/maven2), repository.jboss.org (http://repository.jboss.org/maven2) This breaks a lot of builds. -- 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

15 years, 6 months

3
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 January 2010