Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-2581

Non-existent .jwc file causes confusing error message "Could not parse specification null."

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 4.1.5
    • Fix Version/s: 4.1.7
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      When a non-existent .jwc file is mistakenly referenced from app.application,
      the exception message is quite confusing:

      "Could not parse specification null."

      I propose to change it to something like "The YourComponent.jwc file not found".

      (The real case when the problem arises is when you replace your existing .jwc files with annotation-based configuration
      BUT forget to change app.application.)

        Attachments

        1. myapp.tar.gz
          14 kB
          Albert Tumanov

          Activity

            People

            • Assignee:
              andyhot Andreas Andreou
              Reporter:
              altumano Albert Tumanov
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: