SCION Platform Lifecycle after Activator Initialization

[efux]

Is your feature request related to a problem?

We are using multiple micro-frontends. As soon as the application is started, we send an intent to a micro-frontend, which is handled by the Activator of the micro-frontend. The activator then uses the OutletRouter to display a page.

Currently the host application does not know, if there is somebody listening to the capabilities described in the client's manifest.json. This leads to sent intents being lost, when the intents are sent to early.

Describe alternatives you've considered

Currently we are send a topic message per micro-frontend after the activator is completely initialized. E.g.

Beans.get(MessageClient)
                .publish('activated/casa-angebot-web', null, {retain: true});

And the host application waits until it has received activated/* messages from every necessary micro-frontend before triggering the intent for navigation.

Describe the solution you'd like

There are multiple possible solutions:

• Maybe some of the work (or all?) done by the workaround can be handled by the SCION platform.
• Maybe there is even a possiblity to know if somebody is really handling a capability, so sent intents are not lost.