[
https://issues.apache.org/jira/browse/OFBIZ-10401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473038#comment-16473038 ]
Jacques Le Roux edited comment on OFBIZ-10401 at 5/12/18 11:08 AM:
-------------------------------------------------------------------
I just looked at Suraj's work for OFBIZ-10395 and I think we should use the same way, ie using entity auto and force the default status to IN_PROGRESS. So if we agree we can rename the issue to Migrate createContent and createDataResource services from Minilang to Entity Auto and use
{{<override name="statusId" default-value="IN_PROGRESS"/>}}
No needs to complexify here.
was (Author: jacques.le.roux):
I just looked at Suraj's work for OFBIZ-10395 and I think we should use the same way, ie using entity auto and force the status to IN_PROGRESS. So if we agree we can rename the issue to Migrate createContent and createDataResource services from Minilang to Entity Auto and use
{{<override name="statusId" default-value="IN_PROGRESS"/>}}
No needs to complexify here.
> Migrate createContent and createDataResource services from Minilang to Groovy
> -----------------------------------------------------------------------------
>
> Key: OFBIZ-10401
> URL:
https://issues.apache.org/jira/browse/OFBIZ-10401> Project: OFBiz
> Issue Type: Improvement
> Components: content
> Affects Versions: Trunk
> Reporter: Jacques Le Roux
> Priority: Minor
> Fix For: Upcoming Branch
>
>
> This follows OFBIZ-10393 where things started.
> Deepak suggested to use entity auto for createContent service, but we don't handle automated status creation in entity auto (invokeCreate method) as it's currently done in createContent and createDataResource services Minilang implementations. Where if no status is passed to the service, the 1st one in the CONTENT_STATUS list is picked, here IN_PROGRESS. So using Groovy for these services seems to fit.
> We still need to decide to use blank or the same than currently exists. For the sake of historic compatibility I suggest to keep the same.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
