You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Heath Borders <he...@gmail.com> on 2005/01/14 04:57:52 UTC
Re: Update to forceId
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
<se...@gmail.com> 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
> <se...@gmail.com> 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
hborders@mail.win.org
Re: Update to forceId
Posted by Heath Borders <he...@gmail.com>.
lol.
Maybe we all need Simpson's aliases to seemingly increase the
popularity of our solutions.
I call Dr. Marvin Monroe! :-)
On Fri, 14 Jan 2005 09:24:57 -0500, Sean Schofield
<se...@gmail.com> wrote:
> I have a confession to make. I wrote the last entry. Flanderz = me.
> :-) That's just the nickname I use on the Sun forum (I'm a Simpsons
> fan). I remembered that thread from a long time ago and so I wanted
> to get some people to look at our solution now that we have one.
>
> sean
>
> On Fri, 14 Jan 2005 08:17:38 +0100, Matthias Wessendorf
> <ma...@matthias-wessendorf.de> wrote:
> > FYI:
> >
> > http://tinyurl.com/5kh9m
> >
> > last entry is about "forceId" of MyFaces :-)
> >
> > Regards,
> > Matthias
>
--
-Heath Borders-Wing
hborders@mail.win.org
Re: Update to forceId
Posted by Sean Schofield <se...@gmail.com>.
I have a confession to make. I wrote the last entry. Flanderz = me.
:-) That's just the nickname I use on the Sun forum (I'm a Simpsons
fan). I remembered that thread from a long time ago and so I wanted
to get some people to look at our solution now that we have one.
sean
On Fri, 14 Jan 2005 08:17:38 +0100, Matthias Wessendorf
<ma...@matthias-wessendorf.de> wrote:
> FYI:
>
> http://tinyurl.com/5kh9m
>
> last entry is about "forceId" of MyFaces :-)
>
> Regards,
> Matthias
RE: Update to forceId
Posted by Matthias Wessendorf <ma...@matthias-wessendorf.de>.
FYI:
http://tinyurl.com/5kh9m
last entry is about "forceId" of MyFaces :-)
Regards,
Matthias
> -----Original Message-----
> From: Heath Borders [mailto:heath.borders@gmail.com]
> Sent: Friday, January 14, 2005 5:21 AM
> To: Sean Schofield; MyFaces Discussion
> Subject: Re: Update to forceId
>
>
> Ok. There goes that theory on serialization then.
>
> I guess you're right. This type of thing can really only be
> implemented in the renderer to be guaranteed to work.
>
>
> On Thu, 13 Jan 2005 23:10:23 -0500, Sean Schofield
> <se...@gmail.com> wrote:
> > > 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.
> >
> > Well we can't really count on it being serialized in the
> session. If
> > you choose client-side state, it will *definitely* have a
> new address.
> >
> > > Have you actually given it a try?
> >
> > Yes. I am using session serialization and the memory addresses are
> > definitely different (I can even see them in my debugger)
> and equals
> > is definitely failing (that's what tipped me off in fact.)
> >
> > > -Heath Borders-Wing
> >
> > sean
> >
>
>
> --
> -Heath Borders-Wing
> hborders@mail.win.org
>
Re: Update to forceId
Posted by Heath Borders <he...@gmail.com>.
Ok. There goes that theory on serialization then.
I guess you're right. This type of thing can really only be
implemented in the renderer to be guaranteed to work.
On Thu, 13 Jan 2005 23:10:23 -0500, Sean Schofield
<se...@gmail.com> wrote:
> > 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.
>
> Well we can't really count on it being serialized in the session. If
> you choose client-side state, it will *definitely* have a new address.
>
> > Have you actually given it a try?
>
> Yes. I am using session serialization and the memory addresses are
> definitely different (I can even see them in my debugger) and equals
> is definitely failing (that's what tipped me off in fact.)
>
> > -Heath Borders-Wing
>
> sean
>
--
-Heath Borders-Wing
hborders@mail.win.org
Re: Update to forceId
Posted by Sean Schofield <se...@gmail.com>.
> 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.
Well we can't really count on it being serialized in the session. If
you choose client-side state, it will *definitely* have a new address.
> Have you actually given it a try?
Yes. I am using session serialization and the memory addresses are
definitely different (I can even see them in my debugger) and equals
is definitely failing (that's what tipped me off in fact.)
> -Heath Borders-Wing
sean