>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.... >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 *instance* might belong to an instance of a particular class but in general the toplevel collection role doesn't belong to a class. So if we want to keep all instances of a collection role in the same region (a good thing), the role needs its own region. I mean, we can write some special code for special cases (nested collections), but I'm not sure its worth the effort. Its not like the application should be looking at or caring about the layout of the JCS regions. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
