[Pharo-project] Seaside and KomHttpServer in Pharo 1.2

Schwab,Wilhelm K bschwab at anest.ufl.edu
Fri Oct 8 08:09:34 EDT 2010


What do you do to test your newly converted Seaside apps?  Have you automated it, or is just a matter of trying everything yourself?


From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Torsten Bergmann [astares at gmx.de]
Sent: Friday, October 08, 2010 5:38 AM
To: pharo-project at lists.gforge.inria.fr; dhenrich at vmware.com
Subject: [Pharo-project] Seaside and KomHttpServer in Pharo 1.2

Hi Dale,

again I typically use my MetaSource application to
see if one can bootstrap a full seaside app in Pharo using

Gofer new
   squeaksource: 'MetaSource';
   package: 'ConfigurationOfMetaSource';

((Smalltalk at: #ConfigurationOfMetaSource) project version: '1.4') load

Works well in "Pharo 1.1." but not in "PharoCore 1.2":

In Pharo 1.2 some methods are deprecated and Seaside 3.0 still
uses ConfigurationOfKomHttpServer 1.3 instead of the newer 1.5.

So the question is: is it planned to use the newer KomHttpServer
packages in the near future for Seaside 3.0 so I can switch to
Pharo 1.2 early? Or is this planned when Pharo 1.2 is mature and


GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit
gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl

Pharo-project mailing list
Pharo-project at lists.gforge.inria.fr

More information about the Pharo-dev mailing list