XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Steps to reproduce the problem (Copied from Browser Channell Doc in case these steps will be changed later):

      1. First start the GPII in the CloudBased browserChannel test configuration from the root of universal in a terminal with

      node gpii.js gpii/configs gpii.config.cloudBased.production
      

      2. Then start the client from ../examples/browserChannelClient with

      node browserChannelClient.js
      

      3. Go back to the first terminal window, where CloudBased browserChannel is running, the log shows this error:

      Failed to resolve reference {deviceReporter} - could not match context with name deviceReporter from component { typeName: "gpii.flowManager.browserChannel.handler" gradeNames: ["kettle.request","kettle.request.ws","gpii.flowManager.sessionAware","gpii.flowManager.browserChannel.handler"] id: b34cxx2t-1245}...
      

      The code that requires "

      {deviceReporter}

      " is at the browser channel request handler.

      As per the first step, the cloud based GPII is running and the device reporter does not make sense to be included in the cloud. But the browser channel request handler does require the present of the device reporter. Is this example using the wrong config file? The proper config file might be CloudBased + DeviceReporter?

        Attachments

          Activity

            People

            Assignee:
            amb26 Antranig Basman
            Reporter:
            cli@ocad.ca Cindy Qi Li
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: