This bug was detected inside Capella but is probably not limited to Capella.
For instance the following service can't be resolved if it's in the workspace:
public static String test(CapellaElement capellaElement) {
return "OK";
}
This has probably something to do with the class path and/or the different classloader used to load the service and the model.
As a workaround, one can create a plug-in project with his template and service class, use the template registry extension point. Then start a runtime with the input model and create a .genconf file and use the "Browse registry" button to select the template. You can find more details in this discussion.
This bug was detected inside Capella but is probably not limited to Capella.
For instance the following service can't be resolved if it's in the workspace:
This has probably something to do with the class path and/or the different classloader used to load the service and the model.
As a workaround, one can create a plug-in project with his template and service class, use the template registry extension point. Then start a runtime with the input model and create a .genconf file and use the "Browse registry" button to select the template. You can find more details in this discussion.