Opened 5 years ago

Last modified 5 years ago

#1200 new

Preserve schemas in Manifest

Reported by: Aaron Helsinger Owned by: xyang@maxgigapop.net
Priority: major Milestone:
Component: I2AM Version: SPIRAL6
Keywords: Cc: tlehman@maxgigapop.net
Dependencies:

Description

The ION AM uses a fixed set of schemas in the manifest RSpec it returns. It also preserves elements in the request body that it is ignoring.

The problem is that this means that a request with elements defined in custom schemas will still have the custom elements, without the proper schema declarations.

Reproducable using the request RSpec at http://trac.gpolab.bbn.com/gcf/attachment/ticket/548/excl-of-stitching.xml

Here, the request starts:

<rspec type="request" generated_by="Flack" generated="2014-03-05T14:05:11Z" 
    xsi:schemaLocation="http://www.geni.net/resources/rspec/3 http://www.geni.net/resources/rspec/3/request.xsd " 
    xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" 
    xmlns:client="http://www.protogeni.net/resources/rspec/ext/client/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xmlns:emulab="http://www.protogeni.net/resources/rspec/ext/emulab/1"
    xmlns="http://www.geni.net/resources/rspec/3">

And the ION manifest that comes back starts:

<rspec expires="2014-03-05T15:35:39.816Z" generated="2014-03-05T15:35:39.816Z" generated_by="Flack" type="manifest" 
      xmlns="http://www.geni.net/resources/rspec/3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
      xsi:schemaLocation="http://www.geni.net/resources/rspec/3 http://www.geni.net/resources/rspec/3/manifest.xsd">

Change History (1)

comment:1 Changed 5 years ago by Aaron Helsinger

Related: It appears that ION tries to but the schemas/namespaces on the relevant elements. But these are coming out malformed:

    <emulab:openflow_controller url="tcp:192.1.249.135:1716" xmlns="" xmlns:emulab="http://www.protogeni.net/re
sources/rspec/ext/emulab/1" xmlns:ns3="http://www.geni.net/resources/rspec/3"/>

Note the empty xmlns attribute.

Note: See TracTickets for help on using tickets.