Re: [Dev] GSoC Eclipse Plugin for Siddhi

Hi Suho, The code is shared in [1]. The content assistant feature works only when one or two letter(s) of the needed proposal is typed. For example, if the user typed ""define stream inputStream(volume float);" to get inputStream as a suggestion user needs to type "i" or "inp" or some sub string.

[Dev] [ESB Connectors] gmail.sendMailWithAttachment gives an error

Hi, I'm trying to send an email with an attachment using Gmail connector. I'm getting the error below. didn;t receive an email. Any idea what's the issue? http://ws.apache.org/ns/synapse; name="sendEmail" startOnLoad="true" statistics="disable" trace="disable"

Re: [Dev] [ESB Connector] error when working with google drive connector

Hi Amalka, It should be [1]. [1] https://github.com/wso2-extensions/esb-connector-googledriverest/blob/master/src/test/resources/artifacts/ESB/config/proxies/googledriverest/googledriverest.xml#L69 On Sat, Aug 19, 2017 at 7:31 PM, Amalka Subasinghe wrote: > Hi, > > I'm using

Re: [Dev] [ESB Connectors] gmail.sendMailWithAttachment gives an error

tried following formats, since sample template and sample request shows different properties [1] [1] https://docs.wso2.com/display/ESBCONNECTORS/Working+with+Messages+in+Gmail#WorkingwithMessagesinGmail-sendMailWithAttachment with attachement ama...@wso2.com

Re: [Dev] [ESB Connectors] gmail.sendMailWithAttachment gives an error

Hi Amalka, Thanks for pointing the difference and will update the doc. Please try with this proxy[1] and the request[2]. [1] https://github.com/wso2-extensions/esb-connector-gmail/blob/master/src/test/resources/artifacts/ESB/config/proxies/gmail/gmail_sendMailWithAttachment.xml [2]

[Dev] [ESB Connector] error when working with google drive connector

Hi, I'm using esb 5.0.0 and downloaded google drive connector from store.wso2.com and added to the ESB and enabled. When I try to create a proxy service with google drive init operation. it does not allow me to do so..gives an error. amalkasubasin...@gmail.com x

[Dev] Improve Default Claim Handler logic

Hi All, In the current implementation of the DefaultClaimHandler[1] claim handling logic involves the below steps when retrieving claims for local and federated scenarios, 1. Loading local claims and claims mappings 2. Loading all non-empty claims of the user #1 involves several DB calls where