[Seaside-dev] WAError: You can no longer call #addLoadScript: on WASession

Julian Fitzell jfitzell at gmail.com
Wed Mar 18 11:35:50 UTC 2009


Hmm... the script you sent loads the same version of Javascript-Core
(Javascript-Core-jf.46.mcz) that I have in my image. That is the
package that should have that method in it.

I checked a 2.8 image and it has the exact version of the method you
say you have.

Again, the only thing I can think of is that you have Seaside 2.8
loaded in the image as well. But if you can figure out where that
method is coming from and can pinpoint something else as a cause, I'd
be happy to hear what it is.

Julian

On Wed, Mar 18, 2009 at 11:50 AM, Sebastian Sastre <ssastre at seaswork.com> wrote:
> As said, I've used a fresh pharo image. I've sent you in private the script I've
> used to load 2.9a3
> cheers
> sebastian
>
>> -----Mensaje original-----
>> De: seaside-dev-bounces at lists.squeakfoundation.org
>> [mailto:seaside-dev-bounces at lists.squeakfoundation.org] En
>> nombre de Julian Fitzell
>> Enviado el: Wednesday, March 18, 2009 07:37
>> Para: Seaside - developer list
>> Asunto: Re: [Seaside-dev] WAError: You can no longer call
>> #addLoadScript: on WASession
>>
>> That's 2.8 code, I think. If I look at versions of that method in my
>> image, even the oldest one I have (Sep. 7) does not call
>> #addLoadScript: on the session (and the method paramter should be
>> anObject).
>>
>> I don't know what code you have there but I'm pretty sure it's not
>> 2.9a3. Did you perhaps try to load 2.9 into an image that already had
>> 2.8?
>>
>> Julian
>>
>> On Wed, Mar 18, 2009 at 11:29 AM, Sebastian Sastre
>> <ssastre at seaswork.com> wrote:
>> > ah yes, it's a fresh pharo core 248 with 2.9a3
>> > I'm seeing:
>> >
>> > WATagBrush>>script: aPrototype
>> >        aPrototype isNil
>> >                ifTrue: [ ^ self ].
>> >        (aPrototype respondsTo: #id:)
>> >                ifTrue: [ aPrototype id: self ensureId ].
>> >
>> >        aPrototype session addLoadScript: aPrototype
>> >
>> >
>> > sebastian
>> >
>> >> -----Mensaje original-----
>> >> De: seaside-dev-bounces at lists.squeakfoundation.org
>> >> [mailto:seaside-dev-bounces at lists.squeakfoundation.org] En
>> >> nombre de Julian Fitzell
>> >> Enviado el: Wednesday, March 18, 2009 07:22
>> >> Para: Seaside - developer list
>> >> Asunto: Re: [Seaside-dev] WAError: You can no longer call
>> >> #addLoadScript: on WASession
>> >>
>> >> This is 2.9a3? I don't see any senders in my image calling
>> >> #addLoadScript: on Session. You'll need to give a stack trace...
>> >>
>> >> Julian
>> >>
>> >> On Wed, Mar 18, 2009 at 11:05 AM, Sebastian Sastre
>> >> <ssastre at seaswork.com> wrote:
>> >> > hi there,
>> >> > I'm seeing this for in place editor and friends. Not only
>> >> in my app but in
>> >> > seaside tests.
>> >> > should I have to add this as an issue in google code?
>> >> > sebastian
>> >> >
>> >> > _______________________________________________
>> >> > seaside-dev mailing list
>> >> > seaside-dev at lists.squeakfoundation.org
>> >> > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>> >> >
>> >> _______________________________________________
>> >> seaside-dev mailing list
>> >> seaside-dev at lists.squeakfoundation.org
>> >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>> >
>> > _______________________________________________
>> > seaside-dev mailing list
>> > seaside-dev at lists.squeakfoundation.org
>> > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>> >
>> _______________________________________________
>> seaside-dev mailing list
>> seaside-dev at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>


More information about the seaside-dev mailing list