December 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3420) MatchMode doesn't escape wildcard characters

by Hontvári József (JIRA)

MatchMode doesn't escape wildcard characters -------------------------------------------- Key: HHH-3420 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3420 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.2 Environment: MySQL Reporter: Hontvári József Priority: Minor One can think that by specifying e.g. MatchMode.START in a "like" restriction Hibernate takes care of escaping SQL LIKE wildcard characters in the supplied pattern. It doesn't, actually Hibernate only inserts a % before the first character. I am not sure what was the intent of the original author (Gavin King), so the issue may only be missing documentation. However I don't see any other useful purpose of this class then providing database independent escaping. It seems that all databases use the % wildcard, so there is no need to provide database indpeendence to that. It can be argued that this might create a security problem for an unaware developer, so I set issue type to 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

16 years, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-489) add @AttributeOverride with formula support

by Amir Pashazadeh (JIRA)

add @AttributeOverride with formula support ------------------------------------------- Key: ANN-489 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-489 Project: Hibernate Annotations Type: Improvement Components: binder Versions: 3.2.0.ga Reporter: Amir Pashazadeh @AttributeOverride currently just have name and column properties, there can be an alternative with formula support (instead of column support). -- 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

16 years, 12 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-1035) Safety: 'Run SchemaExport' menu option

by Karel-Henk Nijhuis (JIRA)

Safety: 'Run SchemaExport' menu option -------------------------------------- Key: HBX-1035 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1035 Project: Hibernate Tools Issue Type: Improvement Components: eclipse Reporter: Karel-Henk Nijhuis The 'Run SchemaExport' option that is accessible from the configuration context menu inside the Eclipse 'Hibernate Configurations' view does not give any feedback. Choosing this option, however, results in executing DDL on the database which erases all data inside the configured database. The schema export option could also be interpreted as a way to get the schema's SQL without executing the DDL. I would suggest to give more appropriate feedback before this operation is run. -- 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

16 years, 12 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3499) NamingStrategy should support naming foreign keys and indexes

by Geoffrey De Smet (JIRA)

NamingStrategy should support naming foreign keys and indexes ------------------------------------------------------------- Key: HHH-3499 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3499 Project: Hibernate Core Issue Type: Improvement Components: metamodel Affects Versions: 3.3.1 Reporter: Geoffrey De Smet hbm2ddl always generates foreign key constraints based on hashcodes, like this: alter table apple add index FK365FA4BB24B1D45C (lemon_id), add constraint FK365FA4BB24B1D45C foreign key (lemon_id) references lemon (id); Some databases don't support enough characters for foreign key names to generate a readable foreign key name, so that's a sensible default. However, those of use that use databases like MySQL etc, would like a readable foreign key name, such as: alter table apple add index FK_Apple_lemon (lemon_id), add constraint FK365FA4BB24B1D45C foreign key (lemon_id) references lemon (id); We can do that by annotating every entity with @Index in JPA, or specifying it in a hbm file, but we can't do it generally, by extending DefaultNamingStrategy or ImprovedNamingStrategy. Here's a proposition on how we could do it: - In the NamingStrategy interface, next to the method foreignKeyColumnName, add a method: public String foreignKeyConstraintName(String propertyName, String propertyEntityName, String propertyTableName, String referencedColumnName - DefaultNamingStrategy and ImprovedNamingStrategy should implement it as it is now, based on hashcodes. - If a mapping has an @Index JPA annotation or it's specified in a hbm file, that override counts. -- 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

16 years, 12 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2355) CGLIBLazyInitializer can not access a public member if parent class is not public

by Daniel Beland (JIRA)

CGLIBLazyInitializer can not access a public member if parent class is not public --------------------------------------------------------------------------------- Key: HHH-2355 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2355 Project: Hibernate3 Type: Bug Versions: 3.2.1 Reporter: Daniel Beland In hibernate 3.2.1, CGLIBLazyInitializer cannot acces a public method if it has been inherited from a parent class that is not public. Let's say we have a class A, modifier = default (package) with a public method getName() (and setName(String name)). Then I create a public class B that extends A. in my code I can retrieve B from the database: B b = session.load(B.class, new Integer(1), LockMode.NONE); I receive b with all the values set correctly (So at this point, Hibernate was able to use the method setName() correctly). In my code if I then try to use b.getName(), I receive and error: java.lang.IllegalAccessException-->Class org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer can not access a member of class A with modifiers "public" But I am not trying to access A.getName(), but B.getName() (which is a public method in a public class). This was working perfectly with Hibernate 2.1.7c and 3.1.3. The full information about my problem can be found here: http://forum.hibernate.org/viewtopic.php?t=969453 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-330) NegativeArraySizeException if you use FullTextQuery.setMaxResults(Integer.MAX_VALUE)

by Hardy Ferentschik (JIRA)

NegativeArraySizeException if you use FullTextQuery.setMaxResults(Integer.MAX_VALUE) ------------------------------------------------------------------------------------ Key: HSEARCH-330 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-330 Project: Hibernate Search Issue Type: Bug Reporter: Hardy Ferentschik Seems to be a Lucene bug, but maybe we should add a work around? http://forum.hibernate.org/viewtopic.php?p=2401667 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2745) NullPointerException when eager fetching joined many-to-many with native SQL query

by Mihail Fridliand (JIRA)

NullPointerException when eager fetching joined many-to-many with native SQL query ---------------------------------------------------------------------------------- Key: HHH-2745 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2745 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.1 Environment: Hibernate 3.2.1, DB2 Reporter: Mihail Fridliand NullPointerException when joining many-to-many assoziation with native SQL query: java.lang.NullPointerException at org.hibernate.loader.custom.sql.SQLQueryParser.resolveProperties(SQLQueryParser.java:182) at org.hibernate.loader.custom.sql.SQLQueryParser.resolveCollectionProperties(SQLQueryParser.java:135) at org.hibernate.loader.custom.sql.SQLQueryParser.substituteBrackets(SQLQueryParser.java:98) at org.hibernate.loader.custom.sql.SQLQueryParser.process(SQLQueryParser.java:51) at org.hibernate.loader.custom.sql.SQLCustomQuery.<init>(SQLCustomQuery.java:110) at org.hibernate.engine.query.NativeSQLQueryPlan.<init>(NativeSQLQueryPlan.java:43) at org.hibernate.engine.query.QueryPlanCache.getNativeSQLQueryPlan(QueryPlanCache.java:114) at org.hibernate.impl.SessionFactoryImpl.checkNamedQueries(SessionFactoryImpl.java:444) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:351) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1291) The SQLQueryReturnProcessor ignores many-to-many assoziations: private void addCollection(String role, String alias, Map propertyResults) { SQLLoadableCollection collectionPersister = ( SQLLoadableCollection ) factory.getCollectionPersister( role ); alias2CollectionPersister.put( alias, collectionPersister ); String suffix = generateCollectionSuffix(); log.trace( "mapping alias [" + alias + "] to collection-suffix [" + suffix + "]" ); alias2CollectionSuffix.put( alias, suffix ); collectionPropertyResultMaps.put( alias, propertyResults ); if ( collectionPersister.isOneToMany() ) { SQLLoadable persister = ( SQLLoadable ) collectionPersister.getElementPersister(); addPersister( alias, filter( propertyResults ), persister ); } } Mapping of a many-to-many: <hibernate-mapping> <class name="A" table="A" schema="TEST" > <set name="manyToMany" inverse="true" table="AC" > <key> <column name="A_OID" not-null="true" /> </key> <many-to-many class="C"> <column name="C_OID" not-null="true" /> </many-to-many> </set> </class> <class name="C" table="C" schema="TEST"> </class> <resultset name="AandC"> <return alias="a" class="A"/> <return-join alias="c" property="a.manyToMany"/> </resultset> <sql-query name="getAandC" resultset-ref="AandC" > <![CDATA[ select DISTINCT {a.*},{c.*} from A a join AC ac on a.OID = ac.A_OID join C c on c.C_OID=ac.C_OID ]]> </sql-query> </hibernate-mapping> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2276) Can not get N first results of query with DB2 dialect (neither with setMaxResults nor with setFetchSize)

by Fred (JIRA)

Can not get N first results of query with DB2 dialect (neither with setMaxResults nor with setFetchSize) -------------------------------------------------------------------------------------------------------- Key: HHH-2276 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2276 Project: Hibernate3 Type: Bug Components: query-criteria Versions: 3.1.2 Environment: DB2 V7 version = DSN07012 DB OS = zOS IBM DB2 JDBC Universal Driver Architecture Version du pilote JDBC : 2.1.34 Using dialect: org.hibernate.dialect.DB2Dialect Reporter: Fred I can't get the N first records from a select request using the setMaxResults method. HB generates a request that can not be understood by DB2 (select * from ( select rownumber() over() as rownumber etc.... see first stacktrace below) Moreover, using setFetchSize does not work (see second stack trace below the first one). Is there a way to tell HB to append " fetch first 10 rows only" to the query (as a workaround) ? Because my DB2 can understand that one : select * from MYTABLE where numseq = '2' fetch first 10 rows only thanks ! Fred STACK WITH SETMAXRESULTS : Hibernate: select * from ( select rownumber() over() as rownumber_, * from A165D.TB3PARCV where TVOY='D' ) as temp_ where rownumber_ <= ? [01/12/06 12:03:17:516 CET] 2d68c035 SystemOut O 12:03:17,516 67422 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -104, SQLState: 42601 12:03:17,516 67422 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -104, SQLState: 42601 12:03:17,516 67422 ERROR JDBCExceptionReporter (logExceptions, 72 ) - ILLEGAL SYMBOL "(". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: , FROM INTO 12:03:17,516 67422 ERROR JDBCExceptionReporter (logExceptions, 72 ) - ILLEGAL SYMBOL "(". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: , FROM INTO 12:03:17,516 67422 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -516, SQLState: 26501 12:03:17,516 67422 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -516, SQLState: 26501 12:03:17,547 67453 ERROR JDBCExceptionReporter (logExceptions, 72 ) - THE DESCRIBE STATEMENT DOES NOT SPECIFY A PREPARED STATEMENT 12:03:17,547 67453 ERROR JDBCExceptionReporter (logExceptions, 72 ) - THE DESCRIBE STATEMENT DOES NOT SPECIFY A PREPARED STATEMENT 12:03:17,547 67453 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -514, SQLState: 26501 12:03:17,547 67453 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -514, SQLState: 26501 12:03:17,578 67484 ERROR JDBCExceptionReporter (logExceptions, 72 ) - THE CURSOR SQL_CURLN300C4 IS NOT IN A PREPARED STATE 12:03:17,578 67484 ERROR JDBCExceptionReporter (logExceptions, 72 ) - THE CURSOR SQL_CURLN300C4 IS NOT IN A PREPARED STATE 12:03:17,578 67484 ERROR WAction (execute, 56 ) - org.hibernate.exception.SQLGrammarException: could not execute query org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:65) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2153) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029) at org.hibernate.loader.Loader.list(Loader.java:2024) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:117) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1607) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:121) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:169) [...] Caused by: com.ibm.db2.jcc.a.SqlException: ILLEGAL SYMBOL "(". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: , FROM INTO at com.ibm.db2.jcc.a.cy.e(cy.java:1507) at com.ibm.db2.jcc.a.cy.a(cy.java:1117) at com.ibm.db2.jcc.a.cy.a(cy.java:1103) at com.ibm.db2.jcc.b.bd.h(bd.java:131) at com.ibm.db2.jcc.b.bd.a(bd.java:42) at com.ibm.db2.jcc.b.r.a(r.java:31) at com.ibm.db2.jcc.b.bs.g(bs.java:149) at com.ibm.db2.jcc.a.cy.l(cy.java:1097) at com.ibm.db2.jcc.a.cz.bb(cz.java:1554) at com.ibm.db2.jcc.a.cz.d(cz.java:1986) at com.ibm.db2.jcc.a.cz.S(cz.java:424) at com.ibm.db2.jcc.a.cz.executeQuery(cz.java:407) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(WSJdbcPreparedStatement.java:426) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:139) at org.hibernate.loader.Loader.getResultSet(Loader.java:1669) at org.hibernate.loader.Loader.doQuery(Loader.java:662) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2150) ... 52 more _____________________________________________________________________________________________________ STACK WITH SETFETCHSIZE() : [01/12/06 12:20:57:250 CET] 28ea8033 SystemOut O 11:20:57,250 403719 ERROR WAction (execute, 56 ) - org.hibernate.MappingException: No Dialect mapping for JDBC type: 3 org.hibernate.MappingException: No Dialect mapping for JDBC type: 3 at org.hibernate.dialect.TypeNames.get(TypeNames.java:56) at org.hibernate.dialect.TypeNames.get(TypeNames.java:81) at org.hibernate.dialect.Dialect.getHibernateTypeName(Dialect.java:192) at org.hibernate.loader.custom.CustomLoader.getHibernateType(CustomLoader.java:170) at org.hibernate.loader.custom.CustomLoader.autoDiscoverTypes(CustomLoader.java:138) at org.hibernate.loader.Loader.getResultSet(Loader.java:1678) at org.hibernate.loader.Loader.doQuery(Loader.java:662) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2150) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029) at org.hibernate.loader.Loader.list(Loader.java:2024) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:117) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1607) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:121) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:169) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3044) Dialect.getSchemaSeparator() defined as char whereas sybase uses '..' as schema delimiter

by Alexis Haumont (JIRA)

Dialect.getSchemaSeparator() defined as char whereas sybase uses '..' as schema delimiter ----------------------------------------------------------------------------------------- Key: HHH-3044 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3044 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.0.5 Environment: Hibernate 3.0.5 used with Sybase ASE 12.5.4 Reporter: Alexis Haumont With Sybase ASE, the naming pattern for schema indexes objects is : schema..tableName But the abstract class org.hibernate.dialect.Dialect has the following method signature : /** * The separator between the schema/catalog/tablespace name and the table name. */ public char getSchemaSeparator() { return '.'; } It should be : public String getSchemaSeparator() { return "."; } and as such could ne overriden in SybaseDialect as : public String getSchemaSeparator() { return ".."; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2877) native query (createSQL) cannot map the JDBC type text

by Bas van den Berg (JIRA)

native query (createSQL) cannot map the JDBC type text ------------------------------------------------------- Key: HHH-2877 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2877 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: MySQL 5.0.45, InnoDB Schema. Hibernate 3.2.5, Hibernate Annotations 3.3.0 Reporter: Bas van den Berg Priority: Minor When you invoke a SQLQuery in which a column of JDBC type text is queried an exception is thrown: org.hibernate.MappingException: No Dialect mapping for JDBC type: -1 see topic http://forum.hibernate.org/viewtopic.php?p=2366178#2366178 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2707) supports on-delete set-null (like in MySql 5)

by Emmanuel Bernard (JIRA)

supports on-delete set-null (like in MySql 5) --------------------------------------------- Key: HHH-2707 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2707 Project: Hibernate3 Issue Type: New Feature Components: core 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

17 years

4
5
0 / 0

[Hibernate-JIRA] Created: (ANN-598) Add ON clause to @ForeignKey

by Christian Bauer (JIRA)

Add ON clause to @ForeignKey ---------------------------- Key: ANN-598 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598 Project: Hibernate Annotations Issue Type: New Feature Components: binder Reporter: Christian Bauer More important than it sounds: @org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID") I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via: <hibernate-mapping> <database-object> <create> alter table FEED drop constraint FK_FEED_DIRECTORY_ID; alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key (DIRECTORY_ID) references NODE on delete cascade; </create> <drop></drop> </database-object> </hibernate-mapping> This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an option - I don't want to hardcode my HSQL datatypes. So we should accept a parameter on @ForeignKey (I know that the Hibernate binder doesn't have that notion at all, we need it in native Hibernate as well) that accepts "[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right thing during schema export. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3662) Merging read-only entities causes AssertionError("Merged entity does not have status set to MANAGED...")

by jpk (JIRA)

