I disagree, the properties files are way more of a pain than data in the database, especially for end-users or if you only have access to the application. To have to edit a file and restart the server to change your payment processor settings... isn't that a little bit of pain?
-David On Dec 17, 2009, at 4:08 PM, Scott Gray wrote: > The properties have been mostly moved to the database for 'easier' > configuration (I don't really see the ease to be honest). So > payment.properties is still supported but I guess you could say deprecated > and the PaymentGatewayConfig entities are the new way to configure the > payment gateways. > > Regards > Scott > > HotWax Media > http://www.hotwaxmedia.com > > On 18/12/2009, at 6:58 AM, Mauricio Tavares wrote: > >> What is the difference between these two files as far as payment >> gateways are concerned? At first glance they both seem to provide the >> "constant" (host, port, userID, etc) values for each payment gateway. >> But, I could be confused as always. :) >
