April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-416) Analyze Payload and how this could be used to store id and class in the index and not the document

by Emmanuel Bernard (JIRA)

Analyze Payload and how this could be used to store id and class in the index and not the document -------------------------------------------------------------------------------------------------- Key: HSEARCH-416 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-416 Project: Hibernate Search Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-228) Write a reliability test under stress

by Emmanuel Bernard (JIRA)

Write a reliability test under stress ------------------------------------- Key: HSEARCH-228 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-228 Project: Hibernate Search Issue Type: Task Reporter: Emmanuel Bernard Fix For: 3.1.0 Write an app inserting, updating deleting concurrently Also searching concurrently and make sure data is reliable during search all that during stress conditions. -- 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
12
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-119) Enable lucene similarity seach based on term frequency vector by QBE-like query

by Xin Wu (JIRA)

Enable lucene similarity seach based on term frequency vector by QBE-like query --------------------------------------------------------------------------------- Key: HSEARCH-119 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-119 Project: Hibernate Search Issue Type: New Feature Reporter: Xin Wu Scenario: Your bookstore application needs a function as follow: When a user see a list of books, there is a similar books button for each book. If user clicks this button of one book item, the similar books will be listed. The similarity is evaluated by all terms in summary of the book and similarity score is dirived from Lucene search similarity package which uses term frequency vectors in calculation. It will compare the target in all corresponding documents in the index and return the hits in order. Note: this funtion is not same as fuzzy query which still needs a definite query condition. In the contrast, similarity search only needs one or several fields (of object/document)to be specified and the rest will be automatically caculated by lucene. A QBE-like API should be used to make such query. You can specify the fields in such query. Please see discussion about this topic in the forum: http://forum.hibernate.org/viewtopic.php?t=979692 -- 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
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-469) Filter caching using causes excessive memory use

by Dobes Vandermeer (JIRA)

Filter caching using causes excessive memory use ------------------------------------------------ Key: HSEARCH-469 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-469 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.1.1.GA Environment: hibernate-core-3.3.2.GA Reporter: Dobes Vandermeer The CachingWrapperFilter uses the reader instance (CacheableMultiReader) as a key for the caching. However, the reader instance keeps pointers to byte arrays in its "normsCache" and in the "normsCache" of its sub-readers; each array has one byte for each document in the index and in some cases there will be multiple of these arrays associated with differet fields. For an index with millions of records this can result in an apparent "leak" of hundreds of megabytes of memory as those readers are not re-used and the MRU cache used by default will keep up to 128 hard references to the readers by default. The search system must either re-use or delete the normsCache, OR the cache key for these filters should be tied to something else that doesn't keep references to potentially huge data arrays. Otherwise the scalability of the search subsystem is significantly impacted when using filters, as you must have enough heap to accommodate up to 128 times as many copies of the norms arrays. -- 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
14
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-434) Make use of NumericField

by Emmanuel Bernard (JIRA)

Make use of NumericField ------------------------- Key: HSEARCH-434 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-434 Project: Hibernate Search Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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

4
39
0 / 0

[Hibernate-JIRA] Created: (EJB-435) @SqlResultSetMapping gives Invalid Column for columns not in select clause

by Rachit (JIRA)

@SqlResultSetMapping gives Invalid Column for columns not in select clause -------------------------------------------------------------------------- Key: EJB-435 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-435 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.GA Environment: DB: Oracle 10g, OS: Win XP, Hibernate 3 using JPA entitymanager Reporter: Rachit Hi, A very simple usage of SqlResultSetMapping. I want to retrieve only country Name using native query. I have specified one column country name to be fetched and mapped in Object. @SqlResultSetMapping(name = "CountryCountry", entities = { @EntityResult(entityClass = Country.class, fields = { @FieldResult(name = "countryName", column = "COUNTRY_NAME") }) public void testComplexer0NativeQuery() { em = emf.createEntityManager(); Query query = em.createNativeQuery( "select iso.COUNTRY_NAME from Country iso", "CountryCountry"); List list = query.getResultList(); System.out.println(list.size()); System.out.println(list.get(0).getClass()); } Running this I get "INFO: could not read column value from result set: ISO1_2_0_; Invalid column name" exception. The whole stack trace : javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at org.springframework.test.ConditionalTestCase.runBare(ConditionalTestCase.java:76) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2231) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:312) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1722) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:165) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:175) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:67) ... 21 more Caused by: java.sql.SQLException: Invalid column name at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269) at oracle.jdbc.driver.OracleStatement.get_column_index(OracleStatement.java:6348) at oracle.jdbc.driver.OracleResultSetImpl.findColumn(OracleResultSetImpl.java:1557) at oracle.jdbc.driver.OracleResultSet.getString(OracleResultSet.java:1549) at org.hibernate.type.StringType.get(StringType.java:41) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:184) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:173) at org.hibernate.loader.Loader.getKeyFromResultSet(Loader.java:1121) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:588) at org.hibernate.loader.Loader.doQuery(Loader.java:724) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) ... 28 more Hibernate is trying to fetch all the columns present in entity to create the object. I am only interested in column/s I have specified in "@FieldResult". If I retrieve all fields in entity, It works fine though. Thanks and Regards. -- 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

5
4
0 / 0

[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

15 years, 6 months

1
4
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

15 years, 6 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

15 years, 6 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

15 years, 6 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

15 years, 6 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

15 years, 6 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

15 years, 6 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, 6 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, 6 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5168) DB2Dialect generates CROSS JOINs which aren't supported

by Grzegorz Olędzki (JIRA)

DB2Dialect generates CROSS JOINs which aren't supported ------------------------------------------------------- Key: HHH-5168 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5168 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-Final Environment: Hibernate 3.5.0-Final, using hibernate-jpa-2.0-api-1.0.0.Final.jar, DB2/NT SQL09013 Reporter: Grzegorz Olędzki When executing a simple JPQL query: {code} SELECT st FROM ScheduledTask st WHERE (NOT st.status = 'COMPLETED') AND st.active = TRUE AND st.task.group = :group {code} Hibernate generates the following SQL query: {code} select scheduledt0_.QSID as col_0_0_ from SCHSCHEDTASK_QS scheduledt0_ cross join SCHTASK_QT task1_ where scheduledt0_.QTID=task1_.QTID and scheduledt0_.QSSTATUS<>'COMPLETED' and scheduledt0_.QSACTIVE=1 and task1_.QTGROUP=? {code} which crashes with: {code} 2010-04-28 10:14:18,551 WARN [org.hibernate.util.JDBCExceptionReporter]/[org.hibernate.util.JDBCExceptionReporter] SQL Error: -104, SQLState: 42601 2010-04-28 10:14:18,552 ERROR [org.hibernate.util.JDBCExceptionReporter]/[org.hibernate.util.JDBCExceptionReporter] DB2 SQL error: SQLCODE: -104, SQLSTATE: 42601, SQLERRMC: cross;TASK_QS scheduledt0_;<space> 2010-04-28 10:14:18,552 WARN [org.hibernate.util.JDBCExceptionReporter]/[org.hibernate.util.JDBCExceptionReporter] SQL Error: -727, SQLState: 56098 2010-04-28 10:14:18,553 ERROR [org.hibernate.util.JDBCExceptionReporter]/[org.hibernate.util.JDBCExceptionReporter] DB2 SQL error: SQLCODE: -727, SQLSTATE: 56098, SQLERRMC: 2;-104;42601;cross|TASK_QS scheduledt0_|<space> 2010-04-28 10:14:18,554 WARN [org.hibernate.util.JDBCExceptionReporter]/[org.hibernate.util.JDBCExceptionReporter] SQL Error: -727, SQLState: 56098 2010-04-28 10:14:18,554 ERROR [org.hibernate.util.JDBCExceptionReporter]/[org.hibernate.util.JDBCExceptionReporter] DB2 SQL error: SQLCODE: -727, SQLSTATE: 56098, SQLERRMC: 2;-104;42601;cross|TASK_QS scheduledt0_|<space> {code} The very same JPQL query works on MySQL database (the actual SQL query uses CROSS JOIN too). When trying to run the same SQL on DB2 manually in a database client the error message is the same (-104, 42601). A subtle change in the query, i.e. replacing CROSS JOIN with a comma (,) seems to fix the problem - both manually and using Hibernate-based application. Using the following DB2Dialect seems to help: {code} public class DB2Dialect extends org.hibernate.dialect.DB2Dialect { @Override public String getCrossJoinSeparator() { return ", "; } } {code} -- 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

5
9
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, 6 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, 6 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, 6 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, 6 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

[Hibernate-JIRA] Created: (HHH-2007) Hibernate doesn't support optional one-to-one associations

by Andrei Iltchenko (JIRA)

Hibernate doesn't support optional one-to-one associations ---------------------------------------------------------- Key: HHH-2007 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2007 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Reporter: Andrei Iltchenko Hibernate doesn't properly support optional one-to-one associations, e.g. Person (0..1) -- (0..1) Passport. The Hibernate books and reference all talk of two ways of mapping one-to-one associations: 1. using a many-to-one fk association with a unique constraint on the fk; 2. using a pk association. the trouble with both of them is that they enforce the mandatory property of an association end, which sometimes is not desirable. The first way enforces the mandatory property with the uniqueness constraint on the fk, the other by using the fact that one table's pk is its fk. I tried to see if I could adapt the 1st way of representing one-to-ones to support optional association ends. What I did was simply remove the unique and not null constrains from DDL generated (without removing it it would be impossible to have a Person record that doesn't reference a Passport record): from CREATE TABLE Person ( PassUniqueId VARCHAR (32) NOT NULL, version INTEGER NOT NULL, uniqueId VARCHAR (32) NOT NULL, name VARCHAR (40) NULL, PRIMARY KEY (uniqueId), UNIQUE(PassUniqueId), FOREIGN KEY (PassUniqueId) REFERENCES Passport (uniqueId) ); to CREATE TABLE Person ( PassUniqueId VARCHAR (32) NULL, version INTEGER NOT NULL, uniqueId VARCHAR (32) NOT NULL, name VARCHAR (40) NULL, PRIMARY KEY (uniqueId), FOREIGN KEY (PassUniqueId) REFERENCES Passport (uniqueId) ); but leave the uniqueness attribute in the mapping file: <many-to-one name="pass" class="application.business.logic.Passport" cascade="save-update,merge" unique="true" > <column name="PassUniqueId"/> </many-to-one> The resulting solution worked fine and I was able to create instances of Person not linked to a Passport. However Hibernate didn't succed in keeping the association from degrading into a many-to-one. It enabled me to create two Persons linked with the same Passport: PASSUNIQUEID | VIRSION | UNIQUEID | Name ================================================ 0d8b3919fffff | 1 | 0d5fb1dcfff | John 0d8b3919fffff | 0 | 10fd07bdfff | Sam A subsequent attempt at retrieving such Persons with Hibernate failed: org.hibernate.HibernateException: More than one row with the given identifier was found: 0d8b3919ffffffd60151e135b6da0164, for class: application.business.logic.Passport. Hibernate should be able to impose the single end property of such associations without relying on the underlying RDBMS engine and never allow them to degrade to many-to-ones. -- 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: (HV-24) Improve the default message of InvalidStateException

by Mike Quilleash (JIRA)

Improve the default message of InvalidStateException ---------------------------------------------------- Key: HV-24 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-24 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 3.0.0.ga Environment: Any Reporter: Mike Quilleash Doing a printStackTrace on InvalidStateException does not give the actual invalid values anywhere. Would greatly improving debugging speed if this was included by default as often this indicates a programming error. Currently I have to run the code again and debug the right place to find out what the InvalidValues are. -- 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

