On Tue, Jan 11, 2005 at 06:16:15PM +0100, Erik Bruchez wrote:
Can you try using the FlatFileResourceManager instead of the WebAppResourceManagerFactory to see if that changes things? The oxf.resources.flatfile.rootdir parameter also has to be set in that case.
Yep, that works! At least, I can't reproduce the problem anymore during many test changes I just made.
What are the (dis)advantages of using each of them?
In both cases, you are creating a sandbox for your application files. But with the WebAppResourceManager, they are loaded through the Servlet API, while with the FlatFileResourceManager, they are loaded through the File API. The first has the advantage that for deployment, you don't have to configure a root directory: the resources are directly in the WAR file. The second requires configuring a root directory, which doesn't have to be located in the WAR file hierarchy: it can be anywhere on the file system.
I don't know if what you were hitting was a bug (or "feature") of Tomcat, or of our WebAppResourceManager, because to find out the last modification date, we try to obtain the real path to the file, so we end up using the File API as well.
-Erik
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