Merging read-only entities causes AssertionError("Merged entity does not have status set to MANAGED...") -------------------------------------------------------------------------------------------------------- Key: HHH-3662 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3662 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: Windows XP Reporter: jpk What worked for me in 3.2.6 now doesn't: merging read-only entities. The following error now occurs when attempting to merge an entity: org.hibernate.AssertionFailure: Merged entity does not have status set to MANAGED; EntityEntry[com.tll.model.impl.AccountHistory#71794688](READ_ONLY) status=READ_ONLY Note this entity class of mine has the @Immutable annotation and removing it prevents this AssertionError from occurring. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2766) many-to-one with property-ref run into an recursive issue

by René Fuchs (JIRA)

many-to-one with property-ref run into an recursive issue --------------------------------------------------------- Key: HHH-2766 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2766 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Informix 10 Reporter: René Fuchs With many-to-one and property-ref, hibernate resolve always the whole referenced entity. So we have alway an eager issue. If the resolved entity includes one or more other references to non primary keys, these entities will be also resolved and so on. In a big legacy database, if I read only one entity, I get 100 selects or a very very long joined sql (fetch="join"). I think the problem ist located in: org.hibernate.type.EntityType public Object resolve(Object obj, SessionImplementor sessionimplementor, Object obj1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3677) g

by pioneer (JIRA)

g - Key: HHH-3677 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3677 Project: Hibernate Core Issue Type: Sub-task Reporter: pioneer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-310) Out of Mem on Sorted ScrollableResults

by Sanne Grinovero (JIRA)

Out of Mem on Sorted ScrollableResults -------------------------------------- Key: HSEARCH-310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-310 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.0.1.GA Environment: Java SE, 3.0.1.GA Reporter: Sanne Grinovero Fix For: 3.1.0 http://forum.hibernate.org/viewtopic.php?p=2400452 I think this is more appropriate for 3.1.1 Emmanuel said: "The implementation suffers several flows: - we do create an EntityInfo[] as big as the number of hits - we lazily load this array but we never release "old content" - we lazily load the content (ie objects) by window but we never release it Some Soft reference based cache can help." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2882) QueryKey.equals() returning false with distributed caching

by Daniel Campagnoli (JIRA)

QueryKey.equals() returning false with distributed caching ---------------------------------------------------------- Key: HHH-2882 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2882 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.5 Reporter: Daniel Campagnoli We noticed some issues recently with the query cache when using Coherence as the cache provider. This was due to instances of org.hibernate.cache.QueryKey not being equal after being serialized then deserialized. The equals check was failing on the [ResultTransformer customTransformer] field which in our case had an instance of RootEntityResultTransformer (which comes from the field CriteriaSpecification.ROOT_ENTITY). This is because RootEntityResultTransformer doesnt override equals, so the check is done by reference equality. When the QueryKey has been serialized and deserialized out of the cache, the instance will always be different, so the equals check will fail. A fix for this to be implement equals for RootEntityResultTransformer (and possibly the other ResultTransformer's). I used the following which worked fine. public boolean equals(Object obj) { return obj != null && this.getClass() == obj.getClass(); } ps. I created HHH-1665 a while ago, a real simple fix, could that be looked at :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3035) could not read column value from result set: MEDFAC1_14_0_; Invalid column name SQL Error: 17006, SQLState: null

by sanjeev singh (JIRA)

could not read column value from result set: MEDFAC1_14_0_; Invalid column name SQL Error: 17006, SQLState: null ---------------------------------------------------------------------------------------------------------------- Key: HHH-3035 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3035 Project: Hibernate3 Issue Type: Bug Components: core, query-criteria, query-hql, query-sql Affects Versions: 3.2.2 Environment: JDK5 , Hibernate Junit Test case,WIndows XP Reporter: sanjeev singh The following is my section of hibernate mapping file. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping package="gov.njdhss.hippocrates.ems.valueobjects"> <class name="HeprEmsMedfacFacilityVO" table="HEPR_MEDFAC"> <id name="medfacId" column="MEDFAC_ID" type="java.lang.Long"> <generator class="sequence"> <param name="sequence">HEPR_MEDFAC_SEQ</param> </generator> </id> <property name="medfacName" type="java.lang.String" column="MEDFAC_NAME" update="true" insert="true"> </property> <property name="facCode" type="java.lang.String" column="FAC_CODE" update="true" insert="true"> </property> </class> <sql-query name="allfacility"> <return alias="facilities" class="HeprEmsMedfacFacilityVO" > <return-property name="medfacName" column="MEDFAC_NAME"/> </return> <![CDATA[ select facilities.MEDFAC_NAME AS medfacName from HEPR_MEDFAC facilities ]]> </sql-query> </hibernate-mapping> I am trying to execute the query using the following client code: public List getAllFacility() { List listAllFacilities = null; listAllFacilities = getHibernateTemplate().findByNamedQuery( "allfacility"); return listAllFacilities; } The following is the error: Hibernate: select facilities.MEDFAC_NAME AS medfacName from HEPR_MEDFAC facilities - could not read column value from result set: MEDFAC1_14_0_; Invalid column name - SQL Error: 17006, SQLState: null - Invalid column name - Loading XML bean definitions from class path resource [org/springframework/jdbc/support/sql-error-codes.xml] - SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase] Any idea if it is a bug or there is any error in my 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

17 years

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-554) NPE with @Id on @OneToOne

by Loïc Minier (JIRA)

NPE with @Id on @OneToOne ------------------------- Key: ANN-554 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-554 Project: Hibernate Annotations Type: Bug Versions: 3.2.1 Environment: Hibernate 3.2.2 GA, Hibernate Annotations 3.2.1, J2SE 1.6.0-b105 on Debian GNU/Linux sid, PostgreSQL 7.4 Reporter: Loïc Minier Priority: Minor Hi, (Note: I originally reported this on the forum, but the lack of response suggests this might be a bug in Hibernate Annotations or Hibernate; the forum topic is at: http://forum.hibernate.org/viewtopic.php?t=970823) I hope it's not a misuse of Hibernate, but I'm trying to use @Id on @OneToOne, and this causes the following NPE when running hbm2ddl: java.lang.NullPointerException at org.hibernate.util.StringHelper.qualify(StringHelper.java:264) at org.hibernate.cfg.OneToOneSecondPass.doSecondPass(OneToOneSecondPass.java:196) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1130) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:296) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.tool.ant.ConfigurationTask.getConfiguration(ConfigurationTask.java:56) at org.hibernate.tool.ant.HibernateToolTask.getConfiguration(HibernateToolTask.java:287) at org.hibernate.tool.ant.Hbm2DDLExporterTask.execute(Hbm2DDLExporterTask.java:45) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:171) 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.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) What I'm trying to do at the application level is: Foo class and table long foo_id, primary key FooData fooData, nulllable=true FooData class and table foo_id references Foo(foo_id), nullable=false This is expressed in Java as: @Entity @Table(name = "foo") public class Foo { @Id @GeneratedValue @Column(name = "foo_id") Long id; @OneToOne(mappedBy = "foo", cascade = CascadeType.ALL) FooData fooData; ... @Entity @Table(name = "foo_data") public class FooData { @Id @OneToOne @JoinColumn(name = "foo_id", nullable = false) Foo foo; This causes a NPE here. If I use a real Id on FooData, e.g.: @Id @Column(name = "foo_data_id") Long id; it works, and I end up with: - foo_id in table foo as a primary key - foo_data_id in table foo_data as a primary key - foo_id in table foo_data not null - foo_id in table foo_data references foo_id in table foo I don't want a foo_data_id, I don't need it, hence the lack of it which leads to the NPE. Bye, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2669) Unequivocally map MySQL LOB types to the LONG variant

by Steve Ebersole (JIRA)

Unequivocally map MySQL LOB types to the LONG variant ----------------------------------------------------- Key: HHH-2669 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2669 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 MySQL differentiates different "sizes" of LOBs. Apparently, the smaller types offer no storage benefit nor performance gain. So we should consider mapping the LOB types in the MySQL dialect to the LON variants in all cases. The current setup causes truncation headaches for users, apparently unnecessarily. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
5
0 / 0

[Hibernate-JIRA] Created: (HBX-1032) HibernateConsoleRuntimeException: "Could not load JPA Configuration" for JavaSE JPA project

by Donatas Ciuksys (JIRA)

HibernateConsoleRuntimeException: "Could not load JPA Configuration" for JavaSE JPA project ------------------------------------------------------------------------------------------- Key: HBX-1032 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1032 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.0.GA Environment: Eclipse 3.3.1.1, HibernateTools 3.2.0 GA, JDK 1.6.0_03 Reporter: Donatas Ciuksys Priority: Blocker I have Java SE (not EE) project in Eclipse with standard structure like: /src /META-INF/persistence.xml /bin ... I try to create new Hibernate Configuration in "Hibernate Configurations" pannel. I choose project, select JPA (jdk 1.5+) option, fill in persistence unit "InventorizacijaPU", check whether Classpath tab is OK (it contains my project). Press OK. Trying to expand configuration created, I get this exception: org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:142) at org.hibernate.console.ConsoleConfiguration.buildConfiguration(ConsoleConfiguration.java:496) at org.hibernate.console.ConsoleConfiguration.access$0(ConsoleConfiguration.java:484) at org.hibernate.console.ConsoleConfiguration$2.execute(ConsoleConfiguration.java:203) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:65) at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:185) at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:106) at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:38) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:97) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:103) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:196) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.hibernate.console.HibernateConsoleRuntimeException: Persistence unit not found: 'InventorizacijaPU'. at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:134) ... 11 more This is my persistence.xml: <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="InventorizacijaPU" transaction-type="RESOURCE_LOCAL"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <class>lt.mitsoft.inventorizacija.domain.BuvimoVieta</class> <class>lt.mitsoft.inventorizacija.domain.Inventorizacija</class> <class>lt.mitsoft.inventorizacija.domain.Irasas</class> <class>lt.mitsoft.inventorizacija.domain.IrasuBlokas</class> <class>lt.mitsoft.inventorizacija.domain.Preke</class> <class>lt.mitsoft.inventorizacija.domain.Skanuotojas</class> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.DerbyDialect" />  <property name="hibernate.connection.url" value="jdbc:derby://localhost:1527/InventorizacijaDB" />  <property name="hibernate.connection.driver_class" value="org.apache.derby.jdbc.ClientDriver" /> <property name="hibernate.connection.username" value="admin" /> <property name="hibernate.connection.password" value="admin" /> <property name="hibernate.cache.provider_class" value="org.hibernate.cache.NoCacheProvider" />  </properties> </persistence-unit> </persistence> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
10
0 / 0

