[
https://issues.apache.org/jira/browse/TAPESTRY-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569445#action_12569445
]
Howard M. Lewis Ship commented on TAPESTRY-1978:
------------------------------------------------
There's no essential reason to use Defense.notBlank() if a more custom error
message would be more useable. I'm just surprised that a blank expression
could make it that far; i.e., I'd expect an earlier check, before we invoke
BindingSource.
> When passing in empty parameter, 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
> Priority: Minor
>
> 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]
