> The way I envision it is that the app will have a file system-based > download by default, and will also have in place the capability to > download from a user-defined database if the user wants to, but the app > would in no way, by default, require a database. Probably something as > simple as having the required parameters passed via request from a JSP, > for demonstration purposes, should suffice. Does that sound reasonable to > you Martin?
Actually, I take a small part of this back... Since we're talking about this sample app using the custom action mappings as well, what I was originall thinking was an action apping for file downloads and another for database downloads. The one for database downloads would contain all the required attributes in the mapping. The point that this doesn't change though, which I think is the central point, is that the app doesn't require a database, not by default anyway. If a user wanted to see that in action, only then would they have to change the config file and make use of whatever database they want. In my view, this is a fair compromise of giving a full, useful example, while still not adding and dependencies. Your thoughts? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
