Search code examples
javaportal

Optional module dependencies in Port@l

In Port@l, all declared module dependencies seem to be mandatory. Is it possible to have optional dependencies in a module? If so, how are they declared?

Solution

  • Port@l modules are potentially incomplete Spring Application Contexts. Beans that are referenced from the application context but are not part of it must be declared as dependencies in the module interface and it will be considered as mandatory.

    However, if you declare as a dependency in the module interface a bean that is alreay part of the application context, Port@l will consider it an optional dependency.