Details
Description
Currently, for the scanner, if a connection is opened, we generate a connection indication towards the host application.
In this indication, we give the CC object instance as the consumption path. All other paths (production and config) is set to zero. This is bullshit of course.
We should properly specify the involved assembly instances in the production and consumption path. We may consider to give the CC instance attribute 10 as configuration path, to still allow the host to map between the indication and the corresponding CC instance, but this then needs to be documented thoroughly, since it is a deviation from the adapter's behavior.