Launch an external application from visual works

Generally, people don't package up Seaside web applications - but that's
not to say you shouldn't be able to do it. I'll open an AR to
investigate a common solution for this problem.

Cheers,
Michael

Carl Gundel wrote:

Have a look at what I do in BottomFeeder - see package RSS-ErrorHandling in
the public store.  It's a small package; just browse it from the Published
items list.


----- Original Message -----
From: "Carl Gundel" <[hidden email]>
To: <[hidden email]>
Sent: Tuesday, October 09, 2007 10:33 PM
Subject: Best error notifier for Seaside?


> When I package my Seaside application RuntimeEmergencyNotifier is the
> error notifier that gets used by default.  Of course I don't really want
> to use this because any unhandled exceptions will cause the server to
> quit.  What would be a better choice for use with a packaged Seaside app?
>
> -Carl Gundel
> http://www.runbasic.com
>
>

Or just save headless and set your own handler in your application settings to render whatever you wish back to the client avoiding use of rtp altogether.

Cheers!

-Boris
(Sent from a BlackBerry)

----- Original Message -----
From: James Robertson <[hidden email]>
To: [hidden email] <[hidden email]>
Sent: Tue Oct 09 20:41:31 2007
Subject: Re: Best error notifier for Seaside?

Have a look at what I do in BottomFeeder - see package RSS-ErrorHandling in
the public store.  It's a small package; just browse it from the Published
items list.


----- Original Message -----
From: "Carl Gundel" <[hidden email]>
To: <[hidden email]>
Sent: Tuesday, October 09, 2007 10:33 PM
Subject: Best error notifier for Seaside?


> When I package my Seaside application RuntimeEmergencyNotifier is the
> error notifier that gets used by default.  Of course I don't really want
> to use this because any unhandled exceptions will cause the server to
> quit.  What would be a better choice for use with a packaged Seaside app?
>
> -Carl Gundel
> http://www.runbasic.com
>
>

When we deliver Web applications based on WTK we normally deliver a
headless server with the base and a parcel with the application - that
means when you create a new version of the application you can just put
the parcel on the server and restart the WTK server via web interface.
As a result it reloads the parcel ("Clear all of the cached data, reload
all parcels specified on the command line, and re-read server
configuration files.") and so gets the new version running without ever
having to stop the server.
The headless server can be created by the WTK Launcher menu...

Regards,
Magnus

Carl Gundel schrieb:
--
Magnus Schwarz * Senior Smalltalk Architect * mailto:[hidden email]
phone:+49 231 97599-0 * fax:+49 231 97599-20
Georg Heeg eK Dortmund
Handelsregister: Amtsgericht Dortmund  A 12812
---------------------------------------------------
PGP PUBLIC KEY BLOCK via http://www.heeg.de/~magnus