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

Alan Krueger (JIRA) noreply at atlassian.com
Tue Jul 3 12:11:52 EDT 2007


    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_27386 ] 

Alan Krueger commented on HHH-1265:
-----------------------------------

I'm seeing this as well.  This has been outstanding for quite a while, is there any chance of this being included in an upcoming release?

> 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
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1 beta 2, 3.1
>         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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the hibernate-issues mailing list