[
https://issues.apache.org/jira/browse/WICKET-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-1657.
-----------------------------------
Resolution: Won't Fix
Fix Version/s: 1.4-M3
Assignee: Igor Vaynberg
ive tweaked the message a little bit.
this of course IS an error. the problem is not that "bar" wicket id of fragment
was not found, but that you used "foo" instead of the id provided by the
componetId argument
> AjaxFallbackDefaultDataTable gives misleading error when fragment markup
> cannot be found
> ----------------------------------------------------------------------------------------
>
> Key: WICKET-1657
> URL: https://issues.apache.org/jira/browse/WICKET-1657
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-extensions
> Affects Versions: 1.3.0-final
> Reporter: Nick Johnson
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4-M3
>
>
> If you call cellItem.add(new Fragment("foo","bar", myPage, model), but the
> fragment markup for "bar" isn't found in the markup for myPage,
> AjaxFallbackDefaultDataTable complains, "failed to add a
> component with id [cell] to the provided [cellItem] object." The error
> suggests making sure that cellItem.add was called.
> This error can be misleading, especially since cellItem.add was called. What
> really happened was the fragment with a given ID wasn't found, which should
> really have been an error in its own right.
> It would be nice if the error message gave a better description indicating
> the reason why the component failed to add (e.g., an error in handling the
> Fragment).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
