[jira] Closed: (OFBIZ-548) Refactor upsRateInquire two services upsRateInquire and upsRateInquireByZipCode

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

[jira] Closed: (OFBIZ-548) Refactor upsRateInquire two services upsRateInquire and upsRateInquireByZipCode

Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marco Risaliti closed OFBIZ-548.
--------------------------------

    Resolution: Fixed

This improvement has been already implemented a long time ago and so we can close this issue.

Thanks
Marco

> Refactor upsRateInquire two services upsRateInquire and upsRateInquireByZipCode
> -------------------------------------------------------------------------------
>
>                 Key: OFBIZ-548
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-548
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>            Reporter: Anil K Patel
>
> The upsRateInquire service takes shippingContactMechId parameter. This parameter is used to get PostalCode on the postal Address. Which in turn is used for RateInquire.
> If we break this service into two,
> 1) upsRateInquireByZipCode, this service will switch shippingContactMechId for PostalCode. It service will have almost  the code that current upsRateInquire has.
> 2) upsRateInquire. All this service will have is code to read PostalAddress from shippingContactMechId. Read PostalCode from PostalAddress and then call upsRateInquireByZipCode,
> If we did this, We will be able Provide Shipping Estimate as first step of CheckOut process for Anonymous user.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.