commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hans Gilde <>
Subject RE: [jelly] refillComponent tag ? (was Re: swing example)
Date Sun, 06 Nov 2005 16:49:03 GMT
Should be fine. It would implement ContainerTag and would just clear the
container, then run its body. The body components would add themselves and
then it may need of call pack if it's visible. There are a couple of tricky
bits, like ensuring that it's addChild method has all the features of
ComponentTag's addChild.

It could extend ComponentTag, but one would have to look carefully at what
must be overridden.

One question is: this new tag is essentially acting like the original panel
in terms of allowing children to add components to it. Would it go one step
further and allow you to change the bean fields of that panel using
attributes in the tag?

For instance, would this work:

	<sw:panel name="myPanel" var="myList"/>

<!--refillComponent is now proxying for the panel tag above-->
<sw:refillComponent name="yourPanel" ref="myList">
	<sw:label>the panel now has the bean property

-----Original Message-----
From: Paul Libbrecht [] 
Sent: Friday, November 04, 2005 8:05 AM
To: Jakarta Commons Users List
Subject: [jelly] refillComponent tag ? (was Re: swing example)

Can other Jelly-Swing users comment on such a tag. It really looks to 
be able to solve quite many issues I've met thus far.



Le 3 nov. 05, à 21:35, Dário Luís Coneglian Oliveros a écrit :
> Regarding your reloadable strategy, I think it would be great to have 
> something like that. We can discuss it later if you wish.
> [...]
>> Just thinking out loud, I seem to encounter that the following might 
>> be
>> enough:
>> <sw:frame>
>>   blabla
>>    <sw:panel var="myList"/>
>>   </sw:frame>
>> and somewhere else (e.g. as a child of action:
>> <sw:refillComponent name="panel">
>>    <sw:label>casdasa</sw:label>
>>    ....
>> </sw:refillComponent>
>> That is, we would introduce a "target" element that would allow an
>> component to be cleared than repopulated by its content...
>> This seems suddenly pretty easy to implement compared to the
>> "reloadable" kind of things I expected. Would it fit your task ?

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message