Why not just use:

<t:container xmlns:t="http://tapestry.apache.org/schema/tapestry_5_3.xsd";>
    <t:eventlink zone="aZone"/>
    <t:zone t:id="aZone" id="aZone" />
</t:container>

?

On 7/03/2012 4:18 PM, Jochen Frey wrote:
Hi!

A general pattern for an Eventlink with an Ajax zone can look something like 
this:

X.java:
public class CTest {
     @InjectComponent @Property private Zone aZone;
}

X.tml:
<t:container xmlns:t="http://tapestry.apache.org/schema/tapestry_5_3.xsd";>
     <t:eventlink zone="prop:aZone.clientId"/>
     <t:zone t:id="aZone"/>
</t:container>


Where in essence I use a @Property in Java to generate the correct clientId for 
the t:zone parameter to the eventlink.

I was wondering if there's a way to guarantee the correct clientID (not the 
t:id) without going through a Java @Property.


Looking at the documentation one might hope that something like this would work:

<t:container xmlns:t="http://tapestry.apache.org/schema/tapestry_5_3.xsd";>
     <t:eventlink zone=
                "component:aZone"
        />
     <t:zone t:id="aZone"/>
</t:container>


But "component:aZone" doesn't get the ID (which I expected from the 
documentation here: Binding Expressions - component: 
http://tapestry.apache.org/component-parameters.html), but instead I gets the actual Zone 
Object (which is great for many other use cases).

And as far as I can tell, it's not possible to do something like this (see 
below) either:

        "component:aZone.clientId"

Am I missing something, or is it simply a requirement to go through the java 
class?

Thanks so much!
Jochen
---
   joc...@jochenfrey.com
   +1.415.366.0450
   @jochen_frey


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to