<div dir="ltr"><div>Oooh ok. You're right. This is seaside behaviour, nothing is related to Zinc:<br><br>WAAdmin applicationExceptionHandlingDefaults at: #exceptionHandler "--> WAHtmlErrorHandler". <br><br>
<br></div><div>I've registered WAWalkbackErrorHandler as the exception handler for my app and it is now working. Here's the simplest setting to make it work:<br><br></div><div>CCRootComponent class>>initialize<br>
| app |<br> super initialize.<br> app := WAAdmin register: self asApplicationAt: 'my-super-app'.<br> app exceptionHandler: WAWalkbackErrorHandler.<br></div><div><br></div><div>Is the WAHtmlErrorHandler the new exception handler in Seaside or did I configure something wrong?<br>
<br></div><div>Thanks a lot Sven :)<br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 16, 2014 at 11:14 AM, Sven Van Caekenberghe <span dir="ltr"><<a href="mailto:sven@stfx.eu" target="_blank">sven@stfx.eu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi François,<br>
<br>
I suspect you are confusing two aspects.<br>
<br>
Zinc can catch errors in its handler and report them in a user friendly page (standard behaviour) with the proper response code, or it can let the error through so that you end up in the debugger (debugMode: true) - see ZnSingleThreadedServer>>#handleRequestProtected:<br>
<br>
However, when using Seaside, all this is not necessary. Zinc is bit of overkill in this case, because Seaside wants to do more itself, including the error handling.<br>
<br>
In my image, this all works fine and as expected (as per the Seaside book / the standard instructions). You should have WAWalkbackErrorHandler as #exceptionHandler.<br>
<br>
Sven<br>
<br>
BTW, at first sight, your code looks OK to me.<br>
<div class="HOEnZb"><div class="h5"><br>
On 16 Apr 2014, at 10:55, François Stephany <<a href="mailto:tulipe.moutarde@gmail.com">tulipe.moutarde@gmail.com</a>> wrote:<br>
<br>
> Actually it works fine but I still doesn't have a debugger popping up in case of error. I still get a 500 page with the error message. This is how I start it:<br>
><br>
> CCZincStaticServerAdaptor startOn: 8080.<br>
> CCZincStaticServerAdaptor default server debugMode: true.<br>
><br>
> Any thing that I'm missing?<br>
><br>
><br>
> On Tue, Apr 15, 2014 at 6:06 PM, François Stephany <<a href="mailto:tulipe.moutarde@gmail.com">tulipe.moutarde@gmail.com</a>> wrote:<br>
> I quickly put this together:<br>
> It will serve stuff placed in the assets directory (which must sit next to the image). Nothing really fancy but does the job:<br>
><br>
> ZnSeasideStaticServerAdaptorDelegate subclass: #CCStaticServerDelegate<br>
> instanceVariableNames: ''<br>
> classVariableNames: ''<br>
> category: 'Cocotte-Web'<br>
><br>
> CCStaticServerDelegate>>handleRequest: znRequest<br>
> znRequest url firstPathSegment = 'assets'<br>
> ifTrue: [<br>
> znRequest url removeFirstPathSegment. "eats the /assets/"<br>
> ^self staticDelegate handleRequest: znRequest ]<br>
> ifFalse: [ ^self adaptor process: znRequest ]<br>
><br>
> CCStaticServerDelegate>>initializeStaticDelegate<br>
> | assetDirectory |<br>
> assetDirectory := (FileLocator imageDirectory / 'assets').<br>
> ^ ZnStaticFileServerDelegate new<br>
> directory: (ZnFileSystemUtils directory: assetDirectory) ;<br>
> yourself<br>
><br>
> And the Adaptor:<br>
><br>
> ZnZincStaticServerAdaptor subclass: #CCZincStaticServerAdaptor<br>
> instanceVariableNames: ''<br>
> classVariableNames: ''<br>
> category: 'Cocotte-Web'<br>
><br>
> ZnZincStaticServerAdaptor>>defaultDelegate<br>
> ^ CCStaticServerDelegate with: self<br>
><br>
><br>
> On Sun, Apr 13, 2014 at 3:16 PM, Johan Brichau <<a href="mailto:johan@inceptive.be">johan@inceptive.be</a>> wrote:<br>
> To serve static files from a directory during development, there still is the Seaside-Filesystem package.<br>
> -> Load the 'Filesystem' group from ConfigurationOfSeaside3<br>
><br>
> But I also do intend to replace it with serving static files from Zinc directly though. But, in the meantime, it's doing the job.<br>
><br>
> Johan<br>
><br>
> On 10 Apr 2014, at 08:39, François Stephany <<a href="mailto:tulipe.moutarde@gmail.com">tulipe.moutarde@gmail.com</a>> wrote:<br>
><br>
> > Ok. I've got quite a bit of external files, I'll roll my own ;)<br>
> ><br>
> > thanks !<br>
> > <br>
> > _______________________________________________<br>
> > seaside mailing list<br>
> > <a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
> > <a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
><br>
> _______________________________________________<br>
> seaside mailing list<br>
> <a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
> <a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
><br>
><br>
> _______________________________________________<br>
> seaside mailing list<br>
> <a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
> <a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div><br></div>