tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Andreou (JIRA)" <...@tapestry.apache.org>
Subject [jira] Resolved: (TAPESTRY-2581) Non-existent .jwc file causes confusing error message "Could not parse specification null."
Date Sun, 08 Nov 2009 01:14:32 GMT

     [ https://issues.apache.org/jira/browse/TAPESTRY-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Andreou resolved TAPESTRY-2581.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.1.7

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


Mime
View raw message