In my deployment set-up, I want to keep the application level property files outside of the EAR file, so that if we ever need to modify the contents of these files, we won't have to re-deploy the EAR file.
There are two ways (that I know) to do this. One is hardcode the location of the property file on the server, but that bring up the issue of having J2EE components accessing resources on the server , not to mention a bunch of other issues if we have a clustered setup. The 2nd option is using a URL provider. I'm trying to set it up as per the
Actually there's many ways to do what you are talking about. You could set up resource bundles on the server which contain property files and without having to re-deploy or reconfigure the EARs, reconfigure them to use different bundles.
You could set a server/jvm property that points to a specific directory or URL.
You could even serve the files/settings from a database.
There's a ton of possibilities for what you are asking, but the best, I've found is to either use resource bundles or set a server property that points to a specific network path.