Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Capella/Tutorials/InformationView

< Capella‎ | Tutorials
Revision as of 05:10, 6 February 2019 by Felix.dorner@gmail.com (Talk) (started collecting some things about the information view to make it better.)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page collects useful things to know about the allmighty Capella 'Information View'. Just type Ctrl-3 + Information View to open it.

The information view has 2 main purposes in Capella:

  • Displays validation results
  • Can be used to log arbitrary messages

In any case, a message displayed in the view can have more or one Objects, usually Model Elements, attached to it. You can see these attached objects in the context menu of a message (Related Elements is the name I think).

The view can be configured in different flavours:

  • Grouped by Message severity
  • Grouped by Rule ID
  • Flat

The following columns are displayed:

Category: - For validation results, this is the category of the rule, as shown in the Model Validation Preference Page. - For other elements, this is the 'source' value of the underlying Diagnostic. - Special rule for EMF validation diagnostics.

  • Severity: Just the severity of the marker
  • Rule Set: The marker attribute IValidationConstants.TAG_PREFERENCE_EPF_FILE value
  • Rule ID: The unqualified rule ID for validation results, or the diagnostic source for other markers. Special code handles EMF validation markers
  • Message: The underlying marker message attribute value
  • Date: The underlying marker creation time
  • Resource: the value of MarkerViewUtil.PATH_ATTRIBUTE for the underlying marker


Unsolved problems:

  • Special code to pretty print maker source attribute for emf validation rules. A diagnostic source is usually a plugin identifier, something more machine readable and we want something pretty-printed..
  • Many of the columns are really only useful for validation results, not for arbitrary log entries
  • Limited/no support to display tree structures: We start with a Diagnostic, which is a Tree, but the view linearizes it.

Back to the top