Ok that way looks like it would work as long as you don't mind using submit 
buttons instead of hyperlinks.  It seems that the mechanism for supporting this 
is very similiar to what is happening behind the scenes to make the ActionLink 
work, so is this type of functionality going to be deprecated as well?

Are there any other ways to deal with an item in a list as an object in the 
listener (as opposed to getting an id and recreating it using DirectLink) or is 
using the Submit button the best way to accomplish this?

Thanks!

Mark
-----Original Message-----
From: Patrick Casey [mailto:[EMAIL PROTECTED]
Sent: Wed 11/2/2005 8:43 PM
To: 'Tapestry users'
Subject: RE: What to replace ActionLinks with?
 

        What about something like this:

                                        <span jwcid="@Foreach"
source="ognl:object.options" value="ognl:item" element="tr">
                                                <td><input type="text"
jwcid="@Insert" value="ognl:item.value"/></td>
                                                <td><input type="text"
jwcid="@Insert" value="ognl:item.text"/></td>
                                            
                                            <td><input type="submit"
jwcid="@Submit" listener="ognl:listeners.moveUp" selected="ognl:actedOn"
tag="ognl:item" label="Move Up"</td>
                                            <td><input type="submit"
jwcid="@Submit" listener="ognl:listeners.moveDown" selected="ognl:actedOn"
tag="ognl:item" label="Move Down"</td>
                                                        <td><input
type="submit" jwcid="@Submit" listener="ognl:listeners.moveDelete"
selected="ognl:actedOn" tag="ognl:item" label="Delete" onClick="return
confirmDelete()"</td>            
                                            
                                        </span>

        Then just have your listener check the value of actedOn to see which
particular object was the target of the action?

        --- Pat

> -----Original Message-----
> From: Mark Shead [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 02, 2005 5:38 PM
> To: Tapestry users
> Subject: RE: What to replace ActionLinks with?
> 
> So going forward is Tapestry going to no longer support transparently
> working with objects across a request response cycle?  Is there going to
> be a way to take an object that is in a list on a page and perform an
> action on it without using an id and looking the object up again?
> 
> --Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to