[ 
https://issues.apache.org/jira/browse/OFBIZ-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373125#comment-15373125
 ] 

Pierre Smits commented on OFBIZ-7781:
-------------------------------------

following up on this posting by [~mbrohl] 
https://issues.apache.org/jira/browse/OFBIZ-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372940#comment-15372940

The decision on 'do we want this'? should never be the first question answered. 
There is a difference between what a business needs and what contributor(s) 
wants for the project.

The rationale (or pre-amble) is that the business requirements of the adopting 
companies can vary from company to company (even within one industry sector) 
due to e.g. varying legal aspects. 

Then the first question should be: can we facilitate those adopters with more 
flexibility regarding the aspect of - in the case of OFBIZ-7611 - tracking 
fields. After that question, the next follow up question would be: 'how would 
that solution be? in order to find a solution that is acceptable by the greater 
OFBiz community. 

And then comes the ultimate question that each individual contributor has to 
answer for himself: do I want to spent my time on this matter to help the 
fellow contributor to bring the accepted solution direction to a successful 
incorporation in the code base and enhance the appeal of the product and the 
project. 



> Have a configurable solution with respect to the default fields of all 
> entities
> -------------------------------------------------------------------------------
>
>                 Key: OFBIZ-7781
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7781
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: datamodel
>    Affects Versions: Trunk
>            Reporter: Pierre Smits
>
> This issue follows up on comments posted in the  OFBIZ-7622 sub-task.
> Currently the fields to be added to all entities are defined in 
> ModelEntity.java. This is a limited list consisting of:
> * public static final String STAMP_FIELD = "lastUpdatedStamp";
> * public static final String STAMP_TX_FIELD = "lastUpdatedTxStamp";
> * public static final String CREATE_STAMP_FIELD = "createdStamp";
> * public static final String CREATE_STAMP_TX_FIELD = "createdTxStamp";
> After the implemented code change of the sub task mentioned above, a new 
> discussion evolved through postings of comments on the subject of how to get 
> more flexibility in.
> This issue is a starting point and potentially a place holder for sub 
> subtasks to get to a more flexible solution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to