From kuszinger at giscom.hu  Tue Mar  1 14:30:41 2016
From: kuszinger at giscom.hu (Robert Kuszinger)
Date: Tue Mar  1 14:30:53 2016
Subject: [Seaside] form action change to external link?
In-Reply-To: <B96F91ED-26AB-4246-BA42-C4476700FF2C@stfx.eu>
References: <CAA+-=mWw_bz0QN8B+eNDADVCzvFPK5Mt6VQoApJD+Fm6yppP9g@mail.gmail.com>
	<B96F91ED-26AB-4246-BA42-C4476700FF2C@stfx.eu>
Message-ID: <CAJS2e5gbr8zEJFLfKwDmLeVDPf7h9UOfobSg7f==FhWUgP76ow@mail.gmail.com>

Hello Everyone!

I'm still working on my large file upload project on a windows server (so
ngix won't play :( ).
I have a good uploader and also technique to solve upload outside Seaside
(or VA WebCOnnection as I did before) and then come back into the session
afterwards.

But to make it I need to hack the seaside form to put my own link into the
ACTION=".....".

Here is what I did, but it seems that action is overwritten by Seaside to
its usual internal form action (understandably)


f := html form.

f with:[

   .... form creaton code here.... works well, no problem.......

].

*f action: 'http://localhost/home/html/upload_large.asp
<http://localhost/home/html/upload_large.asp>'.*

And when looking at generated page source:

<form accept-charset="utf-8" method="post" action="
*/uploader?_s=jdXt_Vzp8dKoK3M9&amp;_k=C197PyH7ka66mXVd*">


So, how to hack my own action into the form?


thanks
Robert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160301/e8a08519/attachment.htm
From alejandroinfante91 at gmail.com  Tue Mar  1 16:22:12 2016
From: alejandroinfante91 at gmail.com (Alejandro Infante)
Date: Tue Mar  1 16:22:18 2016
Subject: [Seaside] form action change to external link?
In-Reply-To: <CAJS2e5gbr8zEJFLfKwDmLeVDPf7h9UOfobSg7f==FhWUgP76ow@mail.gmail.com>
References: <CAA+-=mWw_bz0QN8B+eNDADVCzvFPK5Mt6VQoApJD+Fm6yppP9g@mail.gmail.com>
	<B96F91ED-26AB-4246-BA42-C4476700FF2C@stfx.eu>
	<CAJS2e5gbr8zEJFLfKwDmLeVDPf7h9UOfobSg7f==FhWUgP76ow@mail.gmail.com>
Message-ID: <D5511812-9D04-4D02-8CC0-48C29751E3DB@gmail.com>

Hi!
The WABrush>>with: call must be the last call to a brush. So instead of:

html form
	with: [ stuff? ];
	action: 'http://localhost/home/html/upload_large.asp <http://localhost/home/html/upload_large.asp>'

Try:

html form
	action: 'http://localhost/home/html/upload_large.asp <http://localhost/home/html/upload_large.asp>';
	with: [ stuff? ]

I have tried and it works :)

Cheers!
Alejandro

> On Mar 1, 2016, at 11:30 AM, Robert Kuszinger <kuszinger@giscom.hu> wrote:
> 
> 
> 
> Hello Everyone!
> 
> I'm still working on my large file upload project on a windows server (so ngix won't play :( ).
> I have a good uploader and also technique to solve upload outside Seaside (or VA WebCOnnection as I did before) and then come back into the session afterwards.
> 
> But to make it I need to hack the seaside form to put my own link into the ACTION=".....".
> 
> Here is what I did, but it seems that action is overwritten by Seaside to its usual internal form action (understandably)
> 
> 
> f := html form.
> 
> f with:[
> 
>    .... form creaton code here.... works well, no problem.......
> 
> ].
> 
> f action: 'http://localhost/home/html/upload_large.asp <http://localhost/home/html/upload_large.asp>'.
> 
> And when looking at generated page source:
> 
> <form accept-charset="utf-8" method="post" action="/uploader?_s=jdXt_Vzp8dKoK3M9&amp;_k=C197PyH7ka66mXVd">
> 
> 
> So, how to hack my own action into the form?
> 
> 
> thanks
> Robert
> 
> 
> 
> 
> 
> 
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160301/8a47f30a/attachment.htm
From kuszinger at giscom.hu  Tue Mar  1 16:40:49 2016
From: kuszinger at giscom.hu (Robert Kuszinger)
Date: Tue Mar  1 16:41:00 2016
Subject: [Seaside] form action change to external link?
In-Reply-To: <D5511812-9D04-4D02-8CC0-48C29751E3DB@gmail.com>
References: <CAA+-=mWw_bz0QN8B+eNDADVCzvFPK5Mt6VQoApJD+Fm6yppP9g@mail.gmail.com>
	<B96F91ED-26AB-4246-BA42-C4476700FF2C@stfx.eu>
	<CAJS2e5gbr8zEJFLfKwDmLeVDPf7h9UOfobSg7f==FhWUgP76ow@mail.gmail.com>
	<D5511812-9D04-4D02-8CC0-48C29751E3DB@gmail.com>
Message-ID: <CAJS2e5hhL-WZZ+WxCBT5pCSTg-LHwgEe-nCz9oQL5zN62E+KDw@mail.gmail.com>

Thanks!

I'll go like this.

R


Alejandro Infante <alejandroinfante91@gmail.com> ezt ?rta (id?pont: 2016.
m?rc. 1., K, 17:22):

> Hi!
> The WABrush>>with: call must be the last call to a brush. So instead of:
>
> html form
> with: [ stuff? ];
> action: *'http://localhost/home/html/upload_large.asp
> <http://localhost/home/html/upload_large.asp>'*
>
> Try:
>
> html form
> action: *'http://localhost/home/html/upload_large.asp
> <http://localhost/home/html/upload_large.asp>'*;
> with: [ stuff? ]
>
> I have tried and it works :)
>
> Cheers!
> Alejandro
>
> On Mar 1, 2016, at 11:30 AM, Robert Kuszinger <kuszinger@giscom.hu> wrote:
>
>
>
> Hello Everyone!
>
> I'm still working on my large file upload project on a windows server (so
> ngix won't play :( ).
> I have a good uploader and also technique to solve upload outside Seaside
> (or VA WebCOnnection as I did before) and then come back into the session
> afterwards.
>
> But to make it I need to hack the seaside form to put my own link into the
> ACTION=".....".
>
> Here is what I did, but it seems that action is overwritten by Seaside to
> its usual internal form action (understandably)
>
>
> f := html form.
>
> f with:[
>
>    .... form creaton code here.... works well, no problem.......
>
> ].
>
> *f action: 'http://localhost/home/html/upload_large.asp
> <http://localhost/home/html/upload_large.asp>'.*
>
> And when looking at generated page source:
>
> <form accept-charset="utf-8" method="post" action="
> */uploader?_s=jdXt_Vzp8dKoK3M9&amp;_k=C197PyH7ka66mXVd*">
>
>
> So, how to hack my own action into the form?
>
>
> thanks
> Robert
>
>
>
>
>
>
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160301/4fce09a1/attachment.htm
From hilaire at drgeo.eu  Fri Mar  4 16:07:28 2016
From: hilaire at drgeo.eu (Hilaire)
Date: Fri Mar  4 16:07:42 2016
Subject: [Seaside] Bootstrap + WATableReport
Message-ID: <nbcbs0$h9l$1@ger.gmane.org>

Hello,

Was there an attempt to mix in the Bootstrap tbsTable and the Seaside
WATableReport component?

Thanks

Hilaire

-- 
Dr. Geo
http://drgeo.eu

From stephan at stack.nl  Sat Mar  5 23:59:57 2016
From: stephan at stack.nl (Stephan Eggermont)
Date: Sun Mar  6 00:00:14 2016
Subject: [Seaside] Re: Bootstrap + WATableReport
In-Reply-To: <nbcbs0$h9l$1@ger.gmane.org>
References: <nbcbs0$h9l$1@ger.gmane.org>
Message-ID: <nbfrtt$r83$1@ger.gmane.org>

On 04/03/16 17:07, Hilaire wrote:
> Hello,
>
> Was there an attempt to mix in the Bootstrap tbsTable and the Seaside
> WATableReport component?

In QCMagritte we have a MAReport based one: QCBMagritteReport.
And there is TBSMagritteReport in Bootstrap-Magritte-Core

Stephan


From hilaire at drgeo.eu  Sun Mar  6 09:03:23 2016
From: hilaire at drgeo.eu (Hilaire)
Date: Sun Mar  6 09:05:06 2016
Subject: [Seaside] Re: Bootstrap + WATableReport
In-Reply-To: <nbfrtt$r83$1@ger.gmane.org>
References: <nbcbs0$h9l$1@ger.gmane.org> <nbfrtt$r83$1@ger.gmane.org>
Message-ID: <nbgror$98e$2@ger.gmane.org>

Thanks for the update.

Hum, yes, I finally subclass TableReport and only two methods need some
edit.

Hilaire

Le 06/03/2016 00:59, Stephan Eggermont a ?crit :
>>
> 
> In QCMagritte we have a MAReport based one: QCBMagritteReport.
> And there is TBSMagritteReport in Bootstrap-Magritte-Core
> 
> Stephan

-- 
Dr. Geo
http://drgeo.eu

From bobn at rogers.com  Sat Mar 12 15:03:36 2016
From: bobn at rogers.com (bobn@rogers.com)
Date: Sat Mar 12 15:05:18 2016
Subject: [Seaside] size limit with onInput: and jQuery callback:value:
References: <1554090642.298775.1457795016572.JavaMail.yahoo.ref@mail.yahoo.com>
Message-ID: <1554090642.298775.1457795016572.JavaMail.yahoo@mail.yahoo.com>

Hello,We're seeing a problem where entering large text into a textArea causes the component to no longer be responsive. In our case, using VW 7.10.1, the problem only happens if we're using a reverse proxy (either HA Proxy or Apache). To debug the problem, I set up a development VW image running Seaside on port 7771 and HA Proxy on another server, redirecting port 80 to 7771. I then connected two sessions: one directly to the Seaside image, and one by way of the HA Proxy server. The directly connected session works fine, no limit on entered text that I can see. HA Proxy session has problems if the text entered is around 3500 (the exact number varies).?
Cincom suggested putting a break into?SiouX.NetHttpResponder>>createRequestFrom: which shows that jQuery callback from onInput is not being sent.
So, to isolate the problem (and get some help on this forum), I coded an example in a new Pharo 4.0 image, with Seaside 3.1. This example, however, has the same symptom as my VW + HA Proxy configuration: once the entered text is past around 3500, the onInput ajax callback no longer responds. I'm hoping someone can shed some light on this problem... I have some unhappy users.?
renderContentOn: html
 html heading: 'Text Editor'. html textArea style: 'width: 820px; height: 200px; ';? value: self enteredText; onInput: ( html jQuery ajax? callback: [:stringValue | self enteredText: stringValue] value: html jQuery this value); onBlur: ( (html jQuery id: 'displayedText') load html: [:renderer |? self renderEnteredTextOn: renderer]). html horizontalRule. self renderEnteredTextOn: html.

renderEnteredTextOn: html
 html div id: 'displayedText'; with: [? html big: 'size: ', self enteredText size printString; break. html text: self enteredText]

Thanks,?
Bob NemecHTS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160312/63ed4675/attachment.htm
From johan at inceptive.be  Sun Mar 13 09:02:15 2016
From: johan at inceptive.be (Johan Brichau)
Date: Sun Mar 13 09:02:20 2016
Subject: [Seaside] size limit with onInput: and jQuery callback:value:
In-Reply-To: <1554090642.298775.1457795016572.JavaMail.yahoo@mail.yahoo.com>
References: <1554090642.298775.1457795016572.JavaMail.yahoo.ref@mail.yahoo.com>
	<1554090642.298775.1457795016572.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <5D6370D6-CE4A-4103-95E3-19B1C083F4FA@inceptive.be>

Hi Bob,

Have you tried setting the ajax request to type POST instead of the (standard) GET?

		onInput: (
			html jQuery ajax 
				type: ?POST?;
				callback: [:stringValue | self enteredText: stringValue]
				value: html jQuery this value);

Web servers (and proxies) often set a maximum url length. Since a GET request encodes both the Seaside callback number and the entered text into the url, it will most probably be truncated by the web server.
In most cases I observed, it was only the entered text that was truncated, but depending on the position of the parameters, it may also truncate the Seaside callback number. As a result, the callback will not be invoked.

I did not try your example, so if this is not the case, ping me back and I will take a closer look.

Also: I often ask myself why people copy/paste entire documents in textareas :))

Hope it helps
Johan

> On 12 Mar 2016, at 16:03, bobn@rogers.com wrote:
> 
> Hello,
> We're seeing a problem where entering large text into a textArea causes the component to no longer be responsive. In our case, using VW 7.10.1, the problem only happens if we're using a reverse proxy (either HA Proxy or Apache). To debug the problem, I set up a development VW image running Seaside on port 7771 and HA Proxy on another server, redirecting port 80 to 7771. I then connected two sessions: one directly to the Seaside image, and one by way of the HA Proxy server. The directly connected session works fine, no limit on entered text that I can see. HA Proxy session has problems if the text entered is around 3500 (the exact number varies). 
> 
> Cincom suggested putting a break into SiouX.NetHttpResponder>>createRequestFrom: which shows that jQuery callback from onInput is not being sent.
> 
> So, to isolate the problem (and get some help on this forum), I coded an example in a new Pharo 4.0 image, with Seaside 3.1. This example, however, has the same symptom as my VW + HA Proxy configuration: once the entered text is past around 3500, the onInput ajax callback no longer responds. I'm hoping someone can shed some light on this problem... I have some unhappy users. 
> 
> renderContentOn: html
> 
> 	html heading: 'Text Editor'.
> 	html textArea
> 		style: 'width: 820px; height: 200px; '; 
> 		value: self enteredText;
> 		onInput: (
> 			html jQuery ajax 
> 				callback: [:stringValue | self enteredText: stringValue]
> 				value: html jQuery this value);
> 		onBlur: (
> 			(html jQuery id: 'displayedText') load html: [:renderer | 
> 				self renderEnteredTextOn: renderer]).
> 	html horizontalRule.
> 	self renderEnteredTextOn: html.
> 
> 
> renderEnteredTextOn: html
> 
> 	html div id: 'displayedText'; with: [ 
> 		html big: 'size: ', self enteredText size printString; break.
> 		html text: self enteredText]
> 
> 
> Thanks, 
> 
> Bob Nemec
> HTS
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160313/9a836149/attachment.htm
From bobn at rogers.com  Sun Mar 13 15:40:14 2016
From: bobn at rogers.com (bobn@rogers.com)
Date: Sun Mar 13 15:40:16 2016
Subject: [Seaside] size limit with onInput: and jQuery callback:value:
In-Reply-To: <5D6370D6-CE4A-4103-95E3-19B1C083F4FA@inceptive.be>
References: <5D6370D6-CE4A-4103-95E3-19B1C083F4FA@inceptive.be>
Message-ID: <223763481.665491.1457883614060.JavaMail.yahoo@mail.yahoo.com>

Adding type: 'POST' did indeed fix the problem, in both the Pharo image, and in VW + HA Proxy.?Interesting that VW without HA Proxy worked fine (made for some fun diagnostics).
Much thanks,Bob 

    On Sunday, March 13, 2016 5:02 AM, Johan Brichau <johan@inceptive.be> wrote:
 

 Hi Bob,
Have you tried setting the ajax request to type POST instead of the (standard) GET?
 onInput: ( html jQuery ajax? type: ?POST?; callback: [:stringValue | self enteredText: stringValue] value: html jQuery this value);
Web servers (and proxies) often set a maximum url length. Since a GET request encodes both the Seaside callback number and the entered text into the url, it will most probably be truncated by the web server.In most cases I observed, it was only the entered text that was truncated, but depending on the position of the parameters, it may also truncate the Seaside callback number. As a result, the callback will not be invoked.
I did not try your example, so if this is not the case, ping me back and I will take a closer look.
Also: I often ask myself why people copy/paste entire documents in textareas :))
Hope it helpsJohan

On 12 Mar 2016, at 16:03, bobn@rogers.com wrote:
Hello,We're seeing a problem where entering large text into a textArea causes the component to no longer be responsive. In our case, using VW 7.10.1, the problem only happens if we're using a reverse proxy (either HA Proxy or Apache). To debug the problem, I set up a development VW image running Seaside on port 7771 and HA Proxy on another server, redirecting port 80 to 7771. I then connected two sessions: one directly to the Seaside image, and one by way of the HA Proxy server. The directly connected session works fine, no limit on entered text that I can see. HA Proxy session has problems if the text entered is around 3500 (the exact number varies).?
Cincom suggested putting a break into?SiouX.NetHttpResponder>>createRequestFrom: which shows that jQuery callback from onInput is not being sent.
So, to isolate the problem (and get some help on this forum), I coded an example in a new Pharo 4.0 image, with Seaside 3.1. This example, however, has the same symptom as my VW + HA Proxy configuration: once the entered text is past around 3500, the onInput ajax callback no longer responds. I'm hoping someone can shed some light on this problem... I have some unhappy users.?
renderContentOn: html
 html heading: 'Text Editor'. html textArea style: 'width: 820px; height: 200px; ';? value: self enteredText; onInput: ( html jQuery ajax? callback: [:stringValue | self enteredText: stringValue] value: html jQuery this value); onBlur: ( (html jQuery id: 'displayedText') load html: [:renderer |? self renderEnteredTextOn: renderer]). html horizontalRule. self renderEnteredTextOn: html.

renderEnteredTextOn: html
 html div id: 'displayedText'; with: [? html big: 'size: ', self enteredText size printString; break. html text: self enteredText]

Thanks,?
Bob NemecHTS_______________________________________________
seaside mailing list
seaside@lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160313/3dfeaef7/attachment-0001.htm
From johan at inceptive.be  Sun Mar 13 16:28:37 2016
From: johan at inceptive.be (Johan Brichau)
Date: Sun Mar 13 16:28:41 2016
Subject: [Seaside] size limit with onInput: and jQuery callback:value:
In-Reply-To: <223763481.665491.1457883614060.JavaMail.yahoo@mail.yahoo.com>
References: <5D6370D6-CE4A-4103-95E3-19B1C083F4FA@inceptive.be>
	<223763481.665491.1457883614060.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <509D0EBC-C914-446E-BF92-9DA66B292EC2@inceptive.be>


> On 13 Mar 2016, at 16:40, <bobn@rogers.com> <bobn@rogers.com> wrote:
> 
> Interesting that VW without HA Proxy worked fine (made for some fun diagnostics).

The web server in VW probably does not limit the size of the url.

Web browsers typically do this too but the limits currently are ridiculously high. 
Both NGINX and Zinc have settings to set the limit.

Anyway, glad you can make your users happy again 

