Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-12812

Fix error log in Runtime Beans when no corresponding supertype is found

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • None
    • site-toolkit
    • None
    • Pulsar
    • Platform 222 - 14.0 Hangover, Platform 223 - 2019 Follow-up, Pulsar 234 - ContentSearch Fin

    Description

      Setting the parent bean of a Runtime Bean happens in 2 ways.

      1) If the generated Runtime Bean has a supertype which is created in the same namespace, then this supertype is used as parent bean (if there are more than 1 supertypes which are created in the same namespace, than the first one is used).

      2) If the generated RuntimeBean has no supertype which is created in the same namespace, then hippo:document, hippo:compound and hippogallery:imageset types are searched in the supertypes list. If any of them found, then it is used as supertype. If none of them is found, then an error is logged and the parent bean is set as null.

      This logic should be improved to support other possible supertypes.

      Attachments

        1. extendedHippoMirror.yaml
          2 kB
        2. extendedThirdPartyType.yaml
          3 kB
        3. main.yaml
          0.2 kB
        4. myproject.cnd
          0.9 kB
        5. myproject.yaml
          0.2 kB
        6. newsdocument.yaml
          7 kB
        7. thirdparty.cnd
          0.2 kB
        8. thirdPartyType.yaml
          2 kB
        9. thirdparty.yaml
          0.1 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ekarakus Erdem Karakus
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: