[
https://issues.apache.org/jira/browse/OFBIZ-12965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831679#comment-17831679
]
Pierre Smits edited comment on OFBIZ-12965 at 3/28/24 9:05 AM:
---------------------------------------------------------------
Hi [~jleroux],
We are all aware of the complexities in service definitions in xml
IMO, each entity definition should have entity-auto services regarding the CRUD
processes, preferably in the datamodel component. And any other more complex
service definition in groovy or java should call such entity-auto service.
was (Author: pfm.smits):
Hi [~jleroux],
We are all aware of the complexities in service definitions in xml
IMO, each entity definition should have entity-auto services regarding the CRUD
processes, preferably in the datamodel component. And any other more complex
service definition in groovy or java should call such service.
> Convert WorkEffortServices.xml mini-lang to groovyDSL (partial)
> ---------------------------------------------------------------
>
> Key: OFBIZ-12965
> URL: https://issues.apache.org/jira/browse/OFBIZ-12965
> Project: OFBiz
> Issue Type: Sub-task
> Components: workeffort
> Reporter: Nicolas Malin
> Assignee: Nicolas Malin
> Priority: Minor
> Labels: groovy, mini-lang
> Fix For: Upcoming Branch
>
>
> Convert the following service :
> * createWorkEffort
> * updateWorkEffort
> * deleteWorkEffort
> * copyWorkEffort
> * createWorkEffortAndPartyAssign
> createWorkEffort contains too functionnal logic on the base code so split it
> on different services and intoduce :
> * assocAcceptedCustRequestToWorkEffort, run throught seca
> * createWorkEffortStatus
> createWorkEffortAndPartyAssign use the entity-auto logic so create services
> createWorkEffortPartyAssignment, updateWorkEffortPartyAssignment and
> expireWorkEffortPartyAssignment to make them more generic
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
