Yes, we should be defaulting to a single node, unclustered jboss cache rather than having to supply yet another thirdparty jar to handle the baseline cache.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott Marlow > Sent: Monday, April 03, 2006 2:05 PM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] Unassigned for 4.0.4 > > Does anyone reading this understand how "JBAS-2868 Missing > jar ehcache-1.1.jar for Hibernate support" should be fixed? > > It is only of the few unassigned issues left. I'm wondering > if Hibernate could use JBossCache for the level one cache > instead of ehCache (easy hibernate cache). This might be a > nice alternative to adding the ehCache jar to the 4.0.4 as release. > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
