You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Victor Ott (JIRA)" <ji...@apache.org> on 2009/10/20 15:41:59 UTC
[jira] Commented: (WICKET-2527) wicket:enclosure child attribute
search path has changed
[ https://issues.apache.org/jira/browse/WICKET-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767809#action_12767809 ]
Victor Ott commented on WICKET-2527:
------------------------------------
I updated to 1.4.2 today and got struck by this issue in same constellation. Nevertheless, I couldn't reproduce the suggested workaround. In fact this issue might be a duplicate of WICKET-2513.
My constellation (simplified):
<wicket:enclosure child="savingsCell">
<tr>
<td class="centerBold">
<wicket:message key="key1">[Savings]</wicket:message>
</td>
<td wicket:id="savingsCell">
[...etc]
</td>
</tr>
<wicket:enclosure>
Debugging through Wicket source showed that Enclosure.ensureAllChildrenPresent() failed to retrieve the component for the <wicket:message...> tag (it has always the id "_message").
My workaround: replaced the <wicket:message...> tag with a label.
PS
As I see now, this should be already fixed since revision 821982 (Mon Oct 5 19:35:59 2009 UTC) of .../internal/Enclosure.java, which obviously didn't make it in 1.4.2, although 1.4.2 was announced on 9th of october.
> wicket:enclosure child attribute search path has changed
> --------------------------------------------------------
>
> Key: WICKET-2527
> URL: https://issues.apache.org/jira/browse/WICKET-2527
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.2
> Environment: project with created with archetype, only HomePage.html and HomePage.properties modified
> Reporter: Mikko Tiihonen
> Assignee: Juergen Donnerstag
> Fix For: 1.4.3
>
> Attachments: myproject.zip
>
>
> <wicket:enclosure child="id"> has changed in how it interprets nested elements. Now elements on the same depth as the wanted child must be also explicitly listed in the child attribute.
> example based on the HelloPage.html of the archetype:
> This worked in wicket 1.4.1:
> <wicket:enclosure child="message">
> <ud>
> <li><wicket:message key="text">header</wicket:message></li>
> <li wicket:id="message">message will be here</li>
> </ud>
> </wicket:enclosure>
> In wicket 1.4.2 the following is needed instead:
> <wicket:enclosure child="text:message">
> <ud>
> <li><wicket:message key="text">header</wicket:message></li>
> <li wicket:id="message">message will be here</li>
> </ud>
> </wicket:enclosure>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.