Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.0-beta-1
-
Fix Version/s: 1.0-beta-1
-
Component/s: PicoContainer (Java)
-
Labels:None
-
Number of attachments :
Description
The hardest part here is what to do when a component is registered that is not Serializable.
In that case, it should be removed from the internal lists/maps prior to serialization, and reinitialised upon deserialisation.
PicoContainer's responsability should only be:
- instantiate new components that were not serialised (those that were not Serializable).
- Rewire the dependencies.
This shouldn't be so hard to do. The hardest part is dealing with all the internal collections without getting them oput of sync.
Issue Links
- depends upon
-
PICO-22 Add the ability for components to be re-initialized with their dependencies after creation
-
Activity


Assignee | Aslak Hellesoy [ rinkrank ] | Paul Hammant [ paul ] |

Resolution | Fixed [ 1 ] | |
Status | Assigned [ 2 ] | Closed [ 6 ] |
This is a more concrete specification of
PICO-22