[Hibernate-JIRA] Created: (EJB-403) QueryTest - Native Query for Update using alias causes failure

by Juraci Paixao Krohling (JIRA)

QueryTest - Native Query for Update using alias causes failure -------------------------------------------------------------- Key: EJB-403 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-403 Project: Hibernate Entity Manager Issue Type: Patch Components: EntityManager Environment: PostgreSQL 8.2.3 and Entity Manager Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: QueryTest.diff Even though it says in documentation that it supports table aliases in "update" clauses[1], the below test fails when using it. Removing the table alias is enough to make it successful. org.hibernate.ejb.test.QueryTest#testUpdateQuery [1] http://www.postgresql.org/docs/8.2/interactive/sql-update.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
13
0 / 0

[Hibernate-JIRA] Created: (ANN-779) Test EmbeddedGenericsTest generates a table name "too long" for DB2

by Juraci Paixao Krohling (JIRA)

Test EmbeddedGenericsTest generates a table name "too long" for DB2 ------------------------------------------------------------------- Key: ANN-779 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-779 Project: Hibernate Annotations Issue Type: Bug Environment: Annotations Trunk / DB2 v9.1 Reporter: Juraci Paixao Krohling Annotations test EmbeddedGenericsTest#testWorksWithGenericCollectionOfElements generates the table name "EmbeddedGenericsTest$PopularBook_editions", but DB2 complains about its lengh: DB2 SQL error: SQLCODE: -107, SQLSTATE: 42622, SQLERRMC: EMBEDDEDGENERICSTEST$POPULARBOOK_ID;30 This error message says that the name exceeds the 30 characters limit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3554) Investigate how bulk updates can be supported

by Adam Warski (JIRA)

Investigate how bulk updates can be supported --------------------------------------------- Key: HHH-3554 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3554 Project: Hibernate Core Issue Type: Task Components: envers Reporter: Adam Warski -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2317) CGLIB unable to lazy load classes in diff. classloader than hibernate jars

by Jason Novotny (JIRA)

CGLIB unable to lazy load classes in diff. classloader than hibernate jars --------------------------------------------------------------------------- Key: HHH-2317 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2317 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Reporter: Jason Novotny Please see http://forum.hibernate.org/viewtopic.php?p=2334617#2334617 for more details and possible fix -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3229) Make cascade rules more transparent/explicit/deterministic

by Chris Bredesen (JIRA)

Make cascade rules more transparent/explicit/deterministic ---------------------------------------------------------- Key: HHH-3229 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3229 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6, 3.2.5, 3.2.4.sp1 Reporter: Chris Bredesen Cascade rules are prone to different behavior based on the order in which properties appear in mapping XML. It is possible that an unexpected TransientObjectException may arise from certain operations when an object graph with circular references is merged (and possibly persisted/updated, etc). For example, if a transient instance is reachable through more than once path from a root entity, it is not clear whether operations will be cascaded to it. The order in which the properties are mapped plays a part in determining cascade paths, but the rules are not documented. Possible resolutions include: 1. Documenting the rules so that a programmer can make educated decisions about mapping. 2. Enhancing the algorithm such that order no longer matters and the rules are deterministic. 3. ??? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

6
12
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-329) Workers ThreadPools breaks ThreadLocals

by Grégoire Rolland (JIRA)

Workers ThreadPools breaks ThreadLocals --------------------------------------- Key: HSEARCH-329 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-329 Project: Hibernate Search Issue Type: Bug Components: directory provider Affects Versions: 3.1.0.GA Reporter: Grégoire Rolland When Implementing multi-domains (multi-databases) FSDirectory based on thread local (to get the thread environment, database name, etc...), the threadpool used by workers "forgot" the thread local variables on the second call (for searching, indexing). Works great with 3.0.1 release, but not with 3.1.0.GA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3095) Invalid queries when using subclasses and one-to-many associations

by Sebastien Blind (JIRA)

Invalid queries when using subclasses and one-to-many associations ------------------------------------------------------------------ Key: HHH-3095 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3095 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, bug identified on sybase Reporter: Sebastien Blind Priority: Blocker Attachments: src-cat.zip This bug report builds on top of the topic found in the forum at http://forum.hibernate.org/viewtopic.php?t=977453 Basically, there seems to be an issue in the way hibernate treats a collections of objects that extend a base class. The attached example has: a Cat class a DomesticCat class (extends Cat) a Cage class (can contain multiple DomesticCat) The generated SQL is below - the filter cats0_.CAGE_ID=? should really be cats0_1_.CAGE_ID=? select cats0_.CAGE_ID as CAGE3_1_, cats0_.CAT_ID as CAT1_1_, cats0_.CAT_ID as CAT1_0_0_, cats0_1_.CAGE_ID as CAGE2_2_0_ from CAT cats0_ inner join DCAT cats0_1_ on cats0_.CAT_ID=cats0_1_.CAT_ID where cats0_.CAGE_ID=? As of now, I am not aware of any configuration that would work around this problem. Please let me know if you know otherwise. Thanks, Sebastien -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-790) ImmutableTest leaves an active transaction

by Juraci Paixao Krohling (JIRA)

ImmutableTest leaves an active transaction ------------------------------------------ Key: ANN-790 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-790 Project: Hibernate Annotations Issue Type: Patch Environment: PostgreSQL 8.2.3 and Annotations from trunk Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: ImmutableTest.java.diff ImmutableTest leaves an active transaction and makes PostgreSQL waits until it is finished (which never occurs). The attached patch fixes it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
3
0 / 0

[Hibernate-JIRA] Created: (HBX-779) jdbc reengineer sql-type problem with oracle 9i

by jacky hua (JIRA)

