Community
Participate
Working Groups
With the introduction of the RWTContext, for each 'static' class that lies in application scope, an accessor class was introduced. E.g. the LifeCycleFactory was renamed to LifeCycleFactoryInstance and LifeCycleFactory serves now as an accessor class where each method just obtains an instance of LifeCycleFactoryInstance and delegates the actual work. The purpose of this work is to reduce the number of classes by 'inlining' the accessor methods and then removing the accessor classes. After that the ...Instance classes can be renamed back to their original names. E.g. LifeCycleFactoryInstance would become LifeCycleFactory.
I decided to do this work in chunks. Part 1 includes BrandingManager, EntryPointManager and LifeCycleFactory
Part 2: ServiceManager, StartupPage, StartupPageConfigurer Changes are in CVS HEAD
Part 3: SettingStoreManager, ConfigurationReader, ApplicationStore, PhaseListenerRegistry Changes are in CVS HEAD
Part 4: ThemeAdapterUtil (now named ThemeAdapterManager), ThemeManagerInstance ThemeManagerInstance was renamed to ThemeManagerHolder. Also I left the ThemeManager#getInstance() and resetInstance() for now. The way to the actual ThemeManager is via another indirection (ThemeManagerHolder) and RWTFactory.getThemeManager().getInstance().doSomething(...) is too verbose and there are too many places where the ThemeManager is called.
Part 5: TextSizeStorageRegistry Changes are in CVS HEAD
Part 6: ImageFactory, FontDataFactory, ImageDataFactory, InternalImageFactory Changes are in CVS HEAD
Part 7: DisplaysHolder, JSLibraryConcatenator, JSLibraryConcatenator, AdapterFactoryRegistry Changes are in CVS HEAD
Part 8 (almost done): ResourceRegistry, ResourceFactory
Part 9: ResourceManager (renamed to ResourceManagerProvider)
The rest: ResourceManagerImpl The ResourceManagerImpl was removed from the ApplicationContext to avoid calling ResourceManagerImpl#getInstance() multiple times as it led to the ResourceManagerImpl instance being re-configured with each call. ResourceManagerImpl#getInstance() was renamed to createInstance() and creates and configures a new instance of ResourceManagerImpl. All clients of the resource manager now call the ResourceManagerProvider to obtain an instance. The ResourceManagerProvider together with the DefaultResourceManagerFactory now handles creating and accessing the single ResourceManagerImpl instance per ApplicationContext. Changes are in CVS HEAD
