1) It seems that you use something like this
<t:zone t:id="zone" id="prop:zoneFilterPropertyId">
...
<t:select zone="prop:zoneFilterPropertyId" .../>
...
</t:zone>
public String getZoneFilterPropertyId() {
return zone.getClientId();
}
It makes a recursion in zoneId retrieval. You just need to remove id
parameter from zone.
<t:zone t:id="zone">
...
<t:zone>
On Mon, Feb 25, 2013 at 1:39 AM, bhorvat <horvat.z.bo...@gmail.com> wrote:
> Hi sody,
>
> Thanks for your info. I have managed to get to the same conclusion but you
> have explained a few problems that I was having :)
>
> 1) I found some old mail treads so I managed to figure this part on my own.
> However I prefer your solution but for some reason it isnt really working.
> For some reason I am getting StackOverFlowException
>
>
> com.bomahabo.flow.tapestry.components.layout.FilterData.getZoneFilterPropertyId(FilterData.java:138)
> org.apache.tapestry5.internal.bindings.PropBinding.get(PropBinding.java:59)
>
> org.apache.tapestry5.internal.transform.ParameterWorker$3$1.readFromBinding(ParameterWorker.java:263)
>
> org.apache.tapestry5.internal.transform.ParameterWorker$3$1.get(ParameterWorker.java:381)
>
> org.apache.tapestry5.corelib.components.Zone.conduit_get_idParameter(Zone.java)
> org.apache.tapestry5.corelib.components.Zone.getClientId(Zone.java:248)
>
> com.bomahabo.flow.tapestry.components.layout.FilterData.getZoneFilterPropertyId(FilterData.java:138)
> org.apache.tapestry5.internal.bindings.PropBinding.get(PropBinding.java:59)
>
> org.apache.tapestry5.internal.transform.ParameterWorker$3$1.readFromBinding(ParameterWorker.java:263)
>
> org.apache.tapestry5.internal.transform.ParameterWorker$3$1.get(ParameterWorker.java:381)
>
> org.apache.tapestry5.corelib.components.Zone.conduit_get_idParameter(Zone.java)
> org.apache.tapestry5.corelib.components.Zone.getClientId(Zone.java:248)
>
> com.bomahabo.flow.tapestry.components.layout.FilterData.getZoneFilterPropertyId(FilterData.java:138)
> org.apache.tapestry5.internal.bindings.PropBinding.get(PropBinding.java:59)
>
> 2) Yea I have seen this behvariour. To be honest I dont mind it as it only
> calls my handler method so I dont have any problem still any way to prevent
> select component from adding its javascript that will trigger an event?
>
> 3) Thanks for this I have implemented as per your suggestion. Well I have
> used triggerEvent that receives a list of object or in my case one object
>
> 4) To be honest I was under the impression that I cant really use this but
> I
> will give a it a closer look that is for sure
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Mixng-cant-find-zone-parameter-tp5720157p5720195.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
BR
Ivan
