You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@wicket.apache.org by Ephraim Rosenfeld <er...@knoa.com> on 2015/10/01 20:26:15 UTC

RE: placeholder causes the BaseWicketTester#startComponentInPage to fail

Hello Martin:

I created the following ticket: https://issues.apache.org/jira/browse/WICKET-5989

Thank you,

- Ephraim

-----Original Message-----
From: Martin Grigorov [mailto:mgrigorov@apache.org] 
Sent: Wednesday, September 30, 2015 5:45 PM
To: users@wicket.apache.org
Subject: Re: <wicket:header-items/> placeholder causes the BaseWicketTester#startComponentInPage to fail

Hi,

Please create a quickstart app with 6.20.0 and attach it to a ticket in JIRA.
Thanks!

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Wed, Sep 30, 2015 at 11:37 PM, Ephraim Rosenfeld <er...@knoa.com>
wrote:

> Hello Wicket Team:
>
> After adding the <wicket:header-items/> placeholder to the <head> tag 
> of my base web page, my unit tests fails when the 
> BaseWicketTester#startComponentInPage is called, with the following message:
> Error while parsing the markup for the autogenerated page: More than 
> one <wicket:header-items/> detected in the <head> element. Only one is allowed.
>
> I am overriding the BaseWicketTester#createPageMarkup to return the 
> markup of a dummy page that extends my base page w/ the 
> <wicket:header-items/> placeholder.
>
> When I put a break-point in the test, I see that the String returned 
> from the BaseWicketTester#createPageMarkup test method makes the 
> placeholder a non-emtpy tag, i.e. 
> "<wicket:header-items></wicket:header-items>" instead of "<wicket:header-items/>", although that may not matter.
>
> I am using Wicket version 6.15.0.
>
> Any idea as to why this is happening would greatly be appreciated.
>
> Thank you,
>
> - Ephraim
>