Great, this does the trick!

Thanx a lot,
cheers,
Martin


On Sun, 2007-05-27 at 23:11 +0700, Ivan Dubrov wrote:
> You can contribute to ComponentClassResolver service mappings from
> prefix (e.g, "mod1") to package, like the following:
> 
> public static void
> contributeComponentClassResolver(Configuration<LibraryMapping>
> configuration) {
>     configuration.add(new LibraryMapping("mod1",
> "org.comp.app.mod1.presentation"));
>     configuration.add(new LibraryMapping("mod2",
> "org.comp.app.mod2.presentation"));
> }
> 
> All your pages will be available at paths like "mod1/pagename" and all
> components in mod1 available as "<t:mod1.componentname>" in templates.
> 
> Martin Grotzke wrote:
> > Hi,
> >
> > I have a question concerning the configuration of tapestry5
> > with the context-param "tapestry.app-package" and the support
> > of multiple modules per application (several root-packages).
> >
> > We have an application that first has modules and then layers
> > for each module, like the following:
> >
> > org.comp.app.mod1.presentation
> > org.comp.app.mod1.business
> > org.comp.app.mod1.dao
> >
> > org.comp.app.mod2.presentation
> > org.comp.app.mod2.business
> > org.comp.app.mod2.dao
> >
> > the presentation packages shall contain subpackages
> > for services, pages and components, e.g. 
> >
> > org.comp.app.mod1.presentation.pages
> > org.comp.app.mod1.presentation.components
> > org.comp.app.mod1.presentation.services
> >
> >
> > The quickstart archetype generated an AppModule class in
> > org.comp.app.mod1.presentation.services, but AFAICS
> > this is intended to configure the application, and therefore
> > should be located in a package like
> > org.comp.app.common.presentation.services.
> >
> > Then I would like to specify "org.comp.app" as the
> > "tapestry.app-package", or specify several root packages,
> > for each module the presentation package.
> >
> > I already tried the first approach, but it failed with 404 NOT_FOUND
> > if I requested a specific page at /app/mypage (e.g. with
> > MyPage.java in org.comp.app.mod1.presentation.pages).
> >
> > How is such an architecture supported by T5?
> >   
> > Thanx in advance,
> > cheers,
> > Martin
> >
> >
> >   
> 
> 
-- 
Martin Grotzke
http://www.javakaffee.de/blog/

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to