Add constraint to check whether mapped elements are available
Issue #354
new
Just like the check for return type and parameter types, there should be a constraint that ensures that mapped classes are (still) available. This includes classes from extended aspects etc.
For example, if a user creates a mapping and later deletes a class that is mapped, an error will occur during saving.