Uploaded image for project: 'ONOS'
  1. ONOS
  2. ONOS-4406

ResourceService practically requires an IntentId as a consumer

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.6.0
    • Component/s: None
    • Labels:
      None
    • Story Points:
      2
    • Epic Link:
    • Sprint:
      Goldeneye Green Sprint #3

      Description

      In aspect of method signatures, ResourceService seems to accept any implementation of ResouceConsumer as a consumer of resources. But actually, application's unique implementation can't be used because Kryo used in ResourceStore can't serialize them. Because of that, IntentId is currently the only possible implementation of ResourceConsumer. We need to allow applications to use its own ResouceConsumer implementation instead of IntentId.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            • Assignee:
              naoki Naoki Shiota
              Reporter:
              naoki Naoki Shiota
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: