RE: FW: [Hibernate-devel] Getting Collections to pull data from t he cache

[Urberg, J. <ju...@ve...>]

>>And I would expect 3 SQL statements with all the many-to-ones and
>>collections should get resolved from the cache.
>
>To enable caching, you need to add
>
><jcs-cache usage="read-write"/>
>
>to all <class>, <set>, <map>, <list>, <array>, <primitive-array> elements
>that you want to cache.

Ahh, I thought that was optional.  That would explain it.  

So I tried it out and got the following warning:

   WARNING: Could not instantiate cache - probably the JCS jar is
missing:... 

Then I looked at the JCS web site to see what the dependencies are and found
the following:

   commons-configuration  1.0-dev  commons-configuration-1.0-dev.jar  
   commons-logging  1.0  commons-logging-1.0.jar  
   commons-lang  1.0-dev  commons-lang-1.0-dev.jar  
   concurrent  1.0  concurrent-1.0.jar  
   hsqldb  1.7.0  hsqldb-1.7.0.jar  
   log4j  1.1.3  log4j-1.1.3.jar  
   servletapi  2.2  servletapi-2.2.jar  
   javagroups  2.0  javagroups-2.0.jar  
   jisp  1.0.2  jisp-1.0.2.jar  
   tomcat-util  3.2.1  tomcat-util-3.2.1.jar  
   velocity  1.3-dev  velocity-1.3-dev.jar  
   xmlrpc  1.1  xmlrpc-1.1.jar  
   stratum  1.0-b2-dev  stratum-1.0-b2-dev.jar  

Anyone know where I can find all these in one spot?  (I can't find
commons-configuration anywhere)  Maybe it's time to build a third party jar
file so folks (like me for example) don't have to track all this stuff down
seperately.

>>My first shot at this returned:
>>
>>cirrus.hibernate.HibernateException: You tried to persist an object with a
>>reference to a transient instance - save the transient instance first

I figured this one out.  I was getting a little too tricky.  My set function
put an adapter around a class to make it fit another interface and then
returned the same wrapper; which also implemented the interface of the
original class; in the getter.  I changed the getter to return the original
instead of the wrapped class and all is well.  I take it this functionality
is based on object identity instead of Object.equals()?

Regards,
John