jdbc reengineer sql-type problem with oracle 9i ----------------------------------------------- Key: HBX-779 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-779 Project: Hibernate Tools Type: Bug Components: reverse-engineer Versions: 3.2beta8 Environment: windowsxp sp2, jdk 1.4.2, eclipse 3.1.2 Reporter: jacky hua I used the ant task hibernate-tools provided like the below to generate hbms xml <target name="default" description="generate hbm"> <delete dir="./generate"/> <mkdir dir="./generate"/> <hibernatetool destdir="./generate"> <jdbcconfiguration configurationfile="./metadata/hibernate.cfg.xml" revengfile="./metadata/hibernate.reveng.xml" packagename="net.ema.examples.sa" detectmanytomany="true" detectoptimisticlock="true"> </jdbcconfiguration> <hbm2hbmxml destdir="./generate" /> </hibernatetool> </target> the ./metadata/hibernate.cfg.xml like the below: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-reverse-engineering SYSTEM "http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" > <hibernate-reverse-engineering> <schema-selection match-catalog="TITAN" match-schema="TITAN" /> <type-mapping>   <sql-type jdbc-type="NUMERIC" precision="1" hibernate-type="boolean" />  <sql-type jdbc-type="NUMERIC" precision="19" hibernate-type="long" /> <sql-type jdbc-type="TIMESTAMP" hibernate-type="java.util.Date" /> </type-mapping>  <table-filter match-name="BIN$.*" exclude="true" /> </hibernate-reverse-engineering> But the <sql-type jdbc-type="NUMERIC" precision="19" hibernate-type="long" /> didn't work, also generate big_decimal type not long type, otherwise the others two sql-type rules worked. the not affected column:USER_ID was pk of my table. the generated hbm file is like the below: <class name="net.ema.examples.sa.UserModel" table="T_SA_USER" schema="TITAN"> <id name="userId" type="big_decimal"> <column name="USER_ID" scale="0" /> <generator class="assigned" /> </id> <property name="logonName" type="string"> <column name="LOGON_NAME" length="60" /> </property> <property name="password" type="string"> <column name="PASSWORD" length="80" /> </property> <property name="isOrgAdmin" type="java.lang.Boolean"> <column name="IS_ORG_ADMIN" precision="1" scale="0" /> </property> <property name="remark" type="string"> <column name="REMARK" length="400" /> </property> <property name="createDate" type="java.util.Date"> <column name="CREATE_DATE" length="11" /> </property> <property name="status" type="string"> <column name="STATUS" length="2" /> </property> </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

17 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3620) Oracle - testWithClause fails due to "Missing IN or OUT parameter at index:: 1"

by Juraci Paixao Krohling (JIRA)

Oracle - testWithClause fails due to "Missing IN or OUT parameter at index:: 1" ------------------------------------------------------------------------------- Key: HHH-3620 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3620 Project: Hibernate Core Issue Type: Bug Components: testsuite Affects Versions: 3.3.x Environment: Oracle 9i, Branch_3_3 Reporter: Juraci Paixao Krohling Test testWithClause (org.hibernate.test.hql.WithClauseTest) fails due to "Missing IN or OUT parameter at index:: 1" Stack trace: 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.hql.QueryLoader.list(QueryLoader.java:401) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:364) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1149) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102) at org.hibernate.test.hql.WithClauseTest.testWithClause(WithClauseTest.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:168) at org.hibernate.junit.functional.FunctionalTestCase.runTest(FunctionalTestCase.java:125) at junit.framework.TestCase.runBare(TestCase.java:134) at org.hibernate.junit.UnitTestCase.runBare(UnitTestCase.java:63) 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 org.hibernate.junit.functional.FunctionalTestClassTestSuite.runTest(FunctionalTestClassTestSuite.java:115) at junit.framework.TestSuite.run(TestSuite.java:227) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.run(FunctionalTestClassTestSuite.java:84) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:76) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) 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: java.sql.SQLException: Missing IN or OUT parameter at index:: 1 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146) at oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:1711) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3311) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3361) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1808) at org.hibernate.loader.Loader.doQuery(Loader.java:697) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) ... 31 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
6
0 / 0

[Hibernate-JIRA] Created: (EJB-381) EntityManager doesn't care about INSERT trigger of Oracle XE

by Juergen Zimmermann (JIRA)

EntityManager doesn't care about INSERT trigger of Oracle XE ------------------------------------------------------------ Key: EJB-381 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-381 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate EM 3.4.0, Hibernate Annotations 3.4.0, Hibernate Commons Annotations 3.1.0, Hibernate 3.3.0.SP1, Hibernate Validator 3.1.0.CR2, JDK 1.6.0_07 Reporter: Juergen Zimmermann I have an abstract entity class with 2 derived concrete classes: @Entity @Table(name="kunde") @Inheritance @DiscriminatorColumn(name="art", length=1) @XmlRootElement @XmlSeeAlso({ Firmenkunde.class, Privatkunde.class }) @XmlAccessorType(XmlAccessType.FIELD) public abstract class Kunde implements java.io.Serializable { @Id @GeneratedValue(generator="kunde_sequence_name") @SequenceGenerator(name="kunde_sequence_name", sequenceName="kunde_k_id_seq", allocationSize=1) @Column(name="k_id", nullable=false) @XmlAttribute(name="id", required=true) protected Long id = KEINE_ID; @Version @XmlTransient protected int version = ERSTE_VERSION; @Column(length=32, nullable=false) @XmlElement(required=true) protected String nachname = ""; ... @Column(length=32, unique=true) protected String username = ""; ... } The table is created as follows: CREATE TABLE kunde( k_id NUMBER(16) NOT NULL PRIMARY KEY, version NUMBER(8) DEFAULT 0, nachname VARCHAR2(32) NOT NULL, ... art VARCHAR2(2) DEFAULT 'P', ... username VARCHAR2(32) NOT NULL UNIQUE, ... ); Additionally there is this sequence and insert trigger for column username. CREATE SEQUENCE kunde_k_id_seq START WITH 200 NOMAXVALUE / CREATE OR REPLACE TRIGGER kunde_trigger_insert BEFORE INSERT ON kunde FOR EACH ROW BEGIN :NEW.username := TO_CHAR(:NEW.k_id); END; / New objects are inserted into the database using this code which works fine with PostgreSQL. However, using Oracle XE the insert trigger isn't considered: public List<Kunde> insertKunden(List<Kunde> kunden) { if (kunden == null || kunden.isEmpty()) { return new ArrayList<Kunde>(0); } for (Kunde k: kunden) { em.persist(k); } return kunden; } The attribute "username" is null using Oracle XE, but using PostgreSQL it has the value produced by the INSERT trigger. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-404) QueryTest - PostgreSQL - "ERROR: operator does not exist: character varying = bytea"

by Juraci Paixao Krohling (JIRA)

QueryTest - PostgreSQL - "ERROR: operator does not exist: character varying = bytea" ------------------------------------------------------------------------------------ Key: EJB-404 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-404 Project: Hibernate Entity Manager Issue Type: Patch Components: EntityManager Environment: PostgreSQL and Entity Manager Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: QueryTest_2.diff Test org.hibernate.ejb.test.QueryTest#testIsNull fails due to this query: select i from Item i where (i.descr is null and :descr is null) or i.descr = :descr When changing the query to what it reads below, it works properly: select i from Item i where i.descr = :descr or (i.descr is null and :descr is null) As this happened only with PostgreSQL, I assume this is an issue with either the driver or with the database itself. Will dig into pgsql's site to find out more about this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
8
0 / 0

[Hibernate-JIRA] Created: (EJB-407) Some tests are not closing the EM or finishing transactions

by Juraci Paixao Krohling (JIRA)

Some tests are not closing the EM or finishing transactions ----------------------------------------------------------- Key: EJB-407 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-407 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: UnclosedEM-UnfinishedTransactions.diff The below tests are not closing the EM or not finishing transactions (committing/rolling back), causing the test to hang indefinitely when the EM tries to drop the database entities after the test finishes: org/hibernate/ejb/test/callbacks/CallbacksTest.java org/hibernate/ejb/test/emops/FlushTest.java org/hibernate/ejb/test/lock/LockTest.java org/hibernate/ejb/test/exception/ExceptionTest.java org/hibernate/ejb/test/transaction/FlushAndTransactionTest.java The attached patch closes the EM and/or rolls back the unfinished transaction. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
5
0 / 0

[Hibernate-JIRA] Created: (EJB-337) Entity scaning failing when path protocol is "file:" (not jar) and it contains spaces

by valery gorbunov (JIRA)

