Well, I would think that since its all just serialized in the session, that when it was de-serialized, it would still all have the same memory address. This might not actually be the case, but I would think that it might be.
Have you actually given it a try? On Thu, 13 Jan 2005 22:36:51 -0500, Sean Schofield <[EMAIL PROTECTED]> wrote: > Big problem here. None of the classes implement the equals method. > When you refresh (or post) the page, a new instance of the component > is created (with a different memory address.) Default implementation > of equals method will return false in this case. > > See entry for MYFACES-80 for more details about the potential solution. > > sean > > On Thu, 13 Jan 2005 16:08:00 -0500, Sean Schofield > <[EMAIL PROTECTED]> wrote: > > > Again, why don't you just associate an id with the component instance > > > and then do an equals check. If its the same component, then it will > > > return true and there is no problem to report. > > > > That's what I'm trying to do. Although it occurs to me there is a bug > > in my logic. I'm throwing the exception if the component equals the > > one in the map. I need to throw the exception if its *not* equal. > > DUH. I will submit a patch tonight. > > > > > -Heath Borders-Wing > > > > sean > > > -- -Heath Borders-Wing [EMAIL PROTECTED]
