Tapestry
  1. Tapestry
  2. TAPESTRY-2581

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

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor 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.)

      1. myapp.tar.gz
        14 kB
        Albert Tumanov

        Activity

        Hide
        Albert Tumanov added a comment -

        Test case (based on minimal myapp application)

        Show
        Albert Tumanov added a comment - Test case (based on minimal myapp application)
        Hide
        Hudson added a comment -

        Integrated in tapestry-4.1-trunk #11 (See http://hudson.zones.apache.org/hudson/job/tapestry-4.1-trunk/11/)

        Show
        Hudson added a comment - Integrated in tapestry-4.1-trunk #11 (See http://hudson.zones.apache.org/hudson/job/tapestry-4.1-trunk/11/ )

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development