Re: Entity and Service definition

[Divesh Dutta]

Very good initiative.

Thanks
--
Divesh Dutta .

On Sun, Jul 17, 2016 at 6:00 PM, Rishi Solanki 
wrote:

> Starter effort on this under - OFBIZ-7828. Community review / feedback /
> suggestion / concerns are welcome.
>
> Thanks!
>
> Rishi Solanki
> Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>
> On Thu, Jul 14, 2016 at 9:58 AM, Rishi Solanki 
> wrote:
>
> > Thank you everyone for your approval and suggestion. We would try to
> > follow most, and log Jira accordingly. Soon will start on this.
> >
> > Nicolas, thanks for pointing expire action on entity-auto.
> >
> > Jacques, Pierre, thanks for suggestion on managing Jira tickets, and you
> > guys anyways helped us in our last effort in managing Jira tickets and
> > review. Thanks for that.
> >
> > Plan is something like this, we would pick the easy entities first where
> > we found minimum changes. After delivering few we will be able to
> establish
> > practice internally, on what items we should take care before fixing an
> > entity/service. We would like to go slow initially, and as soon as we
> start
> > on it delivery process will more clear.
> >
> >
> > Thanks again for your help, and looking forward for same in the big
> effort
> > planned.
> >
> >
> >
> > Rishi Solanki
> > Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> >
> > On Wed, Jul 13, 2016 at 2:36 PM, Jacques Le Roux <
> > jacques.le.r...@les7arts.com> wrote:
> >
> >> Le 13/07/2016 à 09:39, Pierre Smits a écrit :
> >>
> >>> At this moment in time, I can't fathom how much effort is involved in
> >>> this
> >>> factoring, but I suggest to break it down as much as possible into
> >>> separate
> >>> JIRA issues. For instance, the rework on the removal of the
> >>> OrderHeaderNoteView
> >>> and OrderItemAndShipGroupAssoc from the OrderHeader entity can be a
> >>> separate issue. Please be aware, that this might have a big impact in
> >>> various functions/services/etc.
> >>>
> >>> Best regards,
> >>>
> >>> Pierre Smits
> >>>
> >> That's a good advice Pierre, from what I have seen these last months
> from
> >> the HW effort, I'm confident they are totally aware of what to do :)
> >>
> >> Jacques
> >>
> >>
> >
>

Re: Entity and Service definition

[Rishi Solanki]

Starter effort on this under - OFBIZ-7828. Community review / feedback /
suggestion / concerns are welcome.

Thanks!

Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Thu, Jul 14, 2016 at 9:58 AM, Rishi Solanki 
wrote:

> Thank you everyone for your approval and suggestion. We would try to
> follow most, and log Jira accordingly. Soon will start on this.
>
> Nicolas, thanks for pointing expire action on entity-auto.
>
> Jacques, Pierre, thanks for suggestion on managing Jira tickets, and you
> guys anyways helped us in our last effort in managing Jira tickets and
> review. Thanks for that.
>
> Plan is something like this, we would pick the easy entities first where
> we found minimum changes. After delivering few we will be able to establish
> practice internally, on what items we should take care before fixing an
> entity/service. We would like to go slow initially, and as soon as we start
> on it delivery process will more clear.
>
>
> Thanks again for your help, and looking forward for same in the big effort
> planned.
>
>
>
> Rishi Solanki
> Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>
> On Wed, Jul 13, 2016 at 2:36 PM, Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
>> Le 13/07/2016 à 09:39, Pierre Smits a écrit :
>>
>>> At this moment in time, I can't fathom how much effort is involved in
>>> this
>>> factoring, but I suggest to break it down as much as possible into
>>> separate
>>> JIRA issues. For instance, the rework on the removal of the
>>> OrderHeaderNoteView
>>> and OrderItemAndShipGroupAssoc from the OrderHeader entity can be a
>>> separate issue. Please be aware, that this might have a big impact in
>>> various functions/services/etc.
>>>
>>> Best regards,
>>>
>>> Pierre Smits
>>>
>> That's a good advice Pierre, from what I have seen these last months from
>> the HW effort, I'm confident they are totally aware of what to do :)
>>
>> Jacques
>>
>>
>

