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

Alexander Morozov updated WICKET-3448:
--------------------------------------

    Description: 
I found very odd Wicket behavior in case then user tries to update by Ajax a 
panel "wrapped" by not trivial border component (see quickstart - 
HomePage.html).
There are no troubles with Ajax update with no border and with BoxBorder (check 
HomePageTest#testAjaxPanelRefresh_NoBorder, 
HomePageTest#testAjaxPanelRefresh_BoxBorder).
But if I create more complex border component like this:
    <wicket:border>
      <div class="b1" wicket:id="border">
        <div class="b2" wicket:id="border">
          <div class="b3" wicket:id="border">
            <div class="test-content">
              <wicket:body/>
            </div>
          </div>
        </div>
      </div>
    </wicket:border>
, I got the exception "MarkupException: close tag not found"  (see 
HomePageTest#testAjaxPanelRefresh_MyBorder1).

If I remove one nested block "<div class="b3" wicket:id="border">" from the 
markup and Java - test passed (see HomePageTest#testAjaxPanelRefresh_MyBorder2).

For now, I haven't found the cause of the issue, hence I can't provider a patch.

Thank you

  was:
I found very odd Wicket behavior in case then user tries to update by Ajax a 
panel "wrapped" by not trivial border component (see quickstart - 
HomePage.html).
There are no troubles with Ajax update with no border and with BoxBorder (check 
HomePageTest#testAjaxPanelRefresh_NoBorder, 
HomePageTest#testAjaxPanelRefresh_BoxBorder).
But if I create more complex border component like above:
    <wicket:border>
      <div class="b1" wicket:id="border">
        <div class="b2" wicket:id="border">
          <div class="b3" wicket:id="border">
            <div class="test-content">
              <wicket:body/>
            </div>
          </div>
        </div>
      </div>
    </wicket:border>
, I got the exception "MarkupException: close tag not found"  (see 
HomePageTest#testAjaxPanelRefresh_MyBorder1).

If I remove one nested block "<div class="b3" wicket:id="border">" from the 
markup and Java - test passed (see HomePageTest#testAjaxPanelRefresh_MyBorder2).

For now, I haven't found the cause of the issue, hence I can't provider a patch.

Thank you


> MarkupException: close tag not found - after ajax update
> --------------------------------------------------------
>
>                 Key: WICKET-3448
>                 URL: https://issues.apache.org/jira/browse/WICKET-3448
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.15
>         Environment: Win7_x64, JDK 1.6u23_x64
>            Reporter: Alexander Morozov
>         Attachments: wicket-1.4.15-quickstart.7z
>
>
> I found very odd Wicket behavior in case then user tries to update by Ajax a 
> panel "wrapped" by not trivial border component (see quickstart - 
> HomePage.html).
> There are no troubles with Ajax update with no border and with BoxBorder 
> (check HomePageTest#testAjaxPanelRefresh_NoBorder, 
> HomePageTest#testAjaxPanelRefresh_BoxBorder).
> But if I create more complex border component like this:
>     <wicket:border>
>       <div class="b1" wicket:id="border">
>         <div class="b2" wicket:id="border">
>           <div class="b3" wicket:id="border">
>             <div class="test-content">
>               <wicket:body/>
>             </div>
>           </div>
>         </div>
>       </div>
>     </wicket:border>
> , I got the exception "MarkupException: close tag not found"  (see 
> HomePageTest#testAjaxPanelRefresh_MyBorder1).
> If I remove one nested block "<div class="b3" wicket:id="border">" from the 
> markup and Java - test passed (see 
> HomePageTest#testAjaxPanelRefresh_MyBorder2).
> For now, I haven't found the cause of the issue, hence I can't provider a 
> patch.
> Thank you

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to