Michael, I have a single page in my application. Currently, I use that page's properties file for storing "notes" and the "format" call to get the text to display. What I need is access to the IMessages that is stored in that page so I can get access to "other" strings in that same properties file. I could take the long way around for every access by getting a cycle and then the current page (doesn't change) and then have it format it for me. Or I can get a copy of the messages and store them in my visit object for whenever I need them. If my classes that need the access to the messages where tapestry components and such, then I wouldn't have to jump through hoops, but they are data objects.
So, my messages are at an application level not a component level. Thoughts? regards, Mark -----Original Message----- From: Michael Prescott [mailto:[EMAIL PROTECTED] Sent: Wed 12/14/2005 3:24 PM To: Tapestry users Subject: RE: When to "getMessages" I can't help you with your question, but I'm curious - from a design perspective, should the messages be in Tapestry resource components at all? Are you using this for an automated test? (If so, then perhaps you could check for the presence of something else, like a span's non-internationalized id attribute.) Michael -----Original Message----- From: Mark Stang [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 14, 2005 5:14 PM To: Tapestry users Subject: When to "getMessages" Hi, I am using 3.03. I need access to a page's messages and to save them off in the Visit object for access by non-tapestry components. What I need to know is when/what method to override. I tried the constructor of my page and that is too soon. So, at what point in the life cycle should I do this? Thoughts? thanks, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
