Skip to content

Report broken references in contained connection properties 馃 - #3115

Open
lwrage wants to merge 2 commits into
masterfrom
3106_report_connection_reference_errors
Open

Report broken references in contained connection properties 馃#3115
lwrage wants to merge 2 commits into
masterfrom
3106_report_connection_reference_errors

Conversation

@lwrage

@lwrage lwrage commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Fixes #3106

Cause

CacheContainedPropertyAssociationsSwitch collected reference-instantiation problems for copied contained associations, but the semantic-connection branch recorded the association in SCProperties without reporting those problems. The equivalent component branch reported them.

Correction

Report the collected problems after retaining the semantic-connection association. The diagnostic is attached to the connection instance because the copied association in SCProperties is detached from the instance resource at that point.

Regression

Issue3106Test uses a valid external AADL model with matching Actual_Processor_Binding and Actual_Connection_Binding references. A refinement removes the referenced instance object. The test verifies that both associations retain the declarative platform.core path and that instantiation reports two missing-reference errors. An unrefined control verifies that resolvable references produce no errors.

The regression failed before the production change with one reported error instead of two.

Validation

  • Focused Issue3106Test offline Maven -T6 verify: 2 tests, 0 failures, 0 errors
  • Related Issue2929Test offline Maven -T6 verify: 3 tests, 0 failures, 0 errors
  • Related Issue3104Test offline Maven -T6 verify: 7 tests, 0 failures, 0 errors
  • Clean root-reactor offline Maven -T6 install with tycho.localArtifacts=ignore: all 137 projects succeeded

Dependencies

None. The branch is based directly on origin/master at 7729ae9.

Residual risk

The new diagnostic is located on the connection instance rather than the copied ReferenceValue because that copied value is not attached to a resource when the problem is reported. Reporting is limited to associations that are retained; constant overrides keep their existing behavior.

Model equivalent contained reference values on a component and connection, then refine away their target. Assert that both associations remain declarative and that instantiation reports both missing references, while the unrefined control remains error-free.
Report reference-instantiation issues when a contained property association is retained for a semantic connection. Place the diagnostic on the attached connection instance because the copied association stored in SCProperties is not yet part of the instance resource.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A broken reference in a contained property association on a connection is not reported 馃

2 participants