Type constraining a criteria beyond the definition of a component is not allowed unless it is type constrained to the same ...

Type constraining a criteria beyond the definition of a component is not allowed unless 
it is type constrained to the same class for all properties.
This criteria constrains the component that uses the relationship {0} beyond the scope of its definition. The path
in the component targets {1} as the end point.All properties in the criteria that are targeted to this 
component must target class {1} with or without using a type constraint. If they target a class 
different from {1}, they must still target 
one single class for all properties. If you have one or more abstract classes in the criteria that are
type constrained and some that are not, consider applying the same type constraint to all. Please refer to the documentation for more details.