Ticket #6 (assigned task)
Replace singleton-style classes by beans using a registry mechanism
| Reported by: | SebastianMarsching | Owned by: | SebastianMarsching |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core (general) | Version: | |
| Keywords: | refactoring modularization spring factories singleton | Cc: |
Description (last modified by SebastianMarsching) (diff)
At the moment the Pustefix core uses many classes that implement the singleton pattern by using static fields and methods.
This mechanism causes two major problems:
- Initialization and usage of this classes can hardly be traced throughout the code.
- The scope of the instances of these classes is always tied to the class loader.
In order to solve these issues all (or at least most of) these classes should be rewritten to use a single registry instead of static fields for life-cycle management. This central registry could be provided by a Spring ApplicationContext.
These issue is related to ticket:5. This ticket depends on ticket:7.
Change History
Note: See
TracTickets for help on using
tickets.
