Well > I ran into problems with Hibernate because I had to access the DB > from two different JVMs (one from a webapp, another from an admin > console) and EHCache is a per-process cache.
Sounds to me like you are claiming a problem with hibernate when in fact it is not - it is a problem with the way YOU configured hibernate. If you read section 19.2 of the reference - that's the section titled second level caches - you would've seen a list of commonly used caches and their capabilities. There are two commonly used caches that support clusters, 10 secs of googling and voila: http://swarmcache.sourceforge.net/ http://www.jboss.org/products/jbosscache > I will the first to admit I make mistakes, > no one is perfect) but there is absolutely no need to making > remarks such as "See! This is why you got banned" which are > inflammatory. > I've already found one design advantage of Cayenne, > cross-VM caching I consider the above inflmatory, what exactly is the DESIGN advantage? > I am seriously considering dumping Hibernate in favor of Cayenne > because the former has a multitude of bugs and usability issues I ran > into which the authors refuse to acknowledge (don't mention the word > "bug" on their discussion forum or else they will ban you. No joke!). > Anyone who honestly thinks their software has no bugs *has* to be > delusional in my book. I also found the above statement inflamatory. I saw your jira/forum posts, no one refused to fix anything - most of them were fixable by rtfm. -Igor ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
