or or or... if you care about it you can replace the key and just have the
cache generate the key accordingly.
Accomodating fatkey patterns is something we can do. It was there first I
then removed it to "cut through the chase" and get a solid implementation
out, let us know...
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jay Walters
|Sent: Thursday, November 09, 2000 1:48 PM
|To: 'jBoss'
|Subject: RE: [jBoss-User] Two instances of one entity?
|
|
|I don't know about the fat key from ejb-interest, but thanks for the info.
|I'm trying to see what I can figure out which avoids the extra
|fields in the
|pk...
|
|-----Original Message-----
|From: Rickard Oberg [mailto:[EMAIL PROTECTED]]
|Sent: Thursday, November 09, 2000 3:21 PM
|To: jBoss
|Subject: Re: [jBoss-User] Two instances of one entity?
|
|
|Hey
|
|
|> Does this mean that jBoss is really performing some operation on my PK
|class
|> to determine if two PKs are equal which is different than calling the
|> .equals method? I am contemplating putting a few bits of extra
|information
|> into the PK class which isn't really part of the PK and if that
|will throw
|> off jBoss in figuring out which entities are the same then I'll have to
|come
|> up with a better way...
|
|Oh yeah, now I remember the "Fat key" pattern on EJB-INTEREST... yeah that
|would screw things up...
|
|/Rickard
|
|
|
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
