Uploaded image for project: 'Identity Provider'
  1. Identity Provider
  2. IDP-1482

Spring context reloads failing on parent beans property type conversions

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0, 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.2.1, 3.3.0, 3.3.1, 3.4.0, 3.3.2, 3.3.3, 3.4.1, 3.4.2, 3.4.3, 3.4.4, 4.0.0
    • Fix Version/s: None
    • Component/s: Configuration
    • Labels:
      None

      Description

      There's some kind of Spring bug that manifests by failing to properly track the state of bean properties internally when there are property type conversions involved (which is most of the time of course).

      When a parent bean is used to define new child beans in two different reloadable service contexts (e.g. the filter and resolver, doesn't matter which ones), things seem to work. But if one of the service contexts directly references a parent bean to inject it into something else, that seems to corrupt the state of the parent bean.

      A later reload of the other context with the child bean in it fails because it ends up with unconverted property values pulled in from the parent bean but without the properties marked as needing conversion, and it causes Spring to attempt to set the property values without converting them, and you get type mismatch errors.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            cantor.2@osu.edu Scott Cantor
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated: