loading latest Seaside 3.01 in Gemstone

Good catch Nick ... I'll update the config first thing Monday...and fix the error handler ...

Dale
________________________________________
From: [hidden email] [[hidden email]] On Behalf Of Nick Ager [[hidden email]]
Sent: Saturday, November 13, 2010 8:51 AM
To: GemStone Seaside beta discussion
Subject: [GS/SS Beta] loading latest Seaside 3.01 in Gemstone

Hi Dale,

I've loaded the latest Seaside "3.0.1" release into a clean image with:

Gofer project load: 'Seaside30'.

I found a bug in GRTextOrBinaryCodecStream initialization which I've corrected checked into the gemstone Seaside30 repository as Grease-GemStone-Core-NickAger.28.mcz, the check-in comment reads:

corrected a typo in the method name #initalize GRTextOrBinaryCodecStream>>#initializeOn:
which stopped the initialization method being called and hence the inst var wasn't being properly initialized.

For my installation this was a critical bug which stopped GemStone producing an HTTP response - so I guess your latest ConfigurationOfSeaside30 should be updated....

I also noticed that with a clean installation of Seaside 3.0.1 the Welcome application (and I presume other default installed applications), are configured with the error handler was set to WAWalkback rather than one of the GemStone error handlers - which confuses matters if an error occurs...

Cheers

Nick

Nick,

I just took a look at the Pier app that I just loaded and the error
handler is set correctly to WARemoteDebuggingWalkbackErrorHandler.

I loaded this in to a GLASS 1.0-beta.8.4 using the following expressions:

   MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [[
     Gofer project load: 'Pier2' version: '2.0.7'.
     Gofer project
        load: 'Seaside30'
        version: '3.0.1'
        group: #('Seaside-Adaptors-FastCGI').
   ] on: Warning do: [:ex | Transcript cr; show: ex description. ex
resume ]].

How did you do your install?

I will try some other combos tomorrow...

Dale

On 11/13/2010 08:51 AM, Nick Ager wrote:

Nick,

It turns out that there was a problem with the Seaside30 configuration
file. I had made a change that "shouldn't affect anything of importance"
to the existing baseline specifications (breaking a rule to boot) which
caused the latestVersion method to return the wrong thing.

I've fixed that problem and now a clean install should work.

Thanks for tripping over that problem...

Dale

On 11/13/2010 08:51 AM, Nick Ager wrote:

Nick,

I've just released Grease1.0.1.1 and Seaside3.0.1.1 that includes your
fix plus some recent updates from Philippe and Lukas...

Dale

On 11/13/2010 08:51 AM, Nick Ager wrote: