[
https://issues.apache.org/jira/browse/OFBIZ-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490053#comment-15490053
]
Taher Alkhateeb commented on OFBIZ-8156:
----------------------------------------
Hello,
In reviewing the patch for this work, I notice that you only focus on removing
Fedex. Why only Fedex? The system supports DHL, UPS, USPS but all the removal
I'm seeing is only for Fedex. I also note that this does not look like a
disentanglement to me (no redesign) but rather just removal of Fedex specific
data, labels, widgets and code.
So my questions are:
- Why only fedex, and leaving other shipment methods intact?
- What do you mean by disentanglement?
> Disentangle Fedex solution from current integrated state
> --------------------------------------------------------
>
> Key: OFBIZ-8156
> URL: https://issues.apache.org/jira/browse/OFBIZ-8156
> Project: OFBiz
> Issue Type: Sub-task
> Components: commonext, datamodel, order, product,
> specialpurpose/ecommerce, specialpurpose/oagis, specialpurpose/webpos
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Priority: Minor
> Labels: 3rdParty, integration, shipment
> Attachments: OFBIZ-8156-FedexRemoval.patch
>
>
> Disentanglement of the 3rd party shipment integration for FedEx gives the
> OFBiz adopter more flexibility, reduces the default code base and offers the
> project more opportunities with respect to attracting product specific
> contributors, better code and faster release cycles.
> Requirements of the disentangled solution:
> * should not need a separate entity to capture configuration elements
> * configuration should be contained in the component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
