Uploaded image for project: 'Hippo Site Toolkit 2'
  1. Hippo Site Toolkit 2
  2. HSTTWO-4619

Wrong HippoCompound type check in runtime beans would result in a wrong behaviour

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 13.2.2, 13.3.0
    • Component/s: None
    • Labels:
      None
    • Similar issues:
    • Processed by team:
      Platform
    • Sprint:
      Platform 211 Eng OKRs

      Description

      Class type check in runtime beans to test whether a class is an instance of HippoCompound or not would result in a wrong behaviour if a content bean is inherited from another content bean. It should be fixed by doing the correct check.

       

       

          private Class<?> getDelegateeClass(final String superMethodName) {
              if (METHOD_GET_HIPPO_HTML.equals(superMethodName)) {
                  if (HippoCompound.class.isAssignableFrom(parentBean)) {
                      return HippoCompound.class;
                  } else {
                      return HippoDocument.class;
                  }
              } else {
                  return HippoBean.class;
              }
          }
      

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ekarakus Erdem Karakus
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: