COA requires compiled interaction/object classes on the classpath for anything that gets injected into the federation. As part of the code restructure, we eliminated the java-base directory as well as the dependency on the java-base directory from the deployment exporter pom.xml. If you try to use a COA action, I expect there is some type of runtime exception related to class not found.
The deployment exporter needs to generate a src/ directory with Java code for all the interaction/object classes required by COA. It should not pull in a dependency from the federates exporter output because that solution has always been silly.
COA requires compiled interaction/object classes on the classpath for anything that gets injected into the federation. As part of the code restructure, we eliminated the java-base directory as well as the dependency on the java-base directory from the deployment exporter pom.xml. If you try to use a COA action, I expect there is some type of runtime exception related to class not found.
The deployment exporter needs to generate a src/ directory with Java code for all the interaction/object classes required by COA. It should not pull in a dependency from the federates exporter output because that solution has always been silly.