I really like ActionLink since it works a lot like WebObjects works (link-wise). If it is deprecated, that'll just make things more difficult since serializing objects or putting the primary key of database records on the URL isn't really desirable (for my stuff, at least).
/dev/mrg -----Original Message----- From: Alan Chandler [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 11:20 AM To: [email protected] Subject: Re: What to replace ActionLinks with? On Thursday 03 Nov 2005 01:37, Mark Shead wrote: > So going forward is Tapestry going to no longer support transparently > working with objects across a request response cycle? I think that is probably my lack of knowlege. I think you can pass objects as parameters - but I suspect you have to be able to serialize them or something. Don't really know. In the instance I gave, that was not what I needed to do. I was building a new object (Marriage) to write into my database, and it just needed the ID values. -- Alan Chandler http://www.chandlerfamily.org.uk Open Source. It's the difference between trust and antitrust. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