cheers
Johan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160313/09bdb2f1/attachment.htm
From jkott at image-ware.com  Mon Mar 14 06:03:07 2016
From: jkott at image-ware.com (Jerry Kott)
Date: Mon Mar 14 06:03:13 2016
Subject: [Seaside] size limit with onInput: and jQuery callback:value:
In-Reply-To: <509D0EBC-C914-446E-BF92-9DA66B292EC2@inceptive.be>
References: <5D6370D6-CE4A-4103-95E3-19B1C083F4FA@inceptive.be>
	<223763481.665491.1457883614060.JavaMail.yahoo@mail.yahoo.com>
	<509D0EBC-C914-446E-BF92-9DA66B292EC2@inceptive.be>
Message-ID: <2FE3F583-BAF6-497C-9802-ED9B2C8A29DA@image-ware.com>

Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160313/551e9c7b/signature.pgp
From brauer at nordakademie.de  Sat Mar 19 13:59:07 2016
From: brauer at nordakademie.de (Johannes Brauer)
Date: Sat Mar 19 13:59:11 2016
Subject: [Seaside] How do I reset the Seaside administrator password?
 (Pharo2, Seaside 3.0.10)
Message-ID: <F6731127-DFCD-45D2-A8C0-862FEDFB7E81@nordakademie.de>

Hi,
I lost my administrator password in a Pharo2-Seaside 3.0 image. In the Seaside-FAQs I found:


(WADispatcher default entryPoints at: 'config')
        preferenceAt: #login put: 'new id'.
(WADispatcher default entryPoints at: 'config')
        preferenceAt: #password put: 'new password'.

Both expressions don?t work because enttyPoints is not understood. What works is


(WADispatcher default entryPointAt: 'config')
        preferenceAt: #login put: 'new id'.

But If I try the same for password

(WADispatcher default entryPointAt: 'config')
        preferenceAt: #password put: 'new id'.

I get the exception WAAttributeNotFound, i. e. #password is not found.

What can I do?

Johannes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160319/b50f92bb/attachment.htm
From david at tibbe.info  Sun Mar 20 12:20:40 2016
From: david at tibbe.info (David Tibbe)
Date: Sun Mar 20 12:20:55 2016
Subject: [Seaside] How do I reset the Seaside administrator password?
	(Pharo2, Seaside 3.0.10)
In-Reply-To: <F6731127-DFCD-45D2-A8C0-862FEDFB7E81@nordakademie.de>
References: <F6731127-DFCD-45D2-A8C0-862FEDFB7E81@nordakademie.de>
Message-ID: <56EE9598.8080302@tibbe.info>

Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 834 bytes
Desc: OpenPGP digital signature
Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160320/b612cc7f/signature-0001.pgp
From brauer at nordakademie.de  Sun Mar 20 16:43:10 2016
From: brauer at nordakademie.de (Johannes Brauer)
Date: Sun Mar 20 16:43:13 2016
Subject: [Seaside] How do I reset the Seaside administrator password?
	(Pharo2, Seaside 3.0.10)
In-Reply-To: <56EE9598.8080302@tibbe.info>
References: <F6731127-DFCD-45D2-A8C0-862FEDFB7E81@nordakademie.de>
	<56EE9598.8080302@tibbe.info>
Message-ID: <C6B32423-A7F8-4919-B81A-3DA6446AA078@nordakademie.de>

thanks a lot, David!

Johannes
> Am 20.03.2016 um 13:20 schrieb David Tibbe <david@tibbe.info>:
> 
> Hi Johannes,
> 
> the preference is named #passwordHash. As the name indicates, the
> password is stored in non-plaintext, so you have to use the following:
> 
> (WADispatcher default entryPointAt: 'config')
> 	preferenceAt: #passwordHash put: (GRPlatform current secureHashFor:
> 'new id').
> 
> 
> In Seaside 3.1, #entryPointAt: will not work anymore, so you may use
> #handlerAt: instead.
> 
> BR,
>  David
> 
> 
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

From johan at inceptive.be  Sun Mar 20 18:46:47 2016
From: johan at inceptive.be (Johan Brichau)
Date: Sun Mar 20 18:46:51 2016
Subject: [Seaside] Seaside 3.1 and 3.2 in Pharo 5
Message-ID: <A417D39C-4FC3-4D98-955A-7BB411DEE1F3@inceptive.be>

Hi Seasiders,

If you are looking to use Seaside in Pharo 5, please go ahead and let us know if you run into any issues.
Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are green.

Also: I know the finalization of 3.2.0 is long overdue, so news about that is coming soon.

Johan
From tudor at tudorgirba.com  Sun Mar 20 18:50:14 2016
From: tudor at tudorgirba.com (Tudor Girba)
Date: Sun Mar 20 18:50:13 2016
Subject: [Seaside] Seaside 3.1 and 3.2 in Pharo 5
In-Reply-To: <A417D39C-4FC3-4D98-955A-7BB411DEE1F3@inceptive.be>
References: <A417D39C-4FC3-4D98-955A-7BB411DEE1F3@inceptive.be>
Message-ID: <595FE7F1-A76F-4F4E-B19E-1F2119E26FA4@tudorgirba.com>

Hi Johan,

Thanks a lot for this effort!

Doru


> On Mar 20, 2016, at 7:46 PM, Johan Brichau <johan@inceptive.be> wrote:
> 
> Hi Seasiders,
> 
> If you are looking to use Seaside in Pharo 5, please go ahead and let us know if you run into any issues.
> Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are green.
> 
> Also: I know the finalization of 3.2.0 is long overdue, so news about that is coming soon.
> 
> Johan_______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

--
www.tudorgirba.com
www.feenk.com

"One cannot do more than one can do."




From pdebruic at gmail.com  Thu Mar 24 04:36:10 2016
From: pdebruic at gmail.com (Paul DeBruicker)
Date: Thu Mar 24 05:05:48 2016
Subject: [Seaside] Re: Cannot load Seaside anymore in a just-migrated
 GemStone [WAS] Re: [Glass] Zinc 2.4.3 on Gemstone
In-Reply-To: <CAA+-=mUkoMGR3KEkR8+VOW3-Wc3FOawQyiv-JTqKDCHJO-fudw@mail.gmail.com>
References: <CAA+-=mUkoMGR3KEkR8+VOW3-Wc3FOawQyiv-JTqKDCHJO-fudw@mail.gmail.com>
Message-ID: <1458794170458-4886222.post@n4.nabble.com>

Hi Mariano,


I just ran into this issue.  Did you end up finding a solution?


Thanks

Paul



Mariano Martinez Peck wrote
> On Thu, Oct 15, 2015 at 4:25 PM, Mariano Martinez Peck <

> marianopeck@

