Skip to content

mw/com: Remove SOME/IP configuration structs#406

Open
sahithi-nukala wants to merge 4 commits into
eclipse-score:mainfrom
sahithi-nukala:sah_remove_someip_config_structs
Open

mw/com: Remove SOME/IP configuration structs#406
sahithi-nukala wants to merge 4 commits into
eclipse-score:mainfrom
sahithi-nukala:sah_remove_someip_config_structs

Conversation

@sahithi-nukala
Copy link
Copy Markdown
Contributor

@sahithi-nukala sahithi-nukala commented May 11, 2026

  • Delete SomeIpServiceInstanceDeployment, SomeIpServiceInstanceId, SomeIpEventInstanceDeployment, and SomeIpFieldInstanceDeployment source files
  • Remove SOME/IP from BindingInformation variants in ServiceInstanceDeployment and ServiceInstanceId
  • Remove SOME/IP from the JSON config schema and config parser
  • Remove SOME/IP-related error codes from ConfigurationError
  • Remove SOME/IP visitor lambdas from all plumbing factory implementations
  • Update design and implementation documentation

Remove the placeholder SOME/IP configuration structs that were never
connected to a real transport implementation:
- SomeIpServiceInstanceDeployment
- SomeIpServiceInstanceId
- SomeIpEventInstanceDeployment
- SomeIpFieldInstanceDeployment
- Remove SOME/IP from BindingInformation variants in
  ServiceInstanceDeployment and ServiceInstanceId
- Remove SOME/IP binding type and error codes from config_parser,
  configuration_error, and mw_com_config_schema.json
- Fix operator== and operator< for blank binding in ServiceInstanceId
- Remove SOME/IP targets from BUILD
- Update tests and test helpers accordingly
- Remove SomeIpServiceInstanceDeployment visitor lambdas from all
  binding factory implementations
- Remove CreateSomeIpBindingInstanceIdentifier from test helper
- Remove SOME/IP typed test cases from all plumbing factory tests
- Remove SOME/IP visitor from GetServiceInstanceId in instance_identifier
instances.
What is **not** visible here: Whether `"abc/abc/TirePressurePort"` is a provided or required service instance. Both
could be possible, since we do support 1 to n mappings in both cases.
Here we have a mapping of `"abc/abc/TirePressurePort"` to two different concrete technical instances: The first one is a
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here (and only here) I would keep the SOME/IP part. Why, because it shows, which general flexibility we do foresee within our config. So keep the old text - maybe with a slight adaption:

SOME/IP based instance (so ...

hypothetic SOME/IP based instance (so ...

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

- Remove SOME/IP from supported bindings lists in README files
- Update example configurations to use SHM-only binding
- Remove SomeIpServiceInstanceDeployment from structural_view.puml
@sahithi-nukala sahithi-nukala force-pushed the sah_remove_someip_config_structs branch from 374e0b3 to 4a16710 Compare May 13, 2026 18:05
@sahithi-nukala sahithi-nukala requested a review from crimson11 May 13, 2026 18:07
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.

2 participants