Yes that's true. Is including pages in a component library not common ? Calling it a "component library" makes it sound like it's only for components. Was modules supported mainly as component libraries ?
On Wed, Aug 29, 2012 at 9:57 PM, Lance Java <lance.j...@googlemail.com>wrote: > If you are writing a component library then yes, you will need a > LibraryMapping. > I've never included pages in a component library (only components) but I'm > assuming that your page names will have require a prefix (as specified in > your library mapping). > > For instance, if your app package "foo.bar", your class was > "foo.bar.pages.baz.MyPage" and your library prefix was "mylibrary", I would > expect your page name to be "mylibrary.baz/MyPage" > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/t5-3-4-Plugin-blocks-tp5715810p5715893.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*
