com.neurosys.ecom.strategy.service

Interface CumulativeChargeStrategy<P extends Product,U extends User>

All Superinterfaces:

ChargeStrategy<P,U>, Strategy

All Known Subinterfaces:

PromotionStrategy<P,U>, SaleStrategy<P,U>, TaxStrategy<P,U>

All Known Implementing Classes:

AbstractChargeStrategy, DefaultDiscountStrategy, DefaultOrderStrategy, DefaultPackagingStrategy, DefaultPromotionStrategy, DefaultSaleStrategy, DefaultShippingStrategy, DefaultSubOrderStrategy, DefaultTaxStrategy

public interface CumulativeChargeStrategy<P extends Product,U extends User>
extends ChargeStrategy<P,U>

Using rules to calculate data where the result may requires Cumulative analysis of all Products and not just on a per product

Author:

Arjun Dhar

Method Summary

Modifier and Type	Method and Description
<CONTEXT> Amount	calculate(Map<P,Number> productQtyMap, U user, String currency, List<PromotionForUser> promotions, Amount subTotal, Number quantityTotal, CONTEXT context) Calculate raw amount for product(s)

Methods inherited from interface com.neurosys.ecom.strategy.service.ChargeStrategy

calculate

Methods inherited from interface com.neurosys.ecom.strategy.service.Strategy

getVersion

Method Detail

calculate

<CONTEXT> Amount calculate(Map<P,Number> productQtyMap,
                           U user,
                           String currency,
                           List<PromotionForUser> promotions,
                           Amount subTotal,
                           Number quantityTotal,
                           CONTEXT context)

Calculate raw amount for product(s)

Parameters:

productQtyMap - as Map of Product to Number (Quantity)

user - as U @NUllable true

currency - as String @nullable true. A null implies default currency. Note: If not null then this will override subTotal Amount.getCurrency().

List - of PromotionForUsers @nullable true - if Promotions do not apply then it can be null

subTotal - as Amount; many scenarios use the Sub-Total of products to calculate other params. So provide that as a defined context variable. @nullable true

quantityTotal - as Number; many scenarios use the quantityTotal of products to calculate other params @nullable true

context - as additional case driven params that can be supplied @nullable true

Returns:

Amount @nullable true (implementation dependent) For Promotions; if there is a discount then Amount.getTotal() should be positive; while Amount.getDiscount() should be negative number. This is because a Discount is DEDUCTED. So while it makes sense to DEDUCT a positive value from TOTAL; the discount itself should be ADDED hence = > Existing Total - (This Discount as Total) Existing Discount - (-This Discount) = Existing Discount + This Discount