Tapestry 5
  1. Tapestry 5
  2. TAP5-1188

Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.2.1
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      As currently implemented, live class reloading only takes into account the service implementation class (plus any inner classes of the implemention class). If the implementation class extends from a base class, the base class is not scanned for changes, and is not reloaded when it (or the actual implementation class) changes.

        Issue Links

          Activity

          Howard M. Lewis Ship created issue -
          Howard M. Lewis Ship made changes -
          Field Original Value New Value
          Link This issue relates to TAP5-1233 [ TAP5-1233 ]
          Howard M. Lewis Ship made changes -
          Assignee Howard M. Lewis Ship [ hlship ]
          Howard M. Lewis Ship made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Howard M. Lewis Ship made changes -
          Status In Progress [ 3 ] Closed [ 6 ]
          Fix Version/s 5.2.1 [ 12315230 ]
          Resolution Fixed [ 1 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development