7
14
0 / 0

[Hibernate-JIRA] Created: (HHH-4618) Support pagination: total rows ignore limit

by Dave (JIRA)

Support pagination: total rows ignore limit ------------------------------------------- Key: HHH-4618 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4618 Project: Hibernate Core Issue Type: New Feature Components: core Environment: JBoss 5.1.0GA Reporter: Dave Limit is used for pagination, but total number of rows must be known to calculate page count. Currently we have to use two queries: 1. select * from Student where age<30 limit 20; 2. select count(*) from Student where age<30; For complex query with joins/huge tables, it can be a performance issue. For Criteria API query with group by, there is no way to get row count, for example criteria.setProjection(Projection.projectionList().add(Projections.groupProperty("name")).add(Projections.sum(score))); Currently there is no way to get row count of this query using Criteria API. For MYSQL, SQL_CALC_FOUND_ROWS and FOUND_ROWS() are used to get row count ignoring limit. Pagination is used for all web application. Hibernate should support it in HQL and Criteria API. -- 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: (HSEARCH-449) Consider LUCENE-1575 carefully: not scoring by default?

by Sanne Grinovero (JIRA)

Consider LUCENE-1575 carefully: not scoring by default? ------------------------------------------------------- Key: HSEARCH-449 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-449 Project: Hibernate Search Issue Type: Sub-task Reporter: Sanne Grinovero -- 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
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-457) Analyzers in Lucene 3.0 don't have a default constructor

by Sanne Grinovero (JIRA)

Analyzers in Lucene 3.0 don't have a default constructor -------------------------------------------------------- Key: HSEARCH-457 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-457 Project: Hibernate Search Issue Type: Sub-task Components: analyzer Reporter: Sanne Grinovero we're going to need a factory of analyzers or something; could be nice to use "simple" names to embed support for the most common analyzers (the advanced anaylzers are probably most commonly picked from Solr). Analyzers like StopWords where needing parameters anyway to make sense. -- 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

4
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-435) New token stream API, is there a benefit, work on our part?

by Emmanuel Bernard (JIRA)

New token stream API, is there a benefit, work on our part? ----------------------------------------------------------- Key: HSEARCH-435 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-435 Project: Hibernate Search Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-371) Refactor DocumentBuilder and introduce abstract base class

by Hardy Ferentschik (JIRA)

Refactor DocumentBuilder and introduce abstract base class ---------------------------------------------------------- Key: HSEARCH-371 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-371 Project: Hibernate Search Issue Type: Task Components: engine Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.2.0 Further improvement of the document builder. Introducing a common base class and moving some methods into there and taking care of some not so nice method overriding between the two existing DocumentBuilders will further improve the design of these classes. -- 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
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4072) ManyToMany with single table inheritance fails when multiple subclasses

by david sinclair (JIRA)

ManyToMany with single table inheritance fails when multiple subclasses ----------------------------------------------------------------------- Key: HHH-4072 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4072 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.2 Environment: Windows XP, Java 1.6 Reporter: david sinclair Priority: Critical I have a base entity named BusinessSoftwareMatrixElement declare as such @Entity @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name = "software_type", discriminatorType = DiscriminatorType.STRING) @DiscriminatorValue("Software") @Audited BusinessSoftwareMatrixElement ...{ } I then have a subclass of BusinessSoftwareMatrixElement that is a mapped super class which defines a many to many relationship. @MappedSuperclass @Audited public abstract class BusinessOSProcessServiceMatrixElement extends BusinessSoftwareMatrixElement { private Set<BusinessOSMatrixElement> applicableOperatingSystems = new HashSet<BusinessOSMatrixElement>(); @ManyToMany(fetch = FetchType.LAZY, cascade = {CascadeType.REMOVE, CascadeType.REFRESH }, targetEntity = BusinessOSMatrixElement.class) @JoinTable(name="matrix_elements_procserv_aos", joinColumns=@JoinColumn(name="sw_guid"), inverseJoinColumns = @JoinColumn(name="os_guid")) public Set<BusinessOSMatrixElement> getApplicableOperatingSystems() { return applicableOperatingSystems; } } There are then to subclasses that add no new fields, only different discriminators @Entity @DiscriminatorValue("Database") @Audited public class BusinessDBMatrixElement extends BusinessOSProcessServiceMatrixElement { @Entity @DiscriminatorValue("Application") @Audited public class BusinessAppMatrixElement extends BusinessOSProcessServiceMatrixElement { Running the ant task to create the DDL results in an exception being thrown for that many to many table. Caused by: org.hibernate.DuplicateMappingException: Duplicate class/entity mapping matrix_elements_procserv_aos_AUD at org.hibernate.tool.ant.HibernateToolTask.reportException(HibernateToolTask.java:226) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:189) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108) ... 24 more Caused by: org.hibernate.DuplicateMappingException: Duplicate class/entity mapping matrix_elements_procserv_aos_AUD at org.hibernate.cfg.Mappings.addClass(Mappings.java:141) at org.hibernate.cfg.HbmBinder.bindRoot(HbmBinder.java:167) at org.hibernate.cfg.Configuration.add(Configuration.java:716) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:531) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:291) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1162) at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:102) at org.hibernate.envers.ant.AnnotationConfigurationTaskWithEnvers.doConfiguration(AnnotationConfigurationTaskWithEnvers.java:38) at org.hibernate.tool.ant.ConfigurationTask.getConfiguration(ConfigurationTask.java:55) at org.hibernate.tool.ant.HibernateToolTask.getConfiguration(HibernateToolTask.java:302) at org.hibernate.tool.ant.Hbm2DDLExporterTask.createExporter(Hbm2DDLExporterTask.java:51) at org.hibernate.tool.ant.ExporterTask.execute(ExporterTask.java:39) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:186) -- 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

