> > > Is the "@ImportModule(CommonModule.class)" required? > > For multi-module development with the common module project open and > live-class-reloadable, yes. If you're just adding the common module JAR to > the main project (or any project using it as a dependency) as a JAR > directly, no. You can use both @ImportModule/@SubModule and the > manifest
The Manifest configuration is back! Thank you for clarification Thiago! > entry at the same time without problems: Tapestry-IoC will only include > one module class once no matter how many different times and ways you > include it. > > > But of course I had the problem that it doesn't seem to run my > > contributeHibernateEntityPackageManager in HappyModule to add my > entities > > package (in my common module) to hibernate - maybe this is why. I'm > away > > from my work PC so I will have to check next time. > > That's why. > > > Also, is AppModule here needed? > > https://github.com/sveine/tapestry-multi-module- > demo/blob/master/common/src/main/java/com/demo/commonlib/service > s/AppModule.java > > If you main webapp project has anything Tapestry-IoC-related, like > declaring services, contributing to them, decorating them or advising > them, yes. Is this correct? Isn't only https://github.com/sveine/tapestry-multi-module-demo/blob/master/common/src/main/java/com/demo/commonlib/services/CommonModule.java read in commonlib, not AppModule.java? > > > If we do have to put "@ImportModule(CommonModule.class)" in the > > non-common appmodules then it means that if we grab a module from > some > > library or > > repository that we need to know the name of the module which needs to > be > > imported for it to work (i'm sure this can't be right). > > Yes, but you'll only use that when you have the library open as a project > in your IDE. Remember, you still should add the manifest file entry to > your library JARs. > > > There is a good chance my understanding is wrong, but in my > understanding > > it's best to have the module be auto loaded without it needing importing, > > simply by adding it to the classpath (or pom.xml), otherwise the main > > projects need to know about the details of how the shared module work. > > Same sentence above. Use both when developing in parallel. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
