Uploaded image for project: 'Groovy'
  1. Groovy
  2. GROOVY-3142

Unable to access inherited private fields from a closure within an inherited method

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 5.0.0-alpha-1
    • groovy-runtime
    • None

    Description

      class B {
    String data
    B(arg) {
        arg.each() { this.@data = it }
    }
}
class C extends B {
    C(arg) {
        super(arg)
    }
}
new C(["test"])

      The previous unexpectedly produce: Exception thrown: groovy.lang.MissingFieldException: No such field: data for class: C

      class B {
    private String data
    public String getData() { this.@data }
    private setData(String value) { this.@data = value }
    B(arg) {
        arg.each() { data = it }
    }
}
class C extends B {
    C(arg) {
        super(arg)
    }
}

new C(["test"])

      And this one produce a similar issue: Exception thrown: groovy.lang.ReadOnlyPropertyException: Cannot set readonly property: data for class: C

      Both is related to the fact that the closure is routed throught C and not B which is the expectation. In the second sample, providing a protected setter is a workaround.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. GROOVY-4083 private members should be accessible in closures used from sub classes

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. GROOVY-4084 Private class property not visible from closure in a super. invoked method

          • Major - Major loss of function.
          • Closed
          is related to

          Sub-task - The sub-task of the issue GROOVY-3073 Private inheritance bug: Closure accessing private method

          • Major - Major loss of function.
          • Closed

          Sub-task - The sub-task of the issue GROOVY-5438 Private field inaccessible in closure when using a subclass

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Task - A task that needs to be done. GROOVY-3010 fix private field visibility

          • Major - Major loss of function.
          • Open

          Activity

            People

              emilles Eric Milles
              softec Denis Gervalle
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: