Re: [Architecture] Proposed ESB connector scenario - Integrating Shopify with MailChimp, Facebook, ZohoCRM, CallRail and Shippo.

Hi Please find the comments for the Shopify Connector below. Authorization flow is not implemented(OAuth 2-get access token from the code). No copyright header in xml configuration files. The year should be 2005-2015 in copyright header in the ShopifyConnectorIntegrationTest.java file.

Re: [Architecture] Proposed ESB connector scenario - Integrating Shopify with MailChimp, Facebook, ZohoCRM, CallRail and Shippo.

Hi Rasika, Can you please give your inside on Kesavan's questions. Specially on Authorization flow is not implemented(OAuth 2-get access token from the code). There are empty fields in the sample request of ‘ listCustomers’ ,’ listFulfillments’,’listOrders’,’’ methods in the

Re: [Architecture] Proposed ESB connector scenario - Integrating Freshdesk with Nexmo, ActiveCollab, Gmail, FluidSurveys and Disqus

Hi, In Freshdesk ConnectorV2 integration test,One method is failing. The readme file says that any valid text can be added for 'noteBody' property but the method checks the different value. I have shared the test failing method. FAILED: testAddNoteWithOptionalParameters FreshDesk

Re: [Architecture] Proposed ESB connector scenario - Integrating PeopleHR with ZohoRecruit, ActiveCollab, ZohoPeople, Deputy and Xero

Hi Rasikah, Please find the comments for the Xero ESB connector below: - Post methods didn't have the checking for mandatory and optional parameters. - Add copyright header in all template files. - The year should be 2005-2015 in copyright header - Copyright (c) 2005-2010,

Re: [Architecture] Proposed ESB connector scenario - Integrating PeopleHR with ZohoRecruit, ActiveCollab, ZohoPeople, Deputy and Xero

Hi rasika, Please let us know why you did not consider about ? - Post methods didn't have the checking for mandatory and optional parameters. On Fri, Jan 16, 2015 at 1:45 PM, Keerthika Mahendralingam keerth...@wso2.com wrote: Hi Rasikah, Please find the comments for the Xero ESB

Re: [Architecture] ESB connector scenario - Integrating Eventbrite with GoToWebinar, Facebook, ConstantContact, Gmail, Nexmo and SurveyMonkey

Hi All, i have reviewed gotowebinar connector. There are some Issues. - Integration tests are skipped because of the error in setting environment. - All methods are working manually. - No copyrights added for all xml configuration files. - Unwanted empty lines and spaces

Re: [Architecture] Proposed ESB connector scenario - Integrating ZOHO CRM with Campaign Monitor, CallRail, Twitter, Facebook, Quickbooks and JIRA

Hi Rasiaka, This mail is regard Zoho CRM - There is no method called getSearchRecords in API,instead of that, they have getSearchRecordsByPDC.It is missing. - Mandatory parameters id and content is missed in File uploading. - All test cases are failed by set Environment error. Can

[Architecture] cApp deployer support for WSO2 CEP

Hi All, Here, the cApp deployer for CEP is also another AppDeploymentHandler implementation which is going to handle the following files specific to CEP product. For below hot-deployable files, 1. eventbuilders 2. eventformatters 3. executionplans 4. inputeventadaptors 5. outputeventadaptors

Re: [Architecture] Proposed ESB connector scenario - Integrating Shopify with MailChimp, Facebook, ZohoCRM, CallRail and Shippo.

Hi, Please find the recommendation for the Shippo connector below. 1. Copyrights headers should be added in each xml configuration files(year should be 2005-2015). 2. The value v1 should be added to apiUrl. 3. There are unwanted empty lines and spaces in all xml configuration files and

Re: [Architecture] cApp deployer support for WSO2 CEP

Looks good, please provide an update on the folder structure. Thanks Suho On Fri, Jan 16, 2015 at 2:26 PM, Ayash ayashkan...@wso2.com wrote: Hi All, Here, the cApp deployer for CEP is also another AppDeploymentHandler implementation which is going to handle the following files specific to

[Architecture] ESB Connector Scenario-Integrating Zoho Invoice with Gmail and Stripe

Hi All, Myself(asha...@wso2.com) and Naasheer Ali(naashe...@wso2.com) propose an ESB Connector Scenario by integrating Zoho Invoice, Gmail and Stripe together. Please find document below: https://docs.google.com/a/wso2.com/document/d/1f5t4D8T3P5MAqmfkMkqbzHqGRuaCSfdmSXzcTPzoRb0/edit Thank

Re: [Architecture] ESB Connector Scenario-Integrating Zoho Invoice with Gmail and Stripe

*Overview* Zoho Invoice is a simple, intuitive invoicing software designed to help you craft the perfect invoice, track payments and get paid faster online *Benifits* Zoho allows to focus on the business to get more sales, get paid, support the customers and make the business more productive.

Re: [Architecture] Default version number when switching the build to released versions of jars

Our goal is to release components independently of each other. This means we are considering components as individual projects. Unique group IDs will help us to manage them better, specially in nexus. I am not quite sure of releasing 1.0.0 version of existing components. This will confuse our

[Architecture] ESB Connector Scenario - Integrating Teamwork with JIRA, Gmail, FreshBooks and Stripe

Overview Teamwork is a collaborative project management system which provides a simple way to manage teams and projects. Benefits of Teamwork - Teamwork provides project management facilities such as task management, file sharing, time tracking, milestone tracking, etc. - The

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

Hi Frank, Please find below comments/answers regarding the queries. 1. Can we add arrow heads to the lines between the phases (aka individual chevrons)? E.g. in later releases we will likely support to draw directed graphs without inferring the direction of an arrow

[Architecture] Replacing BAM Toolbox Format with CAR

Hi everyone, From BAM 3.0, we are thinking of replacing the toolbox packaging to CAR files. The main motive for this came with CEP also requiring a packaging format for their artifacts. So either, they also needed to use our toolbox format, or else, go to a CAR packaging format, which is used