[jira] [Commented] (OFBIZ-7828) Entity and Service definition

[Rishi Solanki (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7828) Entity and Service definition

[Arun Patidar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Patidar reassigned OFBIZ-7828:
---

Assignee: Arun Patidar

> 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
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7828) Entity and Service definition

[Rishi Solanki (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rishi Solanki updated OFBIZ-7828:
-
Priority: Major  (was: Minor)

> 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
>
> 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
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7828) Entity and Service definition

[Rishi Solanki (JIRA)]

Rishi Solanki created OFBIZ-7828:


 Summary: 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
Priority: Minor


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
(v6.3.4#6332)

Re: Entity and Service definition

[Rishi Solanki]

Thank you everyone for your approval and suggestion. We would try to follow
most, and log Jira accordingly. Soon will start on this.

Nicolas, thanks for pointing expire action on entity-auto.

Jacques, Pierre, thanks for suggestion on managing Jira tickets, and you
guys anyways helped us in our last effort in managing Jira tickets and
review. Thanks for that.

Plan is something like this, we would pick the easy entities first where we
found minimum changes. After delivering few we will be able to establish
practice internally, on what items we should take care before fixing an
entity/service. We would like to go slow initially, and as soon as we start
on it delivery process will more clear.


Thanks again for your help, and looking forward for same in the big effort
planned.



Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Wed, Jul 13, 2016 at 2:36 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Le 13/07/2016 à 09:39, Pierre Smits a écrit :
>
>> At this moment in time, I can't fathom how much effort is involved in this
>> factoring, but I suggest to break it down as much as possible into
>> separate
>> JIRA issues. For instance, the rework on the removal of the
>> OrderHeaderNoteView
>> and OrderItemAndShipGroupAssoc from the OrderHeader entity can be a
>> separate issue. Please be aware, that this might have a big impact in
>> various functions/services/etc.
>>
>> Best regards,
>>
>> Pierre Smits
>>
> That's a good advice Pierre, from what I have seen these last months from
> the HW effort, I'm confident they are totally aware of what to do :)
>
> Jacques
>
>

Re: Entity and Service definition

[Jacques Le Roux]

Le 13/07/2016 à 09:39, Pierre Smits a écrit :

At this moment in time, I can't fathom how much effort is involved in this
factoring, but I suggest to break it down as much as possible into separate
JIRA issues. For instance, the rework on the removal of the OrderHeaderNoteView
and OrderItemAndShipGroupAssoc from the OrderHeader entity can be a
separate issue. Please be aware, that this might have a big impact in
various functions/services/etc.

Best regards,

Pierre Smits

That's a good advice Pierre, from what I have seen these last months from the 
HW effort, I'm confident they are totally aware of what to do :)

Jacques

Re: Entity and Service definition

[Pranay Pandey]

+1

Thanks for posting idea in detail.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Tue, Jul 12, 2016 at 2:01 PM, Rishi Solanki 
wrote:

> Dear Folks,
>
> While working/reviewing recent work in community, I observed some
> improvement/fixes required at entity and related service implementation.
> For few entities like InvoiceAttribute, InvoiceType, etc. no service exists
> to create/update/delete. At the time of writing migration scripts I always
> see lack of such services, which can be used to define new types or
> attributes. Also Many entities have some other problems in basic design of
> CRUD operations and in definitions;
>
> On further look into this in detail found many such entities which do not
> have services. I would like to propose a refactoring at basic design level
> which covers following which does not impact on functionality we have;
>
> 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.
>
> After this effort, OFBiz will have minimum direct use of delegator,
> enriched use of service engine, we would be able to established
> patterns/best practice to introduce a new entities, and writing new
> services.
>
> I would love to hear more improvements in this area from community. We will
> add them in this effort only.
>
>
> Rishi Solanki
> Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>

Re: Entity and Service definition

[Arun Patidar]

+1 for all suggestions.

Thanks & Regards
---
Arun Patidar
Manager, Enterprise Software Development
HotWax Systems
www.hotwaxsystems.com

On Tuesday 12 July 2016 02:01 PM, Rishi Solanki wrote:

Dear Folks,

While working/reviewing recent work in community, I observed some
improvement/fixes required at entity and related service implementation.
For few entities like InvoiceAttribute, InvoiceType, etc. no service exists
to create/update/delete. At the time of writing migration scripts I always
see lack of such services, which can be used to define new types or
attributes. Also Many entities have some other problems in basic design of
CRUD operations and in definitions;

On further look into this in detail found many such entities which do not
have services. I would like to propose a refactoring at basic design level
which covers following which does not impact on functionality we have;

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.

After this effort, OFBiz will have minimum direct use of delegator,
enriched use of service engine, we would be able to established
patterns/best practice to introduce a new entities, and writing new
services.

I would love to hear more improvements in this area from community. We will
add them in this effort only.


Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

Re: Entity and Service definition

[Pierre Smits]

I am all for improving the code base towards more consistency.

Having service definitions for CRUD functions for all entities, but the
view entities, is part of that. And it opens the opportunity to get a
potential future where OFBiz is opened up - in a relative easy way - to the
external environments via REST over HTTP microservices and what not.

I also concur with the posting done earlier by Taher: be careful when
migrating services to engine="entity-auto", as the devil is always in the
details.

At this moment in time, I can't fathom how much effort is involved in this
factoring, but I suggest to break it down as much as possible into separate
JIRA issues. For instance, the rework on the removal of the OrderHeaderNoteView
and OrderItemAndShipGroupAssoc from the OrderHeader entity can be a
separate issue. Please be aware, that this might have a big impact in
various functions/services/etc.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Wed, Jul 13, 2016 at 8:55 AM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:

> +1
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Wed, Jul 13, 2016 at 11:19 AM, Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
> > +1
> >
> > Jacques
> >
> >
> >
> > Le 12/07/2016 à 14:02, Nicolas Malin a écrit :
> >
> >> Hi Rishi,
> >>
> >> :) I totaly agree with your remarks
> >>
> >> In line
> >>
> >> Le 12/07/2016 10:31, Rishi Solanki a écrit :
> >>
> >>> Dear Folks,
> >>>
> >>> While working/reviewing recent work in community, I observed some
> >>> improvement/fixes required at entity and related service
> implementation.
> >>> For few entities like InvoiceAttribute, InvoiceType, etc. no service
> >>> exists
> >>> to create/update/delete. At the time of writing migration scripts I
> >>> always
> >>> see lack of such services, which can be used to define new types or
> >>> attributes. Also Many entities have some other problems in basic design
> >>> of
> >>> CRUD operations and in definitions;
> >>>
> >>> On further look into this in detail found many such entities which do
> not
> >>> have services. I would like to propose a refactoring at basic design
> >>> level
> >>> which covers following which does not impact on functionality we have;
> >>>
> >>> 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.
> >>>
> >> Agree
> >>
> >>> 2) Many entities having service implementation exists but they can be
> >>> simply convert into entity-auto, that means can use the power OFBiz
> >>> provides.
> >>>
> >> I has been started this work from 2 years :) , and currently I have
> >> stopped by Shipment Entities with a premission service refactoring
> >> https://issues.apache.org/jira/browse/OFBIZ-7113 and
> >> https://issues.apache.org/jira/browse/OFBIZ-6996
> >>
> >> I'm sure we can found some other service to convert ;)
> >>
> >>> 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.
> >>>
> >> After the migration, I would be move all generic service crud on the
> data
> >> model component to detect what missing service and list the reason
> >>
> >>> 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.
> >>>
> >> 1, I created the action expire on entity-auto to manage that ;)
> >>
> >>>
> >>> After this effort, OFBiz will have minimum direct use of delegator,
> >>> enriched use of service engine, we would be able to established
> >>> patterns/best practice to introduce a new entities, and writing new
> >>> services.
> >>>
> >> I appreciate your message :) it's pretty good to read that
> >>
> >>>
> >>> I would love to hear more improvements in this area from community. We
> >>> will
> >>> add them in this effort only.
> >>>
> >>>
> >>> Rishi Solanki
> >>> Manager, Enterprise Software Development
> >>> HotWax Systems Pvt. Ltd.
> >>> Direct: +91-9893287847
> >>> http://www.hotwaxsystems.com
> >>>
> >>>
> >>
> >>
> >
>

