November 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2135) Hibernate Deserialization: In org.hibernate.type.SerializableType the code makes a test for the return of a null object by simply testing the object as to whether or not it is null.

by Lamon Gray (JIRA)

Hibernate Deserialization: In org.hibernate.type.SerializableType the code makes a test for the return of a null object by simply testing the object as to whether or not it is null. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2135 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2135 Project: Hibernate3 Type: Improvement Versions: 3.2.0.cr5 Environment: HIbernate 3.2.1 & NCR TeradataJBOss 4.0.x & JBoss Cache 1.2.4 Reporter: Lamon Gray In org.hibernate.type.SerializableType the code makes a test for the return of a null object by simply testing the object as to whether or not it is null. public Object get(ResultSet rs, String name) throws HibernateException, SQLException { byte[] bytes = (byte[]) Hibernate.BINARY.get(rs, name); if ( bytes==null) { return null; } else { return fromBytes(bytes); } } Fairly reasonable, however in my testing of the Teradata dialect i am finding that often the value in the column is null but that the return is coming back as an empty array. The following code would seem to be a bit more robust in my opinion: public Object get(ResultSet rs, String name) throws HibernateException, SQLException { byte[] bytes = (byte[]) Hibernate.BINARY.get(rs, name); if ( bytes==null || Array.getLength(bytes)==0) { return null; } else { return fromBytes(bytes); } } Can someone tell me if this is done this way for a reason? Or maybe the JDBC driver is returning the incorrect value (IE. it should be returning a null value as opposed to an empty array)? -- 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 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2206) SessionImpl tries to deserialize itself in an incorrect order

by Steve Ebersole (JIRA)

SessionImpl tries to deserialize itself in an incorrect order ------------------------------------------------------------- Key: HHH-2206 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2206 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Reporter: Steve Ebersole Assigned to: Steve Ebersole Fix For: 3.2.1 SessionImpl attempts to read its JDBCContext and ConnectionManager state before its ConnectionReleaseMode has been read during deserialization. This can lead to connection leaks because the ConnectionManager does not know the correct release mode to use. -- 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 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1767) read-only cache for immutable collection causes unnecessary warning

by Emilio Oca (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1767?page=c... ] Emilio Oca commented on HHH-1767: --------------------------------- The patch works for me, test it ok on 3.2cr2. Warning no longer shows > read-only cache for immutable collection causes unnecessary warning > ------------------------------------------------------------------- > > Key: HHH-1767 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1767 > Project: Hibernate3 > Type: Patch > Components: core > Versions: 3.1.3 > Reporter: Alex Burgel > Priority: Trivial > Attachments: SessionFactoryImpl.patch > > > SessionFactoryImpl always says collections are mutable when calling the CacheFactory, even if the mapping file says otherwise. this causes a warning in the CacheFactory -- 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 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (ANN-366) Create some specialized converter for number

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-366?page=co... ] Emmanuel Bernard commented on ANN-366: -------------------------------------- Handling signed elements is not easy. Basically we need a header such as negative_header < positive-header through natural comparator Plus for negative numbers we have to invert them so that -3 < -2 and not the other way around with a natural omparator @Pad(shift=4, signed=true) or @Pad(max=9999, signed=true) Note that decimals are harmless Also the Lucene recommendation is to use a Query filter rather than a RangeQuery, but ihis will defect the firstResult / maxResult > Create some specialized converter for number > -------------------------------------------- > > Key: ANN-366 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-366 > Project: Hibernate Annotations > Type: New Feature > Components: lucene > Reporter: Emmanuel Bernard > Fix For: 3.3.0.Alpha1 > > > Typically, the numbers are padded to match the alphabetical ordering > 007 > 023 > 234 > This can be done manually through a converter but this would be nice to have it built-in -- 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 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-485) Subclass QueryParser to handle bridge conversion (esp for range query)

by Emmanuel Bernard (JIRA)

Subclass QueryParser to handle bridge conversion (esp for range query) ---------------------------------------------------------------------- Key: ANN-485 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-485 Project: Hibernate Annotations Type: New Feature Components: lucene Reporter: Emmanuel Bernard Fix For: 3.3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1265) classcastexception when using dom4jsession to save xml of a versioned class

by Jeremiah Marcum (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1265?page=all ] Jeremiah Marcum updated HHH-1265: --------------------------------- Attachment: patches.zip The patches I described previously attached in a zip file. > classcastexception when using dom4jsession to save xml of a versioned class > --------------------------------------------------------------------------- > > Key: HHH-1265 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1265 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1, 3.1 beta 2 > Environment: hibernate 3.1 oracle windows > Reporter: Winston Huang > Attachments: hibernate_test.zip, patches.zip > > > when importing from xml format and trying to save the instance using dom4jsession, i got the following exception. it would succeed if i don't use an optimistic locking object (with versioning). see the attached test case for details. i have a many-to-many set relationship from user to role. the xml data files are in User.xml and Role.xml. loading Role.xml is fine. but loading User.xml failed. > log4j:WARN No appenders could be found for logger (org.hibernate.cfg.Environment). > log4j:WARN Please initialize the log4j system properly. > Exception in thread "main" java.lang.ClassCastException: org.dom4j.tree.DefaultElement > at org.hibernate.event.def.DirtyCollectionSearchVisitor.processCollection(DirtyCollectionSearchVisitor.java:50) > at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:104) > at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:64) > at org.hibernate.event.def.AbstractVisitor.processEntityPropertyValues(AbstractVisitor.java:58) > at org.hibernate.event.def.DefaultFlushEntityEventListener.isUpdateNecessary(DefaultFlushEntityEventListener.java:301) > at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:111) > at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:190) > at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:70) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:730) > at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:329) > at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:86) > at TestDom4jVersionedObject.main(TestDom4jVersionedObject.java:26) -- 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 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1265) classcastexception when using dom4jsession to save xml of a versioned class

