[Seaside] Re: initialRequest: / updateRoot: / updateUrl:

Johan Brichau johan at inceptive.be
Fri May 20 07:38:10 UTC 2011

But wait...

... is updateUrl: supposed to be invoked recursively on the subcomponents? 
I wonder if that makes sense because you would have to know in which order the traversal happens to meaningfully update the url in each subcomponent. No?

Can you try to implement updateRoot: on your subcomponent? Is that one called? (this one propagates for sure to the children)

On 20 May 2011, at 09:32, Francois Stephany wrote:

>> Did you override #initialize / #initialRequest / #updateUrl: somewhere without doing a super call?
> I've rechecked and they all seem to be ok.
>> I also think it's better to refrain from lazy initialization when using Seaside, since it's a source of bugs like this.
>> Although I think it's not an issue in this case because the #children method calls it.
> I've removed the lazy initialization and setup my visibleComponent in #initialize but still have the problem.
> Mmmmm...
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list