[Seaside] WATask calling another WATask
johan at inceptive.be
Tue Jun 10 15:48:26 UTC 2014
So it's not a Gemstone specific issue? You also have it in Pharo?
It sounds familiar to https://code.google.com/p/seaside/issues/detail?id=744
gotta run now but I'm online later on...
On 10 Jun 2014, at 17:39, Mariano Martinez Peck <marianopeck at gmail.com> wrote:
> Hi guys,
> I have a strange situation. I have a main WATask subclass called XXX. In XXX's #go I do a #call: to another task YYY and I get a "WATaskNotDelegated: This task has no delegation.". Of course, I put a halt in YYY's #go and it does not halt at all. It seems task XXX is trying to RENDER task YYY.
> What is even more funny, is that if in XXX instead of directly calling task YYY, I do a #call: to another regular WAComponent, I get the answer and then I call task YYY, that works!!!!
> Any idea what could be the problem? Are tasks allowed to do a #call: to other tasks?
> Thanks in advance,
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside