[jira] [Comment Edited] (OFBIZ-10540) Warning in console logs related to entity definitions

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Comment Edited] (OFBIZ-10540) Warning in console logs related to entity definitions

Nicolas Malin (Jira)

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

Nicolas Malin edited comment on OFBIZ-10540 at 9/4/18 7:32 AM:
---------------------------------------------------------------

At the beginning, I didn't understand why I have this warning ... now I understand, in my mind WorkEffortContactMech has been the same pattern for OrderContactMech. But not, and after many read, I didn't see the error, like an illusion :/ .

So WorkEffortContactMech haven't contactMechPurposeTypeId and this change the generic function that I introduce during the reformat. I upload a corrective patch [^OFBIZ-10540.patch](no tested at all yet) if you want control it (now I doubt :) ). Oh I see you path to later, I will include it on mine. Thanks [~deepak.nigam]

[~deepak.dixit] I didn't see any performance issue by the view-entity inclusion, I used it to homogenize source code, centralize the contactMech view logical and apply same pattern to help generic function creation. With your remark, I will recheck it to be sure.


was (Author: soledad):
At the beginning, I didn't understand why I have this warning ... now I understand, in my mind WorkEffortContactMech has been the same pattern for OrderContactMech. But not, and after many read, I didn't see the error, like an illusion :/ .

So WorkEffortContactMech haven't contactMechPurposeTypeId and this change the generic function that I introduce during the reformat. I upload a corrective patch [^OFBIZ-10540.patch](no tested at all yet) if you want control it (now I doubt :) ).

[~deepak.dixit] I didn't see any performance issue by the view-entity inclusion, I used it to homogenize source code, centralize the contactMech view logical and apply same pattern to help generic function creation. With your remark, I will recheck it to be sure.

> Warning in console logs related to entity definitions
> -----------------------------------------------------
>
>                 Key: OFBIZ-10540
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10540
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL COMPONENTS
>    Affects Versions: Trunk
>            Reporter: Deepak Nigam
>            Assignee: Nicolas Malin
>            Priority: Minor
>         Attachments: OFBIZ-10540.patch, OFBiz-10540.patch, OFBiz-10540.patch
>
>
> On trunk, following warnings related to entity definitions are coming:
> 2018-08-27 14:10:32,129 |delegator-startup-1 |GenericDelegator |W| =-=-=-=-= Found 5 warnings when checking the entity definitions:
> 2018-08-27 14:10:32,130 |delegator-startup-1 |GenericDelegator |W| [RelationRelatedFieldNotFound] The field "partyId" of related entity FacilityContactMech was specified in the keymaps but is not found for relation FacilityContactMech of entity FacilityAndContactMech.
> 2018-08-27 14:10:32,131 |delegator-startup-1 |GenericDelegator |W| [RelationFieldNotFound] The field partyId was specified in the keymaps but is not found for relation FacilityContactMech of entity FacilityAndContactMech.
> 2018-08-27 14:10:32,131 |delegator-startup-1 |GenericDelegator |W| [RelationRelatedFieldNotFound] The field "contactMechPurposeTypeId" of related entity WorkEffortContactMech was specified in the keymaps but is not found for relation WorkEffortContactMech of entity WorkEffortAndContactMech.
> 2018-08-27 14:10:32,131 |delegator-startup-1 |GenericDelegator |W| [RelationFieldNotFound] The field contactMechPurposeTypeId was specified in the keymaps but is not found for relation WorkEffortContactMech of entity WorkEffortAndContactMech.
> 2018-08-27 14:10:32,131 |delegator-startup-1 |GenericDelegator |W| [RelationFieldNotFound] The field contactMechPurposeTypeId was specified in the keymaps but is not found for relation ContactMechPurposeType of entity WorkEffortAndContactMech.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)