[Hibernate-JIRA] Created: (HHH-2835) Setting org.hibernate.type logging to debug produces no logging

by Jeremy Grodberg (JIRA)

Setting org.hibernate.type logging to debug produces no logging --------------------------------------------------------------- Key: HHH-2835 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2835 Project: Hibernate3 Issue Type: Bug Components: core, documentation Affects Versions: 3.2.5, 3.2.4 Environment: Hibernate 3.2.4.ga and Hibernate 3.2.5.ga with MySQL5Dialect (configured with Hibernate Annotations 3.3.0.ga and Spring 2.0.6) Reporter: Jeremy Grodberg Priority: Minor According to the online documentation (labeled as version 3.2.2 at this moment), Table 3.9 "Hibernate Log Categories", as viewed here today: http://www.hibernate.org/hib_docs/v3/reference/en/html/session-configurat... Setting the log4j category "org.hibernate.type" to debug should "Log all JDBC parameters". However, it produces no output at all. When I go on to set "org.hibernate" to debug, I get output like this: DEBUG: org.hibernate.jdbc.AbstractBatcher - about to open PreparedStatement (open PreparedStatements: 0, globally: 0) DEBUG: org.hibernate.SQL - select count(*) from album where genreID=? DEBUG: org.hibernate.loader.Loader - bindNamedParameters() 126 -> genreId [1] DEBUG: org.hibernate.jdbc.AbstractBatcher - about to open ResultSet (open ResultSets: 0, globally: 0) DEBUG: org.hibernate.loader.Loader - result row: DEBUG: org.hibernate.jdbc.AbstractBatcher - about to close ResultSet (open ResultSets: 1, globally: 1) DEBUG: org.hibernate.jdbc.AbstractBatcher - about to close PreparedStatement (open PreparedStatements: 1, globally: 1) Note that the JDBC parameters are logged under org.hibernate.loader but nothing appears under org.hibernate.type. FYI, genreId is, in this case, a Long. Perhaps this is expected/desired when using annotations? If so, then please update the documentation. If not, please restore the logging. -- 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

10
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2228) ant eg fails - bad release notes quick start

by Brian Brooks (JIRA)

ant eg fails - bad release notes quick start -------------------------------------------- Key: HHH-2228 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2228 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.0.ga Environment: hibernate 3.2.0.ga Microsoft Windows XP [Version 5.1.2600] java version "1.5.0_07" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03) Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode) Reporter: Brian Brooks Priority: Minor The hibernate 3.2.0.ga release notes http://sourceforge.net/project/shownotes.php?release_id=455849&group_id=4... read as Get Up And Running Quick ------------------------ Demo: (1) copy your JDBC driver to the lib directory (2) edit etc/hibernate.properties (3) run "ant eg" or "build eg" (4) browse the sourcecode in eg/org/hibernate/auction This directions are incorrect. Below is the ant output if these steps are followed. Also, I had to put junit*.jar and antlr*all*.jar in my ANT_HOME/lib before ant eg would work. C:\hibernate-3.2>ant eg Buildfile: build.xml [taskdef] Could not load definitions from resource clovertasks. It could not b e found. eg: [javac] Compiling 8 source files to C:\hibernate-3.2\build\eg [javac] C:\hibernate-3.2\eg\org\hibernate\auction\Main.java:10: cannot find symbol [javac] symbol : class FetchMode [javac] location: package org.hibernate [javac] import org.hibernate.FetchMode; [javac] ^ [javac] C:\hibernate-3.2\eg\org\hibernate\auction\Main.java:11: cannot find symbol [javac] symbol : class FlushMode [javac] location: package org.hibernate [javac] import org.hibernate.FlushMode; [javac] ^ [javac] C:\hibernate-3.2\eg\org\hibernate\auction\Main.java:12: cannot find symbol [javac] symbol : class LockMode [javac] location: package org.hibernate [javac] import org.hibernate.LockMode; [javac] ^ .... -- 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

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3778) Select expression results in more than one column having same name when using connected to Sybase

by vijay gudimella (JIRA)

Select expression results in more than one column having same name when using connected to Sybase -------------------------------------------------------------------------------------------------- Key: HHH-3778 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3778 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: Windows XP, Jboss 4.2 GA, JPA Reporter: vijay gudimella The bug described in HB-705 is still a problem. The application runs fine with MySQL and JavaDb but throws the error "Select expression results in more than one column having same name " with Sybase. HB-705 is marked as "Incomplete" , and status as closed, will there be a "fix" or it is considered "fixed" -- 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

4
6
0 / 0

[Hibernate-JIRA] Created: (HV-307) Support @Past/@Future annotations at types from the Joda Time API

by Gunnar Morling (JIRA)

Support @Past/@Future annotations at types from the Joda Time API ----------------------------------------------------------------- Key: HV-307 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-307 Project: Hibernate Validator Issue Type: New Feature Affects Versions: 4.1.0 Reporter: Gunnar Morling Assignee: Hardy Ferentschik Background: =========== The Bean Validation API specifies the annotations @Past and @Future, which are allowed at the JDK types Date and Calendar. Due to several issues and restrictions of these JDK types the open-source Joda Time API (http://joda-time.sourceforge.net/) which provides alternative date/time types became quite popular within the last years. To do: ====== * Hibernate Validator should add support for @Past/@Future for the Joda API date/times types by providing ConstraintValidator implementations for these types. * The Joda Time API should be added as optional dependency to HV. Upon runtime HV should check reflectively if Joda is on the class path. If that's the case, the Joda validators should be registered. * The HV reference guide should mention the additional types at which the @Past/@Future are supported. -- 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, 7 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3834) Exception: cast() requires two arguments

by Paulo Angelo (JIRA)

Exception: cast() requires two arguments ---------------------------------------- Key: HHH-3834 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3834 Project: Hibernate Core Issue Type: Bug Environment: hibernate3, postgresql 8.3 Reporter: Paulo Angelo Got exaclty the same as in HHH-3285 .: cast() requires two arguments [select f from MenuItem f where ( ( UPPER( TO_ASCII(CAST(convert(f.Menu.Idme, 'UTF8', 'LATIN1') , TEXT),'LATIN1')) LIKE UPPER( TO_ASCII(CAST(convert('M10', 'UTF8', 'LATIN1') , TEXT),'LATIN1')) ) ) order by f.Orde ASC ] But there is not a extra ")" (I think, :) ) -- 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, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (METAGEN-28) Custom UserType not supported in Hibernate's static MetaModel generator

