Hi there, I just downloaded Tapestry 4 beta and tried to compile an application we're currently building using Tapestry 3.0. We're still in development and are really interested in the new features in 4.0.
A couple of the compile problems relate to changes on the services and engine (which will need to be changed) ... which is fine. But we have 100s of compile errors (and probably plenty of references in page templates) due to the removal of the "getMessage(String)" and the "format(*)" methods from the AbstractComponent (and Page). And I couldn't find a reference to this change in the upgrade guide, and these weren't deprecated in 3.0. Any reason why these convenience methods were removed? I guess to cleanup the page and component interfaces? What's the recommended approach to get and format messages now? Is it to just call getMessages().getMessage(String) and getMessages().format(*)? Maybe a note in the release notes or upgrade would help other upgraders like me. :) Thanks, Matt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
