The explorer should hold a status on its contributions, taking into account components that were started in error.
That implies:
- starting Nuxeo not in "strict" mode
- extracting the statuses from the runtime component manager (component might have generated an error at startup, or might be invalid so cannot be handled by the runtime, or might be waiting for a dependency that is not there, for instance)
- holding this error/warning message on the component : the errors shown at startup are currently "bare" messages attached to the runtime component, and cannot be traced back easily to a given component
- depends on
-
NXP-29504 Fix Nuxeo startup logging of duplicate components
- Resolved
-
NXP-29499 Fix error management on invalid operation/chain/codec registration
- Resolved
-
NXP-29573 Better track runtime errors and warnings
- Resolved
-
NXP-29580 Rework descriptor mechanism
- Resolved
- is related to
-
NXP-29571 Allow registering runtime component listeners early
- Resolved
-
NXP-29619 Allow starting nuxeo docker image disabling strict mode
- Resolved
-
NXP-29220 Improve Explorer secure XML content logics
- Resolved
- Is referenced in