[Seaside] Handling not found

[jtuchel at objektfabrik.de]

Torsten,

haven't done it yet, but looking at WAHtmlResponseGenerator, I guess I'd 
start by subclassing it and overriding #notFound.
At least that is where I'd start my experiments. If you need to handle 
stuff with a full-blown component, WAdispatcher #handleFiltered:named:  
is probably a better place to start from..

Joachim


Am 18.10.13 08:32, schrieb Torsten Bergmann:
> Hi,
>
> running a simple seaside demo app using Seaside with Zinc (ZnZincServerAdaptor) and Pharo.
> Its available from
>
>    http://localhost:8080/myapp
>
> and (since I changed the default) also on
>
>    http://localhost:8080
>   
> When entering
>
>    http://localhost:8080/somethingtotallyunknown
>   
> I get a 'not found' which seems to be handled by default in WAResponseGenerator>>notFound.
>
> I would like to have a nice page when nothing is found. Since it should run standalone
> I dont want to catch 404 at the front (apache, nginx) but directly in seaside to redirect
> to a nice "You are lost" page.
>
> How can I register an own #responseGenerator that can handle 404?
>
> Thx
> T.
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>


-- 
-- 
----------------------------------------------------------------------- 
Objektfabrik Joachim Tuchel          mailto:jtuchel at objektfabrik.de 
Fliederweg 1                         http://www.objektfabrik.de
D-71640 Ludwigsburg 		     http://joachimtuchel.wordpress.com
Telefon: +49 7141 56 10 86 0         Fax: +49 7141 56 10 86 1