Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Critical 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 :
      0

      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

          Activity

          Hide
          Aslak Hellesøy added a comment -

          This is a more concrete specification of PICO-22

          Show
          Aslak Hellesøy added a comment - This is a more concrete specification of PICO-22
          Aslak Hellesøy made changes -
          Field Original Value New Value
          Link This issue depends upon PICO-22 [ PICO-22 ]
          Aslak Hellesøy made changes -
          Assignee Aslak Hellesoy [ rinkrank ] Paul Hammant [ paul ]
          Hide
          Aslak Hellesøy added a comment -

          Diddit

          Show
          Aslak Hellesøy added a comment - Diddit
          Aslak Hellesøy made changes -
          Resolution Fixed [ 1 ]
          Status Assigned [ 2 ] Closed [ 6 ]

            People

            • Assignee:
              Paul Hammant
              Reporter:
              Aslak Hellesøy
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: