Hi guys....
I have server running. I uploaded some code in which it adds an instVar to MyWASession subclass. I have run WAAdmin clearSessions and some other clean up code. Still.....when I browse the app I get a DNU when I send the accessor method to that instVar. If I connect with gemTools or topaz, I DO see that instVar and that accessor method..... so I guess that for some reason I may be using an older version of the class? Otherwise I don't get why I get the DNU.... also why would I be using an old version of the class? I don't get it either.
Is there any specific cleanUp I should do in gemstone? Any idea is appreciated. _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Of course...re-registering the app fixes that... On Sat, Feb 15, 2014 at 10:01 AM, Mariano Martinez Peck <[hidden email]> wrote:
Mariano http://marianopeck.wordpress.com _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
In reply to this post by Mariano Martinez Peck
Msriano, We really ought to do something about this one ... perhaps when I get out of the woods working on 3.2? The Seaside component code has direct references to classes via a class var or something ... when you create a new version of a class (and it's subclasses) Seaside is still referencing the old version ...
To fix it we would have to find all the places where classes are directly referenced and replace them with a lookup... Dale
On Sat, Feb 15, 2014 at 5:01 AM, Mariano Martinez Peck <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
On Sat, Feb 15, 2014 at 4:46 PM, Dale Henrichs
<[hidden email]> wrote: > Msriano, > > We really ought to do something about this one ... perhaps when I get out of > the woods working on 3.2? > > The Seaside component code has direct references to classes via a class var > or something ... when you create a new version of a class (and it's > subclasses) Seaside is still referencing the old version ... > > To fix it we would have to find all the places where classes are directly > referenced and replace them with a lookup... WARenderer class >> #default? Cheers Philippe _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
On 15 Feb 2014, at 23:02, Philippe Marschall <[hidden email]> wrote: > On Sat, Feb 15, 2014 at 4:46 PM, Dale Henrichs > <[hidden email]> wrote: >> Msriano, >> >> We really ought to do something about this one ... perhaps when I get out of >> the woods working on 3.2? >> >> The Seaside component code has direct references to classes via a class var >> or something ... when you create a new version of a class (and it's >> subclasses) Seaside is still referencing the old version ... >> >> To fix it we would have to find all the places where classes are directly >> referenced and replace them with a lookup... > > WARenderer class >> #default? That one too, but I guess the following are more likely to be influenced by the application code evolving: WAApplication>>#sessionClass WAApplication>>#initialContinuationClass The library classes (WAApplication>>#addLibrary and WAApplication>>#removeLibrary:) are also subject to this but I guess that gets used less frequently in production sites. At least, this is where we take attention when upgrading our code base and getting new class versions for the classes stored in the application config. Johan _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Free forum by Nabble | Edit this page |