[jira] [Commented] (OFBIZ-9241) Removes ecommerce links from applications

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-9241) Removes ecommerce links from applications

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587176#comment-16587176 ]

Michael Brohl commented on OFBIZ-9241:
--------------------------------------

This solution also implies that the framework knows about the ecommerce plugin which it should not.

We will need some mechanism like we have for the backend applications (e.g. app-bar-display in ofbiz-component). Some kind of hook mechanism or maybe data driven links/content which will only be loaded when the plugin is available.

I have not the time to dig deeper now but encourage the community to think about a sustainable solution or throw in ideas.

> Removes ecommerce links from applications
> -----------------------------------------
>
>                 Key: OFBIZ-9241
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9241
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: ALL APPLICATIONS
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Major
>             Fix For: 17.12.01
>
>         Attachments: OFBIZ-9241.patch, OFBIZ-9241.patch
>
>
> While working on OFBIZ-9206 I remembered how the ecommerce webapp is deeply entrenched in some applications components. This can at least be tested with product and catalog webapp.
> # Get to catalog/control/EditProduct?productId=GZ-1000
> # Click on the "Product Page" button => ecommerce
> There are much more cases (96 occurrences actually) but most of them are not hard dependencies.
> Since the ecommerce component is now a plugin, we need to remove all ecommerce links from applications, I even wonder if this issue is really an improvement or should not be now considered a bug...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)