August 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (METAGEN-12) Investigate why it is not possible to use the Filer API to load non class resources like The API throws a FilerException with the message "Illegal name /META-INF". The call is processingEnv.getFiler().getResource((StandardLocation.CLAS /META-INF/orm.xml

by Hardy Ferentschik (JIRA)

Investigate why it is not possible to use the Filer API to load non class resources like The API throws a FilerException with the message "Illegal name /META-INF". The call is processingEnv.getFiler().getResource((StandardLocation.CLAS /META-INF/orm.xml --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: METAGEN-12 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-12 Project: Hibernate StaticMetamodel Generator Issue Type: Improvement Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik The API throws a FilerException with the message "Illegal name /META-INF". The call in question is: {code} processingEnv.getFiler().getResource((StandardLocation.CLASS_OUTPUT, "/META-INF", "orm.xml" ) {code} Currently we work around this by using {{Class.getResourceAsStream()}} -- 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

14 years, 2 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5427) derby 10.6.1.0 native sequence support broken

by Max Giesbert (JIRA)

derby 10.6.1.0 native sequence support broken --------------------------------------------- Key: HHH-5427 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5427 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2 Environment: apache derby, hibernate 3.5.x/3.6 Reporter: Max Giesbert see also: https://forum.hibernate.org/viewtopic.php?f=1&t=1005637&view=previous Derby 10.6.1 officially supports sequences. (See JIRA-Task: https://issues.apache.org/jira/browse/DERBY-712, Docs: https://issues.apache.org/jira/browse/DERBY-4568). usage (e.g. @Id @GeneratedValue(strategy=GenerationType.SEQUENCE) ) produces: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.dao.InvalidDataAccessResourceUsageException: could not get next sequence value; nested exception is org.hibernate.exception.SQLGrammarException: could not get next sequence value org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:487) org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:430) javax.servlet.http.HttpServlet.service(HttpServlet.java:617) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) fix is: org.hibernate.dialect.DerbyDialect needs to override getSequenceNextValString as follows @Override public String getSequenceNextValString(String sequenceName) { return "values next value for " + sequenceName; } -- 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

14 years, 2 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4876) Postgresql @Lob problem

by Radosław Smogura (JIRA)

Postgresql @Lob problem ----------------------- Key: HHH-4876 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4876 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-4 Environment: Reproducable on Windows and Linux with Postgresql 8.4 Reporter: Radosław Smogura The current version of Hibernate (Beta) wrongly reads PgSQL blob values (mapped from @Lob byte[]). In general Hibernate properly creates OID type columns for storing blobs, but when it read blob it reads oid value instead of LOB referenced by oid valu (so as the output i get 6 bytes length table instead of 120kb table) This works fine in previous release 3.3 / 3.2. This was I saw is: previous version uses getBlob(), but 3.5 version uses getBytes() of resultset 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

14 years, 2 months

4
15
0 / 0

[Hibernate-JIRA] Created: (HHH-4992) Version is incremented when an inverse one-to-many collection is dirtied by adding or removing read-only entities

by Gail Badner (JIRA)

Version is incremented when an inverse one-to-many collection is dirtied by adding or removing read-only entities ----------------------------------------------------------------------------------------------------------------- Key: HHH-4992 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4992 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner If a persistent, read-only entity is added to an inverse one-to-many association, and the owning entity is versioned, then, when flushed, the collection is found to be dirty, the owning entity's version is incremented, but the read-only entity is not actually added or removed from collection. This does not happen when the association is non-inverse. This situation should at least be logged. -- 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

14 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5177) auditing a child of a mapped superclass forces auditing on siblings

by Clint Popetz (JIRA)

auditing a child of a mapped superclass forces auditing on siblings ------------------------------------------------------------------- Key: HHH-5177 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5177 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.2 Reporter: Clint Popetz If I have: @MappedSuperclass public class Parent { } @Audited @Entity public class AuditedChild extends Parent { } @Entity public class NonAuditedChild extends Parent { } envers will try to flush audit data for changes to NonAuditedChild. -- 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

14 years, 2 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4646) Inconsistent behavior with Audited and MappedSuperclass annotations

by Hernán Chanfreau (JIRA)

Inconsistent behavior with Audited and MappedSuperclass annotations ------------------------------------------------------------------- Key: HHH-4646 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4646 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0-Beta-2, 3.3.2 Environment: 1) hibernate 3.5 build from trunk (7 nov 09) 2) hibernate-core-3.3.2ga with envers build from branch envers-hibernate3.3 (7 nov 09) Reporter: Hernán Chanfreau Priority: Minor Attachments: mapperSuperclass2TestPatch.txt Suppose B is a subclass of A. The subclass B is @Entity and is not audited. The superclass A is @MappedSuperclass. The differents/inconsistent behaviors are: - If A has @Audited at class level, envers does not generate audit info when saving an instance of B. - If A has @Audited at field/getter level, envers generates audit info when saving an instance of B. You can find the original discussion in envers forum: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=164340 -- 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

14 years, 2 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-374) Timeout support for lucene searches

by Benjamin Gniza (JIRA)

Timeout support for lucene searches ----------------------------------- Key: HSEARCH-374 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-374 Project: Hibernate Search Issue Type: New Feature Components: query Reporter: Benjamin Gniza Attachments: bit-TimeoutPatched-Hibernate-Search-1.0.1EXPERIMENTAL.zip It would be nice to add support for the TimeLimitedCollector of Lucene (Versions 2.4.0 and above). We needed that feature in our project within a week so we couldn't wait for a new official release and had to imlement it on our own. Check out https://sourceforge.net/projects/timeoutpatchhib/ for our source (LGPL just as requested by hibernate). I attached our current source code to the Jira issue. New versions will be published on sourceforge, please refer to https://sourceforge.net/projects/timeoutpatchhib/ for the most current one. The attached source only includes the code to support the TimeLimitedCollector. We also have an experimental version which tries to find the reason of a BooleanQuery.TooManyClausesException within the offending user search term. For more information take a look at the sourceforge project. Note: We didn't overide the query.setTimeout(int) method because we didn't know if this would have caused other side effects. So we created a method query.setTimeout(long). Changed Methods: - org.hibernate.search.FullTextQuery -- +isSearchTimoutExceeded() -- +setTimeout(long) -- +getTimeout() - org.hibernate.search.query.FullTextQueryImpl -- getQueryHits(IndexSearcher, Integer) -- +isSearchTimoutExceeded() -- +setTimeout(long) -- +getTimeout() - org.hibernate.search.query.QueryHits -- Constructors -- scoreDoc(int) -- updateTopDocs(int) -- +getTopDocCollector(int) -- +getHitCollectorForSearch(TopDocCollector) -- +isTimeLimitExceeded() -- 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

14 years, 2 months

2
5
0 / 0

[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

14 years, 2 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

14 years, 2 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

14 years, 2 months

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2010