-
Type: New Feature
-
Status: Resolved
-
Priority: Minor
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Runtime
-
Epic Link:
-
Tags:
Error / Debug
There are still some cases where Nuxeo Runtime does not behave cleanly and makes debugging harder than needed.
See NXP-16642: should detect
- duplicated component name
- extension point not found
- missing requirements from non optional components
- invalid XML contribution
- missing file referenced from MANIFEST
Startup
When Nuxeo Server starts, in case of error (bad contribution, bad startup handler ...), Nuxeo Runtime should stop right away and display the error if it is a "grave" error or if "strict mode" is enabled.
Use cases to review, warnings at startup also need improvements, see NXP-17707
Tests Setup
Using FeatureRunner is great, but if for some reason there is an error during the setup of one of the feature, the test fails and this is usually very difficult to debug:
- because it does not say there is a setup issue
- because the logs and exceptions are swallowed
-> TODO: give examples
- depends on
-
NXP-16642 verify the following errors are reported in runtime statuses
- Resolved
-
NXP-17707 Add a way to report warning on nuxeoctl status
- Resolved
- duplicates
-
NXP-29504 Fix Nuxeo startup logging of duplicate components
- Resolved
-
NXP-16490 Tighten Nuxeo Runtime
- Open
-
NXP-20418 nuxeoctl start should be in strict mode by default
- Resolved
- is related to
-
NXP-29504 Fix Nuxeo startup logging of duplicate components
- Resolved
- is required by
-
NXP-880 Error text displayed on creation forms
- Closed