This observation is correct - I'll add it to the Release Notes. In addition, you'll want to make sure you add your page classes to tapestry.application and change the package name in there as well:
<meta key="org.apache.tapestry.visit-class" value="org.appfuse.webapp.pages.Visit"/> <meta key="org.apache.tapestry.default-page-class" value="org.appfuse.webapp.pages.BasePage"/> <meta key="org.apache.tapestry.page-class-packages" value="org.appfuse.webapp.pages,org.appfuse.tutorial.webapp.pages"/> Matt On 2/8/07, Sib <[EMAIL PROTECTED]> wrote:
Hi All, A quick note moving from m2 to m3 with tapestry-modular had a few issues in an sample application created from m2. It seems the BasePage and related classes moved packages from org.appfuse.webapp.action to org.appfuse.webapp.pages in case someone runs into a similar issue. You will get errors if you had created and tried to upgrade to m3 by changing your pom.xml. Adjust your classes if you were extending BasePage. Someone please chime in if the observation is incorrect. Sib
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
