Load Seaside into new Gemstone 3.1.0.4

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Load Seaside into new Gemstone 3.1.0.4

dario trussardi
Ciao,

i need to load Seaside into new Gemstone 3.1.0.4.

Into Gemstone 3.1.0.2  i work with  Seaside 3.0.7.1  and i use FastCGI which adaptor for  server web pages.

Anyone can suggest that procedure follow?

I found  this :


And i think to use :

Load Pier, Magritte, and Seaside Avoiding Out of Memory Conditions

If you'd like to install Seaside3.0, Pier and Magritte, the following expression should be used:

| autoCommit|
autoCommit
:= MCPlatformSupport autoCommit.
MCPlatformSupport autoCommit: true. "needed if loading from Topaz"
MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [[
                 
ConfigurationOfMetacello project updateProject.
                 
ConfigurationOfMetacello loadLatestVersion.
                 
Gofer project load: 'Seaside30'group: #( 'ALL').
                 
Gofer project load: 'Pier2' group: 'ALL'.
                 
Gofer project load: 'PierAddOns2' group: 'ALL'.
         
]
                 on
: Warning
                 
do: [:ex |
                         
Transcript cr; show: ex description.
                         ex resume
]].
MCPlatformSupport autoCommit: autoCommit.


it's correct ?

Thanks,

Dario
Reply | Threaded
Open this post in threaded view
|

Re: [Glass] [GS/SS Beta] Load Seaside into new Gemstone 3.1.0.4

Dale Henrichs-3
Dario,

Could you start posting to the new mailing list ([hidden email]). You have been subscribed to the new list (and you should have gotten a welcome message last week).

As of today we will no longer have control over the hosts that serve the [hidden email] mailing list so I don't know how long the old mailing list will be functional...

Dale


From: "Dario Trussardi" <[hidden email]>
To: "beta discussion Gemstone Seaside" <[hidden email]>
Sent: Sunday, June 30, 2013 3:45:03 AM
Subject: [GS/SS Beta] Load Seaside into new Gemstone 3.1.0.4

Ciao,

i need to load Seaside into new Gemstone 3.1.0.4.

Into Gemstone 3.1.0.2  i work with  Seaside 3.0.7.1  and i use FastCGI which adaptor for  server web pages.

Anyone can suggest that procedure follow?

I found  this :


And i think to use :

Load Pier, Magritte, and Seaside Avoiding Out of Memory Conditions

If you'd like to install Seaside3.0, Pier and Magritte, the following expression should be used:

| autoCommit|
autoCommit
:= MCPlatformSupport autoCommit.
MCPlatformSupport autoCommit: true. "needed if loading from Topaz"
MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [[
                 
ConfigurationOfMetacello project updateProject.
                 
ConfigurationOfMetacello loadLatestVersion.
                 
Gofer project load: 'Seaside30'group: #( 'ALL').
                 
Gofer project load: 'Pier2' group: 'ALL'.
                 
Gofer project load: 'PierAddOns2' group: 'ALL'.
         
]
                 on
: Warning
                 
do: [:ex |
                         
Transcript cr; show: ex description.
                         ex resume
]].
MCPlatformSupport autoCommit: autoCommit.


it's correct ?

Thanks,

Dario


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: Load Seaside into new Gemstone 3.1.0.4

Dale Henrichs-3
In reply to this post by dario trussardi
Dario,

There should be no change in the scripts that you use for loading your code between 3.1.0.2 and 3.1.0.4 ... the old scripts should continue to work.

Dale


From: "Dario Trussardi" <[hidden email]>
To: "beta discussion Gemstone Seaside" <[hidden email]>
Sent: Sunday, June 30, 2013 3:45:03 AM
Subject: [GS/SS Beta] Load Seaside into new Gemstone 3.1.0.4

Ciao,

i need to load Seaside into new Gemstone 3.1.0.4.

Into Gemstone 3.1.0.2  i work with  Seaside 3.0.7.1  and i use FastCGI which adaptor for  server web pages.

Anyone can suggest that procedure follow?

I found  this :


And i think to use :

Load Pier, Magritte, and Seaside Avoiding Out of Memory Conditions

If you'd like to install Seaside3.0, Pier and Magritte, the following expression should be used:

| autoCommit|
autoCommit
:= MCPlatformSupport autoCommit.
MCPlatformSupport autoCommit: true. "needed if loading from Topaz"
MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [[
                 
ConfigurationOfMetacello project updateProject.
                 
ConfigurationOfMetacello loadLatestVersion.
                 
Gofer project load: 'Seaside30'group: #( 'ALL').
                 
Gofer project load: 'Pier2' group: 'ALL'.
                 
Gofer project load: 'PierAddOns2' group: 'ALL'.
         
]
                 on
: Warning
                 
do: [:ex |
                         
Transcript cr; show: ex description.
                         ex resume
]].
MCPlatformSupport autoCommit: autoCommit.


it's correct ?

Thanks,

Dario

Reply | Threaded
Open this post in threaded view
|

Re: Load Seaside into new Gemstone 3.1.0.4

JupiterJones
In reply to this post by dario trussardi
Hi Dario,

Did you have any success getting Seaside to load in 3.1.0.4?

I keep getting:

ERROR 2010 , a MessageNotUnderstood occurred (error 2010), a MetacelloVersionConstructor does not understand  #'baseline:with:' (MessageNotUnderstood)

I believe I've updated Metacello.

If there a definitive way to load seaside into GemStone 3.1.0.4?

Cheers,

Jupiter