No, that's part of what Tapestry calls "distributed configuration" You can define separate modules and pack them into separate jars. If you want them used in your AppModule yo can do this in two ways: Either use the @SubModule-annotation telling AppModule, what the other module's class name is. Or pack a MANIFEST.MF with apropriate entry with your jar. Tapestry will scan for that and find your module. Here you'll find more detailed info: http://tapestry.apache.org/tapestry-ioc-configuration.html
----- http://www.winfonet.eu -- View this message in context: http://tapestry.1045711.n5.nabble.com/IoC-services-can-they-come-from-an-external-jar-tp4688157p4689254.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
