Re: [Architecture] BAM 3.0 REST APIs for AnalyticsDataService / Indexing / Search

Hi Gimantha, AFAIK when writing REST APIs you have use POST verb to create a resource and the resource data should be sent as the POST request body. I totally agree with Sinthuja's comment regarding url pattern of *POST /analytics/{tableName}*. IMO you should not use POST methods to the

Re: [Architecture] [AF] Automate Deployment for Forked Repositories - MT NoneMT Cartridges

Hi, I'll be doing this feature. Will breakdown the implementation to two main phases 1st phase : Implement s2git structure. - Initially this feature will put in to test with the appmgt development in appfactory. 2nd phase : per-developer runtime implementation. Regards,

Re: [Architecture] Process center- Multiple predecessor/successor support for chevron diagram editor

Hi Frank, Currently you have to delete one element after the other. Will add selecting more than one element to delete as well. Thanks Regards, Himasha On Sun, Jan 18, 2015 at 9:06 PM, Frank Leymann fr...@wso2.com wrote: Hi Himasha, thanks for your response! Especially adding the

Re: [Architecture] BAM 3.0 REST APIs for AnalyticsDataService / Indexing / Search

Hi Gimantha, I think following the conventions will be more intuitive to the users, and we should have a proper reason to not follow. And the post request is generally needs to be sent to create the object and the back end is going to decide where to create the tables resource, therefore it

[Architecture] Maintaining carbon-store GitHub repo

Hi all, I have started creating carbon-store GitHub repo as suggested in the mail thread Creating carbon-store GitHub repo. Along with *components* and *features* we will be moving *apps* and *jaggery-modules *into this repo. Finally the main repo structure would be like below. ​ -

Re: [Architecture] Maintaining carbon-store GitHub repo

+1 Thanks ! On Mon, Jan 19, 2015 at 7:33 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Please refer the repo structure mentioned above as below. ​​ Sorry about missing it fist-place. Thanks! -Ayesha On Mon, Jan 19, 2015 at 7:24 PM, Ayesha Dissanayaka aye...@wso2.com wrote:

Re: [Architecture] Improve the way of executing integration and selenium tests in AF

On Mon, Jan 19, 2015 at 10:19 AM, Amalka Subasinghe ama...@wso2.com wrote: Hi all, Currently our integration tests and selenium tests runs separately. My idea is it would be good if we can execute all the tests together. 1. We want to generate the code coverage report after executing two

[Architecture] Connector Scenario

Overview The scenario provides the mechanism to handle the high priority issues in JIRA. Business Scenario We can use the JIRA connector with other connectors to implement the scenario. Jira,Salesforce,Twilio,Gmail and ZohoPeople connectors are used in the scenario. The following steps

Re: [Architecture] Connector Scenario

Hi, The diagram was missing in the mail please find the diagram for the scenario. Thanks, Kathees On Mon, Jan 19, 2015 at 11:21 PM, Kathees Rajendram kath...@wso2.com wrote: Overview The scenario provides the mechanism to handle the high priority issues in JIRA. Business Scenario We

Re: [Architecture] BAM 3.0 REST APIs for AnalyticsDataService / Indexing / Search

Hi Sinduja, Thank you for the feedback. On Mon, Jan 19, 2015 at 12:04 PM, Sinthuja Ragendran sinth...@wso2.com wrote: Hi gimantha, Please see the comments inline. On Sun, Jan 18, 2015 at 11:24 PM, Gimantha Bandara giman...@wso2.com wrote: Hi, Currently, I am working on $subject.