Entity scaning failing when path protocol is "file:" (not jar) and it contains spaces ------------------------------------------------------------------------------------- Key: EJB-337 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-337 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA Environment: OS Linux Hibernate 3.2.5ga HiberanteEM -3.3.1ga Reporter: valery gorbunov Priority: Critical Entity scanning failed when path contains spaces Stack trace is: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:74) at org.jboss.util.file.FileProtocolArchiveBrowserFactory.create(FileProtocolArchiveBrowserFactory.java:48) at org.jboss.util.file.FileProtocolArchiveBrowserFactoryTest.testCreate(FileProtocolArchiveBrowserFactoryTest.java:29) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) 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: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:114) at java.util.jar.JarFile.<init>(JarFile.java:133) at java.util.jar.JarFile.<init>(JarFile.java:97) at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:69) ... 24 more Problem in FileProtocolArchiveBrowserFactory class see test: package org.jboss.util.file; import static org.junit.Assert.assertNotNull; import static org.junit.Assert.assertTrue; import java.io.File; import java.net.MalformedURLException; import java.net.URI; import java.net.URISyntaxException; import junit.framework.Assert; import org.junit.Test; /** * * @author Valery Gorbunov <a href=mailto:vgorbunov@comodo.com.ua>vgorbunov(a)comodo.com.ua</a> */ public class FileProtocolArchiveBrowserFactoryTest { @Test public void testCreate() throws MalformedURLException, URISyntaxException { URI uri = new URI("file:/tmp/Path%20with%20space"); File f = new File(uri); if (!f.exists()) { Assert.assertTrue(f.mkdir()); } FileProtocolArchiveBrowserFactory factory = new FileProtocolArchiveBrowserFactory(); Object ab = factory.create(f.toURI().toURL(), null); assertNotNull(ab); assertTrue(ab instanceof DirectoryArchiveBrowser); } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2782) Component getType caches the type value

by Kiss Zoltán (JIRA)

Component getType caches the type value --------------------------------------- Key: HHH-2782 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2782 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: all Reporter: Kiss Zoltán Component class caches the value of the type attribute: public Type getType() throws MappingException { // added this caching as I noticed that getType() is being called multiple times... if ( type == null ) { type = buildType(); } return type; } This forbids the use of 'dynamic attributes'. For eg. if you try to add new properties to an existing dynamic-component with the addProperty method, then the rebuild of the session factory will failed, because the Component property will be invalid during the validation (in the Component there will be a different column span value, then in the cached ComponentType). There should be a method like this in the Component class: public void rebuildType() { type = buildType(); } With the help of this the type could be rebuild if it is necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-770) Confusing error when missing default constructor

by Miguel Griffa (JIRA)

Confusing error when missing default constructor ------------------------------------------------ Key: ANN-770 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-770 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Reporter: Miguel Griffa if a persistent class X is missing the default constructor, instead of reporting the missing default constructor in class X, I obtained a noclassdeffound for a class Y, referenced in class X, which was oviously in classpath. this incorrect error message is very misleading in a debug session. if this problem can't be reproduced easily in current test base please indicate so, I'll try to reproduce my environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3128) NullPointerException while building SessionFactory when using native sql query for loading many-to-many mapped collections

by Juergen Denzel (JIRA)

NullPointerException while building SessionFactory when using native sql query for loading many-to-many mapped collections -------------------------------------------------------------------------------------------------------------------------- Key: HHH-3128 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3128 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6, 3.2.5 Environment: Hibernate 3.2.6 Reporter: Juergen Denzel Attachments: src.zip Hi, I am trying to load a many-to-many mapped collection using a sql query like this: <sql-query name="loadItems"> <load-collection alias="item" role="test.Test.items"/> select {item.*} from Items item where item.id = :id </sql-query> This always fails due to a NullPointerException: java.lang.NullPointerException at org.hibernate.loader.custom.sql.SQLQueryParser.resolveProperties(SQLQueryParser.java:182) at org.hibernate.loader.custom.sql.SQLQueryParser.resolveCollectionProperties(SQLQueryParser.java:135) at org.hibernate.loader.custom.sql.SQLQueryParser.substituteBrackets(SQLQueryParser.java:98) at org.hibernate.loader.custom.sql.SQLQueryParser.process(SQLQueryParser.java:51) at org.hibernate.loader.custom.sql.SQLCustomQuery.<init>(SQLCustomQuery.java:110) at org.hibernate.engine.query.NativeSQLQueryPlan.<init>(NativeSQLQueryPlan.java:43) at org.hibernate.engine.query.QueryPlanCache.getNativeSQLQueryPlan(QueryPlanCache.java:114) at org.hibernate.impl.SessionFactoryImpl.checkNamedQueries(SessionFactoryImpl.java:446) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:352) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300) at test.HibernateTest.testSessionFactory(HibernateTest.java:18) I provided a very simple TestCase + Mappings to illustrate the problem. The exception does not occur for one-to-many mappings. Just for your information, we need this functionality in order to deal with DB2 problems we have. I ran this TestCase against 3.2.5 and 3.2.6 and both failed. Thanks. Juergen Denzel -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-374) persistence.xml <jar-file> not following JSR220 spec

by Jeff Ferber (JIRA)

persistence.xml <jar-file> not following JSR220 spec ---------------------------------------------------- Key: EJB-374 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-374 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.CR2 Environment: regression: 3.3.2.GA, 3.4.0.CR2 Reporter: Jeff Ferber JSR220 says <jar-file> is relative to the root of the persistence unit, which is the place containing the META-INF/persistence.xml This is not the case. Instead, it looks for the jar relative to the JVM working directory. (see JarVisitorFactory.java) So providing an absolute file path in <jar-file> works, but not a relative path because the root changes changes based on the situation and environment. E.g., the directory you run ant, when running tomcat, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3148) Exception thrown by debug trace code: ComponentType toLoggableString

by Pete Geraghty (JIRA)

Exception thrown by debug trace code: ComponentType toLoggableString -------------------------------------------------------------------- Key: HHH-3148 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3148 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: Hibernate 3.2.6.ga HibernateAnnotations 3.3.0.ga Oracle 10g Express Edition Reporter: Pete Geraghty Priority: Minor Attachments: ToLoggableStringExample.txt The method toLoggableString in ComponentType is used to provide tracing output when running with log level DEBUG. In some circumstances it throws a ClassCastException. This is not a good idea in tracing code and obscures underlying problems. In my case the underlying problem was a previous incorrect call to set a parameter value in a query. I saw that previous JIRA issues have mentioned this ClassCastException as a side effect of other underlying problems - it is a distraction and time-waster. Lines 375-378 read: EntityMode entityMode = tuplizerMapping.guessEntityMode( value ); if ( entityMode == null ) { throw new ClassCastException( value.getClass().getName() ); } A better solution would be to just us String.valueOf EntityMode entityMode = tuplizerMapping.guessEntityMode( value ); if ( entityMode == null ) { return String.valueOf(value); } Another possibility would be to concatenate some diagnostic message with String.valueOf, but personally I don't think that be helpful. Stack trace is: Exception in thread "main" java.lang.ClassCastException: java.lang.String at org.hibernate.type.ComponentType.toLoggableString(ComponentType.java:377) at org.hibernate.pretty.Printer.toString(Printer.java:76) at org.hibernate.engine.QueryParameters.traceParameters(QueryParameters.java:277) at org.hibernate.engine.query.HQLQueryPlan.performIterate(HQLQueryPlan.java:210) at org.hibernate.impl.SessionImpl.iterate(SessionImpl.java:1192) at org.hibernate.impl.QueryImpl.iterate(QueryImpl.java:46) at hib.example.EntityWithEmbeddable.main(EntityWithEmbeddable.java:44) Example code for the classes and schema to reproduce is pasted into the attachment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

5
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2112) ClassCastException in StatefulPersistenceContext.getCachedDatabaseSnapshot(...)

by Aleksei Valikov (JIRA)

ClassCastException in StatefulPersistenceContext.getCachedDatabaseSnapshot(...) ------------------------------------------------------------------------------- Key: HHH-2112 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2112 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Reporter: Aleksei Valikov StatefulPersistenceContext.getCachedDatabaseSnapshot(EntityKey key) causes ClassCastException when NO_ROW was put for the certain entity key. Please see the discussion here: http://forum.hibernate.org/viewtopic.php?t=959868&highlight=getcacheddata... In these situations, this method should probably return null. It is very likely since other calling methods check for the returned value to be null . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