by jean-claude cote (JIRA)

Custom UserType not supported in Hibernate's static MetaModel generator ----------------------------------------------------------------------- Key: METAGEN-28 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-28 Project: Hibernate Metamodel Generator Issue Type: Bug Affects Versions: 1.0.0-CR-1 Reporter: jean-claude cote Assignee: Hardy Ferentschik Priority: Minor If an Entity has a custom Hibernate User type @Type it will not get generated in the static MetaModel class "Item_". This seems easy to fix by checking if the element being process has a @Type annotation then process it. AnnotationMetaEntity.isBasicAttribute() ... if(TypeUtils.containsAnnotation(element, Type.class) { return true; } -- 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, 7 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4969) NullPointerException in FromClause.findIntendedAliasedFromElementBasedOnCrazyJPARequirements due to null alias map key

by Jürgen (JIRA)

NullPointerException in FromClause.findIntendedAliasedFromElementBasedOnCrazyJPARequirements due to null alias map key ---------------------------------------------------------------------------------------------------------------------- Key: HHH-4969 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4969 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: Java version: 1.6.0_16,Sun Microsystems Inc. Java VM: Java HotSpot(TM) 64-Bit Server VM 14.2-b01,Sun Microsystems Inc. OS-System: Linux 2.6.25.14-69.fc8,amd64 Hibernate 3.2.4.sp1 JBosss-4.2.3.GA DB2 v8 / JDBC Driver v4.7.85 Reporter: Jürgen Got a NullPointerException in {{org.hibernate.hql.ast.tree.FromClause.findIntendedAliasedFromElementBasedOnCrazyJPARequirements(String)}} due to fromElementByClassAlias Map key being null. Only for certain HQL query, along the lines of: {code} SELECT c FROM C c, IN(c.t) t, IN(c.k.x) x WHERE c.k.u = 'K' AND t.end >= CURRENT_DATE {code} Removing {{IN(c.k.x) x}} or {{c.k.u = 'K'}} will not result in a NullPointerException, most likely due to no null alias key put into the map. specifiedAlias param was "CURRENT_DATE" when findIntendedAliasedFromElementBasedOnCrazyJPARequirements was called. {code} private FromElement findIntendedAliasedFromElementBasedOnCrazyJPARequirements(String specifiedAlias) { ... if ( alias.equalsIgnoreCase( specifiedAlias ) ) { // alias can be null here .. } {code} {code} java.lang.NullPointerException at org.hibernate.hql.ast.tree.FromClause.findIntendedAliasedFromElementBasedOnCrazyJPARequirements(FromClause.java:120) at org.hibernate.hql.ast.tree.FromClause.containsClassAlias(FromClause.java:247) at org.hibernate.hql.ast.tree.FromClause.isFromElementAlias(FromClause.java:135) at org.hibernate.hql.ast.HqlSqlWalker.isNonQualifiedPropertyRef(HqlSqlWalker.java:467) at org.hibernate.hql.antlr.HqlSqlBaseWalker.addrExpr(HqlSqlBaseWalker.java:4382) at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1212) at org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4041) at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:3648) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1762) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1690) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1687) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1687) at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:776) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:577) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.SessionFactoryImpl.checkNamedQueries(SessionFactoryImpl.java:402) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:352) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:713) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:246) at sun.reflect.GeneratedMethodAccessor622.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.server.jmx.LazyMBeanServer.invoke(LazyMBeanServer.java:291) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) {code} -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2606) CharArrayType allways leads to dirty objects

by Aymeric Levaux (JIRA)

CharArrayType allways leads to dirty objects -------------------------------------------- Key: HHH-2606 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2606 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4 Environment: Hibernate 3.2.4 Postgresql 8.2 or Hsqldb Reporter: Aymeric Levaux Attachments: typechararray.zip When you map a property of type char[], the owning object is always considered as dirty even if untouched. I attached a unit test that reproduce the problem. -- 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, 7 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HBX-1068) Hibernate Configurations on Eclipse Ganymede 3.4

by Ricardo M Augusto (JIRA)

Hibernate Configurations on Eclipse Ganymede 3.4 ------------------------------------------------ Key: HBX-1068 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1068 Project: Hibernate Tools Issue Type: Bug Components: eclipse Affects Versions: 3.2.1 Environment: Windows Vista 32bits, hibernate 2.6, eclipse 3.4 (Ganymede) Reporter: Ricardo M Augusto When created hibernate configuration eclipse shows: java.lang.NoClassDefFoundError: org/eclipse/ui/internal/util/SWTResourceUtil at org.hibernate.eclipse.console.workbench.xpl.AnyAdaptableLabelProvider.getImage(AnyAdaptableLabelProvider.java:166) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getImage(WrappedViewerLabelProvider.java:117) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:165) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1012) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:466) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2041) at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:827) at org.eclipse.jface.viewers.AbstractTreeViewer.createAddedElements(AbstractTreeViewer.java:340) at org.eclipse.jface.viewers.AbstractTreeViewer.internalAdd(AbstractTreeViewer.java:270) at org.eclipse.jface.viewers.TreeViewer.internalAdd(TreeViewer.java:652) at org.hibernate.eclipse.console.viewers.xpl.MTreeViewer.add(MTreeViewer.java:106) at org.eclipse.ui.progress.DeferredTreeContentManager$3.runInUIThread(DeferredTreeContentManager.java:353) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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, 7 months

