Hi,
[...] 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.
The documentation is perhaps not 100% accurate here. @Local can be used to restrict service lookup scope to same module so there is already sorts of hierarchy going on. I guess the suggested @ModulePrivate would be similar but controlling service exposure scope instead of lookup scope. Cheers, --Nikla --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