Re: Entity and Service definition

[Amardeep Singh Jhajj]

+1

Thanks & Regards
--
Amardeep Singh Jhajj

On Tue, Jul 12, 2016 at 2:01 PM, Rishi Solanki 
wrote:

> Dear Folks,
>
> While working/reviewing recent work in community, I observed some
> improvement/fixes required at entity and related service implementation.
> For few entities like InvoiceAttribute, InvoiceType, etc. no service exists
> to create/update/delete. At the time of writing migration scripts I always
> see lack of such services, which can be used to define new types or
> attributes. Also Many entities have some other problems in basic design of
> CRUD operations and in definitions;
>
> On further look into this in detail found many such entities which do not
> have services. I would like to propose a refactoring at basic design level
> which covers following which does not impact on functionality we have;
>
> 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.
>
> After this effort, OFBiz will have minimum direct use of delegator,
> enriched use of service engine, we would be able to established
> patterns/best practice to introduce a new entities, and writing new
> services.
>
> I would love to hear more improvements in this area from community. We will
> add them in this effort only.
>
>
> Rishi Solanki
> Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>

Re: Entity and Service definition

[Deepak Dixit]

+1

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Wed, Jul 13, 2016 at 11:19 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> +1
>
> Jacques
>
>
>
> Le 12/07/2016 à 14:02, Nicolas Malin a écrit :
>
>> Hi Rishi,
>>
>> :) I totaly agree with your remarks
>>
>> In line
>>
>> Le 12/07/2016 10:31, Rishi Solanki a écrit :
>>
>>> Dear Folks,
>>>
>>> While working/reviewing recent work in community, I observed some
>>> improvement/fixes required at entity and related service implementation.
>>> For few entities like InvoiceAttribute, InvoiceType, etc. no service
>>> exists
>>> to create/update/delete. At the time of writing migration scripts I
>>> always
>>> see lack of such services, which can be used to define new types or
>>> attributes. Also Many entities have some other problems in basic design
>>> of
>>> CRUD operations and in definitions;
>>>
>>> On further look into this in detail found many such entities which do not
>>> have services. I would like to propose a refactoring at basic design
>>> level
>>> which covers following which does not impact on functionality we have;
>>>
>>> 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.
>>>
>> Agree
>>
>>> 2) Many entities having service implementation exists but they can be
>>> simply convert into entity-auto, that means can use the power OFBiz
>>> provides.
>>>
>> I has been started this work from 2 years :) , and currently I have
>> stopped by Shipment Entities with a premission service refactoring
>> https://issues.apache.org/jira/browse/OFBIZ-7113 and
>> https://issues.apache.org/jira/browse/OFBIZ-6996
>>
>> I'm sure we can found some other service to convert ;)
>>
>>> 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.
>>>
>> After the migration, I would be move all generic service crud on the data
>> model component to detect what missing service and list the reason
>>
>>> 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.
>>>
>> 1, I created the action expire on entity-auto to manage that ;)
>>
>>>
>>> After this effort, OFBiz will have minimum direct use of delegator,
>>> enriched use of service engine, we would be able to established
>>> patterns/best practice to introduce a new entities, and writing new
>>> services.
>>>
>> I appreciate your message :) it's pretty good to read that
>>
>>>
>>> I would love to hear more improvements in this area from community. We
>>> will
>>> add them in this effort only.
>>>
>>>
>>> Rishi Solanki
>>> Manager, Enterprise Software Development
>>> HotWax Systems Pvt. Ltd.
>>> Direct: +91-9893287847
>>> http://www.hotwaxsystems.com
>>>
>>>
>>
>>
>

