Re: ExternalLink.setOutputMarkupId has no effect

[Nick Busey <nb...@me.dium.com>]

I am seeing something similar with WebMarkupContainer. I had to add
'super.onComponentTag(tag);' as the last line of my implementation of
onComponentTag as well to fix this problem. Wicket 1.3



Johannes Fahrenkrug wrote:
> 
> Hi,
> 
> I ran into something concerning ExternalLink and setOutputMarkupId.
> ExternalLink.setOutputMarkupId(true) has no effect.
> I could track this issue down to super.onComponentTag not being called 
> at the end of ExternalLink's onComponentTag.
> 
> Adding
> super.onComponentTag(tag);
> to the end of ExternalLink's onComponentTag would call Component's 
> onComponentTag which in turn would add the markup id.
> 
> Should I open a bug report for this? (I'm using 1.2.6, but I just 
> checked the version in trunk and it seems to have the same problem, 
> although I didn't try it)
> 
> - Johannes
> 
> -- 
> 
>    Johannes Fahrenkrug
>    Tel:    +49 (0)431 5446 246
>    Fax:    +49 (0)431 5446 248
>    E-Mail: jfa@gebeco.de
> 
>    Gebeco GmbH & Co KG
>    Holzkoppelweg 19
>    D-24118 Kiel
> 
>    Handelsregister Kiel Nr. A 3964
>    Steuernummer: 19 285 65407
> 
>    Geschaeftsfuehrung:
>    Ury Steinweg, Vorsitzender der Geschaeftsfuehrung
>    Thomas Bohlander
> 
>    Besuchen Sie uns auch unter / we are also available at:
>    www.gebeco.de oder www.drtigges.de 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/ExternalLink.setOutputMarkupId-has-no-effect-tf3882522.html#a13216236
Sent from the Wicket - Dev mailing list archive at Nabble.com.