[
https://issues.apache.org/jira/browse/TAPESTRY-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779823#action_12779823
]
Hudson commented on TAPESTRY-2581:
----------------------------------
Integrated in tapestry-4.1-trunk #11 (See
[http://hudson.zones.apache.org/hudson/job/tapestry-4.1-trunk/11/])
> 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
> Assignee: Andreas Andreou
> Priority: Minor
> Fix For: 4.1.7
>
> Attachments: myapp.tar.gz
>
>
> 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.
