Interface BroadleafModuleRegistration
- All Known Implementing Classes:
AdminModuleRegistration
public interface BroadleafModuleRegistration
Provides the ability for modules to register themselves with Broadleaf to be used with ConditionalOnBroadleafModule and ModulePresentUtil
in order to provide different behavior in inter-module dependencies.
Module implementations should be registered in a spring.factories file like so:
org.broadleafcommerce.common.condition.BroadleafModuleRegistration=com.broadleafcommerce.mymodule.registration.MyModuleRegistration
In order to preserve compile-time checking, additional modules should be added to the BroadleafModuleRegistration.BroadleafModuleEnum. However, if they aren't,
this can always be checked at runtime instead by just looking for the String-based module name.
- Since:
- 5.2
- Author:
- Phillip Verheyden (phillipuniverse)
-
Nested Class Summary
Nested ClassesModifier and TypeInterfaceDescriptionstatic enumList of modules that are known to have declared aBroadleafModuleRegistrationin theirspring.factories. -
Method Summary
Modifier and TypeMethodDescriptionThe module name that is being registered.
-
Method Details
-
getModuleName
String getModuleName()The module name that is being registered. This should generally be the same as the logging information from aModuleLifecycleLoggingBean.
-