And why are you not using a TextField component? On 10/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > I have a <span class="input" jwcid="@Insert" > value="ognl:currentObjectInput.input" raw="true"/> within a @For. The > input value is something like <input type="text" name="email"/> > which > renders as an input tag correctly. > > What Id like to do is something like an input value of: > > <input jwcid="@TextField" type="text" name="email" > value="ognl:@currentUser.email"/> and have that process the value of > the > TextField and get the email of the currentUser object as the default value > of the TextField. I realize that requires Tap to first process the @Insert > and then do a 2nd processing of the @TextField. > > Can anyone suggest an approach that I might consider to get the behavior I > want? > > r > -- > View this message in context: > http://www.nabble.com/Double-processing-of-%40Insert-tf4667246.html#a13332619 > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- Howard M. Lewis Ship Partner and Senior Architect at Feature50 Creator Apache Tapestry and Apache HiveMind
