tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harish Krishnaswamy <harishksw...@gmail.com>
Subject Re: Tapestry 3.1 and IFormComponent.setIndex
Date Mon, 21 Mar 2005 20:14:42 GMT
Hi Robert,

Yes, I remember the patch! I have to dive into the 3.1 code before I
can answer your question. I am going home 2 weeks from now and
hopefully I will have sometime to take a look then. But my guess is
there will be an alternative way of doing this. Will let you know.

-Harish


On Mon, 21 Mar 2005 09:01:22 -0700, Robert Zeigler
<rdzeigle@u.arizona.edu> wrote:
> Some time ago, Harish (? I believe it was he) submitted a patch
> to add a "setIndex" method to the IFormComponent interface. The
> application of the patch was going to be deferred until 3.1, as I
> recall. The point of the method was to be able to set a particular
> rendering instance of a field as being invalid in cases where the field
> is being rendered within a loop.
> Is this patch still on for 3.1? Or is there going to be an alternative
> methodology for this?
> Thanks,
> 
> Robert
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message