7
15
0 / 0

[Hibernate-JIRA] Created: (HHH-2703) Investigate integration between Spring and WAS TM

by Steve Ebersole (JIRA)

Investigate integration between Spring and WAS TM ------------------------------------------------- Key: HHH-2703 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2703 Project: Hibernate3 Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 Supposedly as a result of Spring and IBM's blood pact, Spring has tight integration with the WAS TM (not sure how that is possible since IBM continually claims that TM access is unsupported whenever this is asked in relation to Hibernate). Anyway, there may be some stuff we could use here... http://blog.interface21.com/main/2007/06/21/spring-framework-certified-on... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

4
5
0 / 0

[Hibernate-JIRA] Created: (ANN-742) Primary key should not be set on nullable column

by Miroslav Havram (JIRA)

Primary key should not be set on nullable column ------------------------------------------------ Key: ANN-742 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-742 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.1.GA Environment: hibernate core 3.2.6.GA Reporter: Miroslav Havram Attachments: create_scripts.zip, test_case.zip After switching to hibernate-annotations 3.3.1.GA, DDL generated for intermediate table for optional one-to-one association tries to set primary key on nullable column. Problem is that some DBMSs (e.g. MS SQL) do not allow that. Using hibernate-annotations-3.3.0.GA: create table personAddress (address_id bigint not null, person_id bigint not null, primary key (person_id)) Using hibernate-annotations-3.3.1.GA: create table personAddress (person_id bigint, address_id bigint, primary key (person_id)) Simple test case and generated DDLs are attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

5
12
0 / 0

[Hibernate-JIRA] Created: (HHH-2124) HibernateException hidden during flush using XA with WAS6

by Ole Dalgaard (JIRA)

HibernateException hidden during flush using XA with WAS6 --------------------------------------------------------- Key: HHH-2124 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2124 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.2, 3.1.3 Environment: Hibernate 3.1.3 Oracle 10G Websphere Application Server 6 Reporter: Ole Dalgaard In an XA environment, using WebSphereExtendedJTATransactionLookup, HibernateExceptions are hidden during flush in this code in CacheSynchronization.java try { if (flush) { log.trace("automatically flushing session"); ctx.managedFlush(); } } catch (RuntimeException re) { setRollbackOnly(); throw re; } After adding some logging to CacheSynchronization.beforeCompletion I got this error message: org.hibernate.HibernateException: Illegal attempt to associate a collection with two open sessions at org.hibernate.collection.AbstractPersistentCollection.setCurrentSession(AbstractPersistentCollection.java:410) at org.hibernate.event.def.OnUpdateVisitor.processCollection(OnUpdateVisitor.java:40) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java(Compiled Code)) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java(Compiled Code)) at org.hibernate.event.def.AbstractVisitor.processEntityPropertyValues(AbstractVisitor.java(Compiled Code)) at org.hibernate.event.def.AbstractVisitor.process(AbstractVisitor.java:123) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performUpdate(DefaultSaveOrUpdateEventListener.java:267) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsDetached(DefaultSaveOrUpdateEventListener.java:216) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:93) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:502) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:494) at org.hibernate.engine.CascadingAction$5.cascade(CascadingAction.java:134) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java(Inlined Compiled Code)) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java(Compiled Code)) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java(Compiled Code)) at org.hibernate.engine.Cascade.cascade(Cascade.java(Compiled Code)) at org.hibernate.event.def.AbstractFlushingEventListener.cascadeOnFlush(AbstractFlushingEventListener.java:130) at org.hibernate.event.def.AbstractFlushingEventListener.prepareEntityFlushes(AbstractFlushingEventListener.java:121) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:65) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:985) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:333) at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:60) at org.hibernate.transaction.WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter$TransactionAdapter$1.invoke(WebSphereExtendedJTATransactionLookup.java:136) at $Proxy11.beforeCompletion(Unknown Source) at com.ibm.ws.jtaextensions.SynchronizationCallbackWrapper.beforeCompletion(SynchronizationCallbackWrapper.java:65) at com.ibm.ws.Transaction.JTA.RegisteredSyncs.distributeBefore(RegisteredSyncs.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TransactionImpl.prePrepare(TransactionImpl.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TransactionImpl.stage1CommitProcessing(TransactionImpl.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TransactionImpl.processCommit(TransactionImpl.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TransactionImpl.commit(TransactionImpl.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TranManagerImpl.commit(TranManagerImpl.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TranManagerSet.commit(TranManagerSet.java(Compiled Code)) at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:716) at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:167) at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:569) at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3801) at com.ibm.ws.webservices.dispatchers.ejb.WSEJBWrapper.postInvoke(WSEJBWrapper.java:153) at com.ibm.ws.webservices.dispatchers.ejb.J2ee14EJBDispatcher.cleanupEnvironment(J2ee14EJBDispatcher.java:197) at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler.invoke(JAXRPCHandler.java:148) at com.ibm.ws.webservices.engine.handlers.WrappedHandler.invoke(WrappedHandler.java:64) at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:225) at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:225) at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:279) at com.ibm.ws.webservices.engine.transport.http.WebServicesServlet.doPost(WebServicesServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at com.ibm.ws.webservices.engine.transport.http.WebServicesServletBase.service(WebServicesServletBase.java:341) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1282) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:673) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:80) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1804) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:84) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:469) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:408) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code)) Without modifying CacheSynchronization I only get this: WTRN0074E: Exception caught from before_completion synchronization operation: java.lang.UnsupportedOperationException at org.hibernate.transaction.WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter$TransactionAdapter.setRollbackOnly(WebSphereExtendedJTATransactionLookup.java:211) at org.hibernate.transaction.CacheSynchronization.setRollbackOnly(CacheSynchronization.java:77) at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:67) at org.hibernate.transaction.WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter$TransactionAdapter$1.invoke(WebSphereExtendedJTATransactionLookup.java:136) at $Proxy11.beforeCompletion(Unknown Source) at com.ibm.ws.jtaextensions.SynchronizationCallbackWrapper.beforeCompletion(SynchronizationCallbackWrapper.java:65) at com.ibm.ws.Transaction.JTA.RegisteredSyncs.distributeBefore(RegisteredSyncs.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TransactionImpl.prePrepare(TransactionImpl.java(Compiled Code)) ..... I use these transaction settings for hibernate: <property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property> <property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.WebSphereExtendedJTATransactionLookup</property> <property name="hibernate.transaction.flush_before_completion">true</property> <property name="hibernate.transaction.auto_close_session">true</property> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

6
12
0 / 0

[Hibernate-JIRA] Created: (ANN-778) Test hangs if an exception is thrown, due to unclosed transaction

by Juraci Paixao Krohling (JIRA)

Test hangs if an exception is thrown, due to unclosed transaction ----------------------------------------------------------------- Key: ANN-778 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-778 Project: Hibernate Annotations Issue Type: Patch Environment: Annotations from trunk on DB2 v91 Reporter: Juraci Paixao Krohling Attachments: ANN-778.diff The test EmbeddedGenericsTest#testWorksWithGenericCollectionOfElements fails on DB2 v91, and the transaction which was started in the "setup" method blocks the execution of any other SQL Statement sent to the server. Thus, the tests needs to be enclosed by a try/catch to issue a rollback in case of failure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3350) Error in creating Schema update script: if exist a view in Oracle db and exist a class with @Entity for this, then raises the "ORA-01702: a view is not appropriate here" exception

by Béla Berecz (JIRA)

Error in creating Schema update script: if exist a view in Oracle db and exist a class with @Entity for this, then raises the "ORA-01702: a view is not appropriate here" exception ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3350 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3350 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Reporter: Béla Berecz (sorry for my bad english) When deploying: 16:28:03,737 INFO [SchemaUpdate] Running hbm2ddl schema update 16:28:03,737 INFO [SchemaUpdate] fetching database metadata 16:28:04,128 INFO [SchemaUpdate] updating schema ... 16:28:59,565 WARN [JDBCExceptionReporter] SQL Error: 1702, SQLState: 42000 16:28:59,565 ERROR [JDBCExceptionReporter] ORA-01702: a view is not appropriate here 16:28:59,565 ERROR [SchemaUpdate] could not complete schema update org.hibernate.exception.SQLGrammarException: could not get table metadata: TABLE_VIEW at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) at org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata(DatabaseMetadata.java:105) at org.hibernate.cfg.Configuration.generateSchemaUpdateScript(Configuration.java:954) at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:140) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:314) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300) 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.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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.GeneratedMethodAccessor3.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.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.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.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy66.start(Unknown Source) at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:120) at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:551) at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:333) at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.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.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.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.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy33.start(Unknown Source) at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:93) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy34.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor21.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.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.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.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.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.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:619) Caused by: java.sql.SQLException: ORA-01702: nézet itt nem fordulhat elő 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:743) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:207) at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:946) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168) at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1614) at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1579) at oracle.jdbc.OracleDatabaseMetaData.getIndexInfo(OracleDatabaseMetaData.java:3485) at com.p6spy.engine.spy.P6DatabaseMetaData.getIndexInfo(P6DatabaseMetaData.java:210) at org.hibernate.tool.hbm2ddl.TableMetadata.initIndexes(TableMetadata.java:130) at org.hibernate.tool.hbm2ddl.TableMetadata.<init>(TableMetadata.java:35) at org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata(DatabaseMetadata.java:90) ... 150 more Problem with TableMetadata.java row 35: initIndexes(meta); I couldn't create index for view in Oracle, hence (I think) drop a SQLGrammarException when running initIndexes(meta). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2599) Inconsistent behaviour with Cascade Refresh and lazy loaded collections

