AnObsoleteRequirementEditComponent does not understand ....

I don't know whether this is a pharo or seaside issue. I'm having a problem where I badly messed up the code in a custom Seaside component class and decide to fix it by deleting it and creating a new class with the same name.  Now when the new class should be getting invoked in Seaside I get: 

MessageNotUnderstood: AnObsoleteRequirementEditComponent class>>requirement:

How do I make Seaside recognize there's a new class? I tried shutting down the image, closing the browser window, clicking replace cache in the config editor, clicking new session, restarting seaside....

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On 17 September 2011 17:15, Mariano Martinez Peck <[hidden email]> wrote:
> Can you try evaluating     Smalltalk fixObsoleteReferences.  ?

<rant>
Hmm, this method is pretty ironic: If the handling of bindings wasn't
totally broken in Pharo this method wouldn't need to exist. If this
method wouldn't exist the model wouldn't be that broken.
</rant>

I suggest to use

   Compiler recompileAll

that shouldn't make the situation worse.

Lukas


--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside