well, frankly don't abuse the trust I put in you guys by handing out the rw
passwd.
We are a unique group in the sense that there are alot of independent rw
passwd, I don't want to see abuses, and I haven't seen any so far.
I don't even consider yours an abuse... the fact that the new caches don't
really work well (don't scale for now, but we are looking at it) is beyond
the point.
It seems to me that the LRU passivating is more complex than the no
passivation (and throws NPEs, sebastien is on it). At least I want the
NoPassivation to be the default in CVS for now. I don't think we can really
go out with this guys quite yet.
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone
|Sent: Tuesday, October 17, 2000 12:54 PM
|To: 'jBoss Developer'
|Subject: RE: [jBoss-Dev] JNDI Problem
|
|
|Hey,
|
|> ||> but this can be done once and cleanly in the persistence
|> manager, better
|> ||> than in many places that call the persistence manager, what do
|> ||you think ?
|> ||
|> ||No, since it may already be set before the PM is called, and in
|> |those cases
|> ||it will be set doubly which is unnecessary.
|> |
|> |k-rect
|>
|> in fact as rickard pointed out, the best place is the
|> container startup
|> (when you start that passivating stuff) and you are done.
|
|Done this way (at startup). Committing soon.
|
|Simon
|
|
