Service Virtualization

Does anyone have a sample RAML file that works generating a vsi?  My RAML file contains !includes and it is not able to be parsed?

I get this error trying to parse all my RAML files.  Even the ones that don't have includes.

java.lang.Exception: RAML failed to parse
at com.itko.lisa.vse.stateful.protocol.http.RAMLPanel.processNewRAML(RAMLPanel.java:503)
at com.itko.lisa.vse.stateful.protocol.http.RAMLPanel.processRAMLChangeAndSelect(RAMLPanel.java:364)
at com.itko.lisa.vse.stateful.protocol.http.RAMLPanel.setRAMLUrl(RAMLPanel.java:784)
at com.itko.lisa.vse.stateful.protocol.http.RAMLPanel$1.actionPerformed(RAMLPanel.java:171)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
at javax.swing.AbstractButton.doClick(AbstractButton.java:376)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:833)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:877)
at java.awt.Component.processMouseEvent(Component.java:6533)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
at java.awt.Component.processEvent(Component.java:6298)
at java.awt.Container.processEvent(Container.java:2236)
at java.awt.Component.dispatchEventImpl(Component.java:4889)
at java.awt.Container.dispatchEventImpl(Container.java:2294)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4525)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466)
at java.awt.Container.dispatchEventImpl(Container.java:2280)
at java.awt.Window.dispatchEventImpl(Window.java:2746)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.awt.EventQueue$4.run(EventQueue.java:731)
at java.awt.EventQueue$4.run(EventQueue.java:729)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Tamika,  what version of RAML are you testing?  I know we only support  RAML version 0.8.  

Thanks

Shiney 

That must be the problem.   It is RAML 1.0

Any plans to support 1.0?

I can check with Product Management.  

RE: "I can check with Product Management". --> Did you hear back from PM on plans to support 1.0?

Tamika,  

Sent an email to PM asking your question on support of RAML 1.0?  Will post as soon as I get an answer/

~Marcy

Tamika,

Found out that RAML 1.0 is on the backlog, but have no idea when it will be in DevTest.

If this something you require now, please open a new support case..

~Marcy

We need this too and have asked PM on webex for when it will be supported. Seems like CA need to prioritise this on their backlog if more customers need it. How hard can it be?

Is the only REAL work around for this is to convert it to a swagger 2.0 document?