You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Szádeczky-Kardoss Szabolcs (JIRA)" <ji...@apache.org> on 2010/11/09 12:27:06 UTC

[jira] Commented: (WICKET-3122) MarkupNotFoundException happens if there's a component inside another with wicket:message attribute

    [ https://issues.apache.org/jira/browse/WICKET-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930098#action_12930098 ] 

Szádeczky-Kardoss Szabolcs commented on WICKET-3122:
----------------------------------------------------

I have migrated over to 1.5-M3, and this issue seems to be fixed. Thanks.

> MarkupNotFoundException happens if there's a component inside another with wicket:message attribute
> ---------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-3122
>                 URL: https://issues.apache.org/jira/browse/WICKET-3122
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5-M2.1
>            Reporter: Szádeczky-Kardoss Szabolcs
>            Assignee: Igor Vaynberg
>            Priority: Minor
>
> Hi,
> I am just in the process of migrating my project to 1.5(-M2.1), and discovered a problem when there's a markup like this:
> <span wicket:message="title:favoriteCount.tip"><wicket:message key="favoriteCount">FAVORITE COUNT</wicket:message><span wicket:id="favoriteCount" /></span>
> and Java file like this:
>         add(new Label("favoriteCount"));
> and appropriate resource file(s) of course,
> then at render time a MarkupNotFoundException is given (Markup not found for Component: [Component id = favoriteCount]). If I remove the wicket:message="title:favoriteCount.tip" part then it is fine, similar to 1.4.x.
> Another small note on issue 2776: I am not sure that reopening it was a good approach but the fix for that one disappeared for 1.5-M2.1. Could you please check that one too? 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.