Stripes

Autoload code doesn't recognize TypeConverters that extend other TypeConverters

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: Release 1.5
  • Fix Version/s: Release 1.5.1, Release 1.6
  • Component/s: None
  • Labels:
    None

Description

The autoload code looks for type params only on the class itself and does not look at superclasses.

Activity

Hide
Ben Gunter added a comment - 22/May/08 2:16 PM

Until this is fixed, @TargetType can be used as a workaround.

Show
Ben Gunter added a comment - 22/May/08 2:16 PM Until this is fixed, @TargetType can be used as a workaround.
Hide
Ben Gunter added a comment - 22/Oct/08 11:44 AM

Fixed fo 1.5.1 and later. ReflectUtil.getActualTypeArguments() was only examining superclasses if the target type was not an interface. This caused the search to come up empty, for example, when one extends an existing type converter or formatter, where the type parameter is defined in the superclass. I just pulled the loop that adds superclasses to the search list out of an else block so that it always executes.

Show
Ben Gunter added a comment - 22/Oct/08 11:44 AM Fixed fo 1.5.1 and later. ReflectUtil.getActualTypeArguments() was only examining superclasses if the target type was not an interface. This caused the search to come up empty, for example, when one extends an existing type converter or formatter, where the type parameter is defined in the superclass. I just pulled the loop that adds superclasses to the search list out of an else block so that it always executes.

People

Vote (0)
Watch (0)

Dates

  • Created:
    22/May/08 2:10 PM
    Updated:
    04/Jan/11 2:38 PM
    Resolved:
    22/Oct/08 11:44 AM