by Jeremiah Marcum (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1265?page=c... ] Jeremiah Marcum commented on HHH-1265: -------------------------------------- I was also having this problem and was able to fix it by patching the following 2 files: Note: I changed DirtyCollectionVisitor.java by adding ' || collection instanceof Element' to the if statement. It may be more appropriate to add ' || !(collection instanceof PersistentCollection) to the if statement so that any collection that needs to be wrapped by its Holder will work instead of just doing that for Elements. Note2: I had to patch Dom4jAccessor.java because it was returning my id as the actual serializable (Long in my case) and not as an element, which was throwing a CCE. This may be because my id was specified as an attribute and not as an element, i'm not sure. Whatever the reason, adding that change fixed it, however it may be better to look further up the line to see what the cause is. Patch for org.hibernate.event.def.DirtyCollectionSearchVisitor.java Index: DirtyCollectionSearchVisitor.java =================================================================== --- DirtyCollectionSearchVisitor.java (revision 10687) +++ DirtyCollectionSearchVisitor.java (working copy) @@ -37,7 +37,7 @@ SessionImplementor session = getSession(); final PersistentCollection persistentCollection; - if ( type.isArrayType() ) { + if ( type.isArrayType() || collection instanceof Element ) { persistentCollection = session.getPersistenceContext().getCollectionHolder(collection); // if no array holder we found an unwrappered array (this can't occur, // because we now always call wrap() before getting to here) Patch for Dom4jAccessor.java Index: Dom4jAccessor.java =================================================================== --- Dom4jAccessor.java (revision 10687) +++ Dom4jAccessor.java (working copy) @@ -168,6 +168,7 @@ } public Object get(Object owner) throws HibernateException { + if (!(owner instanceof Element)) { return owner; } //EARLY RETURN Element ownerElement = (Element) owner; Node attribute = ownerElement.attribute(attributeName); return attribute==null ? null : > classcastexception when using dom4jsession to save xml of a versioned class > --------------------------------------------------------------------------- > > Key: HHH-1265 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1265 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1, 3.1 beta 2 > Environment: hibernate 3.1 oracle windows > Reporter: Winston Huang > Attachments: hibernate_test.zip, patches.zip > > > when importing from xml format and trying to save the instance using dom4jsession, i got the following exception. it would succeed if i don't use an optimistic locking object (with versioning). see the attached test case for details. i have a many-to-many set relationship from user to role. the xml data files are in User.xml and Role.xml. loading Role.xml is fine. but loading User.xml failed. > log4j:WARN No appenders could be found for logger (org.hibernate.cfg.Environment). > log4j:WARN Please initialize the log4j system properly. > Exception in thread "main" java.lang.ClassCastException: org.dom4j.tree.DefaultElement > at org.hibernate.event.def.DirtyCollectionSearchVisitor.processCollection(DirtyCollectionSearchVisitor.java:50) > at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:104) > at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:64) > at org.hibernate.event.def.AbstractVisitor.processEntityPropertyValues(AbstractVisitor.java:58) > at org.hibernate.event.def.DefaultFlushEntityEventListener.isUpdateNecessary(DefaultFlushEntityEventListener.java:301) > at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:111) > at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:190) > at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:70) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:730) > at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:329) > at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:86) > at TestDom4jVersionedObject.main(TestDom4jVersionedObject.java:26) -- 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 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-804) Add inherited properties and id/property stubs

by Mark Hobson (JIRA)

Add inherited properties and id/property stubs ---------------------------------------------- Key: HBX-804 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-804 Project: Hibernate Tools Type: Improvement Components: hbm2doc Versions: 3.2beta8 Reporter: Mark Hobson Attachments: patch.txt The attached patch adds properties inherited from super-entities and stubs for id/property details. I plan to expand on this detail stubs in future, but for the moment they serve as placeholders for anchors. -- 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 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-795) Entity documentation is missing hierarchy information

by Mark Hobson (JIRA)

Entity documentation is missing hierarchy information ----------------------------------------------------- Key: HBX-795 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-795 Project: Hibernate Tools Type: Improvement Components: hbm2doc Versions: 3.2beta8 Reporter: Mark Hobson Attachments: patch.txt The attached patch adds the entity hierarchy tree to the entity page as per javadoc. -- 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 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HBX-802) Hide property summary when no properties and sort alphabetically

by Mark Hobson (JIRA)

Hide property summary when no properties and sort alphabetically ---------------------------------------------------------------- Key: HBX-802 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-802 Project: Hibernate Tools Type: Improvement Components: hbm2doc Versions: 3.2beta8 Reporter: Mark Hobson Attachments: patch.txt The attached patch hides the property summary block for entities with no properties, and for those that do, they are sorted alphabetically as per javadoc. -- 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 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2006