Eclipse - Version: 3.2.1 Build id: M20060921-0945
Hibernate Tools - Version 3.2.0beta8
Hibernate Version - where can i find it?
glazed-lists - Version 1.7.1.alpha20061218

I am a hibernate newbie.
Managed to run the "Hibernate Code Generation" tool within eclipse,
to generate java-Files.
I just wanted to try the new extension provided by the upcoming glazed-lists-version,

So I used
collection-type="ca.odell.glazedlists.hibernate.EventListType"
for one list in my .hbm.xml-file
and got the following error-message when running the code generation



This was easy to solve.
I specified the glazed-list-jar-file in the classpath-table within the console configuration
and I got the followin error-message:


Should I post the used version of EventListTypeTest.java here?
Never used collection-type before. Is this problem related to the unstable state of galzed-lists or is ist my fault?
Has anybody else experienced the same problem?

Thank you :D

never used that usertype, but as far as i can see it tries to instantiate or use an abstract class which probably is caused by some version incompability between that usertype and hibernate or glazedlist.

Try and compile the source against the version of glazedlist and hibernate you use.

btw. I thought a glazedlist was more a ui thing than it was a model thing ? why the need to persist it via hibernate ?

You are right. But glazedlists is based on its interface EventList which adds some methods to the List interface to allow locking and fine graded change notification. This fine graded change notification allows to handle transformations (filtering, sorting, ...) more efficiently.


You do not persist glazedlist-stuff. You persist your data. And since glazedlist does not work with a plain PersistentList you have to put the data into an EventList. The new galzedlists.hibernate-package tries to provide a PersistentEventList which extends hibernate's PersistentList implements glazedlists' EventList. Using collection-type=EventListType hibernate is told to use PersistentEventList. So hibernate put's data into an List which can be directly used with glazedlists.

Don't you think that there are applications where such an direct coupling makes sense?

1. There are some folks who use hibernate within their swing application.
2. There is also some network-related stuff in the glazedlists.io-package (haven't looked into it so far). So there may be cases where it makes sense to use glazedlist within the server code. I think this can be an easy way to implement an immediate-change-notification.



accurate diagnosis, max. :-) The problem was caused by the following hibernate-glazedlists incompatibility:
https://glazedlists.dev.java.net/issues ... cgi?id=387

Thank you for the hint.

At the moment there is no stable release of glazedlists' hibernate package. But publicobject has planned this feature for the next galzedlists release. More about the topic can be found in the glazedlists wiki:

http://publicobject.com/glazedlists/wik ... =Hibernate

ok - good to see the UserCollectionType being put to good use.

and yes, I can see its usage; it's just that sometime users persists things they shouldn't so just wanted to be sure ;)