ofbiz-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rishi Solanki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-7828) Entity and Service definition
Date Sat, 16 Jul 2016 11:03:20 GMT

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

Rishi Solanki commented on OFBIZ-7828:

For service definition we need to follow pattern derived from entities package-name. For example;
for AccommodationClass entity, we have package-name="org.ofbiz.accounting.fixedasset" then
we will add its service definition under accounting/servicedef/services_fixedasset.xml. And
for AccommodationSpot entity, we have package-name="org.ofbiz.order.reservations" then we
will add its service defintion under order/servicedef/services_reservations.xml.

Community, please raise flag in case of concerns in this pattern. Thanks!

> Entity and Service definition
> -----------------------------
>                 Key: OFBIZ-7828
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7828
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL COMPONENTS
>    Affects Versions: Trunk
>            Reporter: Rishi Solanki
>            Assignee: Arun Patidar
> As per discussion on dev list on email thread-: "Entity and Service definition" Here
is the parent task for the same.
> TODO's from same thread, review entities/services on following parameters;
> 1) Many entity definitions having relationships with view-entities, like OrderHeader
entity maintain relationship with OrderHeaderNoteView and OrderItemAndShipGroupAssoc. We should
remove it, maintain the relationship at view-entities level if required. Also change the code
where this relation is in use.
> 2) Many entities having service implementation exists but they can be simply convert
into entity-auto, that means can use the power OFBiz provides.
> 3) As mentioned initially many entities do not have CRUD services exists, we should implement
or use entity-auto for them wherever applicable. Also remove direct use of delegator for them.
> 4) Many entities having from date and thru date, Or status Or Enumeration to manage the
historical data, but services actually remove those entity data. We should change the service
implementation to maintain the historical data.

This message was sent by Atlassian JIRA

View raw message