August 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3417) Update all libs that are used in Hibernate to the latest version

by Nicolae Bucalaete (JIRA)

Update all libs that are used in Hibernate to the latest version ---------------------------------------------------------------- Key: HHH-3417 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3417 Project: Hibernate3 Issue Type: Improvement Affects Versions: 3.3.0.CR2 Reporter: Nicolae Bucalaete Libraries that are used in Hibernate have an old version and must be updated to the latest version. Conflicts can appear in applications where you need to use new versions of the libraries used by Hibernate. -- 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 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-247) Hibernate Search cannot run without apache-solr-analyzer.jar

by Emmanuel Bernard (JIRA)

Hibernate Search cannot run without apache-solr-analyzer.jar ------------------------------------------------------------ Key: HSEARCH-247 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-247 Project: Hibernate Search Issue Type: Bug Components: analyzer Affects Versions: 3.1.0.Beta1 Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.1.0.Beta2 -- 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 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2463) ClassCastException when Hibernate tries to cache results using ResultTransformer

by Peak user (JIRA)

ClassCastException when Hibernate tries to cache results using ResultTransformer -------------------------------------------------------------------------------- Key: HHH-2463 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2463 Project: Hibernate3 Type: Bug Versions: 3.2.2 Reporter: Peak user When Hibernate executes a cacheable query using a ResultTransformer, it will attempt to cache the results AFTER applying the ResultTransformer. The problem is that the ResultTransformer may modify the data in a way that Hibernate won't understand it anymore, and in this case it will generate a ClassCastException when trying to cache it. This problem could be easily solved if Hibernate cached results before applying the ResultTransformer instead of afterwards. Here's a sample code to reproduce this problem: class ToMapResultTransformer implements ResultTransformer { private String[] properties; public ToMapResultTransformer(String[] properties) { this.properties = properties; } public List transformList(List collection) { return collection; } public Object transformTuple(Object[] tuple, String[] aliases) { Map<String,Object> result = new HashMap<String,Object>(tuple.length); for (int i=0; i<tuple.length; i++) { result.put((properties != null ? properties[i] : aliases[i]), tuple[i]); } return result; } } Criteria sqlCriteria = createSqlCriteria(session); sqlCriteria.setProjection(projections); sqlCriteria.setCacheable(true); sqlCriteria.setResultTransformer(new ToMapResultTransformer(properties)); sqlCriteria.list(); The code above produces the following exception: java.lang.ClassCastException: java.util.HashMap at org.hibernate.cache.StandardQueryCache.put(StandardQueryCache.java:83) at org.hibernate.loader.Loader.putResultInQueryCache(Loader.java:2185) at org.hibernate.loader.Loader.listUsingQueryCache(Loader.java:2129) at org.hibernate.loader.Loader.list(Loader.java:2087) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:94) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1569) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283) -- 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 months

7
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2525) Bug when using a ResultTransformer on a cached query

by Sebastien Cesbron (JIRA)

Bug when using a ResultTransformer on a cached query ---------------------------------------------------- Key: HHH-2525 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2525 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Firebird 2.0 on Win XP Reporter: Sebastien Cesbron Attachments: testhib.zip Using a distinct result transformer which a cached like this : query = session.createQuery("select obj from ObjetTest obj left outer join fetch obj.children as obj_0 order by obj.id asc"); query.setResultTransformer(Criteria.DISTINCT_ROOT_ENTITY); query.setCacheable(true); query.list(); This leads to this exception 2007-03-21 14:28:20,589 ERROR : IllegalArgumentException in class: ObjetTest, getter method of property: oid Exception in thread "main" org.hibernate.PropertyAccessException: IllegalArgumentException occurred calling getter of ObjetTest.oid at org.hibernate.property.BasicPropertyAccessor$BasicGetter.get(BasicPropertyAccessor.java:171) at org.hibernate.tuple.entity.AbstractEntityTuplizer.getIdentifier(AbstractEntityTuplizer.java:183) at org.hibernate.persister.entity.AbstractEntityPersister.getIdentifier(AbstractEntityPersister.java:3524) at org.hibernate.persister.entity.AbstractEntityPersister.isTransient(AbstractEntityPersister.java:3240) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:181) at org.hibernate.engine.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:218) at org.hibernate.type.ManyToOneType.disassemble(ManyToOneType.java:163) at org.hibernate.cache.StandardQueryCache.put(StandardQueryCache.java:80) at org.hibernate.loader.Loader.putResultInQueryCache(Loader.java:2118) at org.hibernate.loader.Loader.listUsingQueryCache(Loader.java:2062) at org.hibernate.loader.Loader.list(Loader.java:2020) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:393) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at Test.main(Test.java:33) Caused by: java.lang.IllegalArgumentException: object is not an instance of declaring class 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.hibernate.property.BasicPropertyAccessor$BasicGetter.get(BasicPropertyAccessor.java:145) ... 16 more It seems this is due to a difference in QueryLoader.getResultColumnOrRow. In this method there is a test : else if ( !hasTransform ) { return row.length == 1 ? row[0] : row; } This causes the method to return an instance of ObjetTest in one case and an instance of ObjetTest[1] in the other one. In the latter test, when putting the query into the query cache, hibernate calls the getOid method on an array of ObjetTest and this causes the exception -- 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 months

5
6
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1722) query cache wont work with serialized/deserialized criteria due to ResultTransformer

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1722?page=c... ] Max Rydahl Andersen resolved HHH-1722. -------------------------------------- Resolution: Duplicate > query cache wont work with serialized/deserialized criteria due to ResultTransformer > ------------------------------------------------------------------------------------ > > Key: HHH-1722 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1722 > Project: Hibernate3 > Issue Type: Bug > Components: core > Environment: 3.2.0 svn head > Reporter: Mario Ivankovits > Assignee: Max Rydahl Andersen > Attachments: ResultTransformerIdentity.patch, ResultTransformerIdentity.patch > > > A serialized/deserialized DetachedCriteria do not work correctly with > the query cache. > The problem is the ResultTransformer in QueryKey. > In CriteraImpl the resultTransformer will be set to Criteria.ROOT_ENTITY. > This makes it down into the QueryKey. > After serialize/deserialize the instance of resultTransformer in > CriteriaImpl has changed (not that a surprise ;-) ) and thus - in the > end - the QueryKey changed. > Subsequent lookup in the query-cache will no longer work. > The query will be executed again and put int the query-cache. > The cache grows - every lookup failes. -- 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 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-243) Extrapolate the shard number in properties {shard_nbr}

by Emmanuel Bernard (JIRA)

Extrapolate the shard number in properties {shard_nbr} ------------------------------------------------------ Key: HSEARCH-243 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-243 Project: Hibernate Search Issue Type: Improvement Reporter: Emmanuel Bernard Priority: Minor hibernate.search.Item.indexName = Item{shard_nbr} equivalent to hibernate.search.Item.0.indexName Item0 hibernate.search.Item.1.indexName Item1 -- 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 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-1077) exclude-unlisted-classes in persestence.xml doesn't work for tools

by Antony Stubbs (JIRA)

exclude-unlisted-classes in persestence.xml doesn't work for tools ------------------------------------------------------------------ Key: HBX-1077 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1077 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.2 Environment: n/a Reporter: Antony Stubbs Similar to EJB-212, exclude-unlisted-classes doesnt' seem to work for hibernate tools. I seem to either have to list a .hbm file in the configuration, or include the entity class in the persistence.xml. Although, Eclipse JPA perspective picks up the mapping, when the entity is not listed anywhere and only having exclude-unlisted-classes set to false. When trying to use tools with just exclude-unlisted-classes set, I get "EntityName is not mapped" and no entities appear under the console configuration. -- 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 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3413) Configuration.generateSchemaUpdateScript() uses getTableMetadata() inconsistantly

by Erik Voorbraak (JIRA)

