[jira] Resolved: (WICKET-1829) MarkupComponentBorder skips first tag in MarkupStream

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

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

Igor Vaynberg resolved WICKET-1829.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4-M4
                   1.3.5
         Assignee: Igor Vaynberg

> MarkupComponentBorder skips first tag in MarkupStream
> -----------------------------------------------------
>
>                 Key: WICKET-1829
>                 URL: https://issues.apache.org/jira/browse/WICKET-1829
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.4
>            Reporter: Scott MacKenzie
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.3.5, 1.4-M4
>
>
> If there is no leading markup in a MarkupComponentBorder before the <wicket:border/> tag, the following error will occur:
> Unexpected tag encountered in markup of component border TestComponentBorder. Tag: <wicket:body/>, expected tag: <wicket:border>
> Steps to reproduce:
> Create a ComponentBorder with no leading markup before <wicket:border/>:
> TestComponentBorder.html
> --------------------------------------
> <wicket:border>
> 	<div class="input">
> 		<wicket:body/>
> 	</div>
> </wicket:border>
> TestComponentBorder.java
> --------------------------------------
> public class TestComponentBorder extends MarkupComponentBorder
> {
> }
> This happens because the rendering loop calls stream.next(); when it starts, always skipping the first element.  It should call stream.get() before the loop, then stream.next() at the end.

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