The Essential Project Forum

I understand that the composite application component provider class is the preferred class for applications. The editor has a module section on it and OOTB that section creates application providers. Should I update the editor to focus modules on the composite application provider as the target for that section?

What's the rationale for keeping the modules as just basic application providers?

Thanks,
Paul

Hu Paul,

just to confmr, we recommend using the Application Provider class for application components that are considered to be atomic in nature and cannot be broken down any further from a functional perspectve, e.g. custon-built micro-services, packaged application modules) which is why Application Providers do not have the "contained_ppplication_providers" slot.

However, there is no significant issue in capturing these types of components using the Composite Application Provider class and so if this is your prefertence (for example, to allow ANY application component to be broken down into sub-components), then feel free to update that Editor component in the Editor Builder so that users can select and create instances of Composite Application Provider for sub-modules.

Thanks,

Jason

Thanks, that is very helpful and makes sense. We had someone create a parent "product" as a composite application provider and then various applications that make up the product as it's 'modules'. It didn't make sense within the model. I've shifted them to using Application Family as the parent "product", but I wanted to make sure I understood what the module part was really for. Thank you!!

Paul