Originally posted by Dominic Steng�rd:
Hi Ben,
Thanks for your quick reply. :-)
Yes I will make it a context init parameter. But my question is more related to if it is even possible for a File object within serlvetA in webappA to reach fileA, even though fileA is not located within webappA? FileA will be located somewhere else on the filesystem.
Yes.
You might have issues if the file isn't actually on the same machine as the container (Windows network, NFS, etc..) but if they're on the same machine and you have an absolute path to the file, you shouldn't have a problem.
Other issues could be file permissions, and/or
Java security policies, if your container is running under one.