From: Shapira, Yoav [EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 6:27 AM
Here's another take that's not seen often, but is intriguing: the
java.util.prefs API. It uses the Registry on Windows, and the
filesystem on unix, by default, but that can be changed. If you're
running on Windows
Quoting Will Hartung [EMAIL PROTECTED]:
From: Shapira, Yoav [EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 6:27 AM
Here's another take that's not seen often, but is intriguing: the
java.util.prefs API. It uses the Registry on Windows, and the
filesystem on unix, by default, but that
To get the server info: ServletContext.getServerInfo()
Personally - I would state my webapp needs a directory[or database] to
write/load its configuration. The directory or datasource would be setup
using JNDI. Then its up to the system admin to use the Container specific
functionality to
Hi,
It's not blasphemy ;) It's a good question. Many people take shortcuts
/ cut corners to get around this ;)
b) Require that a database be present and publish the datasource name
that
the web app is looking for, and assume that the user will configure
their
container properly (and, of
This is blasphemy, I know...but...
As far as I know, there is no portable way that a generic Webapp bundled in
a WAR, and dropped into a random container can persist information from one
run of the container to another.
On the one hand, there is no requirement that a WAR be exploded on deploy,
