You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2012/06/15 10:44:42 UTC
[jira] [Commented] (WICKET-4589) Closing tag is
incorrectly setup as autocomponent
[ https://issues.apache.org/jira/browse/WICKET-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295533#comment-13295533 ]
Martin Grigorov commented on WICKET-4589:
-----------------------------------------
Does this cause troubles ?
Because WicketTagIdentifier has a comment saying:
// Make it a Wicket component. Otherwise it would be RawMarkup
Without making it a (auto)component later the MarkupStream cannot find the closing tag.
@Juergen: do you see a problem here ?
> Closing </wicket:container> tag is incorrectly setup as autocomponent
> ---------------------------------------------------------------------
>
> Key: WICKET-4589
> URL: https://issues.apache.org/jira/browse/WICKET-4589
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.0.0-beta2, 1.5.7
> Reporter: Christian Oldiges
> Priority: Minor
>
> The closing instance of the <wicket:container> tag returns true when isAutoComponentTag() is called whereas the opening instance correctly returns false.
> The problem lies probably in the WicketTagIdentifier class which simply checks if there is a wicket:id attribute value and makes all tags (opening or closing) autocomponent tags if there is no wicket:id.
> Obviously any closing tag doesnt have a wicket:id assigned.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira