- v1.0.0-latest-prod
JDK 11 is required for Broadleaf release trains 1.7.0-GA, and beyond.
JDK 17 is supported for Broadleaf release trains 1.8.1-GA, and beyond.
Added support for resolving Applications by context-path.
Introduced a new identifier type of CONTEXT_PATH.
Applications using this type will have their identifier value treated as the first path segment in a URL:
If the identifier is my-app, then it will be resolved on URLs like https://localhost/my-app.
The identifier is expected to only match the first path segment not any arbitrary subsequent segment. Therefore, https://localhost/some-path/my-app would not match.
Fixed issue where vendorRef isn’t populated to the application’s isolated implicit catalog
Note that this is only relevant if broadleaf.common.data.application.configuration.allow-vendor-catalog-in-application-isolated-catalogs is enabled and the isolated catalog is a vendor catalog
Deprecated the property broadleaf.tenant.application.allow-vendor-catalog-in-application-isolated-catalogs, use DataTracking’s broadleaf.common.data.application.configuration.allow-vendor-catalog-in-application-isolated-catalogs instead
Added validations and metadata level restriction to ensure that when vendor catalogs are added as isolated catalogs, they:
Cannot be visible as assigned
Must be excluded from add
This is because content such as categories & products must be added to the vendor catalogs directly at the tenant level instead when they are added as isolated catalogs