You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Antoine Angénieux <aa...@clinigrid.com> on 2007/11/27 12:25:29 UTC
wicket:enclosure bug when parent is a non transperent border in current
trunk version ?
Hi guys,
I'm using the latest trunk version. I have a border (non transparent) in
which portions of markup are made visible / invisible by the use of the
wicket enclosure tag. Here is an example markup :
<!-- This is a non transparent border -->
<span wicket:id="actionsBorder">
<wicket:enclosure child="newLink">
<div class="action">
<a wicket:id="newLink"><img wicket:id="newButton" /></a>
</div>
</wicket:enclosure>
</span>
And I always get an exception in the Enclosure
getChildComponent(CharSequence childId).
I investigated that method a bit, and when looking up for the component
whild id childId in the enclosure parent (thus the
Border.BorderBodyContainer component), the only child visited is... the
Enclosure element!
Then, a MarkupException is thrown by the getComponentChild() method
(line 136) complaining that it could not find my component...
I saw that the code dealing with transparent resolvers, and component
children types (arrays or single child) is rather "touchy" and did not
try to tweak it, as I feared it would cause more dammage than good ;)
I cannot tell you if this problem exists in other wicket versions, as I
rarely need the enclosure tag, and for those rare occasions, I
encountered no problem at all...
I've used a WebMarkupContainer on the div as a workaround, but since
that is exactly the purpose of the <wicket:enclosure /> tag, that's
juste too bad :D
Anybody else god bittent by this one?
Cheers,
Antoine.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicket:enclosure bug when parent is a non transperent border
in current trunk version ?
Posted by Antoine Angénieux <aa...@clinigrid.com>.
Hi Igor,
Igor Vaynberg a écrit :
> please add a jira ticket for this
Done !
https://issues.apache.org/jira/browse/WICKET-1188
Cheers,
Antoine.
>
> -igor
>
>
> On Nov 27, 2007 3:25 AM, Antoine Angénieux <aa...@clinigrid.com> wrote:
>> Hi guys,
>>
>> I'm using the latest trunk version. I have a border (non transparent) in
>> which portions of markup are made visible / invisible by the use of the
>> wicket enclosure tag. Here is an example markup :
>>
>> <!-- This is a non transparent border -->
>> <span wicket:id="actionsBorder">
>> <wicket:enclosure child="newLink">
>> <div class="action">
>> <a wicket:id="newLink"><img wicket:id="newButton" /></a>
>> </div>
>> </wicket:enclosure>
>> </span>
>>
>> And I always get an exception in the Enclosure
>> getChildComponent(CharSequence childId).
>>
>> I investigated that method a bit, and when looking up for the component
>> whild id childId in the enclosure parent (thus the
>> Border.BorderBodyContainer component), the only child visited is... the
>> Enclosure element!
>>
>> Then, a MarkupException is thrown by the getComponentChild() method
>> (line 136) complaining that it could not find my component...
>>
>> I saw that the code dealing with transparent resolvers, and component
>> children types (arrays or single child) is rather "touchy" and did not
>> try to tweak it, as I feared it would cause more dammage than good ;)
>>
>> I cannot tell you if this problem exists in other wicket versions, as I
>> rarely need the enclosure tag, and for those rare occasions, I
>> encountered no problem at all...
>>
>> I've used a WebMarkupContainer on the div as a workaround, but since
>> that is exactly the purpose of the <wicket:enclosure /> tag, that's
>> juste too bad :D
>>
>> Anybody else god bittent by this one?
>>
>> Cheers,
>>
>> Antoine.
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicket:enclosure bug when parent is a non transperent border in current trunk version ?
Posted by Igor Vaynberg <ig...@gmail.com>.
please add a jira ticket for this
-igor
On Nov 27, 2007 3:25 AM, Antoine Angénieux <aa...@clinigrid.com> wrote:
> Hi guys,
>
> I'm using the latest trunk version. I have a border (non transparent) in
> which portions of markup are made visible / invisible by the use of the
> wicket enclosure tag. Here is an example markup :
>
> <!-- This is a non transparent border -->
> <span wicket:id="actionsBorder">
> <wicket:enclosure child="newLink">
> <div class="action">
> <a wicket:id="newLink"><img wicket:id="newButton" /></a>
> </div>
> </wicket:enclosure>
> </span>
>
> And I always get an exception in the Enclosure
> getChildComponent(CharSequence childId).
>
> I investigated that method a bit, and when looking up for the component
> whild id childId in the enclosure parent (thus the
> Border.BorderBodyContainer component), the only child visited is... the
> Enclosure element!
>
> Then, a MarkupException is thrown by the getComponentChild() method
> (line 136) complaining that it could not find my component...
>
> I saw that the code dealing with transparent resolvers, and component
> children types (arrays or single child) is rather "touchy" and did not
> try to tweak it, as I feared it would cause more dammage than good ;)
>
> I cannot tell you if this problem exists in other wicket versions, as I
> rarely need the enclosure tag, and for those rare occasions, I
> encountered no problem at all...
>
> I've used a WebMarkupContainer on the div as a workaround, but since
> that is exactly the purpose of the <wicket:enclosure /> tag, that's
> juste too bad :D
>
> Anybody else god bittent by this one?
>
> Cheers,
>
> Antoine.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org