Well, after some more investigation, I realized that Implementation
interface extends ComponentType interface, so the change I proposed
wouldn't solve the issue.
I'm modifying the componentTypeModelResolver to support resolving
componentType side files following the java import/export as
We have multiple tuscany extensions (implementation types) that has
it's Implementation implemented by extending componentType in order to
re-use some common code. During resolve phase, we have code in
ExtensibleModelResolver to find the proper resolver based on the
interfaces of the
