Uploaded image for project: 'Hibernate Search'
  1. HSEARCH-2759

Handle private/protected field access for @Spatial fields

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: None
    • Fix versions: 6.0.0.Alpha1
    • Components: spatial
    • Labels:
      None

      Description

      Currently, the bean properties used in @Spatial fields must either be public or have a public getter, while other, more standard fields don't have this limitation (we use setAccessible() as necessary).

      That's because we don't use the same techniques to access fields in SpatialFieldBridge as we do everywhere else.

      We should try to add a way to get the location from private/protected fields, but this will require breaking APIs (yes, the SpatialFieldBridge class is API...).

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                yrodiere Yoann Rodière
                Reporter:
                yrodiere Yoann Rodière
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: