You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Bille Jensen (JIRA)" <ji...@apache.org> on 2008/11/02 12:27:44 UTC

[jira] Updated: (WICKET-1657) AjaxFallbackDefaultDataTable gives misleading error when fragment markup cannot be found

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

Frank Bille Jensen updated WICKET-1657:
---------------------------------------

    Fix Version/s:     (was: 1.4-M3)

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