You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2007/01/13 22:33:27 UTC
[jira] Commented: (OFBIZ-300) Support for group shipment cost
estimate and additional span support for feature and base pricing
[ https://issues.apache.org/jira/browse/OFBIZ-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464531 ]
Jacques Le Roux commented on OFBIZ-300:
---------------------------------------
Ray,
Please can you send an updated patch (I guess you have still this changes somewhere) because I can't patch easily with this : too old and especlially pathes not relative.
Thanks
> Support for group shipment cost estimate and additional span support for feature and base pricing
> -------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-300
> URL: https://issues.apache.org/jira/browse/OFBIZ-300
> Project: Apache OFBiz (The Open for Business Project)
> Issue Type: Improvement
> Components: product
> Affects Versions: SVN trunk
> Reporter: Marco Risaliti
> Assigned To: Jacques Le Roux
> Attachments: product.patch
>
>
> It's a copy of the old-jira issue http://jira.undersunconsulting.com/browse/OFBIZ-209 from Ray Barlow.
> ===========================================
> This patch allows more than one cost estimate to be used to calculate shipping. With this group support it is possible to calculate shipping based on more than one feature having more than one price. My needs were to support:
> All large items 5.00 and each additional large item 2.25
> All small items 2.50 and each additional small item 1.00
> I've done this by creating 4 grouped shipping cost estimates using spans to handle the quantity of 1 and a base price scenario. Having completed it I think it could be done using 2 estimates by changing the data but for now it functions as desired and I need some sleep.
> This is at present a backwards compatibile feature and should not change the functionality for any existing shipping cost estimates.
> There is not much code change, I just had to split calcShipmentCostEstimate into two methods so the actual calculation code could be repeatedly called for grouped estimates. It still follows the pattern of find all valid estimates, pick one based on the priorities, calculate the cost. It then checks if the estimate is part of a group and it will then pull from the pre-validated list of estimates for other members of the same group to add to the shipping cost.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira