On 9/17/07, Davor Hrg <[EMAIL PROTECTED]> wrote: > The problem is that you must give action link something > to identify your object. > > in the page you mentioned you have only one instance of > the MatchInfo component that get's rendered multiple times with different > data. > So when your action is called, you have the last element passed as > parameter.
That's what really confused me. I wrongly thought you would get a new MatchInfo Object for every iteration of the loop. Thanks for clearing that up. > if in you AppModule you make following TypeCoercers : > String->DateeeMatch > and > DateeeMatch -> String I have been looking at Type Coercion, and I am still a little confused. As I understand it I need to provide a way for Tapestry to convert my DateeeMatch object to a string. The DateeeMatch is too complex to serialise directly in to the page. Is there some way, I can store it in the session, then use some type of ID to retrieve the correct object from the session. I could then just put the ID in the actually URL. Is there some standard way of providing this type of Coercion in tapestry or do I need to implement all storing to and retrieving from the session functionality my self. According to the docs there's a standard Object -> String coercion in built in, I am currently trying to find the source of that to see if that will give me any pointers. Is this the best approach to Coercion of more complex objects (not single data objects like Strings)? Thanks again for the help. Charlie M --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
