I think it would be easiest if the Zone component had a clientId parameter,
which you could just set to context.propertyId (from PropertyEditContext).
Unfortunately, it does not. Maybe this will work:

aZoneDelegate.tml:
...
<t:zone t:id="zone"/>
...

aZoneDelegate.java:
@Component
private Zone _zone;

public String getZoneClientId()
{
     return _zone.getClientId();
}


Then when you want to use it

<t:actionlink ... t:zone="prop:conditionalZone.zoneClientId"/>

Peter Beshai

On Wed, Apr 9, 2008 at 9:48 AM, Christian Gorbach <[EMAIL PROTECTED]>
wrote:

> hi group, hi howard,
>
> tricky problem here - I need some kind of conditinal zone rendering...(=T5
> ajaxification on/off)
>
> My current solution: custom component, which - depending on a condition -
> does delegate to a zone component (or not).
> <t:aZoneDelegate t:id="conditinalZone"....>
> body here - should always be rendered.
> <t:aZoneDelegate/>
>
> Depending on that condition, I have an actionlink component, pointing to
> the zone above
> <t:actionlink ....t:zone="conditinalZone" />
>
> The problem is that the actionlink's zone parameter points to the
> delegates id and not to the (embedded) zone component  - resulting in
> javascript errors.
> It would be nice if the delegateComponent could forward the id, too. But I
> have not found an solution yet, because tapestry id's are static.
>
> Any suggestions? I also tried to subclass the original zone component but
> this approach was not successfull because of the method's package
> visibility.
>
> tia & best regards
> c)hristian
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to