Fulfillment Common Release Notes

Table of Contents

2.0.2-GA

Removed validation annotations on FulfillmentOptionRequest and related domain since they aren’t always correct and are not extensible.
- These have been replaced by an EntityValidator in Fulfillment Services. Use Fulfillment Services 2.0.3 alongside of Fulfillment Common 2.0.2.

Introduced a new class for representing Distance.
- This is currently used in two places: when determining if an address is within a Fulfillment Destination radius, and determining dimension restrictions for Fulfillment Calculators.
Relaxed the field requirements on Dimensions class.
- Previously, the Dimensions class required that its length field was a non-zero value. This imposed an extra burden on callers of the API to ensure that their dimension values matched this format.
- This was compounded by the fact that the product dimension fields and fulfillment Dimension class used different names for their fields. Now, all fields in the Dimension class can be zero.
- Additionally, if null is passed in for any field, it will be set to zero instead of throwing an exception.
Added supportedFulfillmentTypes field to hold a list of all the FulfillmentTypes that are supported by an application in FulfillmentPricingConfig.
- At this time, this field is available as a hook point for customizations. Framework functionality will be added in a future release.

As of Broadleaf Release Train 2.0.0-GA, all common libraries have been upgraded to Spring Boot 3.

Compatible with all Release Trains after 1.7 unless otherwise noted.