Swagger with 2.16.2 and servlet

Was using this example below as a model with version 2.14.1 http://icantrap.github.io/2015/01/11/swagger-integration-with-standalone-camel-using-embedded-jetty/ Trying to upgrade to 2.16.2 or 2.16.3 did not work. Played with it considerably as the servlet changes and you use camel-swagger-java Gen

Re: Limit swagger API

I have to show an OPTIONS route using rest dsl, which naturally shows up on the api swagger ui. The OPTIONS is the preflight for a POST. I don't know how to hide, if no other way, this would be most welcome. We use routes and annotations, and servlets, and no xml (no web.xml or other). -- Vie

swagger exclude OPTIONS route in UI

Swagger insists on creating an OPTIONS route which it automatically tests before running a POST. Is there a way to have OPTIONS then not appear in the swagger UI? -- View this message in context: http://camel.465427.n5.nabble.com/swagger-exclude-OPTIONS-route-in-UI-tp5778714.html Sent from the

Re: cxfrs swagger

Just to clarify, I could use swagger with cxf, but not cxfrs and camel? Is there no work around using the cxf with swagger examples to let swagger know about the route url by assignment as in the example below ( so far as I tried this, trouble of this nature: Caused by: java.lang.ClassCastExcepti

cxfrs swagger

I have swagger working with rest dsl, but cxfrs doesn't show. This appears in the window: fetching resource list: http://127.0.0.1:9090/api-docs; Please wait. This appears in the console: Uncaught TypeError: Cannot read property 'definitions' of null Tried updating to camel version 2.16.1 and c

Re: Multiple consumers for the same endpoint is not allowed cxfrs vs rest dsl

Thanks for the correct processor link. I'm summarizing main difference between rest dsl routes and cxfrs routes rest dsl can include the method .get .post .put .delete baked into the route This is an advantage if you want a different route for each http method, whereas the cxfrs has paths, params,

Re: Multiple consumers for the same endpoint is not allowed cxfrs vs rest dsl

performInvocation allows you to use the resource file to match http method type (GET POST PUT DELETE) to a method in the resource file. However, it wipes out the Exchange headers and body, and the return value is set to the Exchange.In body, except when null is returned. There doesn't seem to be

Re: Multiple consumers for the same endpoint is not allowed cxfrs vs rest dsl

Yes, thanks, I was referring the interface, though I was using a resource class instead with return nulls. I think I now have a couple of options, I think I could also get the http method from the exchange and pass to the recipient list, just as the operationName is used though operationName gives

Re: Multiple consumers for the same endpoint is not allowed cxfrs vs rest dsl

I see that with performInvocation, it's possible to get the same effect, but only by giving up the idea and convenience of different routes. You may use one route and have the resource file invoke the method according to the http method, (replacing "return null" with a call to a service I presume)

Multiple consumers for the same endpoint is not allowed cxfrs vs rest dsl

Needing to confirm, with cxfrs you can't use the same url and have the REST application choose the proper route based on the http method POST GET PUT DELETE. With rest dsl you can because the method is part of the route, you have something like rest(url).get(etc I tried to cheat by dividing the sa