payment.properties vs AccountingTypeData.xml

[Mauricio Tavares]

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. :)

[Jacques Le Roux]

payment.properties : mostly used by Java code
AccountingTypeData.xml : to be loaded on DB (seed data)
look for
<entity-resource type="data" reader-name="seed" loader="main" location="data/AccountingTypeData.xml"/>

HTH

Jacques


From: "Mauricio Tavares" <[hidden email]>

> 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. :)
>

[Scott Gray-2]

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. :)

[Mauricio Tavares]

On Thu, Dec 17, 2009 at 5:08 PM, Scott Gray <[hidden email]> 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.
>
      I can live with either of them once I know where to put the poor
data in. But, I will say I too like the old style more.

> 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. :)
>
>

[Mauricio Tavares]

On Thu, Dec 17, 2009 at 5:03 PM, Jacques Le Roux
<[hidden email]> wrote:
> payment.properties : mostly used by Java code
> AccountingTypeData.xml : to be loaded on DB (seed data)
> look for <entity-resource type="data" reader-name="seed" loader="main"
> location="data/AccountingTypeData.xml"/>
>
      I was looking in (as some of you are aware of)
PcChargeServices.java and it almost makes me feel it would be able to
read the data in from the database. In fact, I would consider
rewriting buildPccProperties() to do just that. I mean, isn't it doing
about the same as getApi()?

> HTH
>
> Jacques
>
>
> From: "Mauricio Tavares" <[hidden email]>
>
>> 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. :)
>>
>
>

[David E. Jones-2]

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. :)
>

[Scott Gray-2]

Oh don't get me wrong, I understand and agree with why they exist and  
what they are intended to make easier.  I just personally found it  
easier in the past when setting them up to modify the properties file,  
create a patch and restart rather than adding entity xml and reloading  
the data.  I could just modify it with the screens but that would only  
last until the next database refresh on dev or staging.  So IMO easier  
for an end-user, harder for a developer.

Regards
Scott

On 18/12/2009, at 11:40 AM, David E Jones wrote:

>
> 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. :)
>>
>

[David E. Jones-2]

Yes, that's a good point. It's also a good distinction between what works well for end-users (in the database) and what works well for developers (in a revision-controlled file).

That's the reason why I'm not a big fan of the idea of putting form definitions and the like in the database.

In general the direction we're headed with OFBiz, ie to put technical-level config in files and user-level config in the database, is compatible with this. However, sometimes technical people are responsible for some of the user-level configuration. In fact, IMO people are sometimes too optimistic about what end-users can even configure without getting help, and that blurs this line a lot...

-David


On Dec 17, 2009, at 5:31 PM, Scott Gray wrote:

> Oh don't get me wrong, I understand and agree with why they exist and what they are intended to make easier.  I just personally found it easier in the past when setting them up to modify the properties file, create a patch and restart rather than adding entity xml and reloading the data.  I could just modify it with the screens but that would only last until the next database refresh on dev or staging.  So IMO easier for an end-user, harder for a developer.
>
> Regards
> Scott
>
> On 18/12/2009, at 11:40 AM, David E Jones wrote:
>
>>
>> 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. :)
>>>
>>
>