@Sanjeewa, I think we have to provide an abstraction from API-M (something like GWInterface) so that an implementation of that GWInterface can dynamically register with API-M through OSGi. That implementation contains all the logic required to publish a given API to the GW that we are planning to integrate with. There will be quite a few things that we have to do this to work, but in the long run this will be quite useful.
@Shiro: Yes, if we manage to do this, theoretically we can integrate with any GW. But I'm not sure whether its a common requirement at the moment. On Mon, Jan 18, 2016 at 11:39 PM, Shiro Kulatilake <[email protected]> wrote: > Hi, > > Are we looking at making it possible to plug in any gateway - i.e. WSO2 or > non-WSO2 ? - If yes that would be great. > However then > - the API definition itself might have to be customizable - or extensible > from a base model > - the "object" that is propagated to the gateway of choice needs to be > anything as well > > Isn't this the same thing that we do with Greg today to publish APIs to > different gateways through registry extensions ? > > Thank you, > Shiro > > On Mon, Jan 18, 2016 at 11:20 PM, Sanjeewa Malalgoda <[email protected]> > wrote: > >> Hi kasun, >> If we consider current architecture publisher will call to rest api admin >> service and push api configurations created using velosity template. If we >> are having similar service in new gateway and created velosity template >> according to new definition we can easily push apis to new gateway. >> If need we may provide extension point to api publishing. Then we will >> have complete API object in extesion and we can publish to any custom >> gateway as we need. >> Store do not need direct service access of gateway. >> >> Thanks >> sanjeewa. >> >> sent from my phone >> On Jan 18, 2016 10:59 PM, "Kasun Indrasiri" <[email protected]> wrote: >> >>> Hi, >>> >>> When it comes to moving API-M to the new GW in the future, I think >>> having the $subject would be really helpful. This would allow us to plug >>> any arbitrary GW impl along with the required wrappers (implementing the >>> API-GW abstractions). >>> >>> WDYT? >>> >>> Thanks, >>> Kasun. >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > > *Shiroshica Kulatilake | Solutions Architect, WSO2 Inc.+94 776523867 > <%2B94%20776523867> * > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
