You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Hans Bakker (JIRA)" <ji...@apache.org> on 2016/03/16 02:20:33 UTC
[jira] [Closed] (OFBIZ-6923) Improve the decorator for
manufacturing/order/facility component for re-use
[ https://issues.apache.org/jira/browse/OFBIZ-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hans Bakker closed OFBIZ-6923.
------------------------------
Resolution: Fixed
Fix Version/s: Upcoming Branch
Committed revision 1735178.
Thank you Kongrath Suankaewmanee for your contribution.
> Improve the decorator for manufacturing/order/facility component for re-use
> ---------------------------------------------------------------------------
>
> Key: OFBIZ-6923
> URL: https://issues.apache.org/jira/browse/OFBIZ-6923
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing, order, product
> Affects Versions: Trunk
> Reporter: Kongrath Suankaewmanee
> Assignee: Hans Bakker
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-6923.patch
>
>
> 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)