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

FIWARE.Question.Tech.IoT.BackendIoTBroker.Configuration Manager XML Validation

    Details

    • Type: Monitor
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:

      Description

      Created in FIWARE Q/A platform on 28-11-2014 at 13:11
      Answer this issue at http://stackoverflow.com/questions/27188524/fiware-iot-broker-and-iot-configuration-manager-xml-validation

      Question:
      Fiware IoT Broker and IoT Configuration Manager XML Validation
      Description:
      I figured out I had to have another GE, the IoT Configuration Manager working parallel to the IoT Broker in order to manage the entities from which we will get data. Now, it seems that the XMLValidator code is giving me some trouble. I registered an entity via HTTP POST osgi9 directly with the configuration manager. Then I try to access it by communicating via osgi10 with the IoT broker. The IoT Broker communicates with the IoT DIscovery service and gets a response, but then the XMLValidator says the XML is wrong even tough it clearly is not.

      This is the IoT Broker asking for the availability of a resource to the IoT ConfMan:

      2014-11-27 10:31:13,682 | INFO | (HttpConnectionClient.java:initializeConnection:170) | Output

      Stream: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
      <discoverContextAvailabilityRequest>
      <entityIdList>
      <entityId isPattern="false">
      <id>Dorm</id>
      </entityId>
      </entityIdList>
      <attributeList/>
      <restriction>
      <scope>
      <operationScope>
      <scopeType>IncludeAssociations</scopeType>
      <scopeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">SOURCES</scopeValue></operationScope>
      </scope>
      </restriction>
      </discoverContextAvailabilityRequest>

      Then IoT Broker gets:

      2014-11-27 10:31:13,947 | INFO | (HttpConnectionClient.java:initializeConnection:188) |
      <?xml version="1.0" encoding="UTF-8"?><discoverContextAvailabilityResponse>
      <contextRegistrationResponseList>
      <contextRegistrationResponse>
      <contextRegistration>
      <entityIdList>
      <entityId type="Room" isPattern="false">
      <id>Dorm</id>
      </entityId>
      </entityIdList>
      <contextRegistrationAttributeList>
      <contextRegistrationAttribute>
      <name>temperature</name>
      <type>degree</type>
      <isDomain>false</isDomain>
      <metadata>
      <contextMetadata>
      <name>ID</name>
      <type>string</type>
      <value/>
      </contextMetadata>
      <contextMetadata>
      <name/>
      <type/>
      <value/>
      </contextMetadata>
      </metadata>
      </contextRegistrationAttribute>
      </contextRegistrationAttributeList>
      <providingApplication>http://192.168.100.1:70
      </providingApplication>
      </contextRegistration>
      </contextRegistrationResponse>
      </contextRegistrationResponseList>
      <errorCode>
      <code>200</code>
      <reasonPhrase>OK</reasonPhrase>
      <details xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">Result</details>
      </errorCode>
      </discoverContextAvailabilityResponse>

      2014-11-27 10:31:13,949 | INFO | (HttpConnectionClient.java:initializeConnection:218) | Connection Closed!
      2014-11-27 10:31:13,987 | INFO | (XmlValidator.java:error:128) |
      ERROR
      org.xml.sax.SAXParseException; lineNumber: 0; columnNumber: 0; cvc-complex-type.2.4.b: The content of element 'contextRegistration' is not complete. One of '

      {registrationMetaData, providingApplication}

      ' is expected.

      It is clearly seen by the received xml that at least the providingApplication is received but XMLValidator is not seeing this.

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2015-09-25 18:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2015-09-25 18:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False
        Hide
        backlogmanager Backlog Manager added a comment -

        2015-09-25 21:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2015-09-25 21:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False

          People

          • Assignee:
            gessler Stefan Gessler
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: