I understand your point, and I said on my email that this may not be the final solution.
We have things like DSNs and the Bean definitions on CS, the settings we have coming from the DB are part of the application itself, emails, file paths, etc. Our approach to that solution was basically the same "if the DB is down then the application is down anyway, so might as well keep the email settings and application paths in the DB". Once we learn more about ANT we may change our deployment script but for now it is very simple. I'm very happy with the results though. Fernando On Thu, Apr 23, 2009 at 8:45 AM, Al <[email protected]> wrote: > > I don't disagree with you. I am merely working with constraints that > have been placed on me. > > One of the arguments AGAINST is, of course, that if the DB is > inaccessible then the settings won't be available. Of course, I've > argued, if the DB is not available the app is hosed anyway. > > On Apr 22, 2:05 pm, Doug Hughes <[email protected]> wrote: > > I disagree with this sentiment. It's often not the best idea, but if > there > > are practical reasons as to why it's a good idea, then the DB is > > appropriate. This is particuarily important when you consider > configuration > > settings that can be made from an application. It might no't make sense > to > > store that in XML/INI in many cases. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
