You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Kongrath Suankaewmanee (JIRA)" <ji...@apache.org> on 2016/03/08 08:49:40 UTC

[jira] [Updated] (OFBIZ-6923) Improve the decorator for manufacturing component.

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

Kongrath Suankaewmanee updated OFBIZ-6923:
------------------------------------------
    Attachment: manufacturing-decorator.diff

> Improve the decorator for manufacturing component.
> --------------------------------------------------
>
>                 Key: OFBIZ-6923
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6923
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: manufacturing
>    Affects Versions: Trunk
>            Reporter: Kongrath Suankaewmanee
>         Attachments: manufacturing-decorator.diff
>
>
> We have a problem on organize the existing decorator. In this case is manufacturing decorator and also in another decorator too. We cannot use the existing decorator with *main-decorator* that define on another component in *hot-deploy*.
> So, I thought we should make reorganization for decorator like in the partymgr component
> *applications/party/widget/partymgr/CommonScreens.xml*
> All screen should call the common decorator and each common decorator call *main-decorator* in each commonent, so if we have create the new component in *hot-deploy* and it should use the *main-decorator* in their.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)