> >Here i dont understand ( beside the fact that there is a technical issue
i
> >dont figure out ) , why i would want to get 2 JCS cache region for the
> >exactly same class of objects ?
>
> well, for a start we have toplevel collections which don't actually belong
> to any class a particular
>It comes from your auxiliary DC (Disk Cache ) cache.
>My guess is that the path you gave to store objects on the disk is not
>correct or it's a file permission issue.
oh yeah. stupid. I didn't notice the SEVERE. yeah, ummm ... what he said...
just try disabling the auxiliary cache for a start.
- Original Message -
From:
To: "Christian Meunier" <[EMAIL PROTECTED]>
Cc: "Urberg, John" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Friday, August 09, 2002 3:48 PM
Subject: Re: FW: [Hibernate-devel] Getting Collections to pull data from the
ca
AIL PROTECTED]>
To: "'Christian Meunier'" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, August 09, 2002 3:40 PM
Subject: RE: FW: [Hibernate-devel] Getting Collections to pull data from the
cache
> >> Hibernate got everything you need to run JCS, are y
>you can of course use usage='read-only' isnt it ?
yes, if appropriate.
>I am wondering something here:
>
>If we got this simple one to many:
>
>i have declarated the class bar and the class foo to use jcs-cache,
shoudnt
>the collection of bar in the class foo cached automatically ?
No.
>If i
>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
to all , , , , , elements
that you want to cache.
:)
>My first shot at this returned:
>
>cirrus.hibernate.HibernateException: You tried to p
>I would expect the following to happen:
yep, thats right. The problem is that Hibernate models a collection as a
seperate object from the entities contained in the collection. Thats why we
(inefficiently) require two selects to materialize an association
1. To load the collection with ids +
