Details
-
Bug
-
Resolution: Unresolved
-
Neutral
-
None
-
6.0
-
None
-
None
Description
Description
In a use case with 3 CT-based apps I have observed partially erroneous registered apps.
When debugging, we can see that the name (and the registryId) of one app was wrong.
This leads to some problems / unexpected behavior e.g. on the applauncher. (That’s why I got aware of the problem).
Use case / examples
My use case was a light module with 3 CTs - each CT with a CT-based app:
=> content-type-examples (tagged version).
| CT-name as defined | app-name as defined | app name as in registry* |
|---|---|---|
| tourVehicle | tourVehicles-app | tourVehicles-app |
| tourGuide | tourGuides-app | tourOffices-app |
| tourOffice | tourOffices-app | tourOffices-app |
*) checked via debugger
Side problem
The „special“ thing about the use case is, that all the 3 apps are CT-based, and that on startup these CTs (and its apps) may have problems due to relations between CTs and the fact that the CTs are loaded arbitrary. (We have a ticket for this => MGNLCT-80)
To overcome this, in my use case, I usually touch all files for CTs and for apps in the appropriate order to make sure the CTs (and hopefully the apps too) are registered correctly.
When looking carefully at the log - while touching the files to enforce (hopefully) proper registration, we already can see some issues (sometimes); see gist.
Order of touching the files:
- tourVehicle.yaml (CT)
- tourVehicles-app.yaml (app-def.)
- tourGuide.yaml
- tourGuides-app.yaml
- tourOffice.yaml
- tourOffices-app.yaml
Side note
The problem does not always appear, and sometimes the problem may be a bit different. (The 2nd statement is a conclusion from what I have seen on the app-launcher).