I *THINK*, right now, you have on cache-type for the entire system. The best way for this to work IMO, is to be able to specify specialized cache implementations on a per-class-descriptor basis. One of these can be the "no-cache cache".
I agree that doing this as a configuration property is much better than programming it. -Jason On Thu, 2003-01-23 at 08:42, Matthew Baird wrote: > yes you could do this, but it would be nicer, imho, to have this be part of the standard mapping. I've used it in Castor, and it's very effective. > > -----Original Message----- > From: Gelhar, Wallace J. [mailto:[EMAIL PROTECTED]] > Sent: Thu 1/23/2003 8:10 AM > To: OJB Users List > Cc: > Subject: RE: Customizing if a persistente object use the cache or not > > > > Isn't this possible today by using a custom attribute and extending or > rewriting the cache? > > Wally > > -----Original Message----- > From: Jason McKerr [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 23, 2003 9:55 AM > To: OJB Users List > Subject: RE: Customizing if a persistente object use the cache or not > > > Yup, that'd be cooler than an ice-cube sandwich. > > -Jason > > On Thu, 2003-01-23 at 07:49, Matthew Baird wrote: > > I think even better than this would to be have a cache setting like > > Castor does > > > > cache="none|time-limited|count-limited|soft|jcs|custom" > > capacity="" > > > > m > > > > -----Original Message----- > > From: Jason McKerr [mailto:[EMAIL PROTECTED]] > > Sent: Thu 1/23/2003 7:47 AM > > To: OJB Users List > > Cc: > > Subject: Re: Customizing if a persistente object use the cache > or not > > > > > > > > I agree this could be a very useful feature if it's possible. > > > > -jason > > > > On Thu, 2003-01-23 at 07:34, CLARAMONTE Jean-Baptiste wrote: > > > Hello, > > > > > > I would like to know if there is a way to customize for each > object if it > > > can or can't be in cache ? > > > Do you think it could be easy to add this functionality so > that it could be > > > added in the respository, like this for example : > > > > > > <class-descriptor > > > class="Customer" > > > table="CUSTOMER" > > > in-cache="false"> > > > ... > > > </class-descriptor> > > > > > > > > > Like that you could customize which class need to always be up > to date > > > compared to the database and which just need to be loaded one > time (static > > > data). > > > > > > > > > thanks for your opinion on the subject > > > > > > JB > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > ______________________________________________________________________ > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: < mailto:[EMAIL PROTECTED]> > > > > > ______________________________________________________________________ > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED] > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED] > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
