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

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.1.5
• Fix Version/s: 4.1.7
• Component/s: tapestry-core
• Assignee: Andreas Andreou
• Reporter: Albert Tumanov
• Created: 13/Aug/08 11:53
• Updated: 19/Nov/09 04:40
• Resolved: 08/Nov/09 01:13

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.)