Non-existent .jwc file causes confusing error message "Could not parse
specification null."
-------------------------------------------------------------------------------------------
Key: TAPESTRY-2581
URL: https://issues.apache.org/jira/browse/TAPESTRY-2581
Project: Tapestry
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 4.1.5
Reporter: Albert Tumanov
Priority: Minor
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.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
