Uploaded image for project: 'Isis'
  1. Isis
  2. ISIS-236

Classes that are not referenced in the DOM aren't found by the specification loader

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: core-1.0.0
    • Fix Version/s: core-1.3.0
    • Component/s: Core
    • Labels:
      None

      Description

      For example: if you have a field that uses an interface (eg Address) and it returns a concrete type (eg EmailAddress) but that type is not explicitly referred to elsewhere (as a return type or parameter) then the SpecificationLoader will never see it. Hence, if that class gets used (eg an EmailAddress is retrieved from persistent memory) then an exception will occur.

      The best long term solution is to load all classes from the Jar(s) that contain the DOM code. This could be indicated by placing a marker, such as a file, in the metadata.of the Jar.

      In the meantime a simple workaround is to add a method, typically to a service, that uses the concrete class and mark it as hidden. Give the method a name that makes it clear what the method is there for so nobody tries to use it.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                rmatthews Robert Matthews
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: