Seaside packaging as a windows NT service

[PhotonDemon]

Hi All,

I have managed to package Seaside as a windows NT service. The packaging seems to be clean. I start the app with:

Code: Select all

starting
   "This is the entry point into the user code for the service.
   First register the application.  This sets the service status to
   RUNNING and establishes the callback for stopping the service application.
   Then write an entry in the event log.
   Then create and start the server object."

   AbtNtServiceInterface default
      registerService: self name stopSelector: #stopping;
      writeEventLogInformation: 1.

   [
      (WASstServerAdaptor port: 8788) start.
      WAAdmin applicationDefaults initialize.
      WAAdmin initialize; reloadApplications.
      MyRoot initialize.
   ] fork.


The line: "WAAdmin applicationDefaults initialize" solves a problem with a parent of the applicationDefaults for a development configuration being nil that resulted in a walkback. The lines: "WAAdmin initialize; reloadApplications" and "MyRoot initialize" are my attempt (a guess) to get Seaside started. But it doesn't quite make it as "Error 503 Service Unavailable" is the result in the web browser. Any help getting things going is greatly appreciated.

Lou

[joselle]

Hi,

I've packaged my seaside-image yesterday and encounter "Error 503 Service Unavailable" in my web-browser, too.

After including a logger in my startUp-method, like:

Code: Select all

         WASstServerManager default logger: (
            SstFileMessageLog new
               path: 'seaside.log';
               open;
               yourself)

I've detected the reason: WASstHttpServlet has no reference and was excluded by the packager.

My packaged image seems to work fine.

Joselle