7
6
0 / 0

[Hibernate-JIRA] Created: (METAGEN-7) Try to find a way to be able to use @SupportedAnnotationTypes("javax.persistence.Entity") in JPAMetaModelEntityProcessor

by Hardy Ferentschik (JIRA)

Try to find a way to be able to use @SupportedAnnotationTypes("javax.persistence.Entity") in JPAMetaModelEntityProcessor ------------------------------------------------------------------------------------------------------------------------ Key: METAGEN-7 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-7 Project: Hibernate StaticMetamodel Generator Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik At the moment we use @SupportedAnnotationTypes("*"). Better would be to explicitly specify @SupportedAnnotationTypes("javax.persistence.Entity"). Then the processor would only be called if there are any entities annotated with @Entity. However, this also means that the processor is not getting called at all if there is no @Entity which could be the case if all configuration is done via xml. We would need a way to make sure that the processor is called at least once to ensure xml is parsed. Other than that only entities annotated with @Entity should be passed to the processor. At the moment I don't see how we can make this happen :( -- 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, 7 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4075) UnsupportedOperationException when assigning an alias to an indexed collection

by Robert Wruck (JIRA)

UnsupportedOperationException when assigning an alias to an indexed collection ------------------------------------------------------------------------------ Key: HHH-4075 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4075 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2 Environment: Hibernate 3.3.2.GA, MySQL5InnoDBDialect Reporter: Robert Wruck This works: select count(*) from Order o left join o.orderAttributes oa, Attribute a where a.id = 1 and index(oa) = a but accessing elements throws an exception: select count(*) from Order o left join o.orderAttributes oa, Attribute a where a.id = 1 and oa[a] is null or oa[a] = '2' Replacing oa[a] with o.orderAttributes[a] does not throw an exception but also does an inner join, so it's not a workaround. Stack trace: java.lang.UnsupportedOperationException at org.hibernate.hql.ast.tree.IdentNode.resolveIndex(IdentNode.java:66) at org.hibernate.hql.ast.tree.IndexNode.resolve(IndexNode.java:94) at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:117) at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:113) at org.hibernate.hql.ast.HqlSqlWalker.processIndex(HqlSqlWalker.java:956) at org.hibernate.hql.antlr.HqlSqlBaseWalker.addrExpr(HqlSqlBaseWalker.java:4576) at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1289) at org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4243) at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:4084) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1864) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1792) at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:818) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:604) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:288) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:231) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:254) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:185) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:94) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1651) -- 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, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3096) Count operator with idenfication variable w/ composite primary key produces bad sql

by Bob Tiernay (JIRA)

