Thanks to my colleague,
I have implemented a simple and clean solution in the module class of my
component library which hold the whole configuration. Doing something like
this :
public static void contributeComponentClassResolver(
Configuration<LibraryMapping> configuration,
MyConfigurationService conf) {
// Add modules from configuration
for (LibraryMapping mapping : conf.getLibraryMappings()) {
configuration.add(mapping);
}
}
MyConfigurationService is marked as @EagerLoad.
Now the user of my library has only one entry point for the configuration of
module related informations.
--
View this message in context:
http://www.nabble.com/How-to-create-dynamic-contributeXxx-method---tp25647814p25659365.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
