I cannot disregard your post because It solved my problem :D But now you are saying that "InstructionBlocks" page is under " debitCardModule" folder which is under pages, but I still can't see how will the main app locate the page if it doesn't know the contributing module package.
When I first got the page resolution exceptions, the tapestry exception page identified these pages: Page names: - - About - Contact - ExceptionReport - Index - PageCatalog - PropertyDisplayBlocks - PropertyEditBlocks - ServiceStatus (I'm using a maven-generated project so pages like About, Contact will be removed) So my page "adminmodulemenus" isn't there. But after I followed your suggestion which make a lot of sense which is to map my module's package, I forced the app into an exception and now tapestry can find my page: Page names: - - About - Contact - ExceptionReport - Index - PageCatalog - PropertyDisplayBlocks - PropertyEditBlocks - ServiceStatus - *ipkadmin/AdminModuleMenus <<<<<<<* Thanks a lot for your help :) On Wed, Aug 29, 2012 at 4:38 PM, Lance Java <lance.j...@googlemail.com>wrote: > Please disregard my last post as it was wrong (I should take more time > reading the actual problem). > > In Taha's post he refers to a page named > "debitCardModule/instructionblocks". This means that he has a page with > class "foo.bar.basepackage.pages.debitCardModule.InstructionBlocks" where > "foo.bar.basepackage" is the base package for his app. > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/t5-3-4-Plugin-blocks-tp5715810p5715883.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- *Regards,* *Muhammad Gelbana Java Developer*
