[
https://issues.apache.org/jira/browse/OFBIZ-11678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103196#comment-17103196 ]
Suraj Khurana commented on OFBIZ-11678:
---------------------------------------
Yes, I was also thinking about it.
One proposal is to change the existing mini-lang to groovy with suggested changes being incorporated.
Another is to do it in two steps, first change it to groovy code as is and then remove dependency.
Tough in a cursory review, if we remove existing work-effort code dependency, shipment services can be converted to entity-auto as well. :)
So I am in favour fo first proposal.
> Make Shipment services loosely coupled with work-effort generation
> ------------------------------------------------------------------
>
> Key: OFBIZ-11678
> URL:
https://issues.apache.org/jira/browse/OFBIZ-11678> Project: OFBiz
> Issue Type: Improvement
> Components: workeffort
> Affects Versions: Trunk
> Reporter: Suraj Khurana
> Assignee: Suraj Khurana
> Priority: Major
>
> Currently, createShipment and updateShipment services creates/updates work-effort and related code is written inside the same service, this should not be tightly coupled with each other.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Locked
