Uploaded image for project: 'The AndroMDA project'
  1. The AndroMDA project
  2. ANDROMDA-1521

The MetafacadeFactory should take into account inheritance when constructing metafacades

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0-RC1
    • Fix Version/s: 3.0-RC2
    • Component/s: None
    • Labels:
      None

      Description

      Current metafacade mappings are only based on meta object class name, and if one can't be found, then the default metafacade implementation is used (i.e. ModelElementFacade), this causes class cast exceptions for elements that may extend from a mapped meta object but aren't mapped themselves (i.e. not in the andromda-metafacades.xml). When constructing metafacades, we should check to see if there is a mapping specifically for that meta object class and if not go up the inheritance tree of the meta object to get the parent and check if the parent meta object class is mapped, and if so construct that metafacade, this would avoid errors like class cast exceptions when a super meta object isn't mapped and it doesn't need to be.

        Attachments

          Activity

            People

            • Assignee:
              overheat overheat
              Reporter:
              chad Chad Brandon
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: