I decided for the XML defined settings because the customer purchasing the
system should not have to change his existing environment but should be able
to get our system running with the components we supply to him. So defining
the settings in his database would be a change to the environment - and
including a database in our product for _only_ storing settings is a waste
of money for the customer.
I also thought about just using plain .properties files for storing the
settings. This would give the opportunity to change the settings in the bean
which could then persist them to the file system _without_ the necessity of
writing a complex XML Spy-like tool.
But I think I will reconsider the database approach as well although I don't
like the idea of changing the customer's existing system setup. What do you
think about touching the customer's runtime environment?
.bbr
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
