Hi again,
thank you all for your kind advice!
My responses follow:
@Josh: This "lazy" approach didn't work for me anyhow. I got just the same
NPEs. This really is kind of non-deterministic as it sometimes would work and
sometimes it wouldn't. I mean the whole
access-the-servlet-context-while-
Hi!
I simply use this code for it:
public static void contributeApplicationDefaults(
MappedConfiguration configuration) {
ResourceBundle bundle = ResourceBundle.getBundle("Cpu");
Enumeration e = bundle.getKeys();
while (e.hasMoreElements()) {
You can also set them from the command line:
-Dtapestry.production-mode=false
which is mostly how I choose to do it...
On Thu, Jul 21, 2011 at 11:35 AM, Mark wrote:
> On Thu, Jul 21, 2011 at 10:27 AM, Erik Fäßler
> wrote:
>> Goal: Being able to configure my WebApp from
>> file rather than bei
On Thu, Jul 21, 2011 at 10:27 AM, Erik Fäßler wrote:
> Goal: Being able to configure my WebApp from
> file rather than being forced to edit the code every time I change
> deployment (from test to productive for instance;
You probably already know this, but you can set these from web.xml
with some
t;SemedicoToolsSymbols", new
> ContextResourceSymbolProvider(applicationGlobals.getContext(),
> "configuration.properties"), "before:ApplicationDefaults");
> }
>
> but this does not work as described above: At this point of application
> startup, the co
medicoToolsSymbols", new
ContextResourceSymbolProvider(applicationGlobals.getContext(),
"configuration.properties"), "before:ApplicationDefaults");
}
but this does not work as described above: At this point of application
startup, the context (gotten by applicationGlobals