Count operator with idenfication variable w/ composite primary key produces bad sql ------------------------------------------------------------------------------------ Key: HHH-3096 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3096 Project: Hibernate3 Issue Type: Bug Reporter: Bob Tiernay @EmbeddedId private Id id; @Embeddable public static class Id implements Serializable { private static final long serialVersionUID = 6475618094377929936L; @Column(name="TG_ID", nullable = false) private Integer groupId; @Column(name="MBR_ID", nullable = false) private Integer memberId; public Id() { // Empty } public Id(Integer groupId, Integer memberId) { super(); this.groupId = groupId; this.memberId = memberId; } @Override public boolean equals(Object other) { if (other == this) { return true; } else if (other instanceof Id) { return groupId.equals(((Id) other).groupId) && memberId.equals(((Id) other).memberId); } return false; } @Override public int hashCode() { return groupId.hashCode() ^ memberId.hashCode(); } } @NamedQuery(name = "GroupMember.getCountByGroup", query = "SELECT COUNT(gm) FROM GroupMember gm WHERE gm.id.groupId = :groupId") produces Hibernate: /* named HQL query GroupMember.getCountByGroup */ select count((groupmembe0_.TG_ID, groupmembe0_.MBR_ID)) as col_0_0_ from GROUP_MEMBER groupmembe0_ where groupmembe0_.TG_ID=? and the following hibernate exception Caused by: java.sql.SQLException: ORA-00907: missing right parenthesis at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:810) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1039) at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:850) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1134) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3384) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:93) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1787) at org.hibernate.loader.Loader.doQuery(Loader.java:674) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader Which is consistent with what Oracle produces by manual query execution. The problem is the extra set of parenthesis around the composite primary key columns which appear to be invalid (at least for Oracle) The recommend fix would be to use COUNT(*) or count(groupmembe0_.TG_ID, groupmembe0_.MBR_ID) in yhis case -- 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, 7 months

7
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3187) Issue with Hibernate3.0 and weblogic8.1 while setting transaction is marked to setRollbackOnly... (AppSetRollbackOnlyException)

by Anjan Deb (JIRA)

Issue with Hibernate3.0 and weblogic8.1 while setting transaction is marked to setRollbackOnly... (AppSetRollbackOnlyException) ------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3187 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3187 Project: Hibernate3 Issue Type: Task Affects Versions: 3.0 final Environment: hibernate3.0, weblogic8.1, oracle9.1 Reporter: Anjan Deb I am using Hibernate 3.0 with JTA (Weblogic 8.1 SP4). Basically, I am trying to handle transaction/hibernate exceptions in my application. I am managing transactions with UserTransaction. I start a transaction at the begining of the request and after that I am doing some operations on that transaction. And if some exception comes I log it, rollback the transaction and throw the exception. UserTransaction.commit() throws RollbackException if anything goes wrong with the operation, but, it does not return what exactly went wrong, like, exceptions related to SQL Exception or hibernate Exception. It basically dumps all that information to the logs internally and throws RollbackException with the following trace (see below). But this trace has no such information which I can send back to the user. As, information of what went wrong has already been dumped to the server console. I will appreciate if you can tell if there is anyway I can recieve the actual exception trace or am I doing anything wrong with the hibernate configuration?? Thanks in Advance, Anjan ------------------------------------------------------------------------------------------------------------------------------ Actual Exception which transaction dumps to the server console/log ERROR - ORA-00001: unique constraint (NOVATXN.UQ_BROKERS) violated ERROR - ORA-00001: unique constraint (NOVATXN.UQ_BROKERS) violated ERROR - Could not synchronize database state with session org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:69) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:202) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:230) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:980) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:353) at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:59) at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010) at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115) at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1216) at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1990) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:275) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint (NOVATXN.UQ_BROKERS) violated at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:367) at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:8726) at weblogic.jdbc.wrapper.PreparedStatement.executeBatch(PreparedStatement.java:169) at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:58) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:195) ... 27 more RollbackException Trace: 03/17/2008 08:50:09 [EROR] JTATransactionalAction weblogic.transaction.RollbackException: Unknown reason - with nested exception: [weblogic.transaction.internal.AppSetRollbackOnlyException] 03/17/2008 08:50:09 [EROR] JTATransactionalAction com.novarum.nova.application.OperationException: Transaction does not exist 03/17/2008 08:50:09 [DBUG] MessageProcessor Unknown reason java.lang.RuntimeException: Unknown reason at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:54) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) Caused by: com.novarum.nova.application.OperationException: Unknown reason at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:35) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) ... 10 more Caused by: weblogic.transaction.RollbackException: Unknown reason - with nested exception: [weblogic.transaction.internal.AppSetRollbackOnlyException] at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1683) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:325) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) ... 11 more getCause(): com.novarum.nova.application.OperationException: Unknown reason at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:35) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) Caused by: weblogic.transaction.RollbackException: Unknown reason - with nested exception: [weblogic.transaction.internal.AppSetRollbackOnlyException] at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1683) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:325) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) ... 11 more getCause(): weblogic.transaction.internal.AppSetRollbackOnlyException at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:504) at org.hibernate.transaction.CacheSynchronization.setRollbackOnly(CacheSynchronization.java:73) at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:63) at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010) at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115) at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1216) at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1990) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:275) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) --------------- nested within: ------------------ weblogic.transaction.RollbackException: Unknown reason - with nested exception: [weblogic.transaction.internal.AppSetRollbackOnlyException] at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1683) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:325) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) getNested(): weblogic.transaction.internal.AppSetRollbackOnlyException at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:504) at org.hibernate.transaction.CacheSynchronization.setRollbackOnly(CacheSynchronization.java:73) at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:63) at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010) at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115) at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1216) at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1990) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:275) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) Following is the hibernate.cfg.xml <session-factory>  <property name="connection.datasource">jdbc/novaJDBCDataSource</property> <property name="transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property> <property name="transaction.manager_lookup_class">org.hibernate.transaction.WeblogicTransactionManagerLookup</property> <property name="dialect">org.hibernate.dialect.OracleDialect</property> <property name="current_session_context_class">jta</property> <property name="show_sql">false</property> <property name="format_sql">true</property> <property name="hibernate.default_schema">novatxn</property> <property name="jdbc.batch_size">30</property>  <property name="jdbc.batch_versioned_data">false</property> <property name="jdbc.use_streams_for_binary">true</property>  <property name="max_fetch_depth">1</property> <property name="query.substitutions">true 1, false 0, yes 'Y', no 'N'</property>   <property name="query.factory_class">org.hibernate.hql.classic.ClassicQueryTranslatorFactory</property> </session-factory> -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3900) Do not attempt to register Synchronization when Transaction is in STATUS_MARKED_ROLLBACK

by Chris Bredesen (JIRA)

Do not attempt to register Synchronization when Transaction is in STATUS_MARKED_ROLLBACK ---------------------------------------------------------------------------------------- Key: HHH-3900 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3900 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1, 3.2.6 Reporter: Chris Bredesen Priority: Minor In JTASessionContext.currentSession(), a CleanupSync is built and registered. The transaction is verified to be in progress using JTAHelper.isInProgress() which checks for STATUS_ACTIVE or STATUS_MARKED_ROLLBACK. JBossTS (based on the OTS standard) disallows the registration of Synchronizations in STATUS_MARKED_ROLLBACK and so in such cases, JTASessionContext.currentSession() will fail. The stack trace looks something like this (note no wrapped root cause): Caused by: org.hibernate.HibernateException: Unable to register cleanup Synchronization with TransactionManager at org.hibernate.context.JTASessionContext.currentSession(JTASessionContext.java:92) at org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:544) A possible fix is to check only for STATUS_ACTIVE and do any needed cleanup work proactively if the Transaction is in STATUS_MARKED_ROLLBACK rather than relying on CleanupSync. -- 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, 7 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3690) Sybase - FumTest.testCompositeKeyPathExpressions() fails due to subquery with more than one column in select list

by Gail Badner (JIRA)

Sybase - FumTest.testCompositeKeyPathExpressions() fails due to subquery with more than one column in select list ----------------------------------------------------------------------------------------------------------------- Key: HHH-3690 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3690 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Sybase only allows one column in a subquery select list. The only exception is that a subquery in an EXISTS() predicate can have '*' as the select list. This is documented at: http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc32300.150... FumTest.testCompositeKeyPathExpressions() fails with "SybSQLException: Incorrect syntax near ','." The HQL that fails is: "from Fum fum1 where exists elements(fum1.friends)". It fails becuase the elements have a composite ID. The fix described in HHH-3032 should fix this issue since the subquery is used in an EXISTS() predicate.. -- 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, 7 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4510) Add column-level read/write support (HHH-4440) to annotations

