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

Kevin Menard closed TAPESTRY-1978.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.11

I was able to convey the location information by wrapping up in a custom 
Tapestry exception.  I avoided an interface change by using the "description" 
parameter to my advantage.  Since it's largely an open-ended value describing 
the binding, I confined it in my case to the actual parameter name.  I couldn't 
find any place that this narrowing meaning would affect and all existing tests 
pass, so I'm going with it.  If it turns out we need to actually split the 
description from the parameter name, we can do it when it becomes an actual 
problem.

> When supplying an empty parameter binding, indicate problem parameter in 
> error message.
> ---------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1978
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1978
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 5.0.7
>            Reporter: Kevin Menard
>            Assignee: Kevin Menard
>            Priority: Minor
>             Fix For: 5.0.11
>
>
> While prototyping a page recently, I decided to hold off on passing in 
> parameters until I had a good sense of what their names should be.  So, I had 
> something similar to:
> <t:textfield value=""/>
> Clearly this is a broken construct and Tapestry generally recognized it.  I 
> was greeted with the following error message:
> "Parameter expression was null or contained only whitespace."
> And a highlighted block of my template.  Unfortunately, the highlighted block 
> is not where the problem was.  Likewise, the error message really didn't 
> indicate what parameter was broken of what component.  After a little bit of 
> guess-and-check, I caught the obvious error.  It'd be nice if Tapestry 
> handled this for me though.

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

Reply via email to