David E Jones wrote:
On side note I should mention that the direction has been discussed and generally agreed on that application level properties should be done away with (like payment.properties, and many others) and that information should go into the database. The main reason behind that is to support differing initial data for common setups that can simply be loaded into the system when it is run and you can get started quickly and without having to dive into files... oh and also that you can maintain things through a UI instead of through editing properties files.
An interesting idea. Would a single entity be used for that, or would each application have its own entity?
-Adrian
