[
https://issues.apache.org/jira/browse/OFBIZ-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-3985.
----------------------------------
Resolution: Not A Problem
Assignee: Jacques Le Roux
[For the verbosity we could use this
tip|http://www.javaworld.com/javaworld/javatips/jw-javatip50.html] but anyway I
agree it does not have much interested in our case since the Entities fields
names are not changing that much and it's often easy to change them by a S/R.
I close as not a problem
> Using seperate class for constants
> ----------------------------------
>
> Key: OFBIZ-3985
> URL: https://issues.apache.org/jira/browse/OFBIZ-3985
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
> Affects Versions: Release Branch 10.04
> Reporter: Pankaj Savita
> Assignee: Jacques Le Roux
> Priority: Minor
> Fix For: Release Branch 10.04
>
> Attachments: Using_Separate_Constant_Class.patch
>
>
> Hi All,
>
> Why don't we use a separate constant class for defining constants? We can use
> Parameter Constants Design Pattern in OFBiz.
> Database fields & Form Fields can be defined in a Constant class, So that
> whenever fields name changed no need
> to search the entire code. Just need to change it in Constant class. It makes
> easy maintainable code.
>
> I am attaching a sample patch done in accounting component. In this I used a
> seperate class for a accounting specific constatns
> & a common class for OFBiz specific constants.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
