Hi,
On Thu, Feb 27, 2014 at 11:24 PM, Sumedha Rubasinghe <[email protected]>wrote: > I think we need to consider the real external store effect here. > Assumption on delete possibility is there due to external store being a > WSO2 one right now. > > In reality delete will be possible only if external store provides a way > for that. > Actually with current WSO2 external APIStore publishing feature also,if the original API owner trying to delete his API, he's sending a delete API request to other published wso2 external APIStores. Then the deletion from other wso2 external apistores will happen only,if it allowed from those stores. For example ,if the API published in external wso2 APIStore already having an active subscription,the deletion will not happen from that external APIstore,even the original APIPublisher send the delete request to it. I think,same above approach can be used for other Store type publishing as well.. Thanks; > On Feb 28, 2014 7:33 AM, "Lakmali Baminiwatta" <[email protected]> wrote: > >> Hi Jasintha, >> >> >> On 28 February 2014 05:52, Jasintha Dasanayake <[email protected]> wrote: >> >>> Hi Lakmali >>> >>> Yes, this is a required improvement , there are couple of clients >>> already tried out this feature. AFAIK currently, publisher cannot remove an >>> API once it is published to the external stores. will it be allowed with >>> this improvement ? or have we done that purposely ? >>> >> >> It is possible to delete the API once it is published to the external >> stores. If the original publisher deletes the API, it will get deleted from >> other stores as well. >> >> Thanks, >> Lakmali >> >>> >>> Thanks and Regards >>> /Jasintha >>> >>> >>> On Wed, Feb 26, 2014 at 12:36 PM, Lakmali Baminiwatta >>> <[email protected]>wrote: >>> >>>> Hi all, >>>> >>>> In API Manager 1.5.0, we added the support for publishing an API to >>>> multiple external API Stores [1]. Currently we need to pre configure the >>>> required external stores in the api-manager.xml. Hence we have below >>>> limitations. >>>> >>>> - Can not add external store configurations at runtime. >>>> - External store configuration is global and no way to keep per >>>> tenant configuration. >>>> >>>> >>>> So we are planning to add this configuration to registry, so that >>>> stores can be configured in runtime and also each tenant will have their >>>> own confguration. >>>> >>>> [1]http://docs.wso2.org/display/AM160/Publishing+to+API+Stores >>>> >>>> Thanks, >>>> Lakmali >>>> >>>> -- >>>> Lakmali Baminiwatta >>>> Software Engineer >>>> WSO2, Inc.: http://wso2.com >>>> lean.enterprise.middleware >>>> mobile: +94 71 2335936 >>>> blog : lakmali.com >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> *Jasintha Dasanayake * >>> >>> *Software EngineerWSO2 Inc. | http://wso2.com <http://wso2.com/> lean . >>> enterprise . middleware* >>> >>> >>> *mobile :- 0711368118 <0711368118> * >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Lakmali Baminiwatta >> Software Engineer >> WSO2, Inc.: http://wso2.com >> lean.enterprise.middleware >> mobile: +94 71 2335936 >> blog : lakmali.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 > > -- Lalaji Sureshika WSO2, Inc.; http://wso2.com/ email: [email protected]; cell: +94 71 608 6811 blog: http://lalajisureshika.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