Configuration.generateSchemaUpdateScript() uses getTableMetadata() inconsistantly --------------------------------------------------------------------------------- Key: HHH-3413 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3413 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.3.0.CR2 Reporter: Erik Voorbraak Priority: Minor In org.hibernate.cfg.Configuration.generateSchemaUpdateScript(), there are two calls to getTableMetadata(); TableMetadata tableInfo = databaseMetadata.getTableMetadata( table.getName(), ( table.getSchema() == null ) ? defaultSchema : table.getSchema(), ( table.getCatalog() == null ) ? defaultCatalog : table.getCatalog(), table.isQuoted() and TableMetadata tableInfo = databaseMetadata.getTableMetadata( table.getName(), table.getSchema(), table.getCatalog(), table.isQuoted() Shouldn't the second call use the fallback to the default schema and catalog 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-524) Reverse of one-to-one relationships

by Marcio Carvalho (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-524?page=co... ] Marcio Carvalho updated HBX-524: -------------------------------- Attachment: one-to-one-marcio.patch Ok, this is the patch with my modifications that affected OneToOne code generation. I've made other ones, which are related more to ManyToManys and self ManyToManys, but they are not included. I also included the Ejb3PropertyGetAnnotation modifications, since this is my preferred way to work with Hibernate. Hope this helps. Marcio > Reverse of one-to-one relationships > ----------------------------------- > > Key: HBX-524 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-524 > Project: Hibernate Tools > Issue Type: Bug > Components: reverse-engineer > Affects Versions: 3.1beta2 > Environment: HIbernate 3.1, Oracle 9i > Reporter: Andrea Cattani > Assignee: Max Rydahl Andersen > Attachments: one-to-one-marcio.patch, patch.txt > > > Hi, > I've posted this issue to the forum and got this response from Max, Hibernate Team: > "the reveng tools does not detect this as a one-to-one. it probably could, so add a request/patch to jira." > The problem I've faced is the following: > I have two tables, let's say > - table A with column ID (PK) and other fields > - table B with column ID (PK) and other fields > table B has a foreign key constraint against table A, from column ID to column ID (one-to-one) > When I reverese the tables with the HibernateTools I have such a resultant mapping for table B: > <class name="B" table="B" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned" /> > </id> > <[b]many-to-one name[/b]="a" class="A" update="false" insert="false" fetch="select"> > <column name="ID" length="12" not-null="true" unique="true" /> > </many-to-one> > .... > And this one for table A: > <class name="A" table="A" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned"/> > </id> > <set name="b" inverse="true"> > <key> > <column name="ID" length="12" not-null="true" unique="true" /> > </key> > <[b]one-to-many[/b] class="B" /> > </set> > </class> > while I was expecting something like: > [i]<one-to-one name="a" class="A" constrained="true"/>[/i] > in table B, and the same (or nothing) in table A > Thank you > Andi -- 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 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-524) Reverse of one-to-one relationships

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-524?page=co... ] Max Rydahl Andersen commented on HBX-524: ----------------------------------------- Hi Marcio, This is one of the most voted for issues so you bet that others can use one-to-one ;) I just committed the first patch plus updates for handling properti foreign generator strategy for the constrained class, fixed bugs in one-to-one.hbm.ftl, delegated the control to reveng settings and revengstrategy and finally the ever-than-before-needed test cases ;) If you cannot easily align with those changes that is fine but I would still like to get your original patch - at least I can use the JPA templates. About your last comment about findOneToOneOwnerFK then I can't see what that code changes/is-good-for ? Maybe with a full patch I could grasp it. > Reverse of one-to-one relationships > ----------------------------------- > > Key: HBX-524 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-524 > Project: Hibernate Tools > Issue Type: Bug > Components: reverse-engineer > Affects Versions: 3.1beta2 > Environment: HIbernate 3.1, Oracle 9i > Reporter: Andrea Cattani > Assignee: Max Rydahl Andersen > Attachments: patch.txt > > > Hi, > I've posted this issue to the forum and got this response from Max, Hibernate Team: > "the reveng tools does not detect this as a one-to-one. it probably could, so add a request/patch to jira." > The problem I've faced is the following: > I have two tables, let's say > - table A with column ID (PK) and other fields > - table B with column ID (PK) and other fields > table B has a foreign key constraint against table A, from column ID to column ID (one-to-one) > When I reverese the tables with the HibernateTools I have such a resultant mapping for table B: > <class name="B" table="B" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned" /> > </id> > <[b]many-to-one name[/b]="a" class="A" update="false" insert="false" fetch="select"> > <column name="ID" length="12" not-null="true" unique="true" /> > </many-to-one> > .... > And this one for table A: > <class name="A" table="A" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned"/> > </id> > <set name="b" inverse="true"> > <key> > <column name="ID" length="12" not-null="true" unique="true" /> > </key> > <[b]one-to-many[/b] class="B" /> > </set> > </class> > while I was expecting something like: > [i]<one-to-one name="a" class="A" constrained="true"/>[/i] > in table B, and the same (or nothing) in table A > Thank you > Andi -- 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 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2008