[Seaside] call: works intermittently on Pharo
sebastian at flowingconcept.com
Sat Sep 10 14:36:22 UTC 2011
your #addProduct code looks good.
The issue must be somewhere else
On Sep 10, 2011, at 10:27 AM, Larry White wrote:
> Hi, I'm a newbie so apologies if I'm doing something dumb.
> I'm working with Seaside in Pharo using the standard Seaside environment.
> In my application, call: seems to work intermittently. For example, I have this method in one component:
> | editor |
> editor := ProductEditorComponent new.
> (self call: editor)
> ifTrue: [ Dao new addProduct: product ]
> When I run my app, the method gets invoked (a halt statement is hit when I add it to the method), but the ProductEditorComponent never renders and no exception is raised. I see this elsewhere in my app as well. On my login form I have a link to a "forgot password" component that worked for a while then stopped, also without raising an exception.
> I'm assuming that what I'm doing wrong would be obvious to an experienced Seasider since it seems to be easy to get into this state. What causes a component to fail to render when called without raising an error?
> Thanks much for any assistance.
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside