If you have a configuration file which is to be shared across multiple web applications or deployments you could use a shared drive for this which is accessible to all your applications and get it loaded from there. But i still wouldn't suggest having it outside your war as you are creating a dependency on external files.
Cheers! On Dec 12, 11:51 pm, jbdhl <[email protected]> wrote: > Eh, but putting the config files in the war file makes them context- > independent which was exactly what I didn't want? In that case all > installations would ship with the same config file and upgrading from > release N to N+1 would override the config file. I fail to see how > putting the config files in the war-file can be context/installation > dependent. I would like the customer to keep one config file > <somewhere> on his server and separating it from the application war- > file - but where is <somewhere>? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
