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 course, your web app must be compatible with >that database). This option is the one most inline with the J2EE specification and spirit. Some people go further and include a DB with their application (e.g. MySQL, or postgreSQL), and then require the client/sysadmin to configure a directory where the DB can write. This is similar to your system property approach (option c in your original post). 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 this is a decent approach (but then again if you're only running on windows you might make a whole set of choices based on that). Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