>> wrote:
> 
>> Hi guys,
>>
>> I have a weird scenario I cannot solve. I am trying to load my app code
>> (together with all it's dependencies) in a just migrated stone (from
>> GemStone 3.1.0.4 to GemStone 3.2.9). I performed all the steps of the
>> migration.  Yet, I have an error, pasted below. However, if I run the
>> same
>> code to load my app in a fresh 3.2.9 extent, that works perfectly. It
>> only
>> fails in my migrated (from 3.1.0.4) stone.
>>
>> The problem is in
>>
>> WAWalkbackErrorHandler class >> initialize
>> WAAdmin applicationExceptionHandlingDefaults at: #exceptionHandler put:
>> self
>>
>> It fails because the
>>
>> WAConfiguration >> attributeAt: aSymbol
>> ^ self attributeAt: aSymbol ifAbsent: [ WAAttributeNotFound
>> signalWithKey:
>> aSymbol ]
>>
>> gives a key not found.
>>
>> I did a search  in the mailing list and found related threads:
>>
>> http://forum.world.st/Glass-Zinc-2-4-3-on-Gemstone-td4759789.html#a4759875
>> https://github.com/seasidest/seaside/issues/643
>>
>> But none show a solution.
>>
>> And yes, it is obvious it will fail because:
>>
>> WAAdmin applicationExceptionHandlingDefaults allAttributes ->
>>  anIdentityDictionary( )
>>
>> Also, as you can see, the result of WAAdmin
>> applicationExceptionHandlingDefaults has no parent or anything:
>>
>> Inspect aWASharedConfiguration/
>> --------------------
>> .                     -> aWASharedConfiguration
>> (class)@              -> WASharedConfiguration
>> (oop)@                -> 1169561601
>> (committed)@          -> true
>> cachedSearchContexts@ -> anIdentityDictionary(
>> #'exceptionHandler'->aWAAttributeSearchContext)
>> expressions@          -> aDictionary( )
>> name@                 -> 'Application Exception Handling Defaults'
>> parents@              -> anOrderedCollection( )
>>
>>
>> I even tried the re-initialization of Seaside as provided by Bruno the
>> other day:
>>
>> WAAdmin unregister: 'reps'.
>> WAAdmin unregister: 'advisors'.
>> WAAdmin unregister: 'clients'.
>>
>> WAGemStoneProductionErrorHandler  initialize.
>> WAWalkbackErrorHandler initialize.
>> WARemoteDebuggingWalkbackErrorHandler initialize.
>>
>> [
>>    WADispatcher default.
>>    WASystemConfiguration allSubclasses
>>      do: [ :each | each instance buildDescription ] ]
>>      ensure: [ System commitTransaction ] .
>>
>>
>> Still, same error.
>>
>>
>> Any clues? Is there  way I can re-initialize all Seaside?
>>
>>
>> This is the stack:
>>
>> aTDDebugger
>> --------------------
>> 1. WAAttributeNotFound(AbstractException)>>_signalWith: @6 line 25
>> 2. WAAttributeNotFound(AbstractException)>>signal @2 line 47
>> 3. WAAttributeNotFound class>>signalWithKey: @4 line 4
>> 4. [] in ExecBlock0(WAConfiguration)>>attributeAt: @2 line 2
>> 5. IdentityDictionary>>at:ifAbsent: @5 line 8
>> 6. WASharedConfiguration(WAConfiguration)>>attributeAt:ifAbsent: @3 line
>> 2
>> 7. WASharedConfiguration(WAConfiguration)>>attributeAt: @2 line 2
>> 8. WASharedConfiguration(WAUserConfiguration)>>at:put: @2 line 7
>> 9. WAWalkbackErrorHandler class>>initialize @3 line 2
>> 10. MCMethodDefinition>>postload @11 line 6
>> 11. MCMethodDefinition(MCDefinition)>>postloadOver: @2 line 2
>> 12. [] in MCPackageLoader>>basicLoad @3 line 48
>> 13. OrderedCollection(Collection)>>do: @5 line 10
>> 14. OrderedCollection(Collection)>>do:displayingProgress: @2 line 3
>> 15. [] in MCPackageLoader>>basicLoad @15 line 48
>> 16. MCPackageLoader(ExecBlock)>>on:do: @3 line 42
>> 17. [] in MCPackageLoader>>basicLoad @2 line 49
>> 18. MCPackageLoader(ExecBlock)>>ensure: @2 line 12
>> 19. MCPackageLoader>>basicLoad @11 line 51
>> 20. [] in MCPackageLoader>>loadWithNameLike: @2 line 4
>> 21. [] in ExecBlock0(MCPackageLoader)>>useChangeSetNamed:during: @2 line
>> 9
>> 22. ExecBlock0(ExecBlock)>>ensure: @2 line 12
>> 23. MCPackageLoader>>useChangeSetNamed:during: @9 line 9
>> 24. MCPackageLoader>>useNewChangeSetNamedLike:during: @3 line 2
>> 25. MCPackageLoader>>loadWithNameLike: @6 line 4
>> 26. MCVersionLoader>>load @9 line 6
>> 27. MetacelloGoferLoad(GoferLoad)>>execute @6 line 3
>> 28. [] in
>> MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
>> @5 line 17
>> 29. [] in
>> MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
>> @14 line 21
>> 30. MetacelloGemStonePlatform(MetacelloPlatform)>>do:displaying: @2 line
>> 3
>> 31.
>> MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
>> @7 line 5
>> 32.
>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadPackageDirective:gofer:
>> @4 line 4
>> 33. MetacelloPackageLoadDirective>>loadUsing:gofer: @2 line 3
>> 34. [] in
>> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>> @2 line 3
>> 35. OrderedCollection(Collection)>>do: @5 line 10
>> 36.
>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>> @3 line 3
>> 37. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>> 38. [] in
>> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>> @2 line 3
>> 39. OrderedCollection(Collection)>>do: @5 line 10
>> 40.
>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>> @3 line 3
>> 41. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>> 42. [] in
>> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>> @2 line 3
>> 43. OrderedCollection(Collection)>>do: @5 line 10
>> 44.
>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>> @3 line 3
>> 45. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>> 46. [] in
>> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>> @2 line 3
>> 47. OrderedCollection(Collection)>>do: @5 line 10
>> 48.
>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>> @3 line 3
>> 49. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>> 50. [] in
>> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>> @2 line 3
>> 51. OrderedCollection(Collection)>>do: @5 line 10
>> 52.
>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>> @3 line 3
>> 53. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>> 54.
>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadWithPolicy:
>> @7 line 7
>> 55. MetacelloLoaderPolicy>>load @6 line 4
>> 56. MetacelloFetchingMCSpecLoader>>doLoad @4 line 3
>> 57. [] in ExecBlock0(MetacelloMCVersion)>>doLoadRequiredFromArray: @2
>> line
>> 12
>> 58. MetacelloGemStonePlatform(MetacelloPlatform)>>do:displaying: @2 line
>> 3
>> 59. [] in MetacelloMCVersion>>doLoadRequiredFromArray: @7 line 12
>> 60. MetacelloMCVersion(ExecBlock)>>ensure: @2 line 12
>> 61. MetacelloMCVersion>>doLoadRequiredFromArray: @22 line 16
>> 62. Array(Collection)>>loadRequiredForMetacelloMCVersion: @2 line 3
>> 63. MetacelloMCVersion>>load: @2 line 3
>> 64. [] in
>> MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade:
>> @10 line 16
>> 65. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>> 66. [] in MetacelloScriptEngine>>handleNotificationsForAction: @6 line 6
>> 67. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>> 68. [] in MetacelloScriptEngine>>handleNotificationsForAction: @4 line 14
>> 69. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>> 70. [] in MetacelloScriptEngine>>handleNotificationsForAction: @2 line 20
>> 71. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>> 72. MetacelloScriptEngine>>handleNotificationsForAction: @2 line 24
>> 73. [] in
>> MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade:
>> @2 line 5
>> 74. MetacelloScriptEngine(ExecBlock)>>ensure: @2 line 12
>> 75. MetacelloProjectRegistration class>>copyRegistryRestoreOnErrorWhile:
>> @8 line 14
>> 76. MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade: @2
>> line 3
>> 77. MetacelloScriptEngine>>load: @2 line 3
>> 78. [] in MetacelloScriptApiExecutor(MetacelloScriptExecutor)>>execute:
>> @11 line 15
>> 79. [] in MetacelloScriptApiExecutor>>executeString:do: @5 line 6
>> 80. Array(Collection)>>do: @5 line 10
>> 81. MetacelloScriptApiExecutor>>executeString:do: @6 line 4
>> 82. String>>execute:against: @2 line 2
>> 83. MetacelloScriptApiExecutor(MetacelloScriptExecutor)>>execute: @6 line
>> 9
>> 84. Metacello>>execute:args: @8 line 5
>> 85. Metacello>>load: @2 line 2
>> 86. [] in Executed Code
>> 87. ExecBlock0(ExecBlock)>>ensure: @2 line 12
>> 88. Executed Code
>> 89. String(CharacterCollection)>>evaluateIn:symbolList:literalVars: @4
>> line 13
>> 90.
>> TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>evaluateString:
>> @5 line 3
>> 91.
>> TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>doItMenuAction:selectedText:
>> @2 line 2
>> 92.
>> TDWorkspaceClientElementBuilder(TDWindowBuilder)>>handleMenuActions:listElement:actionArg:
>> @12 line 10
>> 93. [] in
>> TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>menuActionBlock
>> @6 line 8
>> 94.
>> TDWorkspaceClientElementBuilder(ExecBlock)>>value:value:value:value:value:
>> @2 line 11
>> 95. GsNMethod class>>_gsReturnToC @1 line 1
>>
>>
>> Thanks in advance for any help.
>>
>> On Thu, Oct 15, 2015 at 1:40 PM, Gerhard Obermann &lt;

> obi068@

> &gt;
>> wrote:
>>
>>> Hi,
>>>
>>> Not really, i only found the following in my notes.
>>>
>>> HTH
>>> Gerhard
>>>
>>>
>>>
>>>    -
>>>
>>>    Load Seaside 3.1.x but don?t initialize Seaside Classes
>>>
>>>
>>> | performInitialization |
>>>
>>> performInitialization := #().
>>>
>>> [
>>>
>>> GsDeployer deploy: [  Metacello new
>>>
>>>    baseline: 'Seaside3';
>>>
>>>    repository: 'github://glassdb/Seaside31:gemstone3.1/repository';
>>>
>>>    load: 'CI'].
>>>
>>> ] on: MCPerformPostloadNotification do: [:ex |
>>>
>>>           (performInitialization includes: ex postloadClass
>>> theNonMetaClass name)
>>>
>>>             ifTrue: [
>>>
>>>               "perform initialization"
>>>
>>>               ex resume: true ]
>>>
>>>             ifFalse: [
>>>
>>>               GsFile gciLogServer: ' Skip ', ex postloadClass name
>>> asString, ' initialization.'.
>>>
>>>                ex resume: false ] ]
>>>
>>>
>>> On Thu, Oct 15, 2015 at 5:47 PM, Mariano Martinez Peck <
>>> 

> marianopeck@

>> wrote:
>>>
>>>> Hi Gerhard,
>>>>
>>>> I am getting the exact same issue. Do you remember what you did to fix
>>>> it?
>>>>
>>>> Thanks,
>>>>
>>>> On Wed, May 21, 2014 at 10:39 AM, Gerhard Obermann &lt;

> obi068@

> &gt;
>>>> wrote:
>>>>
>>>>> Hi Dale!
>>>>>
>>>>> I think as soon as I can load the stuff in my upgraded 3.2. DB, i can
>>>>> test and contribute to zink and/or Glass / Seaside 3.1.
>>>>> If it wont work until tomorrow i have to stay on 3.1.0.5 for the next
>>>>> few months at least.
>>>>>
>>>>> At the moment i am trying to load Seaside 3.1.1 with
>>>>> PS: To be able to load this i have loaded the Baseline packages
>>>>> BaselineOfGLASS1,
>>>>> BaselineOfSeaside3 , BaselineOfZinc manually from my forked GIT clone.
>>>>>
>>>>> GsDeployer deploy: [
>>>>>   Metacello new
>>>>>     configuration: 'Grease';
>>>>>     repository: '
>>>>> http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>>>>>     get.
>>>>>
>>>>>   "Load Seaside31"
>>>>> GsDeployer deploy: [
>>>>>   Metacello new
>>>>>     baseline: 'Seaside3';
>>>>>     repository: 'github://glassdb/Seaside31:gemstone3.1/repository';
>>>>>     load: 'CI'].
>>>>>
>>>>>
>>>>> Not sure if i need to load  Metacello new
>>>>>     baseline: 'GLASS1';
>>>>>     repository: 'github://glassdb/glass:master/repository';
>>>>>     load.
>>>>> after the upgrade.
>>>>>
>>>>> What is the difference between
>>>>>   (ConfigurationOfGLASS project version: '1.0-beta.9.1') load
>>>>> and
>>>>>  Metacello new
>>>>>     baseline: 'GLASS1';
>>>>>     repository: 'github://glassdb/glass:master/repository';
>>>>>     load.
>>>>>
>>>>> *The load of the Seaside package failed with the init of *
>>>>> *WAWalkbackErrorHandler => initialize*
>>>>> * WAAdmin applicationExceptionHandlingDefaults at: #exceptionHandler
>>>>> put: self*
>>>>>
>>>>> [1] WAAttributeNotFound (AbstractException) >> _signalWith:
>>>>> inCextensionArg: nil
>>>>> res: nil
>>>>> .t1: a WAAttributeNotFound occurred (error 2710)
>>>>> receiver: a WAAttributeNotFound occurred (error 2710)
>>>>> [2] WAAttributeNotFound (AbstractException) >> signal
>>>>> receiver: a WAAttributeNotFound occurred (error 2710)
>>>>> [3] WAAttributeNotFound class >> signalWithKey:
>>>>> aSymbol: #'exceptionHandler'
>>>>> receiver: WAAttributeNotFound
>>>>> [4] [] in  ExecBlock0 (WAConfiguration) >> attributeAt:
>>>>> aSymbol: #'exceptionHandler'
>>>>> receiver: nil
>>>>> [5] IdentityDictionary >> at:ifAbsent:
>>>>> aKey: #'exceptionHandler'
>>>>> aBlock: anExecBlock0
>>>>> anAssoc: nil
>>>>> .t1: anExecBlock0
>>>>> receiver: anIdentityDictionary( )
>>>>> [6] WASharedConfiguration (WAConfiguration) >> attributeAt:ifAbsent:
>>>>> aSymbol: #'exceptionHandler'
>>>>> aBlock: anExecBlock0
>>>>> receiver: aWASharedConfiguration
>>>>> [7] WASharedConfiguration (WAConfiguration) >> attributeAt:
>>>>> aSymbol: #'exceptionHandler'
>>>>> aSymbol: #'exceptionHandler'
>>>>> receiver: aWASharedConfiguration
>>>>> [8] WASharedConfiguration (WAUserConfiguration) >> at:put:
>>>>> aSymbol: #'exceptionHandler'
>>>>> anObject: WAWalkbackErrorHandler
>>>>> receiver: aWASharedConfiguration
>>>>> [9] WAWalkbackErrorHandler class >> initialize
>>>>> receiver: WAWalkbackErrorHandler
>>>>> [10] MCMethodDefinition >> postload
>>>>> receiver: aMCMethodDefinition(WAWalkbackErrorHandler
>>>>> class>>initialize)
>>>>>
>>>>>
>>>>> Transcript:
>>>>> Fetched -> FastCGIPool-dkh.2 ---
>>>>> http://seaside.gemstone.com/ss/fastcgi
>>>>> --- http://seaside.gemstone.com/ss/fastcgiredirecting to
>>>>> http://seaside.gemtalksystems.com/ss/fastcgi/FastCGI-dkh.33.mcz
>>>>>
>>>>> Fetched -> FastCGI-dkh.33 --- http://seaside.gemstone.com/ss/fastcgi
>>>>> --- http://seaside.gemstone.com/ss/fastcgi
>>>>> Fetched -> Seaside-Adaptors-FastCGI-dkh.26 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository
>>>>> Loaded -> Grease-Core-JohanBrichau.86 ---
>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>>>>> Loaded -> Grease-GemStone-Core-JohanBrichau.52 ---
>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>>>>> Evaluated -> Grease-GemStone-Core >> initializeTransactionMutex1051
>>>>> Loaded -> Seaside-Core.gemstone-JohanBrichau.815 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-GemStone300-Core-DaleHenrichs.4 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-GemStone-Core-JohanBrichau.66 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-GemStone-Basic-Development-JohanBrichau.29 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Grease-Tests-Core-JohanBrichau.95 ---
>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>>>>> Loaded -> Grease-Tests-GemStone-Core-dkh.14 ---
>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>>>>> Loaded -> Seaside-Component-pmm.101 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-Canvas-pmm.127 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-Email-pmm.25 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-GemStone-Email-JohanBrichau.14 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-InternetExplorer-pmm.7 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-Session.gemstone-JohanBrichau.169 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-GemStone-Session-DaleHenrichs.3 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-RenderLoop-pmm.96 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-Tools-Core.gemstone-dkh.23 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-Flow-pmm.24 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-Examples-pmm.24 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-Widgets-StephanEggermont.35 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-GemStone-Tools-Production-JohanBrichau.15 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-Tools-Web-pmm.119 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>> Loaded -> Seaside-GemStone-Tools-Web-DaleHenrichs.4 ---
>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, May 21, 2014 at 3:06 PM, Dale Henrichs <
>>>>> 

> dale.henrichs@

>> wrote:
>>>>>
>>>>>> Marching Orders! Very good ...
>>>>>>
>>>>>> Johan, Gerhard, et. al., I want to follow your lead and fill in where
>>>>>> the work is needed ...
>>>>>>
>>>>>> Do you guys think that getting Seaside/Zinc/etc. ported to
>>>>>> GemStone3.2
>>>>>> takes precedence over getting Zinc running on GemStone3.1?
>>>>>>
>>>>>> I can take a crack at solving Gerhard's Seaside3.1 loading error, but
>>>>>> Zinc has been on the brink for so long, maybe I should hit it hard
>>>>>> and get
>>>>>> the tests passing in GemStone 3.1 (encoding issues are right up my
>>>>>> alley:)?
>>>>>>
>>>>>> If there are other outstanding problems that folks are looking at
>>>>>> they
>>>>>> can be added into the mix...
>>>>>>
>>>>>> Dale
>>>>>>
>>>>>>
>>>>>> On Tue, May 20, 2014 at 10:42 PM, Johan Brichau &lt;

> johan@

> &gt;
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I have been tampering off and on over the last few months to make
>>>>>>> Zinc 2.4.3 work in Gemstone.
>>>>>>>
>>>>>>> I made a pull request [1] with my changes, though not all tests are
>>>>>>> passing and since most of the changes had to do with encoding, byte
>>>>>>> arrays
>>>>>>> vs strings, multibyte strings, etc... I really need someone to take
>>>>>>> a look
>>>>>>> at them. Also, the pace is quite slow by myself ;-)
>>>>>>>
>>>>>>> This email is just to make sure that the pull request does not go
>>>>>>> unnoticed for someone wanting to take up work on the port.
>>>>>>>
>>>>>>> cheers!
>>>>>>> Johan
>>>>>>>
>>>>>>> [1] https://github.com/glassdb/zinc/pull/48
>>>>>>> _______________________________________________
>>>>>>> Glass mailing list
>>>>>>> 

> Glass@.gemtalksystems

>>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Glass mailing list
>>>>>> 

> Glass@.gemtalksystems

>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Glass mailing list
>>>>> 

> Glass@.gemtalksystems

>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Mariano
>>>> http://marianopeck.wordpress.com
>>>>
>>>
>>>
>>
>>
>> --
>> Mariano
>> http://marianopeck.wordpress.com
>>
> 
> 
> 
> -- 
> Mariano
> http://marianopeck.wordpress.com
> 
> _______________________________________________
> seaside mailing list

> seaside@.squeakfoundation

> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside





--
View this message in context: http://forum.world.st/Re-Cannot-load-Seaside-anymore-in-a-just-migrated-GemStone-WAS-Re-Glass-Zinc-2-4-3-on-Gemstone-tp4855877p4886222.html
Sent from the Seaside General mailing list archive at Nabble.com.
From pdebruic at gmail.com  Thu Mar 24 04:41:00 2016
From: pdebruic at gmail.com (Paul DeBruicker)
Date: Thu Mar 24 05:10:37 2016
Subject: [Seaside] Re: Cannot load Seaside anymore in a just-migrated
 GemStone [WAS] Re: [Glass] Zinc 2.4.3 on Gemstone
In-Reply-To: <1458794170458-4886222.post@n4.nabble.com>
References: <CAA+-=mUkoMGR3KEkR8+VOW3-Wc3FOawQyiv-JTqKDCHJO-fudw@mail.gmail.com>
	<1458794170458-4886222.post@n4.nabble.com>
Message-ID: <1458794460742-4886223.post@n4.nabble.com>


Oh wait.  


WAEnvironment initialize. 


Seemed to have fixed it.  Following the senders of a message helps more than
writing emails some times....



Thanks

Paul



Paul DeBruicker wrote
> Hi Mariano,
> 
> 
> I just ran into this issue.  Did you end up finding a solution?
> 
> 
> Thanks
> 
> Paul
> 
> Mariano Martinez Peck wrote
>> On Thu, Oct 15, 2015 at 4:25 PM, Mariano Martinez Peck <

>> marianopeck@

>>> wrote:
>> 
>>> Hi guys,
>>>
>>> I have a weird scenario I cannot solve. I am trying to load my app code
>>> (together with all it's dependencies) in a just migrated stone (from
>>> GemStone 3.1.0.4 to GemStone 3.2.9). I performed all the steps of the
>>> migration.  Yet, I have an error, pasted below. However, if I run the
>>> same
>>> code to load my app in a fresh 3.2.9 extent, that works perfectly. It
>>> only
>>> fails in my migrated (from 3.1.0.4) stone.
>>>
>>> The problem is in
>>>
>>> WAWalkbackErrorHandler class >> initialize
>>> WAAdmin applicationExceptionHandlingDefaults at: #exceptionHandler put:
>>> self
>>>
>>> It fails because the
>>>
>>> WAConfiguration >> attributeAt: aSymbol
>>> ^ self attributeAt: aSymbol ifAbsent: [ WAAttributeNotFound
>>> signalWithKey:
>>> aSymbol ]
>>>
>>> gives a key not found.
>>>
>>> I did a search  in the mailing list and found related threads:
>>>
>>> http://forum.world.st/Glass-Zinc-2-4-3-on-Gemstone-td4759789.html#a4759875
>>> https://github.com/seasidest/seaside/issues/643
>>>
>>> But none show a solution.
>>>
>>> And yes, it is obvious it will fail because:
>>>
>>> WAAdmin applicationExceptionHandlingDefaults allAttributes ->
>>>  anIdentityDictionary( )
>>>
>>> Also, as you can see, the result of WAAdmin
>>> applicationExceptionHandlingDefaults has no parent or anything:
>>>
>>> Inspect aWASharedConfiguration/
>>> --------------------
>>> .                     -> aWASharedConfiguration
>>> (class)@              -> WASharedConfiguration
>>> (oop)@                -> 1169561601
>>> (committed)@          -> true
>>> cachedSearchContexts@ -> anIdentityDictionary(
>>> #'exceptionHandler'->aWAAttributeSearchContext)
>>> expressions@          -> aDictionary( )
>>> name@                 -> 'Application Exception Handling Defaults'
>>> parents@              -> anOrderedCollection( )
>>>
>>>
>>> I even tried the re-initialization of Seaside as provided by Bruno the
>>> other day:
>>>
>>> WAAdmin unregister: 'reps'.
>>> WAAdmin unregister: 'advisors'.
>>> WAAdmin unregister: 'clients'.
>>>
>>> WAGemStoneProductionErrorHandler  initialize.
>>> WAWalkbackErrorHandler initialize.
>>> WARemoteDebuggingWalkbackErrorHandler initialize.
>>>
>>> [
>>>    WADispatcher default.
>>>    WASystemConfiguration allSubclasses
>>>      do: [ :each | each instance buildDescription ] ]
>>>      ensure: [ System commitTransaction ] .
>>>
>>>
>>> Still, same error.
>>>
>>>
>>> Any clues? Is there  way I can re-initialize all Seaside?
>>>
>>>
>>> This is the stack:
>>>
>>> aTDDebugger
>>> --------------------
>>> 1. WAAttributeNotFound(AbstractException)>>_signalWith: @6 line 25
>>> 2. WAAttributeNotFound(AbstractException)>>signal @2 line 47
>>> 3. WAAttributeNotFound class>>signalWithKey: @4 line 4
>>> 4. [] in ExecBlock0(WAConfiguration)>>attributeAt: @2 line 2
>>> 5. IdentityDictionary>>at:ifAbsent: @5 line 8
>>> 6. WASharedConfiguration(WAConfiguration)>>attributeAt:ifAbsent: @3 line
>>> 2
>>> 7. WASharedConfiguration(WAConfiguration)>>attributeAt: @2 line 2
>>> 8. WASharedConfiguration(WAUserConfiguration)>>at:put: @2 line 7
>>> 9. WAWalkbackErrorHandler class>>initialize @3 line 2
>>> 10. MCMethodDefinition>>postload @11 line 6
>>> 11. MCMethodDefinition(MCDefinition)>>postloadOver: @2 line 2
>>> 12. [] in MCPackageLoader>>basicLoad @3 line 48
>>> 13. OrderedCollection(Collection)>>do: @5 line 10
>>> 14. OrderedCollection(Collection)>>do:displayingProgress: @2 line 3
>>> 15. [] in MCPackageLoader>>basicLoad @15 line 48
>>> 16. MCPackageLoader(ExecBlock)>>on:do: @3 line 42
>>> 17. [] in MCPackageLoader>>basicLoad @2 line 49
>>> 18. MCPackageLoader(ExecBlock)>>ensure: @2 line 12
>>> 19. MCPackageLoader>>basicLoad @11 line 51
>>> 20. [] in MCPackageLoader>>loadWithNameLike: @2 line 4
>>> 21. [] in ExecBlock0(MCPackageLoader)>>useChangeSetNamed:during: @2 line
>>> 9
>>> 22. ExecBlock0(ExecBlock)>>ensure: @2 line 12
>>> 23. MCPackageLoader>>useChangeSetNamed:during: @9 line 9
>>> 24. MCPackageLoader>>useNewChangeSetNamedLike:during: @3 line 2
>>> 25. MCPackageLoader>>loadWithNameLike: @6 line 4
>>> 26. MCVersionLoader>>load @9 line 6
>>> 27. MetacelloGoferLoad(GoferLoad)>>execute @6 line 3
>>> 28. [] in
>>> MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
>>> @5 line 17
>>> 29. [] in
>>> MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
>>> @14 line 21
>>> 30. MetacelloGemStonePlatform(MetacelloPlatform)>>do:displaying: @2 line
>>> 3
>>> 31.
>>> MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
>>> @7 line 5
>>> 32.
>>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadPackageDirective:gofer:
>>> @4 line 4
>>> 33. MetacelloPackageLoadDirective>>loadUsing:gofer: @2 line 3
>>> 34. [] in
>>> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>>> @2 line 3
>>> 35. OrderedCollection(Collection)>>do: @5 line 10
>>> 36.
>>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>>> @3 line 3
>>> 37. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>>> 38. [] in
>>> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>>> @2 line 3
>>> 39. OrderedCollection(Collection)>>do: @5 line 10
>>> 40.
>>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>>> @3 line 3
>>> 41. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>>> 42. [] in
>>> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>>> @2 line 3
>>> 43. OrderedCollection(Collection)>>do: @5 line 10
>>> 44.
>>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>>> @3 line 3
>>> 45. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>>> 46. [] in
>>> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>>> @2 line 3
>>> 47. OrderedCollection(Collection)>>do: @5 line 10
>>> 48.
>>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>>> @3 line 3
>>> 49. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>>> 50. [] in
>>> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>>> @2 line 3
>>> 51. OrderedCollection(Collection)>>do: @5 line 10
>>> 52.
>>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>>> @3 line 3
>>> 53. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>>> 54.
>>> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadWithPolicy:
>>> @7 line 7
>>> 55. MetacelloLoaderPolicy>>load @6 line 4
>>> 56. MetacelloFetchingMCSpecLoader>>doLoad @4 line 3
>>> 57. [] in ExecBlock0(MetacelloMCVersion)>>doLoadRequiredFromArray: @2
>>> line
>>> 12
>>> 58. MetacelloGemStonePlatform(MetacelloPlatform)>>do:displaying: @2 line
>>> 3
>>> 59. [] in MetacelloMCVersion>>doLoadRequiredFromArray: @7 line 12
>>> 60. MetacelloMCVersion(ExecBlock)>>ensure: @2 line 12
>>> 61. MetacelloMCVersion>>doLoadRequiredFromArray: @22 line 16
>>> 62. Array(Collection)>>loadRequiredForMetacelloMCVersion: @2 line 3
>>> 63. MetacelloMCVersion>>load: @2 line 3
>>> 64. [] in
>>> MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade:
>>> @10 line 16
>>> 65. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>>> 66. [] in MetacelloScriptEngine>>handleNotificationsForAction: @6 line 6
>>> 67. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>>> 68. [] in MetacelloScriptEngine>>handleNotificationsForAction: @4 line
>>> 14
>>> 69. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>>> 70. [] in MetacelloScriptEngine>>handleNotificationsForAction: @2 line
>>> 20
>>> 71. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>>> 72. MetacelloScriptEngine>>handleNotificationsForAction: @2 line 24
>>> 73. [] in
>>> MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade:
>>> @2 line 5
>>> 74. MetacelloScriptEngine(ExecBlock)>>ensure: @2 line 12
>>> 75. MetacelloProjectRegistration class>>copyRegistryRestoreOnErrorWhile:
>>> @8 line 14
>>> 76. MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade: @2
>>> line 3
>>> 77. MetacelloScriptEngine>>load: @2 line 3
>>> 78. [] in MetacelloScriptApiExecutor(MetacelloScriptExecutor)>>execute:
>>> @11 line 15
>>> 79. [] in MetacelloScriptApiExecutor>>executeString:do: @5 line 6
>>> 80. Array(Collection)>>do: @5 line 10
>>> 81. MetacelloScriptApiExecutor>>executeString:do: @6 line 4
>>> 82. String>>execute:against: @2 line 2
>>> 83. MetacelloScriptApiExecutor(MetacelloScriptExecutor)>>execute: @6
>>> line 9
>>> 84. Metacello>>execute:args: @8 line 5
>>> 85. Metacello>>load: @2 line 2
>>> 86. [] in Executed Code
>>> 87. ExecBlock0(ExecBlock)>>ensure: @2 line 12
>>> 88. Executed Code
>>> 89. String(CharacterCollection)>>evaluateIn:symbolList:literalVars: @4
>>> line 13
>>> 90.
>>> TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>evaluateString:
>>> @5 line 3
>>> 91.
>>> TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>doItMenuAction:selectedText:
>>> @2 line 2
>>> 92.
>>> TDWorkspaceClientElementBuilder(TDWindowBuilder)>>handleMenuActions:listElement:actionArg:
>>> @12 line 10
>>> 93. [] in
>>> TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>menuActionBlock
>>> @6 line 8
>>> 94.
>>> TDWorkspaceClientElementBuilder(ExecBlock)>>value:value:value:value:value:
>>> @2 line 11
>>> 95. GsNMethod class>>_gsReturnToC @1 line 1
>>>
>>>
>>> Thanks in advance for any help.
>>>
>>> On Thu, Oct 15, 2015 at 1:40 PM, Gerhard Obermann &lt;

>> obi068@

>> &gt;
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Not really, i only found the following in my notes.
>>>>
>>>> HTH
>>>> Gerhard
>>>>
>>>>
>>>>
>>>>    -
>>>>
>>>>    Load Seaside 3.1.x but don?t initialize Seaside Classes
>>>>
>>>>
>>>> | performInitialization |
>>>>
>>>> performInitialization := #().
>>>>
>>>> [
>>>>
>>>> GsDeployer deploy: [  Metacello new
>>>>
>>>>    baseline: 'Seaside3';
>>>>
>>>>    repository: 'github://glassdb/Seaside31:gemstone3.1/repository';
>>>>
>>>>    load: 'CI'].
>>>>
>>>> ] on: MCPerformPostloadNotification do: [:ex |
>>>>
>>>>           (performInitialization includes: ex postloadClass
>>>> theNonMetaClass name)
>>>>
>>>>             ifTrue: [
>>>>
>>>>               "perform initialization"
>>>>
>>>>               ex resume: true ]
>>>>
>>>>             ifFalse: [
>>>>
>>>>               GsFile gciLogServer: ' Skip ', ex postloadClass name
>>>> asString, ' initialization.'.
>>>>
>>>>                ex resume: false ] ]
>>>>
>>>>
>>>> On Thu, Oct 15, 2015 at 5:47 PM, Mariano Martinez Peck <
>>>> 

>> marianopeck@

>>> wrote:
>>>>
>>>>> Hi Gerhard,
>>>>>
>>>>> I am getting the exact same issue. Do you remember what you did to fix
>>>>> it?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> On Wed, May 21, 2014 at 10:39 AM, Gerhard Obermann &lt;

>> obi068@

>> &gt;
>>>>> wrote:
>>>>>
>>>>>> Hi Dale!
>>>>>>
>>>>>> I think as soon as I can load the stuff in my upgraded 3.2. DB, i can
>>>>>> test and contribute to zink and/or Glass / Seaside 3.1.
>>>>>> If it wont work until tomorrow i have to stay on 3.1.0.5 for the next
>>>>>> few months at least.
>>>>>>
>>>>>> At the moment i am trying to load Seaside 3.1.1 with
>>>>>> PS: To be able to load this i have loaded the Baseline packages
>>>>>> BaselineOfGLASS1,
>>>>>> BaselineOfSeaside3 , BaselineOfZinc manually from my forked GIT
>>>>>> clone.
>>>>>>
>>>>>> GsDeployer deploy: [
>>>>>>   Metacello new
>>>>>>     configuration: 'Grease';
>>>>>>     repository: '
>>>>>> http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>>>>>>     get.
>>>>>>
>>>>>>   "Load Seaside31"
>>>>>> GsDeployer deploy: [
>>>>>>   Metacello new
>>>>>>     baseline: 'Seaside3';
>>>>>>     repository: 'github://glassdb/Seaside31:gemstone3.1/repository';
>>>>>>     load: 'CI'].
>>>>>>
>>>>>>
>>>>>> Not sure if i need to load  Metacello new
>>>>>>     baseline: 'GLASS1';
>>>>>>     repository: 'github://glassdb/glass:master/repository';
>>>>>>     load.
>>>>>> after the upgrade.
>>>>>>
>>>>>> What is the difference between
>>>>>>   (ConfigurationOfGLASS project version: '1.0-beta.9.1') load
>>>>>> and
>>>>>>  Metacello new
>>>>>>     baseline: 'GLASS1';
>>>>>>     repository: 'github://glassdb/glass:master/repository';
>>>>>>     load.
>>>>>>
>>>>>> *The load of the Seaside package failed with the init of *
>>>>>> *WAWalkbackErrorHandler => initialize*
>>>>>> * WAAdmin applicationExceptionHandlingDefaults at: #exceptionHandler
>>>>>> put: self*
>>>>>>
>>>>>> [1] WAAttributeNotFound (AbstractException) >> _signalWith:
>>>>>> inCextensionArg: nil
>>>>>> res: nil
>>>>>> .t1: a WAAttributeNotFound occurred (error 2710)
>>>>>> receiver: a WAAttributeNotFound occurred (error 2710)
>>>>>> [2] WAAttributeNotFound (AbstractException) >> signal
>>>>>> receiver: a WAAttributeNotFound occurred (error 2710)
>>>>>> [3] WAAttributeNotFound class >> signalWithKey:
>>>>>> aSymbol: #'exceptionHandler'
>>>>>> receiver: WAAttributeNotFound
>>>>>> [4] [] in  ExecBlock0 (WAConfiguration) >> attributeAt:
>>>>>> aSymbol: #'exceptionHandler'
>>>>>> receiver: nil
>>>>>> [5] IdentityDictionary >> at:ifAbsent:
>>>>>> aKey: #'exceptionHandler'
>>>>>> aBlock: anExecBlock0
>>>>>> anAssoc: nil
>>>>>> .t1: anExecBlock0
>>>>>> receiver: anIdentityDictionary( )
>>>>>> [6] WASharedConfiguration (WAConfiguration) >> attributeAt:ifAbsent:
>>>>>> aSymbol: #'exceptionHandler'
>>>>>> aBlock: anExecBlock0
>>>>>> receiver: aWASharedConfiguration
>>>>>> [7] WASharedConfiguration (WAConfiguration) >> attributeAt:
>>>>>> aSymbol: #'exceptionHandler'
>>>>>> aSymbol: #'exceptionHandler'
>>>>>> receiver: aWASharedConfiguration
>>>>>> [8] WASharedConfiguration (WAUserConfiguration) >> at:put:
>>>>>> aSymbol: #'exceptionHandler'
>>>>>> anObject: WAWalkbackErrorHandler
>>>>>> receiver: aWASharedConfiguration
>>>>>> [9] WAWalkbackErrorHandler class >> initialize
>>>>>> receiver: WAWalkbackErrorHandler
>>>>>> [10] MCMethodDefinition >> postload
>>>>>> receiver: aMCMethodDefinition(WAWalkbackErrorHandler
>>>>>> class>>initialize)
>>>>>>
>>>>>>
>>>>>> Transcript:
>>>>>> Fetched -> FastCGIPool-dkh.2 ---
>>>>>> http://seaside.gemstone.com/ss/fastcgi
>>>>>> --- http://seaside.gemstone.com/ss/fastcgiredirecting to
>>>>>> http://seaside.gemtalksystems.com/ss/fastcgi/FastCGI-dkh.33.mcz
>>>>>>
>>>>>> Fetched -> FastCGI-dkh.33 --- http://seaside.gemstone.com/ss/fastcgi
>>>>>> --- http://seaside.gemstone.com/ss/fastcgi
>>>>>> Fetched -> Seaside-Adaptors-FastCGI-dkh.26 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository
>>>>>> Loaded -> Grease-Core-JohanBrichau.86 ---
>>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>>>>>> Loaded -> Grease-GemStone-Core-JohanBrichau.52 ---
>>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>>>>>> Evaluated -> Grease-GemStone-Core >> initializeTransactionMutex1051
>>>>>> Loaded -> Seaside-Core.gemstone-JohanBrichau.815 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-GemStone300-Core-DaleHenrichs.4 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-GemStone-Core-JohanBrichau.66 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-GemStone-Basic-Development-JohanBrichau.29 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Grease-Tests-Core-JohanBrichau.95 ---
>>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>>>>>> Loaded -> Grease-Tests-GemStone-Core-dkh.14 ---
>>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>>>>>> Loaded -> Seaside-Component-pmm.101 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-Canvas-pmm.127 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-Email-pmm.25 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-GemStone-Email-JohanBrichau.14 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-InternetExplorer-pmm.7 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-Session.gemstone-JohanBrichau.169 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-GemStone-Session-DaleHenrichs.3 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-RenderLoop-pmm.96 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-Tools-Core.gemstone-dkh.23 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-Flow-pmm.24 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-Examples-pmm.24 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-Widgets-StephanEggermont.35 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-GemStone-Tools-Production-JohanBrichau.15 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-Tools-Web-pmm.119 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>> Loaded -> Seaside-GemStone-Tools-Web-DaleHenrichs.4 ---
>>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, May 21, 2014 at 3:06 PM, Dale Henrichs <
>>>>>> 

>> dale.henrichs@

>>> wrote:
>>>>>>
>>>>>>> Marching Orders! Very good ...
>>>>>>>
>>>>>>> Johan, Gerhard, et. al., I want to follow your lead and fill in
>>>>>>> where
>>>>>>> the work is needed ...
>>>>>>>
>>>>>>> Do you guys think that getting Seaside/Zinc/etc. ported to
>>>>>>> GemStone3.2
>>>>>>> takes precedence over getting Zinc running on GemStone3.1?
>>>>>>>
>>>>>>> I can take a crack at solving Gerhard's Seaside3.1 loading error,
>>>>>>> but
>>>>>>> Zinc has been on the brink for so long, maybe I should hit it hard
>>>>>>> and get
>>>>>>> the tests passing in GemStone 3.1 (encoding issues are right up my
>>>>>>> alley:)?
>>>>>>>
>>>>>>> If there are other outstanding problems that folks are looking at
>>>>>>> they
>>>>>>> can be added into the mix...
>>>>>>>
>>>>>>> Dale
>>>>>>>
>>>>>>>
>>>>>>> On Tue, May 20, 2014 at 10:42 PM, Johan Brichau &lt;

>> johan@

>> &gt;
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I have been tampering off and on over the last few months to make
>>>>>>>> Zinc 2.4.3 work in Gemstone.
>>>>>>>>
>>>>>>>> I made a pull request [1] with my changes, though not all tests are
>>>>>>>> passing and since most of the changes had to do with encoding, byte
>>>>>>>> arrays
>>>>>>>> vs strings, multibyte strings, etc... I really need someone to take
>>>>>>>> a look
>>>>>>>> at them. Also, the pace is quite slow by myself ;-)
>>>>>>>>
>>>>>>>> This email is just to make sure that the pull request does not go
>>>>>>>> unnoticed for someone wanting to take up work on the port.
>>>>>>>>
>>>>>>>> cheers!
>>>>>>>> Johan
>>>>>>>>
>>>>>>>> [1] https://github.com/glassdb/zinc/pull/48
>>>>>>>> _______________________________________________
>>>>>>>> Glass mailing list
>>>>>>>> 

>> Glass@.gemtalksystems

>>>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Glass mailing list
>>>>>>> 

>> Glass@.gemtalksystems

>>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Glass mailing list
>>>>>> 

>> Glass@.gemtalksystems

>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Mariano
>>>>> http://marianopeck.wordpress.com
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>> 
>> 
>> 
>> -- 
>> Mariano
>> http://marianopeck.wordpress.com
>> 
>> _______________________________________________
>> seaside mailing list

>> seaside@.squeakfoundation

>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside





--
View this message in context: http://forum.world.st/Re-Cannot-load-Seaside-anymore-in-a-just-migrated-GemStone-WAS-Re-Glass-Zinc-2-4-3-on-Gemstone-tp4855877p4886223.html
Sent from the Seaside General mailing list archive at Nabble.com.
From marianopeck at gmail.com  Thu Mar 24 12:32:41 2016
From: marianopeck at gmail.com (Mariano Martinez Peck)
Date: Thu Mar 24 12:32:43 2016
Subject: [Seaside] Re: Cannot load Seaside anymore in a just-migrated
	GemStone [WAS] Re: [Glass] Zinc 2.4.3 on Gemstone
In-Reply-To: <1458794460742-4886223.post@n4.nabble.com>
References: <CAA+-=mUkoMGR3KEkR8+VOW3-Wc3FOawQyiv-JTqKDCHJO-fudw@mail.gmail.com>
	<1458794170458-4886222.post@n4.nabble.com>
	<1458794460742-4886223.post@n4.nabble.com>
Message-ID: <CAA+-=mXMJ8Y2WxZpSLj3zXfgqBhr8KZYFWWfSm=wKeX8M77RfA@mail.gmail.com>

Hi Paul,

I will answer just in case others may find the same issue in the future.

As you know, at the time of loading a class side #initialize, Monticello
checks if it has already been run or not and only run if it is has not.
Re-initializing seaside (re-sending class side initialize) is the problem
as it brings problems like the one you mention.

The problem is that during the GemStone upgrade, the Monticello caches are
cleared. But Seaside code is still there. So...when you try to load Seaside
again in a upgraded stone, the Monticello cache is empty and hence all
class #initialize are executed again in a env where they HAD already been
initialized before (hence the problem).

The solution I found is to re-load all my app (and seaside) in a way of NOT
executing class side #initialize. This must be done only once as this will
fill monticello cache and next times it will not try to run #initialize
(unless the method source has changed):


  GsDeployer
    deploy: [
      [
      [
      [
      Metacello new
        configuration: 'MyApp';
        repository: 'http://smalltalkhub.com/mc/MyApp/MyApp/main';
        version: '1.6';
        get;
        onConflictUseIncoming: #('Seaside3') useLoaded: #('Grease');
        onUpgrade: [ :ex :loaded :incoming |
              incoming baseName = 'XMLSupport'
                ifTrue: [
                  "I could use #useLoaded but the one currently coming with
GemStone has a broken versionString."
                  ex allowEvenIfLocked ]
                ifFalse: [
                  "default"
                  ex useIncoming ] ];
        load: #('MyPackages') ]
        on: MCPerformPostloadNotification
        do: [ :ex |
          (ex postloadClass name beginsWith: 'WA')
            ifTrue: [
              Transcript
                show:
                  ' Skipping class side initialization of ' , ex
postloadClass name asString.
              ex resume: false ]
            ifFalse: [ ex resume: true ] ] ]
        on: Warning
        do: [ :ex |
          Transcript
            cr;
            cr;
            show: '====================================================';
            cr;
            show: ex description;
            cr;
            cr;
            show: '====================================================';
            cr.
          ex resume ] ]
        ensure: [
          System
            performOnServer:
              'rm -rf /tmp/curl*; rm -rf /tmp/github*; rm -rf
/tmp/*tmpgithub*; rm -rf /tmp/zip.err' ] ].
  System commitTransaction


The important part is the error block for MCPerformPostloadNotification
(which is sent when it is about to run class side #initialize).

Once above code has been run (once), then you can load again your code in
the normal way.


*Dale, we should add this seaside re-load to the upgradeSeaside script...*

Cheers,




On Thu, Mar 24, 2016 at 1:41 AM, Paul DeBruicker <pdebruic@gmail.com> wrote:

>
> Oh wait.
>
>
> WAEnvironment initialize.
>
>
> Seemed to have fixed it.  Following the senders of a message helps more
> than
> writing emails some times....
>
>
>
> Thanks
>
> Paul
>
>
>
> Paul DeBruicker wrote
> > Hi Mariano,
> >
> >
> > I just ran into this issue.  Did you end up finding a solution?
> >
> >
> > Thanks
> >
> > Paul
> >
> > Mariano Martinez Peck wrote
> >> On Thu, Oct 15, 2015 at 4:25 PM, Mariano Martinez Peck <
>
> >> marianopeck@
>
> >>> wrote:
> >>
> >>> Hi guys,
> >>>
> >>> I have a weird scenario I cannot solve. I am trying to load my app code
> >>> (together with all it's dependencies) in a just migrated stone (from
> >>> GemStone 3.1.0.4 to GemStone 3.2.9). I performed all the steps of the
> >>> migration.  Yet, I have an error, pasted below. However, if I run the
> >>> same
> >>> code to load my app in a fresh 3.2.9 extent, that works perfectly. It
> >>> only
> >>> fails in my migrated (from 3.1.0.4) stone.
> >>>
> >>> The problem is in
> >>>
> >>> WAWalkbackErrorHandler class >> initialize
> >>> WAAdmin applicationExceptionHandlingDefaults at: #exceptionHandler put:
> >>> self
> >>>
> >>> It fails because the
> >>>
> >>> WAConfiguration >> attributeAt: aSymbol
> >>> ^ self attributeAt: aSymbol ifAbsent: [ WAAttributeNotFound
> >>> signalWithKey:
> >>> aSymbol ]
> >>>
> >>> gives a key not found.
> >>>
> >>> I did a search  in the mailing list and found related threads:
> >>>
> >>>
> http://forum.world.st/Glass-Zinc-2-4-3-on-Gemstone-td4759789.html#a4759875
> >>> https://github.com/seasidest/seaside/issues/643
> >>>
> >>> But none show a solution.
> >>>
> >>> And yes, it is obvious it will fail because:
> >>>
> >>> WAAdmin applicationExceptionHandlingDefaults allAttributes ->
> >>>  anIdentityDictionary( )
> >>>
> >>> Also, as you can see, the result of WAAdmin
> >>> applicationExceptionHandlingDefaults has no parent or anything:
> >>>
> >>> Inspect aWASharedConfiguration/
> >>> --------------------
> >>> .                     -> aWASharedConfiguration
> >>> (class)@              -> WASharedConfiguration
> >>> (oop)@                -> 1169561601
> >>> (committed)@          -> true
> >>> cachedSearchContexts@ -> anIdentityDictionary(
> >>> #'exceptionHandler'->aWAAttributeSearchContext)
> >>> expressions@          -> aDictionary( )
> >>> name@                 -> 'Application Exception Handling Defaults'
> >>> parents@              -> anOrderedCollection( )
> >>>
> >>>
> >>> I even tried the re-initialization of Seaside as provided by Bruno the
> >>> other day:
> >>>
> >>> WAAdmin unregister: 'reps'.
> >>> WAAdmin unregister: 'advisors'.
> >>> WAAdmin unregister: 'clients'.
> >>>
> >>> WAGemStoneProductionErrorHandler  initialize.
> >>> WAWalkbackErrorHandler initialize.
> >>> WARemoteDebuggingWalkbackErrorHandler initialize.
> >>>
> >>> [
> >>>    WADispatcher default.
> >>>    WASystemConfiguration allSubclasses
> >>>      do: [ :each | each instance buildDescription ] ]
> >>>      ensure: [ System commitTransaction ] .
> >>>
> >>>
> >>> Still, same error.
> >>>
> >>>
> >>> Any clues? Is there  way I can re-initialize all Seaside?
> >>>
> >>>
> >>> This is the stack:
> >>>
> >>> aTDDebugger
> >>> --------------------
> >>> 1. WAAttributeNotFound(AbstractException)>>_signalWith: @6 line 25
> >>> 2. WAAttributeNotFound(AbstractException)>>signal @2 line 47
> >>> 3. WAAttributeNotFound class>>signalWithKey: @4 line 4
> >>> 4. [] in ExecBlock0(WAConfiguration)>>attributeAt: @2 line 2
> >>> 5. IdentityDictionary>>at:ifAbsent: @5 line 8
> >>> 6. WASharedConfiguration(WAConfiguration)>>attributeAt:ifAbsent: @3
> line
> >>> 2
> >>> 7. WASharedConfiguration(WAConfiguration)>>attributeAt: @2 line 2
> >>> 8. WASharedConfiguration(WAUserConfiguration)>>at:put: @2 line 7
> >>> 9. WAWalkbackErrorHandler class>>initialize @3 line 2
> >>> 10. MCMethodDefinition>>postload @11 line 6
> >>> 11. MCMethodDefinition(MCDefinition)>>postloadOver: @2 line 2
> >>> 12. [] in MCPackageLoader>>basicLoad @3 line 48
> >>> 13. OrderedCollection(Collection)>>do: @5 line 10
> >>> 14. OrderedCollection(Collection)>>do:displayingProgress: @2 line 3
> >>> 15. [] in MCPackageLoader>>basicLoad @15 line 48
> >>> 16. MCPackageLoader(ExecBlock)>>on:do: @3 line 42
> >>> 17. [] in MCPackageLoader>>basicLoad @2 line 49
> >>> 18. MCPackageLoader(ExecBlock)>>ensure: @2 line 12
> >>> 19. MCPackageLoader>>basicLoad @11 line 51
> >>> 20. [] in MCPackageLoader>>loadWithNameLike: @2 line 4
> >>> 21. [] in ExecBlock0(MCPackageLoader)>>useChangeSetNamed:during: @2
> line
> >>> 9
> >>> 22. ExecBlock0(ExecBlock)>>ensure: @2 line 12
> >>> 23. MCPackageLoader>>useChangeSetNamed:during: @9 line 9
> >>> 24. MCPackageLoader>>useNewChangeSetNamedLike:during: @3 line 2
> >>> 25. MCPackageLoader>>loadWithNameLike: @6 line 4
> >>> 26. MCVersionLoader>>load @9 line 6
> >>> 27. MetacelloGoferLoad(GoferLoad)>>execute @6 line 3
> >>> 28. [] in
> >>>
> MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
> >>> @5 line 17
> >>> 29. [] in
> >>>
> MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
> >>> @14 line 21
> >>> 30. MetacelloGemStonePlatform(MetacelloPlatform)>>do:displaying: @2
> line
> >>> 3
> >>> 31.
> >>>
> MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
> >>> @7 line 5
> >>> 32.
> >>>
> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadPackageDirective:gofer:
> >>> @4 line 4
> >>> 33. MetacelloPackageLoadDirective>>loadUsing:gofer: @2 line 3
> >>> 34. [] in
> >>>
> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
> >>> @2 line 3
> >>> 35. OrderedCollection(Collection)>>do: @5 line 10
> >>> 36.
> >>>
> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
> >>> @3 line 3
> >>> 37. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
> >>> 38. [] in
> >>>
> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
> >>> @2 line 3
> >>> 39. OrderedCollection(Collection)>>do: @5 line 10
> >>> 40.
> >>>
> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
> >>> @3 line 3
> >>> 41. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
> >>> 42. [] in
> >>>
> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
> >>> @2 line 3
> >>> 43. OrderedCollection(Collection)>>do: @5 line 10
> >>> 44.
> >>>
> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
> >>> @3 line 3
> >>> 45. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
> >>> 46. [] in
> >>>
> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
> >>> @2 line 3
> >>> 47. OrderedCollection(Collection)>>do: @5 line 10
> >>> 48.
> >>>
> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
> >>> @3 line 3
> >>> 49. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
> >>> 50. [] in
> >>>
> ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
> >>> @2 line 3
> >>> 51. OrderedCollection(Collection)>>do: @5 line 10
> >>> 52.
> >>>
> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
> >>> @3 line 3
> >>> 53. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
> >>> 54.
> >>>
> MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadWithPolicy:
> >>> @7 line 7
> >>> 55. MetacelloLoaderPolicy>>load @6 line 4
> >>> 56. MetacelloFetchingMCSpecLoader>>doLoad @4 line 3
> >>> 57. [] in ExecBlock0(MetacelloMCVersion)>>doLoadRequiredFromArray: @2
> >>> line
> >>> 12
> >>> 58. MetacelloGemStonePlatform(MetacelloPlatform)>>do:displaying: @2
> line
> >>> 3
> >>> 59. [] in MetacelloMCVersion>>doLoadRequiredFromArray: @7 line 12
> >>> 60. MetacelloMCVersion(ExecBlock)>>ensure: @2 line 12
> >>> 61. MetacelloMCVersion>>doLoadRequiredFromArray: @22 line 16
> >>> 62. Array(Collection)>>loadRequiredForMetacelloMCVersion: @2 line 3
> >>> 63. MetacelloMCVersion>>load: @2 line 3
> >>> 64. [] in
> >>> MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade:
> >>> @10 line 16
> >>> 65. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
> >>> 66. [] in MetacelloScriptEngine>>handleNotificationsForAction: @6 line
> 6
> >>> 67. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
> >>> 68. [] in MetacelloScriptEngine>>handleNotificationsForAction: @4 line
> >>> 14
> >>> 69. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
> >>> 70. [] in MetacelloScriptEngine>>handleNotificationsForAction: @2 line
> >>> 20
> >>> 71. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
> >>> 72. MetacelloScriptEngine>>handleNotificationsForAction: @2 line 24
> >>> 73. [] in
> >>> MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade:
> >>> @2 line 5
> >>> 74. MetacelloScriptEngine(ExecBlock)>>ensure: @2 line 12
> >>> 75. MetacelloProjectRegistration
> class>>copyRegistryRestoreOnErrorWhile:
> >>> @8 line 14
> >>> 76. MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade: @2
> >>> line 3
> >>> 77. MetacelloScriptEngine>>load: @2 line 3
> >>> 78. [] in MetacelloScriptApiExecutor(MetacelloScriptExecutor)>>execute:
> >>> @11 line 15
> >>> 79. [] in MetacelloScriptApiExecutor>>executeString:do: @5 line 6
> >>> 80. Array(Collection)>>do: @5 line 10
> >>> 81. MetacelloScriptApiExecutor>>executeString:do: @6 line 4
> >>> 82. String>>execute:against: @2 line 2
> >>> 83. MetacelloScriptApiExecutor(MetacelloScriptExecutor)>>execute: @6
> >>> line 9
> >>> 84. Metacello>>execute:args: @8 line 5
> >>> 85. Metacello>>load: @2 line 2
> >>> 86. [] in Executed Code
> >>> 87. ExecBlock0(ExecBlock)>>ensure: @2 line 12
> >>> 88. Executed Code
> >>> 89. String(CharacterCollection)>>evaluateIn:symbolList:literalVars: @4
> >>> line 13
> >>> 90.
> >>>
> TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>evaluateString:
> >>> @5 line 3
> >>> 91.
> >>>
> TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>doItMenuAction:selectedText:
> >>> @2 line 2
> >>> 92.
> >>>
> TDWorkspaceClientElementBuilder(TDWindowBuilder)>>handleMenuActions:listElement:actionArg:
> >>> @12 line 10
> >>> 93. [] in
> >>>
> TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>menuActionBlock
> >>> @6 line 8
> >>> 94.
> >>>
> TDWorkspaceClientElementBuilder(ExecBlock)>>value:value:value:value:value:
> >>> @2 line 11
> >>> 95. GsNMethod class>>_gsReturnToC @1 line 1
> >>>
> >>>
> >>> Thanks in advance for any help.
> >>>
> >>> On Thu, Oct 15, 2015 at 1:40 PM, Gerhard Obermann &lt;
>
> >> obi068@
>
> >> &gt;
> >>> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> Not really, i only found the following in my notes.
> >>>>
> >>>> HTH
> >>>> Gerhard
> >>>>
> >>>>
> >>>>
> >>>>    -
> >>>>
> >>>>    Load Seaside 3.1.x but don?t initialize Seaside Classes
> >>>>
> >>>>
> >>>> | performInitialization |
> >>>>
> >>>> performInitialization := #().
> >>>>
> >>>> [
> >>>>
> >>>> GsDeployer deploy: [  Metacello new
> >>>>
> >>>>    baseline: 'Seaside3';
> >>>>
> >>>>    repository: 'github://glassdb/Seaside31:gemstone3.1/repository';
> >>>>
> >>>>    load: 'CI'].
> >>>>
> >>>> ] on: MCPerformPostloadNotification do: [:ex |
> >>>>
> >>>>           (performInitialization includes: ex postloadClass
> >>>> theNonMetaClass name)
> >>>>
> >>>>             ifTrue: [
> >>>>
> >>>>               "perform initialization"
> >>>>
> >>>>               ex resume: true ]
> >>>>
> >>>>             ifFalse: [
> >>>>
> >>>>               GsFile gciLogServer: ' Skip ', ex postloadClass name
> >>>> asString, ' initialization.'.
> >>>>
> >>>>                ex resume: false ] ]
> >>>>
> >>>>
> >>>> On Thu, Oct 15, 2015 at 5:47 PM, Mariano Martinez Peck <
> >>>>
>
> >> marianopeck@
>
> >>> wrote:
> >>>>
> >>>>> Hi Gerhard,
> >>>>>
> >>>>> I am getting the exact same issue. Do you remember what you did to
> fix
> >>>>> it?
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> On Wed, May 21, 2014 at 10:39 AM, Gerhard Obermann &lt;
>
> >> obi068@
>
> >> &gt;
> >>>>> wrote:
> >>>>>
> >>>>>> Hi Dale!
> >>>>>>
> >>>>>> I think as soon as I can load the stuff in my upgraded 3.2. DB, i
> can
> >>>>>> test and contribute to zink and/or Glass / Seaside 3.1.
> >>>>>> If it wont work until tomorrow i have to stay on 3.1.0.5 for the
> next
> >>>>>> few months at least.
> >>>>>>
> >>>>>> At the moment i am trying to load Seaside 3.1.1 with
> >>>>>> PS: To be able to load this i have loaded the Baseline packages
> >>>>>> BaselineOfGLASS1,
> >>>>>> BaselineOfSeaside3 , BaselineOfZinc manually from my forked GIT
> >>>>>> clone.
> >>>>>>
> >>>>>> GsDeployer deploy: [
> >>>>>>   Metacello new
> >>>>>>     configuration: 'Grease';
> >>>>>>     repository: '
> >>>>>> http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main
> ';
> >>>>>>     get.
> >>>>>>
> >>>>>>   "Load Seaside31"
> >>>>>> GsDeployer deploy: [
> >>>>>>   Metacello new
> >>>>>>     baseline: 'Seaside3';
> >>>>>>     repository: 'github://glassdb/Seaside31:gemstone3.1/repository';
> >>>>>>     load: 'CI'].
> >>>>>>
> >>>>>>
> >>>>>> Not sure if i need to load  Metacello new
> >>>>>>     baseline: 'GLASS1';
> >>>>>>     repository: 'github://glassdb/glass:master/repository';
> >>>>>>     load.
> >>>>>> after the upgrade.
> >>>>>>
> >>>>>> What is the difference between
> >>>>>>   (ConfigurationOfGLASS project version: '1.0-beta.9.1') load
> >>>>>> and
> >>>>>>  Metacello new
> >>>>>>     baseline: 'GLASS1';
> >>>>>>     repository: 'github://glassdb/glass:master/repository';
> >>>>>>     load.
> >>>>>>
> >>>>>> *The load of the Seaside package failed with the init of *
> >>>>>> *WAWalkbackErrorHandler => initialize*
> >>>>>> * WAAdmin applicationExceptionHandlingDefaults at: #exceptionHandler
> >>>>>> put: self*
> >>>>>>
> >>>>>> [1] WAAttributeNotFound (AbstractException) >> _signalWith:
> >>>>>> inCextensionArg: nil
> >>>>>> res: nil
> >>>>>> .t1: a WAAttributeNotFound occurred (error 2710)
> >>>>>> receiver: a WAAttributeNotFound occurred (error 2710)
> >>>>>> [2] WAAttributeNotFound (AbstractException) >> signal
> >>>>>> receiver: a WAAttributeNotFound occurred (error 2710)
> >>>>>> [3] WAAttributeNotFound class >> signalWithKey:
> >>>>>> aSymbol: #'exceptionHandler'
> >>>>>> receiver: WAAttributeNotFound
> >>>>>> [4] [] in  ExecBlock0 (WAConfiguration) >> attributeAt:
> >>>>>> aSymbol: #'exceptionHandler'
> >>>>>> receiver: nil
> >>>>>> [5] IdentityDictionary >> at:ifAbsent:
> >>>>>> aKey: #'exceptionHandler'
> >>>>>> aBlock: anExecBlock0
> >>>>>> anAssoc: nil
> >>>>>> .t1: anExecBlock0
> >>>>>> receiver: anIdentityDictionary( )
> >>>>>> [6] WASharedConfiguration (WAConfiguration) >> attributeAt:ifAbsent:
> >>>>>> aSymbol: #'exceptionHandler'
> >>>>>> aBlock: anExecBlock0
> >>>>>> receiver: aWASharedConfiguration
> >>>>>> [7] WASharedConfiguration (WAConfiguration) >> attributeAt:
> >>>>>> aSymbol: #'exceptionHandler'
> >>>>>> aSymbol: #'exceptionHandler'
> >>>>>> receiver: aWASharedConfiguration
> >>>>>> [8] WASharedConfiguration (WAUserConfiguration) >> at:put:
> >>>>>> aSymbol: #'exceptionHandler'
> >>>>>> anObject: WAWalkbackErrorHandler
> >>>>>> receiver: aWASharedConfiguration
> >>>>>> [9] WAWalkbackErrorHandler class >> initialize
> >>>>>> receiver: WAWalkbackErrorHandler
> >>>>>> [10] MCMethodDefinition >> postload
> >>>>>> receiver: aMCMethodDefinition(WAWalkbackErrorHandler
> >>>>>> class>>initialize)
> >>>>>>
> >>>>>>
> >>>>>> Transcript:
> >>>>>> Fetched -> FastCGIPool-dkh.2 ---
> >>>>>> http://seaside.gemstone.com/ss/fastcgi
> >>>>>> --- http://seaside.gemstone.com/ss/fastcgiredirecting to
> >>>>>> http://seaside.gemtalksystems.com/ss/fastcgi/FastCGI-dkh.33.mcz
> >>>>>>
> >>>>>> Fetched -> FastCGI-dkh.33 ---
> http://seaside.gemstone.com/ss/fastcgi
> >>>>>> --- http://seaside.gemstone.com/ss/fastcgi
> >>>>>> Fetched -> Seaside-Adaptors-FastCGI-dkh.26 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository
> >>>>>> Loaded -> Grease-Core-JohanBrichau.86 ---
> >>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
> >>>>>> Loaded -> Grease-GemStone-Core-JohanBrichau.52 ---
> >>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
> >>>>>> Evaluated -> Grease-GemStone-Core >> initializeTransactionMutex1051
> >>>>>> Loaded -> Seaside-Core.gemstone-JohanBrichau.815 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-GemStone300-Core-DaleHenrichs.4 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-GemStone-Core-JohanBrichau.66 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-GemStone-Basic-Development-JohanBrichau.29 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Grease-Tests-Core-JohanBrichau.95 ---
> >>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
> >>>>>> Loaded -> Grease-Tests-GemStone-Core-dkh.14 ---
> >>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
> >>>>>> Loaded -> Seaside-Component-pmm.101 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-Canvas-pmm.127 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-Email-pmm.25 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-GemStone-Email-JohanBrichau.14 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-InternetExplorer-pmm.7 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-Session.gemstone-JohanBrichau.169 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-GemStone-Session-DaleHenrichs.3 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-RenderLoop-pmm.96 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-Tools-Core.gemstone-dkh.23 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-Flow-pmm.24 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-Examples-pmm.24 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-Widgets-StephanEggermont.35 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-GemStone-Tools-Production-JohanBrichau.15 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-Tools-Web-pmm.119 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>> Loaded -> Seaside-GemStone-Tools-Web-DaleHenrichs.4 ---
> >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Wed, May 21, 2014 at 3:06 PM, Dale Henrichs <
> >>>>>>
>
> >> dale.henrichs@
>
> >>> wrote:
> >>>>>>
> >>>>>>> Marching Orders! Very good ...
> >>>>>>>
> >>>>>>> Johan, Gerhard, et. al., I want to follow your lead and fill in
> >>>>>>> where
> >>>>>>> the work is needed ...
> >>>>>>>
> >>>>>>> Do you guys think that getting Seaside/Zinc/etc. ported to
> >>>>>>> GemStone3.2
> >>>>>>> takes precedence over getting Zinc running on GemStone3.1?
> >>>>>>>
> >>>>>>> I can take a crack at solving Gerhard's Seaside3.1 loading error,
> >>>>>>> but
> >>>>>>> Zinc has been on the brink for so long, maybe I should hit it hard
> >>>>>>> and get
> >>>>>>> the tests passing in GemStone 3.1 (encoding issues are right up my
> >>>>>>> alley:)?
> >>>>>>>
> >>>>>>> If there are other outstanding problems that folks are looking at
> >>>>>>> they
> >>>>>>> can be added into the mix...
> >>>>>>>
> >>>>>>> Dale
> >>>>>>>
> >>>>>>>
> >>>>>>> On Tue, May 20, 2014 at 10:42 PM, Johan Brichau &lt;
>
> >> johan@
>
> >> &gt;
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Hi all,
> >>>>>>>>
> >>>>>>>> I have been tampering off and on over the last few months to make
> >>>>>>>> Zinc 2.4.3 work in Gemstone.
> >>>>>>>>
> >>>>>>>> I made a pull request [1] with my changes, though not all tests
> are
> >>>>>>>> passing and since most of the changes had to do with encoding,
> byte
> >>>>>>>> arrays
> >>>>>>>> vs strings, multibyte strings, etc... I really need someone to
> take
> >>>>>>>> a look
> >>>>>>>> at them. Also, the pace is quite slow by myself ;-)
> >>>>>>>>
> >>>>>>>> This email is just to make sure that the pull request does not go
> >>>>>>>> unnoticed for someone wanting to take up work on the port.
> >>>>>>>>
> >>>>>>>> cheers!
> >>>>>>>> Johan
> >>>>>>>>
> >>>>>>>> [1] https://github.com/glassdb/zinc/pull/48
> >>>>>>>> _______________________________________________
> >>>>>>>> Glass mailing list
> >>>>>>>>
>
> >> Glass@.gemtalksystems
>
> >>>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> Glass mailing list
> >>>>>>>
>
> >> Glass@.gemtalksystems
>
> >>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Glass mailing list
> >>>>>>
>
> >> Glass@.gemtalksystems
>
> >>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Mariano
> >>>>> http://marianopeck.wordpress.com
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Mariano
> >>> http://marianopeck.wordpress.com
> >>>
> >>
> >>
> >>
> >> --
> >> Mariano
> >> http://marianopeck.wordpress.com
> >>
> >> _______________________________________________
> >> seaside mailing list
>
> >> seaside@.squeakfoundation
>
> >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
>
>
>
> --
> View this message in context:
> http://forum.world.st/Re-Cannot-load-Seaside-anymore-in-a-just-migrated-GemStone-WAS-Re-Glass-Zinc-2-4-3-on-Gemstone-tp4855877p4886223.html
> Sent from the Seaside General mailing list archive at Nabble.com.
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>



-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160324/b3595ca9/attachment-0001.htm
From dale.henrichs at gemtalksystems.com  Thu Mar 24 14:16:23 2016
From: dale.henrichs at gemtalksystems.com (Dale Henrichs)
Date: Thu Mar 24 14:16:30 2016
Subject: [Seaside] Re: Cannot load Seaside anymore in a just-migrated
	GemStone [WAS] Re: [Glass] Zinc 2.4.3 on Gemstone
In-Reply-To: <CAA+-=mXMJ8Y2WxZpSLj3zXfgqBhr8KZYFWWfSm=wKeX8M77RfA@mail.gmail.com>
References: <CAA+-=mUkoMGR3KEkR8+VOW3-Wc3FOawQyiv-JTqKDCHJO-fudw@mail.gmail.com>
	<1458794170458-4886222.post@n4.nabble.com>
	<1458794460742-4886223.post@n4.nabble.com>
	<CAA+-=mXMJ8Y2WxZpSLj3zXfgqBhr8KZYFWWfSm=wKeX8M77RfA@mail.gmail.com>
Message-ID: <56F3F6B7.1060707@gemtalksystems.com>

Good point - issue created[1]

[1] https://github.com/GsDevKit/GsDevKit_home/issues/88

On 3/24/16 5:32 AM, Mariano Martinez Peck wrote:
> Hi Paul,
>
> I will answer just in case others may find the same issue in the future.
>
> As you know, at the time of loading a class side #initialize, 
> Monticello checks if it has already been run or not and only run if it 
> is has not. Re-initializing seaside (re-sending class side initialize) 
> is the problem as it brings problems like the one you mention.
>
> The problem is that during the GemStone upgrade, the Monticello caches 
> are cleared. But Seaside code is still there. So...when you try to 
> load Seaside again in a upgraded stone, the Monticello cache is empty 
> and hence all class #initialize are executed again in a env where they 
> HAD already been initialized before (hence the problem).
>
> The solution I found is to re-load all my app (and seaside) in a way 
> of NOT executing class side #initialize. This must be done only once 
> as this will fill monticello cache and next times it will not try to 
> run #initialize (unless the method source has changed):
>
>
>   GsDeployer
>     deploy: [
>       [
>       [
>       [
>       Metacello new
>         configuration: 'MyApp';
>         repository: 'http://smalltalkhub.com/mc/MyApp/MyApp/main';
>         version: '1.6';
>         get;
>         onConflictUseIncoming: #('Seaside3') useLoaded: #('Grease');
>         onUpgrade: [ :ex :loaded :incoming |
>               incoming baseName = 'XMLSupport'
>                 ifTrue: [
>                   "I could use #useLoaded but the one currently coming 
> with GemStone has a broken versionString."
>                   ex allowEvenIfLocked ]
>                 ifFalse: [
>                   "default"
>                   ex useIncoming ] ];
>         load: #('MyPackages') ]
>         on: MCPerformPostloadNotification
>         do: [ :ex |
>           (ex postloadClass name beginsWith: 'WA')
>             ifTrue: [
>               Transcript
>                 show:
>                   ' Skipping class side initialization of ' , ex 
> postloadClass name asString.
>               ex resume: false ]
>             ifFalse: [ ex resume: true ] ] ]
>         on: Warning
>         do: [ :ex |
>           Transcript
>             cr;
>             cr;
>             show: '====================================================';
>             cr;
>             show: ex description;
>             cr;
>             cr;
>             show: '====================================================';
>             cr.
>           ex resume ] ]
>         ensure: [
>           System
>             performOnServer:
>               'rm -rf /tmp/curl*; rm -rf /tmp/github*; rm -rf 
> /tmp/*tmpgithub*; rm -rf /tmp/zip.err' ] ].
>   System commitTransaction
>
>
> The important part is the error block for 
> MCPerformPostloadNotification (which is sent when it is about to run 
> class side #initialize).
>
> Once above code has been run (once), then you can load again your code 
> in the normal way.
>
>
> *Dale, we should add this seaside re-load to the upgradeSeaside script...*
>
> Cheers,
>
>
>
>
> On Thu, Mar 24, 2016 at 1:41 AM, Paul DeBruicker <pdebruic@gmail.com 
> <mailto:pdebruic@gmail.com>> wrote:
>
>
>     Oh wait.
>
>
>     WAEnvironment initialize.
>
>
>     Seemed to have fixed it.  Following the senders of a message helps
>     more than
>     writing emails some times....
>
>
>
>     Thanks
>
>     Paul
>
>
>
>     Paul DeBruicker wrote
>     > Hi Mariano,
>     >
>     >
>     > I just ran into this issue.  Did you end up finding a solution?
>     >
>     >
>     > Thanks
>     >
>     > Paul
>     >
>     > Mariano Martinez Peck wrote
>     >> On Thu, Oct 15, 2015 at 4:25 PM, Mariano Martinez Peck <
>
>     >> marianopeck@
>
>     >>> wrote:
>     >>
>     >>> Hi guys,
>     >>>
>     >>> I have a weird scenario I cannot solve. I am trying to load my
>     app code
>     >>> (together with all it's dependencies) in a just migrated stone
>     (from
>     >>> GemStone 3.1.0.4 to GemStone 3.2.9). I performed all the steps
>     of the
>     >>> migration.  Yet, I have an error, pasted below. However, if I
>     run the
>     >>> same
>     >>> code to load my app in a fresh 3.2.9 extent, that works
>     perfectly. It
>     >>> only
>     >>> fails in my migrated (from 3.1.0.4) stone.
>     >>>
>     >>> The problem is in
>     >>>
>     >>> WAWalkbackErrorHandler class >> initialize
>     >>> WAAdmin applicationExceptionHandlingDefaults at:
>     #exceptionHandler put:
>     >>> self
>     >>>
>     >>> It fails because the
>     >>>
>     >>> WAConfiguration >> attributeAt: aSymbol
>     >>> ^ self attributeAt: aSymbol ifAbsent: [ WAAttributeNotFound
>     >>> signalWithKey:
>     >>> aSymbol ]
>     >>>
>     >>> gives a key not found.
>     >>>
>     >>> I did a search  in the mailing list and found related threads:
>     >>>
>     >>>
>     http://forum.world.st/Glass-Zinc-2-4-3-on-Gemstone-td4759789.html#a4759875
>     >>> https://github.com/seasidest/seaside/issues/643
>     >>>
>     >>> But none show a solution.
>     >>>
>     >>> And yes, it is obvious it will fail because:
>     >>>
>     >>> WAAdmin applicationExceptionHandlingDefaults allAttributes ->
>     >>>  anIdentityDictionary( )
>     >>>
>     >>> Also, as you can see, the result of WAAdmin
>     >>> applicationExceptionHandlingDefaults has no parent or anything:
>     >>>
>     >>> Inspect aWASharedConfiguration/
>     >>> --------------------
>     >>> .                     -> aWASharedConfiguration
>     >>> (class)@              -> WASharedConfiguration
>     >>> (oop)@                -> 1169561601
>     >>> (committed)@          -> true
>     >>> cachedSearchContexts@ -> anIdentityDictionary(
>     >>> #'exceptionHandler'->aWAAttributeSearchContext)
>     >>> expressions@          -> aDictionary( )
>     >>> name@                 -> 'Application Exception Handling Defaults'
>     >>> parents@              -> anOrderedCollection( )
>     >>>
>     >>>
>     >>> I even tried the re-initialization of Seaside as provided by
>     Bruno the
>     >>> other day:
>     >>>
>     >>> WAAdmin unregister: 'reps'.
>     >>> WAAdmin unregister: 'advisors'.
>     >>> WAAdmin unregister: 'clients'.
>     >>>
>     >>> WAGemStoneProductionErrorHandler initialize.
>     >>> WAWalkbackErrorHandler initialize.
>     >>> WARemoteDebuggingWalkbackErrorHandler initialize.
>     >>>
>     >>> [
>     >>>    WADispatcher default.
>     >>>    WASystemConfiguration allSubclasses
>     >>>      do: [ :each | each instance buildDescription ] ]
>     >>>      ensure: [ System commitTransaction ] .
>     >>>
>     >>>
>     >>> Still, same error.
>     >>>
>     >>>
>     >>> Any clues? Is there  way I can re-initialize all Seaside?
>     >>>
>     >>>
>     >>> This is the stack:
>     >>>
>     >>> aTDDebugger
>     >>> --------------------
>     >>> 1. WAAttributeNotFound(AbstractException)>>_signalWith: @6 line 25
>     >>> 2. WAAttributeNotFound(AbstractException)>>signal @2 line 47
>     >>> 3. WAAttributeNotFound class>>signalWithKey: @4 line 4
>     >>> 4. [] in ExecBlock0(WAConfiguration)>>attributeAt: @2 line 2
>     >>> 5. IdentityDictionary>>at:ifAbsent: @5 line 8
>     >>> 6.
>     WASharedConfiguration(WAConfiguration)>>attributeAt:ifAbsent: @3 line
>     >>> 2
>     >>> 7. WASharedConfiguration(WAConfiguration)>>attributeAt: @2 line 2
>     >>> 8. WASharedConfiguration(WAUserConfiguration)>>at:put: @2 line 7
>     >>> 9. WAWalkbackErrorHandler class>>initialize @3 line 2
>     >>> 10. MCMethodDefinition>>postload @11 line 6
>     >>> 11. MCMethodDefinition(MCDefinition)>>postloadOver: @2 line 2
>     >>> 12. [] in MCPackageLoader>>basicLoad @3 line 48
>     >>> 13. OrderedCollection(Collection)>>do: @5 line 10
>     >>> 14. OrderedCollection(Collection)>>do:displayingProgress: @2
>     line 3
>     >>> 15. [] in MCPackageLoader>>basicLoad @15 line 48
>     >>> 16. MCPackageLoader(ExecBlock)>>on:do: @3 line 42
>     >>> 17. [] in MCPackageLoader>>basicLoad @2 line 49
>     >>> 18. MCPackageLoader(ExecBlock)>>ensure: @2 line 12
>     >>> 19. MCPackageLoader>>basicLoad @11 line 51
>     >>> 20. [] in MCPackageLoader>>loadWithNameLike: @2 line 4
>     >>> 21. [] in
>     ExecBlock0(MCPackageLoader)>>useChangeSetNamed:during: @2 line
>     >>> 9
>     >>> 22. ExecBlock0(ExecBlock)>>ensure: @2 line 12
>     >>> 23. MCPackageLoader>>useChangeSetNamed:during: @9 line 9
>     >>> 24. MCPackageLoader>>useNewChangeSetNamedLike:during: @3 line 2
>     >>> 25. MCPackageLoader>>loadWithNameLike: @6 line 4
>     >>> 26. MCVersionLoader>>load @9 line 6
>     >>> 27. MetacelloGoferLoad(GoferLoad)>>execute @6 line 3
>     >>> 28. [] in
>     >>>
>     MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
>     >>> @5 line 17
>     >>> 29. [] in
>     >>>
>     MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
>     >>> @14 line 21
>     >>> 30.
>     MetacelloGemStonePlatform(MetacelloPlatform)>>do:displaying: @2 line
>     >>> 3
>     >>> 31.
>     >>>
>     MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer:
>     >>> @7 line 5
>     >>> 32.
>     >>>
>     MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadPackageDirective:gofer:
>     >>> @4 line 4
>     >>> 33. MetacelloPackageLoadDirective>>loadUsing:gofer: @2 line 3
>     >>> 34. [] in
>     >>>
>     ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>     >>> @2 line 3
>     >>> 35. OrderedCollection(Collection)>>do: @5 line 10
>     >>> 36.
>     >>>
>     MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>     >>> @3 line 3
>     >>> 37. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>     >>> 38. [] in
>     >>>
>     ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>     >>> @2 line 3
>     >>> 39. OrderedCollection(Collection)>>do: @5 line 10
>     >>> 40.
>     >>>
>     MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>     >>> @3 line 3
>     >>> 41. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>     >>> 42. [] in
>     >>>
>     ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>     >>> @2 line 3
>     >>> 43. OrderedCollection(Collection)>>do: @5 line 10
>     >>> 44.
>     >>>
>     MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>     >>> @3 line 3
>     >>> 45. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>     >>> 46. [] in
>     >>>
>     ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>     >>> @2 line 3
>     >>> 47. OrderedCollection(Collection)>>do: @5 line 10
>     >>> 48.
>     >>>
>     MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>     >>> @3 line 3
>     >>> 49. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>     >>> 50. [] in
>     >>>
>     ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>     >>> @2 line 3
>     >>> 51. OrderedCollection(Collection)>>do: @5 line 10
>     >>> 52.
>     >>>
>     MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer:
>     >>> @3 line 3
>     >>> 53. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4
>     >>> 54.
>     >>>
>     MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadWithPolicy:
>     >>> @7 line 7
>     >>> 55. MetacelloLoaderPolicy>>load @6 line 4
>     >>> 56. MetacelloFetchingMCSpecLoader>>doLoad @4 line 3
>     >>> 57. [] in
>     ExecBlock0(MetacelloMCVersion)>>doLoadRequiredFromArray: @2
>     >>> line
>     >>> 12
>     >>> 58.
>     MetacelloGemStonePlatform(MetacelloPlatform)>>do:displaying: @2 line
>     >>> 3
>     >>> 59. [] in MetacelloMCVersion>>doLoadRequiredFromArray: @7 line 12
>     >>> 60. MetacelloMCVersion(ExecBlock)>>ensure: @2 line 12
>     >>> 61. MetacelloMCVersion>>doLoadRequiredFromArray: @22 line 16
>     >>> 62. Array(Collection)>>loadRequiredForMetacelloMCVersion: @2
>     line 3
>     >>> 63. MetacelloMCVersion>>load: @2 line 3
>     >>> 64. [] in
>     >>> MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade:
>     >>> @10 line 16
>     >>> 65. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>     >>> 66. [] in MetacelloScriptEngine>>handleNotificationsForAction:
>     @6 line 6
>     >>> 67. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>     >>> 68. [] in MetacelloScriptEngine>>handleNotificationsForAction:
>     @4 line
>     >>> 14
>     >>> 69. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>     >>> 70. [] in MetacelloScriptEngine>>handleNotificationsForAction:
>     @2 line
>     >>> 20
>     >>> 71. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42
>     >>> 72. MetacelloScriptEngine>>handleNotificationsForAction: @2
>     line 24
>     >>> 73. [] in
>     >>> MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade:
>     >>> @2 line 5
>     >>> 74. MetacelloScriptEngine(ExecBlock)>>ensure: @2 line 12
>     >>> 75. MetacelloProjectRegistration
>     class>>copyRegistryRestoreOnErrorWhile:
>     >>> @8 line 14
>     >>> 76.
>     MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade: @2
>     >>> line 3
>     >>> 77. MetacelloScriptEngine>>load: @2 line 3
>     >>> 78. [] in
>     MetacelloScriptApiExecutor(MetacelloScriptExecutor)>>execute:
>     >>> @11 line 15
>     >>> 79. [] in MetacelloScriptApiExecutor>>executeString:do: @5 line 6
>     >>> 80. Array(Collection)>>do: @5 line 10
>     >>> 81. MetacelloScriptApiExecutor>>executeString:do: @6 line 4
>     >>> 82. String>>execute:against: @2 line 2
>     >>> 83.
>     MetacelloScriptApiExecutor(MetacelloScriptExecutor)>>execute: @6
>     >>> line 9
>     >>> 84. Metacello>>execute:args: @8 line 5
>     >>> 85. Metacello>>load: @2 line 2
>     >>> 86. [] in Executed Code
>     >>> 87. ExecBlock0(ExecBlock)>>ensure: @2 line 12
>     >>> 88. Executed Code
>     >>> 89.
>     String(CharacterCollection)>>evaluateIn:symbolList:literalVars: @4
>     >>> line 13
>     >>> 90.
>     >>>
>     TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>evaluateString:
>     >>> @5 line 3
>     >>> 91.
>     >>>
>     TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>doItMenuAction:selectedText:
>     >>> @2 line 2
>     >>> 92.
>     >>>
>     TDWorkspaceClientElementBuilder(TDWindowBuilder)>>handleMenuActions:listElement:actionArg:
>     >>> @12 line 10
>     >>> 93. [] in
>     >>>
>     TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>menuActionBlock
>     >>> @6 line 8
>     >>> 94.
>     >>>
>     TDWorkspaceClientElementBuilder(ExecBlock)>>value:value:value:value:value:
>     >>> @2 line 11
>     >>> 95. GsNMethod class>>_gsReturnToC @1 line 1
>     >>>
>     >>>
>     >>> Thanks in advance for any help.
>     >>>
>     >>> On Thu, Oct 15, 2015 at 1:40 PM, Gerhard Obermann &lt;
>
>     >> obi068@
>
>     >> &gt;
>     >>> wrote:
>     >>>
>     >>>> Hi,
>     >>>>
>     >>>> Not really, i only found the following in my notes.
>     >>>>
>     >>>> HTH
>     >>>> Gerhard
>     >>>>
>     >>>>
>     >>>>
>     >>>>    -
>     >>>>
>     >>>>    Load Seaside 3.1.x but don?t initialize Seaside Classes
>     >>>>
>     >>>>
>     >>>> | performInitialization |
>     >>>>
>     >>>> performInitialization := #().
>     >>>>
>     >>>> [
>     >>>>
>     >>>> GsDeployer deploy: [  Metacello new
>     >>>>
>     >>>>    baseline: 'Seaside3';
>     >>>>
>     >>>>    repository:
>     'github://glassdb/Seaside31:gemstone3.1/repository';
>     >>>>
>     >>>>    load: 'CI'].
>     >>>>
>     >>>> ] on: MCPerformPostloadNotification do: [:ex |
>     >>>>
>     >>>>           (performInitialization includes: ex postloadClass
>     >>>> theNonMetaClass name)
>     >>>>
>     >>>>             ifTrue: [
>     >>>>
>     >>>>               "perform initialization"
>     >>>>
>     >>>>               ex resume: true ]
>     >>>>
>     >>>>             ifFalse: [
>     >>>>
>     >>>>               GsFile gciLogServer: ' Skip ', ex postloadClass
>     name
>     >>>> asString, ' initialization.'.
>     >>>>
>     >>>>                ex resume: false ] ]
>     >>>>
>     >>>>
>     >>>> On Thu, Oct 15, 2015 at 5:47 PM, Mariano Martinez Peck <
>     >>>>
>
>     >> marianopeck@
>
>     >>> wrote:
>     >>>>
>     >>>>> Hi Gerhard,
>     >>>>>
>     >>>>> I am getting the exact same issue. Do you remember what you
>     did to fix
>     >>>>> it?
>     >>>>>
>     >>>>> Thanks,
>     >>>>>
>     >>>>> On Wed, May 21, 2014 at 10:39 AM, Gerhard Obermann &lt;
>
>     >> obi068@
>
>     >> &gt;
>     >>>>> wrote:
>     >>>>>
>     >>>>>> Hi Dale!
>     >>>>>>
>     >>>>>> I think as soon as I can load the stuff in my upgraded 3.2.
>     DB, i can
>     >>>>>> test and contribute to zink and/or Glass / Seaside 3.1.
>     >>>>>> If it wont work until tomorrow i have to stay on 3.1.0.5
>     for the next
>     >>>>>> few months at least.
>     >>>>>>
>     >>>>>> At the moment i am trying to load Seaside 3.1.1 with
>     >>>>>> PS: To be able to load this i have loaded the Baseline packages
>     >>>>>> BaselineOfGLASS1,
>     >>>>>> BaselineOfSeaside3 , BaselineOfZinc manually from my forked GIT
>     >>>>>> clone.
>     >>>>>>
>     >>>>>> GsDeployer deploy: [
>     >>>>>>   Metacello new
>     >>>>>>     configuration: 'Grease';
>     >>>>>>     repository: '
>     >>>>>>
>     http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>     >>>>>>     get.
>     >>>>>>
>     >>>>>>   "Load Seaside31"
>     >>>>>> GsDeployer deploy: [
>     >>>>>>   Metacello new
>     >>>>>>     baseline: 'Seaside3';
>     >>>>>>     repository:
>     'github://glassdb/Seaside31:gemstone3.1/repository';
>     >>>>>>     load: 'CI'].
>     >>>>>>
>     >>>>>>
>     >>>>>> Not sure if i need to load Metacello new
>     >>>>>>     baseline: 'GLASS1';
>     >>>>>>     repository: 'github://glassdb/glass:master/repository';
>     >>>>>>     load.
>     >>>>>> after the upgrade.
>     >>>>>>
>     >>>>>> What is the difference between
>     >>>>>>   (ConfigurationOfGLASS project version: '1.0-beta.9.1') load
>     >>>>>> and
>     >>>>>>  Metacello new
>     >>>>>>     baseline: 'GLASS1';
>     >>>>>>     repository: 'github://glassdb/glass:master/repository';
>     >>>>>>     load.
>     >>>>>>
>     >>>>>> *The load of the Seaside package failed with the init of *
>     >>>>>> *WAWalkbackErrorHandler => initialize*
>     >>>>>> * WAAdmin applicationExceptionHandlingDefaults at:
>     #exceptionHandler
>     >>>>>> put: self*
>     >>>>>>
>     >>>>>> [1] WAAttributeNotFound (AbstractException) >> _signalWith:
>     >>>>>> inCextensionArg: nil
>     >>>>>> res: nil
>     >>>>>> .t1: a WAAttributeNotFound occurred (error 2710)
>     >>>>>> receiver: a WAAttributeNotFound occurred (error 2710)
>     >>>>>> [2] WAAttributeNotFound (AbstractException) >> signal
>     >>>>>> receiver: a WAAttributeNotFound occurred (error 2710)
>     >>>>>> [3] WAAttributeNotFound class >> signalWithKey:
>     >>>>>> aSymbol: #'exceptionHandler'
>     >>>>>> receiver: WAAttributeNotFound
>     >>>>>> [4] [] in  ExecBlock0 (WAConfiguration) >> attributeAt:
>     >>>>>> aSymbol: #'exceptionHandler'
>     >>>>>> receiver: nil
>     >>>>>> [5] IdentityDictionary >> at:ifAbsent:
>     >>>>>> aKey: #'exceptionHandler'
>     >>>>>> aBlock: anExecBlock0
>     >>>>>> anAssoc: nil
>     >>>>>> .t1: anExecBlock0
>     >>>>>> receiver: anIdentityDictionary( )
>     >>>>>> [6] WASharedConfiguration (WAConfiguration) >>
>     attributeAt:ifAbsent:
>     >>>>>> aSymbol: #'exceptionHandler'
>     >>>>>> aBlock: anExecBlock0
>     >>>>>> receiver: aWASharedConfiguration
>     >>>>>> [7] WASharedConfiguration (WAConfiguration) >> attributeAt:
>     >>>>>> aSymbol: #'exceptionHandler'
>     >>>>>> aSymbol: #'exceptionHandler'
>     >>>>>> receiver: aWASharedConfiguration
>     >>>>>> [8] WASharedConfiguration (WAUserConfiguration) >> at:put:
>     >>>>>> aSymbol: #'exceptionHandler'
>     >>>>>> anObject: WAWalkbackErrorHandler
>     >>>>>> receiver: aWASharedConfiguration
>     >>>>>> [9] WAWalkbackErrorHandler class >> initialize
>     >>>>>> receiver: WAWalkbackErrorHandler
>     >>>>>> [10] MCMethodDefinition >> postload
>     >>>>>> receiver: aMCMethodDefinition(WAWalkbackErrorHandler
>     >>>>>> class>>initialize)
>     >>>>>>
>     >>>>>>
>     >>>>>> Transcript:
>     >>>>>> Fetched -> FastCGIPool-dkh.2 ---
>     >>>>>> http://seaside.gemstone.com/ss/fastcgi
>     >>>>>> --- http://seaside.gemstone.com/ss/fastcgiredirecting to
>     >>>>>> http://seaside.gemtalksystems.com/ss/fastcgi/FastCGI-dkh.33.mcz
>     >>>>>>
>     >>>>>> Fetched -> FastCGI-dkh.33 ---
>     http://seaside.gemstone.com/ss/fastcgi
>     >>>>>> --- http://seaside.gemstone.com/ss/fastcgi
>     >>>>>> Fetched -> Seaside-Adaptors-FastCGI-dkh.26 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository
>     >>>>>> Loaded -> Grease-Core-JohanBrichau.86 ---
>     >>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>     >>>>>> Loaded -> Grease-GemStone-Core-JohanBrichau.52 ---
>     >>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>     >>>>>> Evaluated -> Grease-GemStone-Core >>
>     initializeTransactionMutex1051
>     >>>>>> Loaded -> Seaside-Core.gemstone-JohanBrichau.815 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-GemStone300-Core-DaleHenrichs.4 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-GemStone-Core-JohanBrichau.66 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded ->
>     Seaside-GemStone-Basic-Development-JohanBrichau.29 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Grease-Tests-Core-JohanBrichau.95 ---
>     >>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>     >>>>>> Loaded -> Grease-Tests-GemStone-Core-dkh.14 ---
>     >>>>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache
>     >>>>>> Loaded -> Seaside-Component-pmm.101 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-Canvas-pmm.127 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-Email-pmm.25 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-GemStone-Email-JohanBrichau.14 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-InternetExplorer-pmm.7 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-Session.gemstone-JohanBrichau.169 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-GemStone-Session-DaleHenrichs.3 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-RenderLoop-pmm.96 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-Tools-Core.gemstone-dkh.23 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-Flow-pmm.24 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-Examples-pmm.24 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-Widgets-StephanEggermont.35 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-GemStone-Tools-Production-JohanBrichau.15 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-Tools-Web-pmm.119 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>> Loaded -> Seaside-GemStone-Tools-Web-DaleHenrichs.4 ---
>     >>>>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache
>     >>>>>>
>     >>>>>>
>     >>>>>>
>     >>>>>>
>     >>>>>>
>     >>>>>>
>     >>>>>>
>     >>>>>> On Wed, May 21, 2014 at 3:06 PM, Dale Henrichs <
>     >>>>>>
>
>     >> dale.henrichs@
>
>     >>> wrote:
>     >>>>>>
>     >>>>>>> Marching Orders! Very good ...
>     >>>>>>>
>     >>>>>>> Johan, Gerhard, et. al., I want to follow your lead and
>     fill in
>     >>>>>>> where
>     >>>>>>> the work is needed ...
>     >>>>>>>
>     >>>>>>> Do you guys think that getting Seaside/Zinc/etc. ported to
>     >>>>>>> GemStone3.2
>     >>>>>>> takes precedence over getting Zinc running on GemStone3.1?
>     >>>>>>>
>     >>>>>>> I can take a crack at solving Gerhard's Seaside3.1 loading
>     error,
>     >>>>>>> but
>     >>>>>>> Zinc has been on the brink for so long, maybe I should hit
>     it hard
>     >>>>>>> and get
>     >>>>>>> the tests passing in GemStone 3.1 (encoding issues are
>     right up my
>     >>>>>>> alley:)?
>     >>>>>>>
>     >>>>>>> If there are other outstanding problems that folks are
>     looking at
>     >>>>>>> they
>     >>>>>>> can be added into the mix...
>     >>>>>>>
>     >>>>>>> Dale
>     >>>>>>>
>     >>>>>>>
>     >>>>>>> On Tue, May 20, 2014 at 10:42 PM, Johan Brichau &lt;
>
>     >> johan@
>
>     >> &gt;
>     >>>>>>> wrote:
>     >>>>>>>
>     >>>>>>>> Hi all,
>     >>>>>>>>
>     >>>>>>>> I have been tampering off and on over the last few months
>     to make
>     >>>>>>>> Zinc 2.4.3 work in Gemstone.
>     >>>>>>>>
>     >>>>>>>> I made a pull request [1] with my changes, though not all
>     tests are
>     >>>>>>>> passing and since most of the changes had to do with
>     encoding, byte
>     >>>>>>>> arrays
>     >>>>>>>> vs strings, multibyte strings, etc... I really need
>     someone to take
>     >>>>>>>> a look
>     >>>>>>>> at them. Also, the pace is quite slow by myself ;-)
>     >>>>>>>>
>     >>>>>>>> This email is just to make sure that the pull request
>     does not go
>     >>>>>>>> unnoticed for someone wanting to take up work on the port.
>     >>>>>>>>
>     >>>>>>>> cheers!
>     >>>>>>>> Johan
>     >>>>>>>>
>     >>>>>>>> [1] https://github.com/glassdb/zinc/pull/48
>     >>>>>>>> _______________________________________________
>     >>>>>>>> Glass mailing list
>     >>>>>>>>
>
>     >> Glass@.gemtalksystems
>
>     >>>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>     >>>>>>>>
>     >>>>>>>
>     >>>>>>>
>     >>>>>>> _______________________________________________
>     >>>>>>> Glass mailing list
>     >>>>>>>
>
>     >> Glass@.gemtalksystems
>
>     >>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>     >>>>>>>
>     >>>>>>>
>     >>>>>>
>     >>>>>> _______________________________________________
>     >>>>>> Glass mailing list
>     >>>>>>
>
>     >> Glass@.gemtalksystems
>
>     >>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>     >>>>>>
>     >>>>>>
>     >>>>>
>     >>>>>
>     >>>>> --
>     >>>>> Mariano
>     >>>>> http://marianopeck.wordpress.com
>     >>>>>
>     >>>>
>     >>>>
>     >>>
>     >>>
>     >>> --
>     >>> Mariano
>     >>> http://marianopeck.wordpress.com
>     >>>
>     >>
>     >>
>     >>
>     >> --
>     >> Mariano
>     >> http://marianopeck.wordpress.com
>     >>
>     >> _______________________________________________
>     >> seaside mailing list
>
>     >> seaside@.squeakfoundation
>
>     >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
>
>
>
>     --
>     View this message in context:
>     http://forum.world.st/Re-Cannot-load-Seaside-anymore-in-a-just-migrated-GemStone-WAS-Re-Glass-Zinc-2-4-3-on-Gemstone-tp4855877p4886223.html
>     Sent from the Seaside General mailing list archive at Nabble.com.
>     _______________________________________________
>     seaside mailing list
>     seaside@lists.squeakfoundation.org
>     <mailto:seaside@lists.squeakfoundation.org>
>     http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
>
>
> -- 
> Mariano
> http://marianopeck.wordpress.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160324/c8cefafa/attachment-0001.htm
From tudor at tudorgirba.com  Fri Mar 25 14:47:28 2016
From: tudor at tudorgirba.com (Tudor Girba)
Date: Fri Mar 25 14:47:32 2016
Subject: [Seaside] [ann] pharo consortium membership matching campaign
Message-ID: <ED15F018-4700-4019-BF98-BB701425FDD1@tudorgirba.com>

Hi,

The Pharo Board is proud to announce a special campaign for attracting new Pharo Consortium members during 2016:
http://consortium.pharo.org/web/Membership 

A new fund has been created from which the Consortium will receive the equivalent of one yearly membership fee for every new member, and the increment in yearly fees for every upgrading member. For example, if a new company joins the Consortium as a Silver member (2000 EUR / year), the fund will contribute a one-time amount of 2000 EUR to the Consortium. Similarly, if a company upgrades from Bronze (1000 EUR / year) to Gold (4000 EUR / year), the fund will contribute a one-time amount of 3000 EUR. 

This campaign will take place until the end of 2016, or until the fund is depleted. Currently, the fund totals 21000 EUR, a sum which is graciously supported by three companies:
- LabWare Inc (http://labware.com)
- ObjectProfile (http://objectprofile.com)
- feenk gmbh (http://feenk.com)

This is an exciting development that paves the way to attract more industrial interest around Pharo. Please help us by spreading the word about this campaign.

Cheers,
The Pharo Board
From heniart.thomas at gmail.com  Sat Mar 26 11:59:17 2016
From: heniart.thomas at gmail.com (Thomas Heniart)
Date: Sat Mar 26 11:59:18 2016
Subject: [Seaside] How to use bootstrap popover ?
Message-ID: <CALPibtzYFzBFWn=BE+i3A2r8u1_wX9rM-v6MpYR4kaHudRff=Q@mail.gmail.com>

Hi guys,

I tried to use the bootstrap popover but unfortunately I can't make it work
and I don't know why

I work on a really simple example, just a component register with
JQDevelopmentLibrary and TBSDevelopmentLibrary.

The content of renderContentOn: is
        html script: 'initialize_popover()'.
html tbsButton
beDefault;
attributeAt: 'data-toggle' put: 'popover';
attributeAt: 'title' put: 'Popover test';
attributeAt: 'data-placement' put: 'right';
attributeAt: 'data-content' put: 'This is a test';
with: 'Button popover test'

And the js method initialize_popover() is define in script method of my
component with $("[data-toggle = 'popover']").popover()

And that's all

Then I load this little app, no error in the debugger but when I click on
my button, the popover doesn't appear

Maybe I'm missing something but I don't know what :/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160326/e7e9c0a1/attachment.htm
From bernhard at pieber.com  Sun Mar 27 05:37:35 2016
From: bernhard at pieber.com (Bernhard Pieber)
Date: Sun Mar 27 05:37:43 2016
Subject: Upload large, was: Re: [Seaside] ZINC - Kom ...
In-Reply-To: <783FD498-A3B3-41CD-BAB3-807E5D33F9EB@inceptive.be>
References: <CAJS2e5gNPhiKhA8dJqE5d4tvG_MmLxEm=PpzJge3vT0fEEgXZw@mail.gmail.com>
	<A14BAD65-45B7-434E-881E-84CF989B3023@stfx.eu>
	<CAJS2e5j7bju37PLvqEkOReqcXZiNeZPzhWQxOL0BmKX3b76_qg@mail.gmail.com>
	<98771D4A-2BD7-4228-B765-DCDD891BBDAC@stfx.eu>
	<CAJS2e5hE+nKPDbuuFbDVpQWxh8qxvcYQn1tv-7e8sOgUsyTM+A@mail.gmail.com>
	<B05C8B00-5449-463F-BE78-D3B275779490@gmx.de>
	<783FD498-A3B3-41CD-BAB3-807E5D33F9EB@inceptive.be>
Message-ID: <2C7AF7D1-F248-4084-B9BD-3A512A603E9A@pieber.com>

Hi Johan,

Thanks for your blog post.

I found Nick Ager?s blog posts regarding Nginx:
http://nickager.com/tags/#nginx

You might want to link to them from yours, maybe?

Cheers,
Bernhard

> Am 19.01.2016 um 05:18 schrieb Johan Brichau <johan@inceptive.be>:
> 
> Hi Tobias,
> 
> This is what we do since years :)
> There was a blog post online describing all the details but I don?t find it anymore.
> The only think I can find is Nick Ager?s reply when we had a little trouble setting it up [1]
> 
> I might try to separate off the code to spare you some time.
> It?s quite simple, actually.
> 
> [1] http://forum.world.st/Using-nginx-file-upload-module-td3591666.html
> 
> Johan
> 
>> On 18 Jan 2016, at 18:56, Tobias Pape <Das.Linux@gmx.de> wrote:
>> 
>> Hey all
>> 
>> just my 2ct while skimming the thread.
>> 
>> I have upload problems with my seaside app 
>> and plan to tackle them by utilizing the reverse proxy.
>> In my scenario, that is nginx, wich ships an "upload module"
>> 	https://www.nginx.com/resources/wiki/modules/upload/
>> 
>> Given that, the upload is handled by the reverse proxy and only when
>> the file is already on the file system, the backend (seaside in this case)
>> would get a notification request.
>> 
>> I plan to implement this within the next 6 weeks, so if I get going something
>> usable, I'll probably hand it back to the seaside community :)
>> Remind me if I forget ;)
>> 
>> best regards
>> 	-Tobias
>> 
>> 
>> On 18.01.2016, at 18:00, Robert Kuszinger <kuszinger@giscom.hu> wrote:
>> 
>>> 
>>> Sven,
>>> 
>>> thanks for the demo. Zn without Seaside is just fine if it could work. A one-field form with only the uploaded file could work also. Some javascript addition on client side is acceptable - I'll see then. I understand that a simple file upload is also "composite" data with filename and binary content...
>>> 
>>> Usage: An office need to receive large map / digital survey data files from clients. Now they post it on CD or DVD disks, however the typical amount is 100-200 Mb in one or two or more files (depending one who has heard about ZIP and who hasn't :) - really! ). So we are trying to create an upload portal where they could login and then upload files to folders where folder name contains their ID and date. That's it.
>>> 
>>> No, SSH/SFTP or FTP with OS auth is not acceptable. They want pure browser upload as clients know this from their everyday life. And they could also add metadata about their uploads.
>>> 
>>> Login, auth to existing client database is done in Seaside/Pharo in a few hours, works nicely.
>>> 
>>> I would be great to create the upload receiving part also with Pharo at least.
>>> 
>>> All this stuff is behind and IIS/ARR - tested for large uploads, worked well when extending timeout limitations is IIS (with Kom but eating memory, maybe not so much as Zinc now, but it had the codepage problem I wanted debug earlier). OS is Windows Server 2008 R2Datacenter Edition, IIS 7.5.
>>> 
>>> I'm developing on Linux and testing on Windows Server 2008 configured to the same setup (IIS, ARR, etc.)
>>> 
>>> This is the scenario.
>>> 
>>> Robert
>>> 
>>> 
>>> 
>>> Sven Van Caekenberghe <sven@stfx.eu> ezt ?rta (id?pont: 2016. jan. 18., H, 16:30):
>>> Robert,
>>> 
>>> This is not such an easy problem, you have to really understand HTTP.
>>> 
>>> BTW, such huge uploads don't seem a very good idea anyway, you will get annoying timeouts as well. I am curious, what is in those files ?
>>> 
>>> Now, here is the key idea (pure Zn, no Seaside, quick hack):
>>> 
>>> (ZnServer startOn: 1701)
>>> reader: [ :stream | ZnRequest readStreamingFrom: stream ];
>>> maximumEntitySize: 100*1024*1024;
>>> onRequestRespond: [ :req |
>>>   '/tmp/upload.bin' asFileReference writeStreamDo: [ :out |
>>>      out binary.
>>>      ZnUtils streamFrom: req entity stream to: out ].
>>>   ZnResponse ok: (ZnEntity text: 'done') ];
>>> yourself.
>>> 
>>> You would use it like this:
>>> 
>>> $ echo one two three > data.bin
>>> $ curl -X POST -d @data.bin http://localhost:1701
>>> $ cat /tmp/upload.bin
>>> one two three
>>> 
>>> With a 1Mb data file generated from Pharo:
>>> 
>>> '/tmp/data.txt' asFileReference writeStreamDo: [ :out |
>>> 1 * 1024 timesRepeat: [
>>>   1 to: 32 do: [ :each |
>>>     out << Character alphabet << (each printStringPadded: 5); lf ] ] ]
>>> 
>>> $ curl -v -X POST --data-binary @data2.bin http://localhost:1701
>>> * Rebuilt URL to: http://localhost:1701/
>>> *   Trying ::1...
>>> * connect to ::1 port 1701 failed: Connection refused
>>> *   Trying 127.0.0.1...
>>> * Connected to localhost (127.0.0.1) port 1701 (#0)
>>>> POST / HTTP/1.1
>>>> Host: localhost:1701
>>>> User-Agent: curl/7.43.0
>>>> Accept: */*
>>>> Content-Length: 1048576
>>>> Content-Type: application/x-www-form-urlencoded
>>>> Expect: 100-continue
>>>> 
>>> * Done waiting for 100-continue
>>> * We are completely uploaded and fine
>>> < HTTP/1.1 200 OK
>>> < Content-Type: text/plain;charset=utf-8
>>> < Content-Length: 4
>>> < Date: Mon, 18 Jan 2016 14:56:53 GMT
>>> < Server: Zinc HTTP Components 1.0
>>> <
>>> * Connection #0 to host localhost left intact
>>> done
>>> 
>>> $ diff data2.bin /tmp/upload.bin
>>> 
>>> This code is totally incomplete, you need lots of error handling. Furthermore, working with streaming requests is dangerous, because you are responsible for reading the bodies correctly.
>>> 
>>> Also, if you want an upload in a form, you will have to parse that form (see ZnApplicationFormUrlEncodedEntity and ZnMultiPartFormDataEntity), you will then again take it in memory. These things are normally done for you by Zn and/or Seaside.
>>> 
>>> I also tried with 100Mb, it worked, but it took several minutes, like 10 to 15. The #streamFrom:to: above uses a 16Kb buffer, which is probably too small for this use case. Maybe curl doesn't upload very aggressively. Performance is another issue.
>>> 
>>> That is why I asked what is in the files, what you eventually want to do with it. Is the next processing step in Pharo too ?
>>> 
>>> Maybe all that is needed is giving Pharo more memory. What platform are you on ?
>>> 
>>> Sven
>>> 
>>>> On 18 Jan 2016, at 13:39, Robert Kuszinger <kuszinger@giscom.hu> wrote:
>>>> 
>>>> Sven,
>>>> 
>>>> thanks for the comments. I understand all.
>>>> 
>>>> Could you please clarify this:
>>>> 
>>>> "Technically, it would be possible to write a Zn handler that can accept a large upload in a streaming fashion (and save it to a file for example), but I don't think that will happen with Seaside - so you will pull that all in memory."
>>>> 
>>>> Is there a chance to create a streaming solution? Is it documented somewhere? Why do you think it won't happen with Seaside? Is there a Seaside set or design limitation?
>>>> 
>>>> 
>>>> Answering on how it goes:
>>>> 
>>>> 20 - 40 - 10MB upload in seconds. Now it seems to stuck on a ~ 120 MB upload. Pharo memory (windows OS) seemed to grow ~ 441 MB. "Space is low" warning window appeared. I've clicked on "Proceed" just for curiosity but no reaction in the Pharo gui... hmmm...
>>>> 
>>>> 
>>>> thanks
>>>> Robert
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 2016-01-18 13:27 GMT+01:00 Sven Van Caekenberghe <sven@stfx.eu>:
>>>> 
>>> _______________________________________________
>>> seaside mailing list
>>> seaside@lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> 
>> _______________________________________________
>> seaside mailing list
>> seaside@lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> 
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

From stephan at stack.nl  Sun Mar 27 08:34:49 2016
From: stephan at stack.nl (Stephan Eggermont)
Date: Sun Mar 27 08:35:09 2016
Subject: [Seaside] Re: Upload large, was: Re: ZINC - Kom ...
In-Reply-To: <2C7AF7D1-F248-4084-B9BD-3A512A603E9A@pieber.com>
References: <CAJS2e5gNPhiKhA8dJqE5d4tvG_MmLxEm=PpzJge3vT0fEEgXZw@mail.gmail.com>
	<A14BAD65-45B7-434E-881E-84CF989B3023@stfx.eu>
	<CAJS2e5j7bju37PLvqEkOReqcXZiNeZPzhWQxOL0BmKX3b76_qg@mail.gmail.com>
	<98771D4A-2BD7-4228-B765-DCDD891BBDAC@stfx.eu>
	<CAJS2e5hE+nKPDbuuFbDVpQWxh8qxvcYQn1tv-7e8sOgUsyTM+A@mail.gmail.com>
	<B05C8B00-5449-463F-BE78-D3B275779490@gmx.de>
	<783FD498-A3B3-41CD-BAB3-807E5D33F9EB@inceptive.be>
	<2C7AF7D1-F248-4084-B9BD-3A512A603E9A@pieber.com>
Message-ID: <nd85v9$sje$1@ger.gmane.org>

On 27-03-16 07:37, Bernhard Pieber wrote:
> Hi Johan,
>
> Thanks for your blog post.
>
> I found Nick Ager?s blog posts regarding Nginx:
> http://nickager.com/tags/#nginx
>
> You might want to link to them from yours, maybe?
>

Yes, Nick Ager recently restarted his blog

Stephan

From marianopeck at gmail.com  Sun Mar 27 13:15:21 2016
From: marianopeck at gmail.com (Mariano Martinez Peck)
Date: Sun Mar 27 13:15:23 2016
Subject: [Seaside] How to use bootstrap popover ?
In-Reply-To: <CALPibtzYFzBFWn=BE+i3A2r8u1_wX9rM-v6MpYR4kaHudRff=Q@mail.gmail.com>
References: <CALPibtzYFzBFWn=BE+i3A2r8u1_wX9rM-v6MpYR4kaHudRff=Q@mail.gmail.com>
Message-ID: <CAA+-=mVa1HGsW3QfLM-H+rPNy8vdHs49_N-6sorsyysUYHeRsg@mail.gmail.com>

That looks correct to me. Did you checked in the console of Chrome's
developer tool to see if there was a JS error ?

On Sat, Mar 26, 2016 at 8:59 AM, Thomas Heniart <heniart.thomas@gmail.com>
wrote:

> Hi guys,
>
> I tried to use the bootstrap popover but unfortunately I can't make it
> work and I don't know why
>
> I work on a really simple example, just a component register with
> JQDevelopmentLibrary and TBSDevelopmentLibrary.
>
> The content of renderContentOn: is
>         html script: 'initialize_popover()'.
> html tbsButton
> beDefault;
> attributeAt: 'data-toggle' put: 'popover';
> attributeAt: 'title' put: 'Popover test';
> attributeAt: 'data-placement' put: 'right';
> attributeAt: 'data-content' put: 'This is a test';
> with: 'Button popover test'
>
> And the js method initialize_popover() is define in script method of my
> component with $("[data-toggle = 'popover']").popover()
>
> And that's all
>
> Then I load this little app, no error in the debugger but when I click on
> my button, the popover doesn't appear
>
> Maybe I'm missing something but I don't know what :/
>
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>


-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160327/6d0f862a/attachment-0001.htm
From heniart.thomas at gmail.com  Sun Mar 27 14:33:01 2016
From: heniart.thomas at gmail.com (Thomas Heniart)
Date: Sun Mar 27 14:33:04 2016
Subject: [Seaside] How to use bootstrap popover ?
In-Reply-To: <CAA+-=mVa1HGsW3QfLM-H+rPNy8vdHs49_N-6sorsyysUYHeRsg@mail.gmail.com>
References: <CALPibtzYFzBFWn=BE+i3A2r8u1_wX9rM-v6MpYR4kaHudRff=Q@mail.gmail.com>
	<CAA+-=mVa1HGsW3QfLM-H+rPNy8vdHs49_N-6sorsyysUYHeRsg@mail.gmail.com>
Message-ID: <CALPibtw9G4gQkCHiXhzdEQ2x1jdswcqn68Cnw_VYmfvCv8oa_g@mail.gmail.com>

Yes,

I found the problem, I must do

html script: (html jQuery ready: (html jQuery: 'dom element needed') call:
'popover')

to add a loading script as expected

2016-03-27 15:15 GMT+02:00 Mariano Martinez Peck <marianopeck@gmail.com>:

> That looks correct to me. Did you checked in the console of Chrome's
> developer tool to see if there was a JS error ?
>
> On Sat, Mar 26, 2016 at 8:59 AM, Thomas Heniart <heniart.thomas@gmail.com>
> wrote:
>
>> Hi guys,
>>
>> I tried to use the bootstrap popover but unfortunately I can't make it
>> work and I don't know why
>>
>> I work on a really simple example, just a component register with
>> JQDevelopmentLibrary and TBSDevelopmentLibrary.
>>
>> The content of renderContentOn: is
>>         html script: 'initialize_popover()'.
>> html tbsButton
>> beDefault;
>> attributeAt: 'data-toggle' put: 'popover';
>> attributeAt: 'title' put: 'Popover test';
>> attributeAt: 'data-placement' put: 'right';
>> attributeAt: 'data-content' put: 'This is a test';
>> with: 'Button popover test'
>>
>> And the js method initialize_popover() is define in script method of my
>> component with $("[data-toggle = 'popover']").popover()
>>
>> And that's all
>>
>> Then I load this little app, no error in the debugger but when I click on
>> my button, the popover doesn't appear
>>
>> Maybe I'm missing something but I don't know what :/
>>
>> _______________________________________________
>> seaside mailing list
>> seaside@lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160327/6a7b886d/attachment.htm
From johan at inceptive.be  Sun Mar 27 16:18:09 2016
From: johan at inceptive.be (Johan Brichau)
Date: Sun Mar 27 16:18:13 2016
Subject: [Seaside] How to use bootstrap popover ?
In-Reply-To: <CALPibtw9G4gQkCHiXhzdEQ2x1jdswcqn68Cnw_VYmfvCv8oa_g@mail.gmail.com>
References: <CALPibtzYFzBFWn=BE+i3A2r8u1_wX9rM-v6MpYR4kaHudRff=Q@mail.gmail.com>
	<CAA+-=mVa1HGsW3QfLM-H+rPNy8vdHs49_N-6sorsyysUYHeRsg@mail.gmail.com>
	<CALPibtw9G4gQkCHiXhzdEQ2x1jdswcqn68Cnw_VYmfvCv8oa_g@mail.gmail.com>
Message-ID: <D35C5DFB-FF77-4CE6-8BFE-2ABAB69FE324@inceptive.be>

There is:

html document addLoadScript:  (html jQuery: 'dom element needed') call: 'popover?)

for that

cheers
Johan

> On 27 Mar 2016, at 16:33, Thomas Heniart <heniart.thomas@gmail.com> wrote:
> 
> Yes,
> 
> I found the problem, I must do
> 
> html script: (html jQuery ready: (html jQuery: 'dom element needed') call: 'popover')
> 
> to add a loading script as expected
> 
> 2016-03-27 15:15 GMT+02:00 Mariano Martinez Peck <marianopeck@gmail.com <mailto:marianopeck@gmail.com>>:
> That looks correct to me. Did you checked in the console of Chrome's developer tool to see if there was a JS error ?
> 
> On Sat, Mar 26, 2016 at 8:59 AM, Thomas Heniart <heniart.thomas@gmail.com <mailto:heniart.thomas@gmail.com>> wrote:
> Hi guys,
> 
> I tried to use the bootstrap popover but unfortunately I can't make it work and I don't know why
> 
> I work on a really simple example, just a component register with JQDevelopmentLibrary and TBSDevelopmentLibrary.
> 
> The content of renderContentOn: is
>         html script: 'initialize_popover()'.
> 	html tbsButton
> 		beDefault;
> 		attributeAt: 'data-toggle' put: 'popover';
> 		attributeAt: 'title' put: 'Popover test';
> 		attributeAt: 'data-placement' put: 'right';
> 		attributeAt: 'data-content' put: 'This is a test';
> 		with: 'Button popover test'
> 
> And the js method initialize_popover() is define in script method of my component with $("[data-toggle = 'popover']").popover()
> 
> And that's all
> 
> Then I load this little app, no error in the debugger but when I click on my button, the popover doesn't appear
> 
> Maybe I'm missing something but I don't know what :/
> 
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org <mailto:seaside@lists.squeakfoundation.org>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside <http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>
> 
> 
> 
> 
> -- 
> Mariano
> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>
> 
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org <mailto:seaside@lists.squeakfoundation.org>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside <http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>
> 
> 
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160327/b627113c/attachment.htm
From beisner at alum.mit.edu  Thu Mar 31 20:48:20 2016
From: beisner at alum.mit.edu (Steve Beisner)
Date: Thu Mar 31 20:49:02 2016
Subject: [Seaside] Returning to Smalltalk, learning Seaside,
	some observations and questions.
Message-ID: <CADbHy3z+Q9Z4cfWsqYXC9UEh77n-JpLgTgW8P_T6e+Ysrgi+KQ@mail.gmail.com>

I like Seaside; so much that I'd like to raise some questions
about co-lateral items like documentation, the website, and books.

My background:  I've been programming "forever".  I first saw
Smalltalk demoed at PARC back in the seventies.  I've flirted with
it for years, and was blown away by Seaside as well when I first
ran across it years ago.  For a variety of reasons I'm picking it
up again after a half dozen years. A lot has changed for both
Seaside and Pharo since I last looked, so I decided it'd be
worth my time to try to bring a "beginner's mind" to it, and work
through the website, community resources, documentation, etc.

In short, I'm a fan.  I don't want to offend anyone with these
questions... perhaps it's just my ignorance, but I'd like to help
fix some problems I noticed as a new user coming to the Seaside
site. Here's what I notice:

- Seaside, itself, is obviously under active development by some
  really smart people.

- Is the website not maintained? I lot of stuff looks WAY out of date.
  Most of the listed Blogs have changed their focus from Seaside, or are
  defunct, or haven't been updated in five or six years.  The
  "Success Stories" are stale by years.  Ditto for much of the "Projects"
list.

- "The Book" (Dynamic Web Developmment with Seaside) appears to
  be stalled. Early in the book it says,

      "The online version is always up-to-date and permits
      readers to add notes at the bottom of every page."

  This appears to not be the case (not up-to-date, and I see
  no way to put comments/notes/questions anywhere).

  The "First Component in 15 Minutes" section references what
  seems to be an old version of Pharo: different terminology,
  different menus.  (I am using the 1 click package with Pharo
  and Seaside.)

- The Seaside email list seems to get some good traffic.  Is there any
  way to search the archives for topics? (I don't see any way;
  my suspicion is that there's gold in the archives, if there was
  only a way to find it.)

- How would one go about helping with getting/keeping the book /
  website up-to-date?

- Has there been any thought to using a forum (or Google Groups)
  as a more efficient medium than a mail list for recording and
  making available information and answers to questions?

Again, I know that having a new person come into a community and
immediately start complaining is a drag -- in a big way!
That's not my intent... I plan to persist along my own path, but
maybe I'm overlooking something?  I'd really like improve my own
familiarity with Seaside and perhaps, at the same time, help make
it be more accessible to those who are not already old hands.

Any suggestions or insights would be welcome.

-SteveB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160331/ce27d882/attachment-0001.htm
From johan at inceptive.be  Thu Mar 31 21:54:57 2016
From: johan at inceptive.be (Johan Brichau)
Date: Thu Mar 31 21:55:02 2016
Subject: [Seaside] Returning to Smalltalk, learning Seaside,
	some observations and questions.
In-Reply-To: <CADbHy3z+Q9Z4cfWsqYXC9UEh77n-JpLgTgW8P_T6e+Ysrgi+KQ@mail.gmail.com>
References: <CADbHy3z+Q9Z4cfWsqYXC9UEh77n-JpLgTgW8P_T6e+Ysrgi+KQ@mail.gmail.com>
Message-ID: <51F030D1-F9AC-44BC-BBC1-834647FC10DC@inceptive.be>

Hi Steve,

Welcome back ;)

First off, your observations are correct about the website, documentation, etc? 
These areas need work. There?s work in progress but it advances slowly.

A lot of things have now also moved to github: https://github.com/SeasideSt <https://github.com/SeasideSt> (see the Seaside project wiki there).
Of course, the idea is that the Seaside website references this.

You can search the Seaside mailinglist archives here: http://forum.world.st/Seaside-General-f86180.html <http://forum.world.st/Seaside-General-f86180.html>

A couple of people are maintaining the code and making small increments and advances. 
There?s room for more hands to help, so we welcome anyone who can join the effort. 

cheers
Johan

> On 31 Mar 2016, at 22:48, Steve Beisner <beisner@alum.mit.edu> wrote:
> 
> I like Seaside; so much that I'd like to raise some questions
> about co-lateral items like documentation, the website, and books.
> 
> My background:  I've been programming "forever".  I first saw
> Smalltalk demoed at PARC back in the seventies.  I've flirted with
> it for years, and was blown away by Seaside as well when I first
> ran across it years ago.  For a variety of reasons I'm picking it
> up again after a half dozen years. A lot has changed for both 
> Seaside and Pharo since I last looked, so I decided it'd be
> worth my time to try to bring a "beginner's mind" to it, and work
> through the website, community resources, documentation, etc.
> 
> In short, I'm a fan.  I don't want to offend anyone with these
> questions... perhaps it's just my ignorance, but I'd like to help
> fix some problems I noticed as a new user coming to the Seaside
> site. Here's what I notice:
> 
> - Seaside, itself, is obviously under active development by some
>   really smart people.
> 
> - Is the website not maintained? I lot of stuff looks WAY out of date.
>   Most of the listed Blogs have changed their focus from Seaside, or are
>   defunct, or haven't been updated in five or six years.  The
>   "Success Stories" are stale by years.  Ditto for much of the "Projects" list. 
> 
> - "The Book" (Dynamic Web Developmment with Seaside) appears to
>   be stalled. Early in the book it says,
> 
>       "The online version is always up-to-date and permits 
>       readers to add notes at the bottom of every page."
> 
>   This appears to not be the case (not up-to-date, and I see
>   no way to put comments/notes/questions anywhere).
> 
>   The "First Component in 15 Minutes" section references what 
>   seems to be an old version of Pharo: different terminology,
>   different menus.  (I am using the 1 click package with Pharo
>   and Seaside.)
> 
> - The Seaside email list seems to get some good traffic.  Is there any
>   way to search the archives for topics? (I don't see any way;
>   my suspicion is that there's gold in the archives, if there was
>   only a way to find it.)
> 
> - How would one go about helping with getting/keeping the book /
>   website up-to-date?
> 
> - Has there been any thought to using a forum (or Google Groups)
>   as a more efficient medium than a mail list for recording and
>   making available information and answers to questions?
> 
> Again, I know that having a new person come into a community and 
> immediately start complaining is a drag -- in a big way!  
> That's not my intent... I plan to persist along my own path, but
> maybe I'm overlooking something?  I'd really like improve my own
> familiarity with Seaside and perhaps, at the same time, help make
> it be more accessible to those who are not already old hands.
> 
> Any suggestions or insights would be welcome.
> 
> -SteveB  
> 
> _______________________________________________
> seaside mailing list
> seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160331/49afa527/attachment.htm