Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is Kikaha JAX-RS compliant? #126

Closed
sixman9 opened this issue Jan 12, 2016 · 3 comments
Closed

Is Kikaha JAX-RS compliant? #126

sixman9 opened this issue Jan 12, 2016 · 3 comments

Comments

@sixman9
Copy link

sixman9 commented Jan 12, 2016

It would be great to be able to generate at least WADL or better still Swagger 2.0, to automate client code stub generation.

Thanks

@miere
Copy link

miere commented Jan 12, 2016

Hi @sixman9

Thanks for asking. Kikaha has an API which design looks quite similar to JAX-RS. It is called uRouting API (micro Routing). This choice was made because the JAX-RS license (CDDL 1.1 or GPL2) isn't quite friendly for enterprise development (we already faced some issues regarding this).

Code stub generation is awesome, we were planning to put it on the road for 1.7.0 version. We have created the issue #29 late on 2014 (shame on us... heheh). At that time, Swagger seems to be the right choice for client generation but there is a lot of Code Generator today (although Swagger still the most popular choice).

Have you ever used another Code Generator. Is Swagger the best today (or good enough)?

@sizebay
Copy link

sizebay commented Jan 15, 2016

Hi @miere

There is a nice discussion about this topic at Hacker News that can bring you enlights you to choose which API should be the first one Kikaha will be compatible (if choose one, it doesn't mean that you can make it compatible with another one).

Although, our team have used Swagger for a few months and all we can say is it has been an awesome experience. There is a lot of useful tools that is Swagger compatible and it made our life easier.

Regards

@miere
Copy link

miere commented Feb 8, 2016

I'm closing this issue, once it is a duplicated issue from #29.
@sixman9, please, keep track of this topic at #29 from now on.

@miere miere closed this as completed Feb 8, 2016
@miere miere added the question label Feb 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants