SoapUI fails to parse the NSX RAML file

[lrevnic]

Hello,

When using SOAP-UI 5.2.1 to parse the NSX RAML file the following error is displayed.

2015-10-19 12:30:31,693 ERROR [errorlog] java.lang.RuntimeException: Builder not found for <NodeTuple keyNode=<org.yaml.snakeyaml.nodes.ScalarNode (tag=tag:yaml.org,2002:str, value=displayName)>; valueNode=<org.yaml.snakeyaml.nodes.ScalarNode (tag=tag:yaml.org,2002:str, value=vdsPrepare)>>
java.lang.RuntimeException: Builder not found for <NodeTuple keyNode=<org.yaml.snakeyaml.nodes.ScalarNode (tag=tag:yaml.org,2002:str, value=displayName)>; valueNode=<org.yaml.snakeyaml.nodes.ScalarNode (tag=tag:yaml.org,2002:str, value=vdsPrepare)>>
at org.raml.parser.builder.DefaultTupleBuilder.getBuilderForTuple(DefaultTupleBuilder.java:68)
at org.raml.parser.visitor.YamlDocumentBuilder.onTupleStart(YamlDocumentBuilder.java:264)
at org.raml.parser.visitor.NodeVisitor.doVisitMappingNode(NodeVisitor.java:145)

Thanks,
Lucian

[yfauser]

Hi Lucian,

I'm not familiar with SOAP-UI, so I will need a little help from you here.
Is this what you are using? https://github.com/SmartBear/soapui-raml-plugin ?

• Yves

[lrevnic]

Hi Yves,

Yes. If you need help to reproduce the issue let me know. The challenge is that SOAP UI is one of the most used tools when testing Web Services (SOAP and REST) and since the NSX RAML is getting traction (congratulations for publishing it! 👍 ) I imagine people will hit the SOAP UI issue very soon.

Best regards,
Lucian

[justjacksonn]

Hi... does SOAP UI support RAML? I am not familiar with it either, but if it doesnt parse RAML, I suspect that will be an issue until such a time they support it.

[lrevnic]

Hi,

Yes it does. You can read about it here: https://github.com/SmartBear/soapui-raml-plugin.

HTH,
Lucian

[avoltmer]

Lucian,

Would you be willing to talk to me via phone / WebEx about this issue. I can't seem to reproduce your error. I am at avoltmer@vmware.com

Sincerely,
Andrew

[lrevnic]

Hi Andrew,

Sure. I'll also invite few colleagues who recently encountered the same issue recently.
My email is: teodor-lucian.revnic@hpe.com

Best regards,
Lucian

[avoltmer]

A workaround for this is to comment out all "displayName" rows from get, post, put sections in the NSX RAML. Also set the baseURI directly to the FQDN of the NSX manager. Example:

baseUri: https://nsxmgr-l-01a.corp.local/api