Hi folks, I'm currently trying to understand the structure of the Turbine modules. As far as I understand, the way is as follows:
- The loader checks for the module in its cache (if so configured) - If not found, the AssemblerBrokerService is consulted for an instance of the module - This in turn requests a factory to generate the instance. In the middle of this process the TemplateService and a couple of mappers are involved. Some of them provide their own caching in addition to the loaders. Could some kind soul of the senior developers please shed some light on the reasons for this design. Something obvious I have missed? If there is consent, I'd propose to clean this up a bit and to let the factories do all the work. Would that sound insane to anyone? Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
