Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-2738

@Cached should throw a more sensible exception if field is missing

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 5.8.1
    • None
    • tapestry-core
    • None

    Description

      The value of the annotation is String-based and therefore error-prone, especially during refactoring, etc.

      Currently, the thrown exception is only saying that a field is missing, and the CachedWorker is only visible in the Stacktrace.

      I suggest the worker should catch the exception/missing binding, and rethrow with a better message.

      Attachments

        Activity

          People

            ben-ng Ben Weidig
            ben-ng Ben Weidig
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: