[Seaside-dev] Issue 196 in seaside: 'Application Defaults' shared
config
codesite-noreply at google.com
codesite-noreply at google.com
Mon Oct 6 20:24:19 UTC 2008
Issue 196: 'Application Defaults' shared config
http://code.google.com/p/seaside/issues/detail?id=196
Comment #3 by jfitzell:
Done. Loading the DevelopmentConfiguration into a specific application now
works as
expected, overriding the values in "Application Defaults".
If you add the DevelopmentConfiguration to the "Application Defaults"
(which you
would probably want to do) you run into the same problem where the values
set in the
shared configuration override the ones in the development configuration.
This can be
solved by having a WAAdmin command that adds the development configuration
to all
Applications or that sets the values in the shared configuration instead of
using the
DevelopmentConfiguration, I guess.
Name: Seaside-Environment-jf.18
Author: jf
Time: 6 October 2008, 10:01:15 pm
UUID: ce59e137-2fe4-3b4b-8ce2-f97b15cb12cd
Ancestors: Seaside-Environment-jf.17
Move WAStandardFiles from Core to Environment package.
http://code.google.com/p/seaside/issues/detail?id=190
Create an "Application Defaults" shared configuration in Environment and
add it to
all applications that are registerd with WAAdmin.
http://code.google.com/p/seaside/issues/detail?id=196
Issue attribute updates:
Status: Fixed
Owner: jfitzell
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
More information about the seaside-dev
mailing list