I am not like hierahical interface generated by wadl-client
in Example wadl
https://github.com/rbelouin/wadl-client/blob/master/spec/swagger.js
with path segments (/test/dynamic/{param}) it leads to non-intuitive call
like
var res = client.test.dynamic._.get().withParams(["12345"]).send();
also looking on current version, it has major rewrite since, now it does
not uses promises to dispatch results, but baconjs, which is doubtful
dependency
2015-09-10 16:48 GMT+04:00 Sergey Beryozkin <[email protected]>:
> Thanks for a link, this is quite interesting, having WADL XML converted
> into Swagger JSON, no problems there except that I'm not sure if it can
> cope with converting the XMLSchema grammars into JSON schemas, probably
> unlikely ?
> I linked to it from JIRA, but noted CXF can also optionally offer its own
> WADL JSON representation - which keeps the same structure as WADL XML,
> except that it expects equivalent JSON schemas be available as server
> resources...
> Either way, looks like if this frontend would work with WADL then we can
> get that WADL processed as needed for JS client to operate
>
