You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Albert Tumanov (JIRA)" <de...@tapestry.apache.org> on 2008/08/13 13:54:44 UTC

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

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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

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

Posted by "Albert Tumanov (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Albert Tumanov updated TAPESTRY-2581:
-------------------------------------

    Attachment: myapp.tar.gz

Test case (based on minimal myapp application)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org