IMO combining API definition can lead to many conflicts not just the resources eg. Definitions , Parameters. Thus +1 for suggested approach which is a better solution then combining definitions.
Regards Jo On Tue, Jul 12, 2016 at 7:58 AM, Abimaran Kugathasan <[email protected]> wrote: > Hi All, > > In API Manager 2.0, we are supporting generating SDK of APIs through > Swagger. Currently, we are combining APIs a user has subscribed through an > OAuth application and generates one SDK for all his APIs. > > Problem with this approach is, we are combining subscribed APIs together > and generate the SDK, and the generated SDK has one Java class (in case of > JAVA SDK) to represent the subscribed APIs. And, for each resource we > defined in the APIs, Swagger generates corresponding method with that > resource name. If we have two resource with same name in two different > APIs, then there will be only one method and it's not consistent. > > > As I checked, we can provide one Swagger json file to Swagger Generator > for generating SDK. What will be the best approach to generate SDK for > subscribed APIs. > > Shall we generate SDK for each subscribed API rather than for each Oauth > Application? Because there are lesser chances for requirement to have one > SDK for all the subscribed APIs > > > > -- > Thanks > Abimaran Kugathasan > Senior Software Engineer > > Email : [email protected] > Mobile : +94 773922820 > > <http://stackoverflow.com/users/515034> > <http://lk.linkedin.com/in/abimaran> > <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> > <https://twitter.com/abimaran> > > -- -- *Joseph Fonseka* WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 772 512 430 skype: jpfonseka * <http://lk.linkedin.com/in/rumeshbandara>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