by Steve Ebersole (JIRA)

Add column-level read/write support (HHH-4440) to annotations ------------------------------------------------------------- Key: HHH-4510 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4510 Project: Hibernate Core Issue Type: Bug Components: annotations Reporter: Steve Ebersole See HHH-4440 for 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

15 years, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (METAGEN-30) @Target

by jean-claude cote (JIRA)

@Target ------- Key: METAGEN-30 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-30 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Reporter: jean-claude cote Assignee: Hardy Ferentschik The jpamodelgen does not produce output for fields mapped using the @Embedded/@Target tags. ex: @Entity class House { @Embedded @Target(acme.AddressImpl.class) private Address address; } It only works when the field is of type AddressImpl. Are there plans to support the hiberbate specific annotations? Any plans to support entity mapped using classic hbm.xml files? thanks jean-claude -- 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, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2917) arithmatic of subselect throws NPE

by John Aylward (JIRA)

arithmatic of subselect throws NPE ---------------------------------- Key: HHH-2917 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2917 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 Annotation 3.3.0 VAlidator 3.0.0 MySQL 5.0.44 Reporter: John Aylward Exception Stack: java.lang.NullPointerException at org.hibernate.hql.ast.tree.BinaryArithmeticOperatorNode.getRightHandOperand(BinaryArithmeticOperatorNode.java:185) at org.hibernate.hql.ast.tree.BinaryArithmeticOperatorNode.initialize(BinaryArithmeticOperatorNode.java:20) at org.hibernate.hql.ast.HqlSqlWalker.prepareArithmeticOperator(HqlSqlWalker.java:1011) at org.hibernate.hql.antlr.HqlSqlBaseWalker.arithmeticExpr(HqlSqlBaseWalker.java:2729) at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1278) at org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4041) at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:3600) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1762) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1690) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1687) at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:776) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:577) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) HQL: [SELECT DISTINCT pi.billingAccount.consolidatedBillingAccount.bankAccount FROM com.cicat.bedrock.billing.model.ProviderInvoice AS pi WHERE pi.readyForPayment=true AND (SELECT piad.total FROM com.cicat.bedrock.billing.model.ProviderInvoiceAccountData AS piad WHERE piad.invoice = pi AND piad.providerBillingAccount = pi.billingAccount) > ((SELECT COALESCE(SUM(amount),0) FROM com.cicat.bedrock.billing.model.BankAccountTransaction AS bat1 WHERE bat1.deleted=false AND bat1.providerInvoice = pi) + (SELECT COALESCE(SUM(amount),0) FROM com.cicat.bedrock.billing.model.BankAccountTransactionSplit AS bats1 WHERE bats1.deleted=false AND bats1.bankAccountTransaction.deleted=false AND bats1.providerInvoice = pi)) ] Representative SQL of HQL call: SELECT DISTINCT ba.* from ProviderInvoice AS pi INNER JOIN ProviderBillingAccount AS pba ON pi.billingAccount_id=pba.id INNER JOIN ConsolidatedBillingAccount AS cba ON pba.consolidatedBillingAccount_id=cba.id INNER JOIN BankAccount AS ba ON cba.bankAccount_id=ba.id WHERE pi.readyForPayment=true AND (SELECT piad.total FROM ProviderInvoiceAccountData AS piad WHERE piad.invoice_id = pi.id AND piad.providerBillingAccount_id = pi.billingAccount_id) > ((SELECT COALESCE(SUM(bat1.amount),0) FROM BankAccountTransaction AS bat1 WHERE bat1.deleted=false AND bat1.providerInvoice_id = pi.id) + (SELECT COALESCE(SUM(bats1.amount),0) FROM BankAccountTransactionSplit AS bats1 INNER JOIN BankAccountTransaction bat2 ON bats1.bankAccountTransaction_id=bat2.id WHERE bats1.deleted=false AND bat2.deleted=false AND bats1.providerInvoice_id = pi.id)) -- 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, 7 months

4
15
0 / 0

[Hibernate-JIRA] Created: (HBX-849) Tools does not insert @Type in POJOs for user types defined in reveng.xml

by Zeljko Trogrlic (JIRA)

Tools does not insert @Type in POJOs for user types defined in reveng.xml ------------------------------------------------------------------------- Key: HBX-849 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-849 Project: Hibernate Tools Type: Bug Components: hbm2java, reverse-engineer Environment: jboss-seam-1.1.0.GA, MySQL Reporter: Zeljko Trogrlic I have created reveng.xml file: <hibernate-reverse-engineering> <table catalog="configuration" name="userdb_domain_acl"> <column name="enabled" type="com.siemens.msm.model.mapping.BooleanEnumType" exclude="false"/> </table> </hibernate-reverse-engineering> and included it in build.xml: <jdbcconfiguration propertyfile="build.properties" packagename="${model.package}" revengfile="${project.home}/reveng.xml"/> Generated POJO attribute has proper type, but user type information is missing: @Column(name = "enabled") @Length(max = 42) public Boolean getEnabled() { .... so Hibernate reports error: 3:49:31,397 INFO [TableMetadata] table found: configuration.userdb_domain_acl 13:49:31,397 INFO [TableMetadata] columns: [id, enabled, tablename, domain] 13:49:31,397 WARN [ServiceController] Problem starting service persistence.units:ear=msmgui.ear,unitName=msmgui javax.persistence.PersistenceException: org.hibernate.HibernateException: Wrong column type: enabled, expected: varchar( 2) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:698) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:264) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Annotations should look like this: @Column(name = "enabled") @Type(type="booleanEnum") public Boolean getEnabled() { ... -- 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, 7 months

4
11
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 April 2010