[Seaside] Re: #deploymentMode WAAttributeNotFound

[Julian Fitzell]

Yes, it's meaning was unclear and it was thus removed. The best way to
deploy is to build an image without the Development (and presumably the
tests, and maybe even the admin tools) packages loaded in the first place.
That will ensure nothing "non-deployment" is there. Obviously, what other
steps you might need to do for your own deployment is up to you.

If you still want the dev tools loaded, then the closest thing to turning on
#deploymentMode (for all applications, though) is to remove
WADevelopmentConfiguration from the shared configuration called "Application
Defaults". You can do this from the web UI or with:

WAAdmin applicationDefaults removeParent: WADevelopmentConfiguration
instance

And of course you can add that configuration to any of your applications
instead of to "Application Defaults" if you want development tools for some
apps but not for others.

Julian

On Fri, Jan 8, 2010 at 4:09 PM, Joel Turnbull <joel.turnbull at ardishealth.com
> wrote:

> and Seaside 3.0 BTW
>
>
> On Fri, Jan 8, 2010 at 6:58 PM, Joel Turnbull <
> joel.turnbull at ardishealth.com> wrote:
>
>>
>> I'm trying to register some seaside applications programatically and when
>> I send to them
>>
>> preferenceAt: #deploymentMode put: true.
>>
>> I get WAAttributeNotFound. Looking in the dictionary, sure enough, it is
>> not there. Has the way to set deploymentMode changed?
>>
>> This is running on GemStone.
>>
>> Thanks,
>> Joel Turnbull
>>
>
>
> _______________________________________________
> seaside mailing list
> seaside at 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/20100108/6bbdfb52/attachment.htm