[
https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315398#comment-16315398 ]
Jacques Le Roux commented on OFBIZ-9147:
----------------------------------------
Example components (both) are there to explain/show how things works. The exampleext component is *only * there to demonstrate the extension mechanisms. It as much as simply possible does that. So usage of extension mechanisms are not blurred with other features. That's why it exists and I think it's a good thing. We previsouly had the same idea with the ecomclone component. It was removed because it was redundant with exampleext, and even more locally with ecomseo which demonstrates other usages of extension mechanisms.
Now what we could do is creating an .md file where things would be more explained. This file could be used in a wiki page as an import after a Pandoc conversion to HTML, as I suggested many times and lastly today in OFBIZ-9190
> Disentangle ExampleExt from the codebase
> ----------------------------------------
>
> Key: OFBIZ-9147
> URL:
https://issues.apache.org/jira/browse/OFBIZ-9147> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Pierre Smits
> Priority: Minor
> Labels: refactoring
> Attachments: OFBIZ-9147-component-load.xml.patch
>
>
> Currently the functionality of the ExampleExt component brings nothing more than a few widgets that extend the examples in the Example component. These ExampleExt widgets can as easily exist in the Example component.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Locked
