Thank you Werner, This makes it more clear...
Regards, Gonzalo Abollado. -----Original Message----- From: Werner Guttmann [mailto:[EMAIL PROTECTED] Sent: domingo, 29 de abril de 2007 15:43 To: dev@castor.codehaus.org Cc: [EMAIL PROTECTED] Subject: Re: [castor-dev] Ehcache name in ehcache.xml and ehcache-1.2.4-remote-debugger.jar Gonzalo, Castor internally uses the full qualified name of the domain object(s) as cache names. In other words, if you happen to have a domain object with a qualified name of 'jdo.c1947.Entity', Castor will ask EHCache to create a Cache instance with a name of 'jdo.c1947.Entity' specific to this domain object. There's no such thing as a single cache instance used by Castor internally for all domain objects (like e.g. Hibernate). As a result, this implies that Castor will create as many caches as there' domain objects (allowing you to tailor each of those caches according to your specific needs). With this knowledge, in the configuration file for EHCache it should be pretty straight-forward to either configure cache instances individually, or come up with a mix of standard (default) cache definition and custom ones for those domain objects that actually require a custom cache definition. I hope this answers your question ? Regards Werner Gonzalo Abollado wrote: > Hello, > > Any one can tell me: > > - What's the cache name castor is using for ehcache? > > - Can I or do I have to configure it in ehcache.xml to? > If not, how can I know the name of the cache to change configuration options > and to debug it with ehcache-1.2.4-remote-debugger.jar since a cache name is > a mandatory argument? > > Thanks a lot > Gonzalo Abollado. > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