Re: Entity and Service definition

[Jacques Le Roux]

+1

Jacques


Le 12/07/2016 à 14:02, Nicolas Malin a écrit :

Hi Rishi,

:) I totaly agree with your remarks

In line

Le 12/07/2016 10:31, Rishi Solanki a écrit :

Dear Folks,

While working/reviewing recent work in community, I observed some
improvement/fixes required at entity and related service implementation.
For few entities like InvoiceAttribute, InvoiceType, etc. no service exists
to create/update/delete. At the time of writing migration scripts I always
see lack of such services, which can be used to define new types or
attributes. Also Many entities have some other problems in basic design of
CRUD operations and in definitions;

On further look into this in detail found many such entities which do not
have services. I would like to propose a refactoring at basic design level
which covers following which does not impact on functionality we have;

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.

Agree

2) Many entities having service implementation exists but they can be
simply convert into entity-auto, that means can use the power OFBiz
provides.
I has been started this work from 2 years :) , and currently I have stopped by Shipment Entities with a premission service refactoring 
https://issues.apache.org/jira/browse/OFBIZ-7113 and https://issues.apache.org/jira/browse/OFBIZ-6996


I'm sure we can found some other service to convert ;)

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.

After the migration, I would be move all generic service crud on the data model 
component to detect what missing service and list the reason

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.