by Guy Chua (JIRA)

Inconsistent behaviour with Cascade Refresh and lazy loaded collections ----------------------------------------------------------------------- Key: HHH-2599 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2599 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: 3.2.3, hsqldb/mysql Reporter: Guy Chua Attachments: cascadeTest.zip According to the specs for session.refresh(), the state of the given instance will be re-read from the database. I have a model 'Company' that has 2 lazy collections, departments and employees. Snippet of class Company -------------------------------------------------------------------- @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 1 private Set<Department> departments; // POINT 1 @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 2 private Set<Employee> employees; // POINT 2 Snippet of class CascadeTestRunner -------------------------------------------------------------------- public void doRefreshTest() { session = sessionFactory.openSession(); session.getTransaction().begin(); Company loadedCompany = (Company)session.get(Company.class, companyId); logger.debug(loadedCompany); // session.refresh(loadedCompany); // POINT A session.close(); Set<Department> loadedDepartments = loadedCompany.getDepartments(); logger.debug("TEST for LAZY DEPARTMENTS [START]"); for (Department tmpDepartment : loadedDepartments) { logger.debug(tmpDepartment); // POINT B } logger.debug("TEST for LAZY DEPARTMENTS [END]"); Set<Employee> loadedEmployees = loadedCompany.getEmployees(); logger.debug("TEST for LAZY EMPLOYEES [START]"); for (Employee tmpEmployee : loadedEmployees) { logger.debug(tmpEmployee); // POINT C } logger.debug("TEST for LAZY EMPLOYEES [END]"); } If I run the above code, Point B will give me LazyInitializationException which is the expected behavior. But if i uncomment POINT A, the LazyInitializationException happens at POINT C instead of POINT B. Why should POINT B pass and POINT C fail? Furthermore, with POINT A still uncommented and when I swap the position of POINT 1 with POINT 2, the LazyInitializationException happens at POINT B now. I am wondering why the position of the fields produce the exception at a different location. What happens when a lazy collection annotated with CascadeType.Refresh is refreshed? I am getting varied results, sometimes the collection is initialized, sometimes it is not. Is it supposed to cascade the refresh to lazy elements in the first place? Hope someone can shed some light on this. Test Results ------------------ 1. LazyInitializationException at POINT B @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 1 private Set<Department> departments; // POINT 1 @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 2 private Set<Employee> employees; // POINT 2 // session.refresh(loadedCompany); // POINT A logger.debug(tmpDepartment); // POINT B logger.debug(tmpEmployee); // POINT C 2. LazyInitializationException at POINT C @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 1 private Set<Department> departments; // POINT 1 @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 2 private Set<Employee> employees; // POINT 2 session.refresh(loadedCompany); // POINT A logger.debug(tmpDepartment); // POINT B logger.debug(tmpEmployee); // POINT C 2. LazyInitializationException at POINT B when positions of POINT 1 and POINT 2 are swapped @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 2 private Set<Employee> employees; // POINT 2 @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 1 private Set<Department> departments; // POINT 1 session.refresh(loadedCompany); // POINT A logger.debug(tmpDepartment); // POINT B logger.debug(tmpEmployee); // POINT C -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3642) EJB3 inheritance strategy TABLE_PER_CLASS does not work on HSQLDB

by Wolfgang Knauf (JIRA)

EJB3 inheritance strategy TABLE_PER_CLASS does not work on HSQLDB ----------------------------------------------------------------- Key: HHH-3642 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3642 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: JBoss 5.0GA, Java 1.6, Hypersonic 1.8.0.8 Reporter: Wolfgang Knauf Attachments: InheritanceTablePerClass.ear I use an EJB3 entity bean with inheritance strategy "TABLE_PER_CLASS": @Entity @Inheritance(strategy=InheritanceType.TABLE_PER_CLASS) public abstract class Base implements Serializable { ... When loading a list of base classes, all subclass fields are null. The union subclause in the query does not work on HSQLDB. Attached is a full EJB sample, runnable on JBoss 4.2/5.0 (project export of Eclipse 3.4/WebTools 3.0 with sources). After deploying, it can be tested by browsing to http://localhost:8080/InheritanceTablePerClassWeb/ See this output: ... Loading ALL Item: Child 1, child field 1: null Item: Child 2, child field 2: null Item: Child 3, child field 3: Field of Child3 ... Here, all childs are loaded. The fields of type "Child1" and "Child2" are null, fields of type "Child3" are filled. This is probably a duplicate of http://opensource.atlassian.com/projects/hibernate/browse/HHH-2920 The described workaround to change all NULL expressions to "cast (null as VARCHAR)" results in a working query, but I see no chance to pre-configure this query in the entity manager. I created another bug, because the impact is different (it breaks a feature of EJB3), and so I consider severity to be higher. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-41) Support BeanInfo implementation to receive property names

by Emmanuel Bernard (JIRA)

Support BeanInfo implementation to receive property names --------------------------------------------------------- Key: BVAL-41 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-41 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard Michael - Why section 3.1.2 requires properties to follow the JavaBeans naming convention? In many non-English speaking countries (and projects with ridiculous managers/code standards), other prefixes are used and proper BeanInfo implementations are supplied. Although it is not pretty at all, since they are following the JavaBean spec, I don't think Bean Validation shouldn't work out-of-the-box for them; Emmanuel I reused the Java Persistence wording actually and I explicitly reference the Introspector class. Do people think we should be more cautious here? Speaking for France, I've never seen a project bothering about get/is/set and BeanInfo. People happily used frenglish: getCafeAuLait() Actually I've never seen anybody from the server side bothering about BeanInfos ;) Michael I've got an interesting case for that one: in some JVM languages, another standard is used to represent properties. Let's take, for instance, Scala. In Scala, one could write a bean like: @BeanInfo class Person(var id : Long, var name : String, var surname : String) Scala already maps vars as properties creating a private var, a public getter method named like the var and a setter like var_=. Something like: private var _id : Long def id = _id def id_=(newId: Long) = _id = newId that would translate to Java methods id and id_$eq (since = cannot be used in method names). So, when one use @BeanInfo, a proper BeanInfo subclass is generated by the compiler providing that mapping. Given how popular JVM languages are getting, not following a spec in another one and causing property support in those languages to fail to work doesn't seem nice. BTW, please let the JPA EG know about his as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-82) Migrate ant build to maven2

by Hardy Ferentschik (JIRA)

Migrate ant build to maven2 --------------------------- Key: HSEARCH-82 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-82 Project: Hibernate Search Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Switch from ant to maven2 as build tool. Initally just try to build HSearch with maven. Once it works we can see if we can extract a common HibernateExt parent pom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

4
10
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 December 2008