Tapestry doc says that @SubModule specifies...
> [...] a list of additional classes to be treated as module classes, > exactly as if they were identified in the manifest. Despite the name, > there is no hierarchy of modules in Tapestry IoC. > So services added to submodules would be visible as if they were added to "normal" modules, wouldn't they? -- View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-define-a-private-service-a-service-only-for-another-service-tp5597443p5600325.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
