Re: Where to put server-configuration property files?

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 google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.