1, I created the action expire on entity-auto to manage that ;)


After this effort, OFBiz will have minimum direct use of delegator,
enriched use of service engine, we would be able to established
patterns/best practice to introduce a new entities, and writing new
services.

I appreciate your message :) it's pretty good to read that


I would love to hear more improvements in this area from community. We will
add them in this effort only.


Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

Re: Entity and Service definition

[Nicolas Malin]

Hi Rishi,

:) I totaly agree with your remarks

In line

Le 12/07/2016 10:31, Rishi Solanki a écrit :

Dear Folks,

While working/reviewing recent work in community, I observed some
improvement/fixes required at entity and related service implementation.
For few entities like InvoiceAttribute, InvoiceType, etc. no service exists
to create/update/delete. At the time of writing migration scripts I always
see lack of such services, which can be used to define new types or
attributes. Also Many entities have some other problems in basic design of
CRUD operations and in definitions;

On further look into this in detail found many such entities which do not
have services. I would like to propose a refactoring at basic design level
which covers following which does not impact on functionality we have;

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.

Agree

2) Many entities having service implementation exists but they can be
simply convert into entity-auto, that means can use the power OFBiz
provides.
I has been started this work from 2 years :) , and currently I have 
stopped by Shipment Entities with a premission service refactoring 
https://issues.apache.org/jira/browse/OFBIZ-7113 and 
https://issues.apache.org/jira/browse/OFBIZ-6996


I'm sure we can found some other service to convert ;)

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.
After the migration, I would be move all generic service crud on the 
data model component to detect what missing service and list the reason

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.

1, I created the action expire on entity-auto to manage that ;)


After this effort, OFBiz will have minimum direct use of delegator,
enriched use of service engine, we would be able to established
patterns/best practice to introduce a new entities, and writing new
services.

I appreciate your message :) it's pretty good to read that


I would love to hear more improvements in this area from community. We will
add them in this effort only.


Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

Re: Entity and Service definition

[Swapnil Mane]

+1 for all suggestions, seems good improvements to me :-)

- Best Regards,
Swapnil M Mane
H otWax Systems
 - *The global leader in innovative
enterprise commerce s**olutions **powered by Apache OFBiz.*
ApacheCon US 2015 Silver Sponsor



On Tue, Jul 12, 2016 at 2:01 PM, Rishi Solanki 
wrote:

> Dear Folks,
>
> While working/reviewing recent work in community, I observed some
> improvement/fixes required at entity and related service implementation.
> For few entities like InvoiceAttribute, InvoiceType, etc. no service exists
> to create/update/delete. At the time of writing migration scripts I always
> see lack of such services, which can be used to define new types or
> attributes. Also Many entities have some other problems in basic design of
> CRUD operations and in definitions;
>
> On further look into this in detail found many such entities which do not
> have services. I would like to propose a refactoring at basic design level
> which covers following which does not impact on functionality we have;
>
> 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.
>
> After this effort, OFBiz will have minimum direct use of delegator,
> enriched use of service engine, we would be able to established
> patterns/best practice to introduce a new entities, and writing new
> services.
>
> I would love to hear more improvements in this area from community. We will
> add them in this effort only.
>
>
> Rishi Solanki
> Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>

