-
Notifications
You must be signed in to change notification settings - Fork 27
swagger 2.0 spec fails with SwaggerParserExtension #6
Comments
Hi, Hmm.. Which version of the plugin and soapui/ready-api are you using? /Ole |
Hi Ole, I'm using version 2.1 of the plugin on ready-api 1.3.0 |
Thanks - there is 2.1.1 version on its way out that hopefully fixes this - I can mail it to you directly if you send me your email address!? /Ole |
Actually - this update should already be available from the Plugin Manager - can you check if its there? /Ole |
Hi Ole, I just hit this as well, right after installing the plugin. My Plugin Manager shows the latest available is 2.1 Thanks, |
Hi Ole, I don't see version 2.1.1 in the plugin manager yet. But I'll send you an e-mail to test the plugin directly. Thanks |
Hi guys - the plugin manager should be updated now, can you please have another look there? Sorry for the hassle - thanks for your patience... /Ole |
Working now. Thanks for the quick fix Ole! |
Hi Ole, I'm getting an error that is referenced in #3 Error java.lang.NullPointerException: Cannot get property 'basePath' on null object A part of the swagger.json indicating base path is set: swagger: "2.0", Thanks for the fast response on the previous error! |
When trying to use the swagger import on a swagger spec 2.0 json file I get the following error in soap ui (using swagger core 1.5.* jersey 2 integration).
java.util.ServiceConfigurationError: io.swagger.parser.SwaggerParserExtension: Provider io.swagger.parser.Swagger20Parser not a subtype
When I go back to a 1.3.* integration (swagger spec 1.2) the import completes succesfully.
The text was updated successfully, but these errors were encountered: