Tapestry 5
  1. Tapestry 5
  2. TAP5-715

TypeCoercer.explain incorrectly reports the plan to coerce from primitive types to wrapper types

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.5
    • Fix Version/s: 5.2.0
    • Component/s: tapestry-ioc
    • Labels:
      None

      Description

      I checked 2 cases:

      typeCoercer.explain(boolean.class, Boolean.class)
      returns
      Object --> String, String --> Boolean

      typeCoercer.explain(int.class, Integer.class)
      returns
      Number --> Long, Long --> Integer

      Strange.
      Shouldn't TypeCoercer cast directly to wrapper classes?

        Activity

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Lukasz Jazgar
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development