Yeah.. I remember that email now. I stick my common component library into "core" as well. It looks like this is used for auto-generating library mappings to classpath asset urls for the ClasspathAssetAliasManager... Maybe somebody can think of a different way to do this? Or perhaps how to configure exceptions for overrides?
Josh On Fri, Jun 11, 2010 at 3:31 PM, Manuel Sugawara <manuel.sugaw...@gmail.com> wrote: > On Fri, Jun 11, 2010 at 4:35 PM, Josh Canfield <joshcanfi...@gmail.com>wrote: > >> Read the bit about template inheritance at the bottom of this page: >> http://tapestry.apache.org/tapestry5.1/guide/templates.html >> Although I agree with the sentiment in that page about not overusing >> these features and preferring composition over inheritance. >> >> If you map your PlatformModule to "core" then your components and >> pages can be accessed without a prefix. Your page classes would live >> in x.y.platform.pages. >> > > Just be careful that this might not work in the upcoming tapestry release. > See this > link<http://old.nabble.com/Re:-Libarary-"core"-mapping-not-working-in-5.2.0-SNAPSHOT-p28758883.html> > . > > Regards,<http://old.nabble.com/Re:-Libarary-"core"-mapping-not-working-in-5.2.0-SNAPSHOT-p28758883.html> > Manuel. > -- -- http://www.bodylabgym.com - a private, by appointment only, one-on-one health and fitness facility. -- http://www.ectransition.com - Quality Electronic Cigarettes at a reasonable price! -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
