Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-3552

[Fiware-lab-help] R: [FI-LAB] New Orion Context Broker Release (0.19.0)

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-LAB-HELP
    • Labels:
      None
    • HD-Enabler:
      Orion

      Description

      Hi,

      I have some question regarding the new upgrade. Two weeks ago following the instruction on https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_Quick_Start_for_Programmers I was able to, at example, read some data from Santander city. Now I am not able and the answer I get is “No JSON object could be decoded”. Something is change ?

      Thanks and regards.

      Fabio

      Trilogis

      PS: We are involved into FI-STAR.

      Da: no-reply@account.lab.fiware.org no-reply@account.lab.fiware.org
      Inviato: mercoledì 11 febbraio 2015 13.23
      A: *****@hotmail.com
      Oggetto: [FI-LAB] New Orion Context Broker Release (0.19.0)

      Dear FI-LAB users,

      This announcement is about Orion Context Broker. If you are not using this component you can safety ignore this message.

      A new Orion Context Broker release (0.19.0) has just been released (detailed changelog is below). This is mainly a bugfixing and hardening release of 0.18.1.

      For users of standalone Orion instances (i.e. Orion running in your own virtual machine), you can update to the new version running (as root or using sudo): “yum install contextBroker”. Sometimes yum doesn’t detect the new version, in which case you have to run “yum clean all” before that.

      For users of the global instance at orion.lab.fi-ware.org, the change to 0.19.0 will be done next days.

      For any doubt related with this announcement, please send an email to <fiware-lab-help@lists.fi-ware.org> fiware-lab-help@lists.fi-ware.org mailing list.

      Detailed changelog for this new version:

      • Fix: The option '-multiservice' was ignored and the broker ran always in multiservice mode. Now the option is taken taken into account (Issue #725)
      • Fix: Forwarded requests always in XML (Issue #703)
      • Fix: internal substitution of servicePath defaults ("/" for update-like operations, "/#" for query-like operations)
      • Fix: Temporal hack to allow for forwarding of 'attribute not found in entity found' (Issue #716)
      • Fix: Broker crashes dealing with "GET /v1/contextTypes" operation when DB contains entities of the same type, ones with attributes and others without them (Issue #740)
      • Fix: Service-Path supported for registrations and discoveries (Issue #719)
      • Fix: Service-Path supported for forwarding of registrations between Config Manager and Context Broker (Issue #719)
      • Fix: Service-Path supported for forwarding to Context Providers (Issue #719)
      • Fix: Hash sign (#) in service-path, or multiple service-paths not valid for updateContext requests (Issue #746)
      • Fix: Not forwarding the default Service-Path to context providers (Issue #714)

      Best regards,

      ------
      FI-LAB Staff

      --------------------------------
      You are receiving this message because you are a registered FIWARE Lab user. Should you wish to remove your account, you need to follow four simple steps: 1. Log on FIWARE Lab 2. Click on the dropdown menu next to your user name (upper right corner) 3. Select "Settings" 4. Click on "Cancel account" and confirm

      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-lab-help

      [Created via e-mail received from: Fabio Roncato <****@hotmail.com>]

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            florian Florian Schreiner
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: