Opened 10 years ago

Closed 10 years ago

#3 closed (fixed)

Requested unsupported RSpec V3 sliver results in exception

Reported by: lnevers@bbn.com Owned by: ibaldin@renci.org
Priority: major Milestone:
Component: AM Version: SPIRAL4
Keywords: Error Handling Cc:
Dependencies:

Description

Using version??? on 04/25/2012.

Requesting a sliver with a V3 RSpec (currently not supported according to getverison) results in the following exception:

$ ./src/omni.py -a https://bbn-hn.exogeni.net:11443/orca/xmlrpc createsliver exov3 orca-1node-v3.rspec -t GENI 3
INFO:omni:Loading config file omni_config
INFO:omni:Using control framework pgeni
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+exov3 expires within 1 day on 2012-04-26 02:18:32 UTC
INFO:omni:Creating sliver(s) from rspec file orca-1node-v3.rspec for slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+exov3
INFO:omni:Asked https://bbn-hn.exogeni.net:11443/orca/xmlrpc to reserve resources. Result:
INFO:omni:<!-- Reserved resources for:
	Slice: exov3
	At AM:
	URL: https://bbn-hn.exogeni.net:11443/orca/xmlrpc
 -->
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed createsliver:
  Options as run:
		aggregate: https://bbn-hn.exogeni.net:11443/orca/xmlrpc
		framework: pgeni
		native: True
		rspectype: ('GENI', '3')
  Args: createsliver exov3 orca-1node-v3.rspec
  Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+exov3 expires within 1 day(s) on 2012-04-26 02:18:32 UTC
Asked https://bbn-hn.exogeni.net:11443/orca/xmlrpc to reserve resources. No manifest
 Rspec returned. Error encountered converting RSpec to NDL via converter service: 
ERROR converting from RSpec2 request to RDF-XML:java.lang.Exception: ERROR: unable to 
parse RSpec document: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'rspec'.] 
INFO:omni: ============================================================

Change History (7)

comment:1 Changed 10 years ago by ibaldin@renci.org

Exceptions are a common way of handling errors in Java. This is exception is handled and its message is returned as an error saying the system was unable to parse the provided RSpec. I'm not sure what else should be done here.

comment:2 Changed 10 years ago by ahelsing@bbn.com

Is it possible to identify for the user that the XML schema specified is not supported? That is, to differentiate between 'you have a typo in your RSpec' and 'we don't support that kind of RSpec'?

comment:3 Changed 10 years ago by ibaldin@renci.org

I'm not sure how to differentiate a typo in a document from schema non-compliance with the XML tools I have (aren't they the same thing?). I can simply reinforce the error message with 'Check GetVersion? for supported schemas'

comment:4 Changed 10 years ago by ahelsing@bbn.com

Sorry, I didn't mean typo vs schema non-compliance. I meant typo or schema non compliance VS a schema/namespace which is not supported. That you should be able to tell.

But yes, that extra message probably would help.

comment:5 Changed 10 years ago by ibaldin@renci.org

Look at the last paragraph of http://jaxb.java.net/tutorial/section_3_3-Validation.html

Seems like a lot of effort for a small return...

comment:6 Changed 10 years ago by ibaldin@renci.org

Owner: changed from somebody to ibaldin@renci.org
Status: newassigned

comment:7 Changed 10 years ago by lnevers@bbn.com

Resolution: fixed
Status: assignedclosed

Able to create sliver with V3 RSpec. Closing ticket.

Note: See TracTickets for help on using tickets.