Re: Entity and Service definition

[Rishi Solanki]

Thank you Taher, and yes I had the same concern for it, even when we are
working on enforcing noninstantiability, but we will be able to achieve
zero regression till now by doing internal multi-level QA.

Thanks for pointing this, we will ensure before proceeding for any changes.
:)

Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Tue, Jul 12, 2016 at 2:13 PM, Taher Alkhateeb  wrote:

> Hi Rishi,
>
> Great Ideas, +1 for all suggestions.
>
> I only have one warning because this happened in the past: Do not switch
> from Services to entity-auto without being 100% sure this is the right
> thing to do. Sometimes you miss important logic that breaks things
> elsewhere.
>
> Thank you for the initiative, I love this enthusiasm and energy :)
>
> Cheers!
>
> Taher Alkhateeb
>
> On Tue, Jul 12, 2016 at 11:31 AM, Rishi Solanki 
> wrote:
>
> > Dear Folks,
> >
> > While working/reviewing recent work in community, I observed some
> > improvement/fixes required at entity and related service implementation.
> > For few entities like InvoiceAttribute, InvoiceType, etc. no service
> exists
> > to create/update/delete. At the time of writing migration scripts I
> always
> > see lack of such services, which can be used to define new types or
> > attributes. Also Many entities have some other problems in basic design
> of
> > CRUD operations and in definitions;
> >
> > On further look into this in detail found many such entities which do not
> > have services. I would like to propose a refactoring at basic design
> level
> > which covers following which does not impact on functionality we have;
> >
> > 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.
> >
> > After this effort, OFBiz will have minimum direct use of delegator,
> > enriched use of service engine, we would be able to established
> > patterns/best practice to introduce a new entities, and writing new
> > services.
> >
> > I would love to hear more improvements in this area from community. We
> will
> > add them in this effort only.
> >
> >
> > Rishi Solanki
> > Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> >
>

Re: Entity and Service definition

[Taher Alkhateeb]

Hi Rishi,

Great Ideas, +1 for all suggestions.

I only have one warning because this happened in the past: Do not switch
from Services to entity-auto without being 100% sure this is the right
thing to do. Sometimes you miss important logic that breaks things
elsewhere.

Thank you for the initiative, I love this enthusiasm and energy :)

Cheers!

Taher Alkhateeb

On Tue, Jul 12, 2016 at 11:31 AM, Rishi Solanki 
wrote:

> Dear Folks,
>
> While working/reviewing recent work in community, I observed some
> improvement/fixes required at entity and related service implementation.
> For few entities like InvoiceAttribute, InvoiceType, etc. no service exists
> to create/update/delete. At the time of writing migration scripts I always
> see lack of such services, which can be used to define new types or
> attributes. Also Many entities have some other problems in basic design of
> CRUD operations and in definitions;
>
> On further look into this in detail found many such entities which do not
> have services. I would like to propose a refactoring at basic design level
> which covers following which does not impact on functionality we have;
>
> 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.
>
> After this effort, OFBiz will have minimum direct use of delegator,
> enriched use of service engine, we would be able to established
> patterns/best practice to introduce a new entities, and writing new
> services.
>
> I would love to hear more improvements in this area from community. We will
> add them in this effort only.
>
>
> Rishi Solanki
> Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>

Entity and Service definition

[Rishi Solanki]

Dear Folks,

While working/reviewing recent work in community, I observed some
improvement/fixes required at entity and related service implementation.
For few entities like InvoiceAttribute, InvoiceType, etc. no service exists
to create/update/delete. At the time of writing migration scripts I always
see lack of such services, which can be used to define new types or
attributes. Also Many entities have some other problems in basic design of
CRUD operations and in definitions;

On further look into this in detail found many such entities which do not
have services. I would like to propose a refactoring at basic design level
which covers following which does not impact on functionality we have;

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.

After this effort, OFBiz will have minimum direct use of delegator,
enriched use of service engine, we would be able to established
patterns/best practice to introduce a new entities, and writing new
services.

I would love to hear more improvements in this area from community. We will
add them in this effort only.


Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com