I don't think that the server manager calls #basicStop/#basicStart on startup/shutdown (this is when you explicitly start/stop the server), only #startUp/#shutDown. I might be wrong though ... Lukas On 28 July 2011 20:50, Sven Van Caekenberghe <sven@beta9.be> wrote:
On 28 Jul 2011, at 18:31, Lukas Renggli wrote:
I guess it would be a good idea for the Seaside adaptor to do this automagically ? I'll have a look when I download your freshly backed image.
Yes, the WAServerManager should bring them up again. I suspect this is an issue with Seaside or Pharo; as this is exactly the same problem with Kom.
Now I can fix the ZnZincServerAdaptor when I add the following methods:
ZnZincServerAdaptor>>startUp    self server isNil        ifFalse: [ self server start ]
ZnZincServerAdaptor>>shutDown    self server isNil        ifFalse: [ self server stop ]
The strange thing though is that when the images comes up and I stop the server adaptor manually, the server continues to run :-S
There is something wrong, I just took the build #650 and loaded your commit Zinc-Seaside-lr.17.mcz, created a new Zn adaptor, saved the image and quit: now the image refuses to start!
Did you see #basicStart and #basicStop, these are the ones called by WAServerManager>>#start:
I am trying to figure out how this is supposed to work...
Lukas
-- Lukas Renggli www.lukas-renggli.ch
-- Lukas Renggli www.lukas-renggli.ch