Please report new issues athttps://github.com/DOCGroup
Common Object Request Broker Architecture (CORBA) Specification, Version 3.3 Part 3: CORBA Component Model 15.3.1 Component If a CCM home or component supports an interface, their ComponentInterfaceDescription has a special port named “supports” that can be used in connections for any of the “supported” interfaces. If, in an assembly, a connection is to be provided by any of the component’s or home’s supported interfaces, then the port name of the ComponentExternalPortEndpoint or SubcomponentPortEndpoint class is “supports.” For CCM homes, this port also provides their equivalent interface. The “supports” port for CCM components does not provide the equivalent interface, since this would be problematic for assembly implementations of components.
Created attachment 1440 [details] fix it myself. Seems to work fine
Can you provide an automated unit test as reproducer, see CIAO/tests/DAnCE/ExecutionManager-Deployments for tests that could be used as starting point. I would advice not to depend heavily on supports if possible, it is very likely that a future component model doesn't support this at all.
Another option would be to handle this in the servant as port name, something to look at when we have an automated reproducer
Created attachment 1442 [details] autotest -- cd $CIAO_ROOT/tests/DAnCE && tar xzf test.tgz [jw@cool ExecutionManager-Deployments]$ ./run_test.pl SimpleSuportsConnection.cdp Starting test for deployment SimpleSuportsConnection.cdp Starting Naming Service Invoking node daemon Run node daemon Run node daemon Invoking execution manager Invoking executor - launch the application - SimpleSupports_exec_i::hello - Got the following information from trig port: Test successful; hello from SimpleUser. Teardown the application Executor finished. $ tar czf test.tgz Components/SimpleSupports.idl Components/SimpleSupports.mpc Components/SimpleSupports_exec.h Components/SimpleSupports_exec.cpp ExecutionManager-Deployments/SimpleSuportsConnection.cdp