ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Patidar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-9696) Extend type entities to add name of detail entity where hasTable is true
Date Sat, 23 Sep 2017 04:30:00 GMT

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

Arun Patidar commented on OFBIZ-9696:
-------------------------------------

As we concluded on the mailing list to not extend entity, we should follow convention.  so
updating ticket description and title.

> Extend type entities to add name of detail entity where hasTable is true
> ------------------------------------------------------------------------
>
>                 Key: OFBIZ-9696
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9696
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL COMPONENTS
>    Affects Versions: Trunk
>            Reporter: Arun Patidar
>            Assignee: Arun Patidar
>
> 'hasTable' field of 'Type' entities is used to give an idea that detail entity exists
or not. We generally get the name of detail entity on the basis of typeId field value. 
> For example : 
> ContactMechType,contactMechTypeId = "POSTAL_ADDRESS"  then we go to PostalAddress for
detail.
> similarly,
> ContactMechType,contactMechTypeId = "TELECOM_NUMBER"  then we go to TelecomNumber for
detail.
> We should follow the naming convention.
> Below are some entities that are not following the pattern. Some of them are:
>    - ShipmentGatewayConfigType
>    - PaymentGatewayConfigType



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message