WAAttributeNotFound raised on #scriptGeneratorClass

Hi all,

Using Monticello browser, I just updated a standard 1.2 Pier image to the latest versions of Pharo (PharoCore1.0-#10517), Seaside 3 and Pier 2.

During the update process, WAAttributeNotFound was raised
        upon the call to #preferenceAt: #scriptGeneratorClass put: aClass
        by the following methods:
- JQAllFunctionalTests class >>initialize
- JQUiAllFunctionalTestsclass >>initialize
- SUAllComponentTestsclass >>initialize
- SUAllFunctionalTestsclass >>initialize

I had to bypass the issue by temporarily the code of those methods.
Now, the same exception is raised again,
        when trying to connect to Pier via the local host (http://localhost:8080/pier),
        upon the call to *self handler configuration at: #scriptGeneratorClass*,
        in WARequestContext >> newDocument.

#newDocument has been changed on Feb, 22, 2010.

Does anybody see how this issue could be better fixed; just reverting to the previous code doesn't seem a good idea.
Thanks in advance,
Reza
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> Using Monticello browser, I just updated a standard 1.2 Pier image to the
> latest versions of Pharo (PharoCore1.0-#10517), Seaside 3 and Pier 2.

Generally updating from Seaside 2.8 to Seaside 3.0 does not work, due
to the lack of atomic loading of Monticello. Take a fresh image.

Lukas

--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

At 10:00 11/04/2010, Lukas Renggli wrote:
> > Using Monticello browser, I just updated a standard 1.2 Pier image to the
> > latest versions of Pharo (PharoCore1.0-#10517), Seaside 3 and Pier 2.
>
>Generally updating from Seaside 2.8 to Seaside 3.0 does not work, due
>to the lack of atomic loading of Monticello. Take a fresh image.

Hi Lukas,

Actually, I just loaded the latest packages into Seaside 3.0 + Pier 2
image. I don't use Seaside 2.8 and Pier 1 since a few months.

I just discovered that it was related to the cached
WARequestHandlingConfiguration. Just executed *WAEnvironment
reloadApplications*, and everything is in order now ;-)

Thanks for your support,
Regards,
Reza

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Aha, ok. I had the impression you had an old Seaside and Pier in the same image.

How did you load the Seaside 3 code?

Lukas

--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

At 10:44 11/04/2010, Lukas Renggli wrote:

How did you load the Seaside 3 code?

Just picked this one:
http://www.piercms.com/download

Then upgraded to *PharoCore1.0-#10517*, and the latest Seaside 3.0, and Pier 2 packages, including FFI, RFB, OS-Process, File-Kernel, etc. It took me several hours :-( If the result could help somebody saving that time, please let me know to put the image+changes (~50 M°, unzipped) on a public server for download.

Cheers,
Reza
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> Just picked this one:
> http://www.piercms.com/download
>
> Then upgraded to *PharoCore1.0-#10517*, and the latest Seaside 3.0, and Pier
> 2 packages, including FFI, RFB, OS-Process, File-Kernel, etc. It took me
> several hours :-(

Glad it worked, normally Pharo cannot be updated in an image that has
something else loaded but the core packages.

> If the result could help somebody saving that time, please
> let me know to put the image+changes (~50 M°, unzipped) on a public server
> for download.

There are always daily builds at <http://hudson.lukas-renggli.ch/>
with the latest Pharo, Seaside, Magritte and Pier code. We will soon
update the one-click image too (based on these builds).

Lukas

--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

At 11:14 11/04/2010, Lukas Renggli wrote:
>normally Pharo cannot be updated in an image that has
>something else loaded but the core packages.

Good to know.
It took time, but at the end I was happy with the result 8-)
(although, have not yet tested it thoroughly)
thanks!

>There are always daily builds at <http://hudson.lukas-renggli.ch/>
>with the latest Pharo, Seaside, Magritte and Pier code. We will soon
>update the one-click image too (based on these builds).

That would be great, although, in general, I do prefer updating my
image manually, to get a chance to have a look at the new code during
the merge process.

Take care,
Reza

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki