[Seaside] Possible Pharo1.0 problem. No error indication while parsing and no debugging triigered on error.

Johan Brichau johan.brichau at uclouvain.be
Thu May 13 06:22:51 UTC 2010

Hi Fritz,

There's 2 things here.

First, there is absolutely no parse error. For the parser, it looks as if the 'html' on the next line is a unary message. Therefore, it is syntactically absolutely valid Smalltalk. 
Next, you need to check if you have a WAWalkbackErrorHandler configured for your Seaside application. For this, go to the config page of your app and click the configure button for the ExceptionFilter and select the aforementioned handler.

Hope this helps!

On 13 May 2010, at 01:27, Fritz Schenk wrote:

> Running with Seaside 3.0 on Pharo 1.0
> Simple rendering method with error
> <witherror>
> renderContentOn: html
> 	html heading: count.
> 	html anchor
> 		callback: [ self increase];
> 		with: '++'  "<<<<< error here - missing period"
> 	html space.
> 	html anchor
> 		callback: [self decrease];
> 		with: '--'
> </witherror>
> The error is not indicated while 'accept'ing or prettyprinting. 
> Missing '.' after first with clause.
> when I access the page I get the error:
> <error>
> MessageNotUnderstood: ByteString>>html
> </error>
> the page continues in 'Loading...' state, but there is no debugger in the
> environment.
> Please help.
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Johan Brichau
johan.brichau at uclouvain.be

More information about the seaside mailing list