[Dev] [GSOC][Siddhi][PySiddhi] Sincere Thanks and Future Contributions
Dear All, This mail is to thank everyone who helped me to successfully complete *Google Summer of Code 2017* with project *PySiddhi*. I was able to learn a lot via the project, specially on areas such as *JNI*, *Python Native Programming* and *developing Python Wrappers to Java.* In overall, it has been a great experience and I am grateful for everyone who helped me. Special thanks must go to *Grainier,* *Suho *and *Anjana*, whom helped me throughout as mentors of the project. Also I must thank *Mohan* and *Ramindu* for the help given. I would like to continue my contribution to the project in the future and would like to discuss on how it can be taken forward. GitHub Link: https://github.com/wso2/PySiddhi GSoC Work Summary: https://gist.github.com/madhawav/195b7dc601d94c40958d88be1d56e705 Kind Regards, -- *Madhawa Vidanapathirana* Student Department of Computer Science and Engineering University of Moratuwa Sri Lanka Mobile: (+94) 716874425 Email: madhawavidanapathir...@gmail.com Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSOC][Siddhi][DEV] Deployment and Code Management of PySiddhi
Hi, I have sent the new PRs [1] [2] which merge WSO2 DAS Client with PySiddhi. The Wiki [3] has also been updated, which would require a manual merge since PRs are not possible for GitHub Wikis. Kindly reach me if any changes are required. [1] https://github.com/wso2/PySiddhi/pull/3 [2] https://github.com/wso2/PySiddhi/pull/4 [3] https://github.com/madhawav/PySiddhi/wiki Regards, Madhawa On Fri, Aug 18, 2017 at 7:27 PM, Madhawa Vidanapathirana < madhawavidanapathir...@gmail.com> wrote: > Hi, > > I just noticed that it is not possible to send PRs on Wiki pages I made > for the project, that are available at [1]. I believe a collaborator of > main repository [2] would have to manually review the wiki at [1] and get > it copied to main repository [2]. > > The link [3] describes a technique which can be useful to copy the wiki > pages from [1] to [2]. > > Also, I am looking forward for your comments on updated PRs I sent to > branches master and 3.x of main repository [2]. > > [1] - https://github.com/madhawav/PySiddhi/wiki > [2] - https://github.com/wso2/PySiddhi > [3] - https://stackoverflow.com/questions/10642928/how-to- > pull-request-a-wiki-page-on-github > > Kind Regards, > Madhawa > > On Thu, Aug 10, 2017 at 11:02 AM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> >> I have sent PRs to both branches 3.x and master of [1] with relevant code >> versions. >> Kindly review and let me know any changes that are required. >> >> Meanwhile, I will check on generation of *.whl files which are required >> for distribution to PyPI. >> >> [1] https://github.com/wso2/pysiddhi >> >> Kind Regards, >> Madhawa >> >> On Wed, Aug 9, 2017 at 5:03 PM, Grainier Perera <grain...@wso2.com> >> wrote: >> >>> Hi Madhawa, >>> >>> I have created a branch for PySiddhi 3.x at [1], and we are thinking of >>> maintaining the PySiddhi 4.x in the master branch. Please send PRs to 3.x >>> branch and master branch. >>> >>> [1] https://github.com/wso2/pysiddhi/tree/3.x >>> >>> Regards, >>> >>> On Wed, Aug 9, 2017 at 9:17 AM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I have prepared the branch for PySiddhi 3.1 (in fork of main repo) and >>>> it is available at [1]. However, I am unable to send the PR since 3.1 >>>> branch is not in the main repository at [2]. >>>> >>>> Also, would be requiring a branch for 4.0 to PR the 4.0 version which >>>> will be ready soon. >>>> >>>> [1] https://github.com/madhawav/PySiddhi/tree/3.1 >>>> [2] https://github.com/wso2/PySiddhi >>>> >>>> Kind Regards, >>>> >>>> -- >>>> *Madhawa Vidanapathirana* >>>> Student >>>> Department of Computer Science and Engineering >>>> University of Moratuwa >>>> Sri Lanka >>>> >>>> Mobile: (+94) 716874425 <+94%2071%20687%204425> >>>> Email: madhawavidanapathir...@gmail.com >>>> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 >>>> >>> >>> >>> >>> -- >>> Grainier Perera >>> Senior Software Engineer >>> Mobile : +94716122384 <+94%2071%20612%202384> >>> WSO2 Inc. | http://wso2.com >>> lean.enterprise.middleware >>> >> >> >> >> -- >> *Madhawa Vidanapathirana* >> Student >> Department of Computer Science and Engineering >> University of Moratuwa >> Sri Lanka >> >> Mobile: (+94) 716874425 <+94%2071%20687%204425> >> Email: madhawavidanapathir...@gmail.com >> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 >> > > > > -- > *Madhawa Vidanapathirana* > Student > Department of Computer Science and Engineering > University of Moratuwa > Sri Lanka > > Mobile: (+94) 716874425 <+94%2071%20687%204425> > Email: madhawavidanapathir...@gmail.com > Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 > -- *Madhawa Vidanapathirana* Student Department of Computer Science and Engineering University of Moratuwa Sri Lanka Mobile: (+94) 716874425 Email: madhawavidanapathir...@gmail.com Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSOC][Siddhi][DEV] Deployment and Code Management of PySiddhi
Hi, I just noticed that it is not possible to send PRs on Wiki pages I made for the project, that are available at [1]. I believe a collaborator of main repository [2] would have to manually review the wiki at [1] and get it copied to main repository [2]. The link [3] describes a technique which can be useful to copy the wiki pages from [1] to [2]. Also, I am looking forward for your comments on updated PRs I sent to branches master and 3.x of main repository [2]. [1] - https://github.com/madhawav/PySiddhi/wiki [2] - https://github.com/wso2/PySiddhi [3] - https://stackoverflow.com/questions/10642928/how-to-pull-request-a-wiki-page-on-github Kind Regards, Madhawa On Thu, Aug 10, 2017 at 11:02 AM, Madhawa Vidanapathirana < madhawavidanapathir...@gmail.com> wrote: > Hi, > > I have sent PRs to both branches 3.x and master of [1] with relevant code > versions. > Kindly review and let me know any changes that are required. > > Meanwhile, I will check on generation of *.whl files which are required > for distribution to PyPI. > > [1] https://github.com/wso2/pysiddhi > > Kind Regards, > Madhawa > > On Wed, Aug 9, 2017 at 5:03 PM, Grainier Perera <grain...@wso2.com> wrote: > >> Hi Madhawa, >> >> I have created a branch for PySiddhi 3.x at [1], and we are thinking of >> maintaining the PySiddhi 4.x in the master branch. Please send PRs to 3.x >> branch and master branch. >> >> [1] https://github.com/wso2/pysiddhi/tree/3.x >> >> Regards, >> >> On Wed, Aug 9, 2017 at 9:17 AM, Madhawa Vidanapathirana < >> madhawavidanapathir...@gmail.com> wrote: >> >>> Hi, >>> >>> I have prepared the branch for PySiddhi 3.1 (in fork of main repo) and >>> it is available at [1]. However, I am unable to send the PR since 3.1 >>> branch is not in the main repository at [2]. >>> >>> Also, would be requiring a branch for 4.0 to PR the 4.0 version which >>> will be ready soon. >>> >>> [1] https://github.com/madhawav/PySiddhi/tree/3.1 >>> [2] https://github.com/wso2/PySiddhi >>> >>> Kind Regards, >>> >>> -- >>> *Madhawa Vidanapathirana* >>> Student >>> Department of Computer Science and Engineering >>> University of Moratuwa >>> Sri Lanka >>> >>> Mobile: (+94) 716874425 <+94%2071%20687%204425> >>> Email: madhawavidanapathir...@gmail.com >>> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 >>> >> >> >> >> -- >> Grainier Perera >> Senior Software Engineer >> Mobile : +94716122384 <+94%2071%20612%202384> >> WSO2 Inc. | http://wso2.com >> lean.enterprise.middleware >> > > > > -- > *Madhawa Vidanapathirana* > Student > Department of Computer Science and Engineering > University of Moratuwa > Sri Lanka > > Mobile: (+94) 716874425 <+94%2071%20687%204425> > Email: madhawavidanapathir...@gmail.com > Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 > -- *Madhawa Vidanapathirana* Student Department of Computer Science and Engineering University of Moratuwa Sri Lanka Mobile: (+94) 716874425 Email: madhawavidanapathir...@gmail.com Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSOC][Siddhi][DEV] Deployment and Code Management of PySiddhi
Hi, I have sent PRs to both branches 3.x and master of [1] with relevant code versions. Kindly review and let me know any changes that are required. Meanwhile, I will check on generation of *.whl files which are required for distribution to PyPI. [1] https://github.com/wso2/pysiddhi Kind Regards, Madhawa On Wed, Aug 9, 2017 at 5:03 PM, Grainier Perera <grain...@wso2.com> wrote: > Hi Madhawa, > > I have created a branch for PySiddhi 3.x at [1], and we are thinking of > maintaining the PySiddhi 4.x in the master branch. Please send PRs to 3.x > branch and master branch. > > [1] https://github.com/wso2/pysiddhi/tree/3.x > > Regards, > > On Wed, Aug 9, 2017 at 9:17 AM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> >> I have prepared the branch for PySiddhi 3.1 (in fork of main repo) and it >> is available at [1]. However, I am unable to send the PR since 3.1 branch >> is not in the main repository at [2]. >> >> Also, would be requiring a branch for 4.0 to PR the 4.0 version which >> will be ready soon. >> >> [1] https://github.com/madhawav/PySiddhi/tree/3.1 >> [2] https://github.com/wso2/PySiddhi >> >> Kind Regards, >> >> -- >> *Madhawa Vidanapathirana* >> Student >> Department of Computer Science and Engineering >> University of Moratuwa >> Sri Lanka >> >> Mobile: (+94) 716874425 <+94%2071%20687%204425> >> Email: madhawavidanapathir...@gmail.com >> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 >> > > > > -- > Grainier Perera > Senior Software Engineer > Mobile : +94716122384 <+94%2071%20612%202384> > WSO2 Inc. | http://wso2.com > lean.enterprise.middleware > -- *Madhawa Vidanapathirana* Student Department of Computer Science and Engineering University of Moratuwa Sri Lanka Mobile: (+94) 716874425 Email: madhawavidanapathir...@gmail.com Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [GSOC][Siddhi][DEV] Deployment and Code Management of PySiddhi
Hi, I have prepared the branch for PySiddhi 3.1 (in fork of main repo) and it is available at [1]. However, I am unable to send the PR since 3.1 branch is not in the main repository at [2]. Also, would be requiring a branch for 4.0 to PR the 4.0 version which will be ready soon. [1] https://github.com/madhawav/PySiddhi/tree/3.1 [2] https://github.com/wso2/PySiddhi Kind Regards, -- *Madhawa Vidanapathirana* Student Department of Computer Science and Engineering University of Moratuwa Sri Lanka Mobile: (+94) 716874425 Email: madhawavidanapathir...@gmail.com Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSOC][DAS][DEV] Python Client on DAS 4.0
Hi, I have implemented the endpoints related to Saving, Updating, Listing, Retrieving and Updating of Siddhi Apps in DAS 4.0. Endpoints related to backing and restoring states of DAS 4.0 are yet to be implemented. I have pushed the code with tests to [1]. [1] https://github.com/madhawav/DASPythonClient Also, @Mohan, thank you for directing me to new documentation. Kind Regards, Madhawa On Sun, Jul 16, 2017 at 2:39 PM, Mohanadarshan Vivekanandalingam < mo...@wso2.com> wrote: > > > On Sat, Jul 15, 2017 at 9:24 PM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> >> Where can I find the up to date REST endpoints for DAS 4.0? >> >> The endpoints I am aware so far are available at [1] but they seem to be >> not working (probably outdated). >> >> I tried sending a post request to Endpoint 1 in [1] ( >> http://localhost:9090/siddhi/artifact/deploy) with a Siddhi App as plain >> text request body but the response I got was "Problem accessing: >> /siddhi/artifact/deploy. Reason: Not Found". Postman was used for sending >> the request. >> >> [1] - https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMO >> vt2JHh9RJya2VdHlHOTl4/edit?usp=sharing >> > > Above is outdated. Please refer [0] for latest Siddhi-App APIs. Please use > "admin:admin" as the credentials.. > > [0] https://docs.wso2.com/display/DAS400/apidocs/siddhiapps/ > > Thanks, > Mohan > > >> >> Kind Regards, >> Madhawa >> >> >> >> On Sat, Jul 8, 2017 at 12:47 PM, Sriskandarajah Suhothayan <s...@wso2.com >> > wrote: >> >>> @Ramindu >>> >>> Do we have a doc that has different options that we can have for >>> simulation. If so please share. >>> >>> On Fri, Jul 7, 2017 at 11:18 PM Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> So far I've managed to implement the REST endpoints of Event Simulator >>>> mentioned at [1]. The code is available at repository [2]. >>>> >>>> The objects passed to REST API has been mapped to Python Classes. All >>>> the fields mentioned in POSTMAN samples (attached) given by Ramindu has >>>> been added to the classes. Additionally, most of the POSTMAN samples has >>>> been implemented as tests in Python Code. >>>> >>>> Is their any technique I can use to identify the possible fields of any >>>> object that could be passed to REST API? >>>> >>>> [1] - https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMO >>>> vt2JHh9RJya2VdHlHOTl4/edit?usp=sharing >>>> [2] - https://github.com/madhawav/DASPythonClient >>>> >>>> Kind Regards, >>>> Madhawa >>>> >>>> -- >>>> *Madhawa Vidanapathirana* >>>> Student >>>> Department of Computer Science and Engineering >>>> University of Moratuwa >>>> Sri Lanka >>>> >>>> Mobile: (+94) 716874425 <+94%2071%20687%204425> >>>> Email: madhawavidanapathir...@gmail.com >>>> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 >>>> >>> -- >>> >>> *S. Suhothayan* >>> Associate Director / Architect >>> *WSO2 Inc. *http://wso2.com >>> * <http://wso2.com/>* >>> lean . enterprise . middleware >>> >>> >>> *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog: >>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >>> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* >>> >> >> >> >> -- >> *Madhawa Vidanapathirana* >> Student >> Department of Computer Science and Engineering >> University of Moratuwa >> Sri Lanka >> >> Mobile: (+94) 716874425 <+94%2071%20687%204425> >> Email: madhawavidanapathir...@gmail.com >> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 >> > > > > -- > *V. Mohanadarshan* > *Associate Tech Lead,* > *Data Technologies Team,* > *WSO2, Inc. http://wso2.com <http://wso2.com> * > *lean.enterprise.middleware.* > > email: mo...@wso2.com > phone:(+94) 771117673 <+94%2077%20111%207673> > -- *Madhawa Vidanapathirana* Student Department of Computer Science and Engineering University of Moratuwa Sri Lanka Mobile: (+94) 716874425 Email: madhawavidanapathir...@gmail.com Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSOC][DAS][DEV] Python Client on DAS 4.0
Hi, Where can I find the up to date REST endpoints for DAS 4.0? The endpoints I am aware so far are available at [1] but they seem to be not working (probably outdated). I tried sending a post request to Endpoint 1 in [1] ( http://localhost:9090/siddhi/artifact/deploy) with a Siddhi App as plain text request body but the response I got was "Problem accessing: /siddhi/artifact/deploy. Reason: Not Found". Postman was used for sending the request. [1] - https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt2JHh9RJya2VdHlHOTl4/edit?usp=sharing Kind Regards, Madhawa On Sat, Jul 8, 2017 at 12:47 PM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > @Ramindu > > Do we have a doc that has different options that we can have for > simulation. If so please share. > > On Fri, Jul 7, 2017 at 11:18 PM Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> >> So far I've managed to implement the REST endpoints of Event Simulator >> mentioned at [1]. The code is available at repository [2]. >> >> The objects passed to REST API has been mapped to Python Classes. All the >> fields mentioned in POSTMAN samples (attached) given by Ramindu has been >> added to the classes. Additionally, most of the POSTMAN samples has been >> implemented as tests in Python Code. >> >> Is their any technique I can use to identify the possible fields of any >> object that could be passed to REST API? >> >> [1] - https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt2JHh9 >> RJya2VdHlHOTl4/edit?usp=sharing >> [2] - https://github.com/madhawav/DASPythonClient >> >> Kind Regards, >> Madhawa >> >> -- >> *Madhawa Vidanapathirana* >> Student >> Department of Computer Science and Engineering >> University of Moratuwa >> Sri Lanka >> >> Mobile: (+94) 716874425 <+94%2071%20687%204425> >> Email: madhawavidanapathir...@gmail.com >> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 >> > -- > > *S. Suhothayan* > Associate Director / Architect > *WSO2 Inc. *http://wso2.com > * <http://wso2.com/>* > lean . enterprise . middleware > > > *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog: > http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: > http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: > http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* > -- *Madhawa Vidanapathirana* Student Department of Computer Science and Engineering University of Moratuwa Sri Lanka Mobile: (+94) 716874425 Email: madhawavidanapathir...@gmail.com Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [GSOC][DAS][DEV] Python Client on DAS 4.0
Hi, So far I've managed to implement the REST endpoints of Event Simulator mentioned at [1]. The code is available at repository [2]. The objects passed to REST API has been mapped to Python Classes. All the fields mentioned in POSTMAN samples (attached) given by Ramindu has been added to the classes. Additionally, most of the POSTMAN samples has been implemented as tests in Python Code. Is their any technique I can use to identify the possible fields of any object that could be passed to REST API? [1] - https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt2JHh9RJya2VdHlHOTl4/edit?usp=sharing [2] - https://github.com/madhawav/DASPythonClient Kind Regards, Madhawa -- *Madhawa Vidanapathirana* Student Department of Computer Science and Engineering University of Moratuwa Sri Lanka Mobile: (+94) 716874425 Email: madhawavidanapathir...@gmail.com Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 simulator.postman_collection Description: Binary data ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSOC][DAS][DEV] Incorrect response from DAS 4.0 Event Simulator
Hi Ramindu,
Thank you for the postman samples and quick fix.
After following the procedure you mentioned, I am getting a proper JSON
response from DAS 4.
Regards,
Madhawa
On Wed, Jul 5, 2017 at 12:59 PM, Ramindu De Silva <ramin...@wso2.com> wrote:
> Hi Madhawa,
>
> Please find some postman samples. In some you may have to change the
> "executionPlanName" to "siddhiAppName" is several JSON request bodies.
>
> Best Regards,
> Ramindu.
>
> On Wed, Jul 5, 2017 at 12:47 PM, Ramindu De Silva <ramin...@wso2.com>
> wrote:
>
>> Hi Madhawa,
>>
>> You'll have to clone carbon analytics repo[1]. And then, in the root pom
>> file of product das[2], you will have to change the
>> carbon.analytics.version in the properties section. eg:
>> 2.0.45-SNAPSHOT
>> You will be able to find the version in the carbon analytics from the
>> carbon analytics repo[1]'s root pom file.
>> Then build carbon analytics repo[1]. And then build product das[2].
>>
>>
>> [1] https://github.com/wso2/carbon-analytics
>> [2] https://github.com/wso2/product-das
>>
>> Best Regards,
>>
>>
>> On Wed, Jul 5, 2017 at 12:34 PM, Madhawa Vidanapathirana <
>> madhawavidanapathir...@gmail.com> wrote:
>>
>>> Hi Ramindu,
>>>
>>> I am working with the* product das *repository [1] and the* issue is
>>> still there*. I did a new clone from master branch and did a mvn
>>> install.
>>>
>>> The steps I took are as follows.
>>>
>>>1. Obtained a new clone of repository
>>>2. mvn install
>>>3. Unzipped wso2das-4.0.0-SNAPSHOT.zip created by maven build
>>>4. Started bin/worker.sh
>>>5. Saved a new configuration using POST http://:
>>>/simulation/feed/
>>>6. Waited for 5 seconds
>>>7. Retrieved the saved configuration using GET http://
>>>:/simulation/feed/{simulationName}
>>>
>>>
>>> [1] - https://github.com/wso2/product-das
>>>
>>>
>>>
>>> On Wed, Jul 5, 2017 at 11:01 AM, Ramindu De Silva <ramin...@wso2.com>
>>> wrote:
>>>
>>>> Hi Madhawa,
>>>>
>>>> We have fixed the issue. Please check and let us know.
>>>>
>>>> Thanks,
>>>> Ramindu.
>>>>
>>>> On Wed, Jul 5, 2017 at 10:33 AM, Ramindu De Silva <ramin...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Madhawa,
>>>>>
>>>>> Yes, Simulation configuration should be within inverted commas. I
>>>>> will fix it and let you know.
>>>>>
>>>>> Best Regards,
>>>>> Ramindu.
>>>>>
>>>>> On Wed, Jul 5, 2017 at 9:49 AM, Madhawa Vidanapathirana <
>>>>> madhawavidanapathir...@gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>> Small correction to my previous mail, actually I was using *GET*
>>>>>> http://:/simulation/feed/{simulationName}, and
>>>>>> got the mentioned response from it. I was *not* using
>>>>>> /simulation/single endpoint.
>>>>>>
>>>>>> Any help you can provide is most welcome!
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 5, 2017 at 9:41 AM, Sriskandarajah Suhothayan <
>>>>>> s...@wso2.com> wrote:
>>>>>>
>>>>>>> I don't think you can send a simulation config by calling http://
>>>>>>> :/simulation/single/
>>>>>>>
>>>>>>> @Mohan/Ramindu can you guide him on the API of DAS 4.0 Event
>>>>>>> Simulation
>>>>>>>
>>>>>>> On Tue, Jul 4, 2017 at 9:48 PM, Madhawa Vidanapathirana <
>>>>>>> madhawavidanapathir...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I am currently working on developing a Python Client for DAS 4.0
>>>>>>>> Event Simulator as a part of my GSOC project with WSO2.
>>>>>>>>
>>>>>>>> When I used the REST endpoint *GET* http://:/s
>>>>>>>> imulation/single/{simulationName}, I get a JSON response with an
>>>>>>>> incorrect field value.
>>>>>>>>
>>>>>>>> The JSON response consist of two string fields "status" and
>>>
Re: [Dev] [GSOC][DAS][DEV] Incorrect response from DAS 4.0 Event Simulator
Hi Ramindu,
I am working with the* product das *repository [1] and the* issue is still
there*. I did a new clone from master branch and did a mvn install.
The steps I took are as follows.
1. Obtained a new clone of repository
2. mvn install
3. Unzipped wso2das-4.0.0-SNAPSHOT.zip created by maven build
4. Started bin/worker.sh
5. Saved a new configuration using POST http://:
/simulation/feed/
6. Waited for 5 seconds
7. Retrieved the saved configuration using GET http://
:/simulation/feed/{simulationName}
[1] - https://github.com/wso2/product-das
On Wed, Jul 5, 2017 at 11:01 AM, Ramindu De Silva <ramin...@wso2.com> wrote:
> Hi Madhawa,
>
> We have fixed the issue. Please check and let us know.
>
> Thanks,
> Ramindu.
>
> On Wed, Jul 5, 2017 at 10:33 AM, Ramindu De Silva <ramin...@wso2.com>
> wrote:
>
>> Hi Madhawa,
>>
>> Yes, Simulation configuration should be within inverted commas. I will
>> fix it and let you know.
>>
>> Best Regards,
>> Ramindu.
>>
>> On Wed, Jul 5, 2017 at 9:49 AM, Madhawa Vidanapathirana <
>> madhawavidanapathir...@gmail.com> wrote:
>>
>>> Hi,
>>> Small correction to my previous mail, actually I was using *GET* http://
>>> :/simulation/feed/{simulationName}, and got the
>>> mentioned response from it. I was *not* using /simulation/single
>>> endpoint.
>>>
>>> Any help you can provide is most welcome!
>>>
>>>
>>> On Wed, Jul 5, 2017 at 9:41 AM, Sriskandarajah Suhothayan <s...@wso2.com
>>> > wrote:
>>>
>>>> I don't think you can send a simulation config by calling http://
>>>> :/simulation/single/
>>>>
>>>> @Mohan/Ramindu can you guide him on the API of DAS 4.0 Event Simulation
>>>>
>>>> On Tue, Jul 4, 2017 at 9:48 PM, Madhawa Vidanapathirana <
>>>> madhawavidanapathir...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am currently working on developing a Python Client for DAS 4.0 Event
>>>>> Simulator as a part of my GSOC project with WSO2.
>>>>>
>>>>> When I used the REST endpoint *GET* http://:/s
>>>>> imulation/single/{simulationName}, I get a JSON response with an
>>>>> incorrect field value.
>>>>>
>>>>> The JSON response consist of two string fields "status" and "message"
>>>>> where the value of "message" is an *invalid JSON text* describing a
>>>>> Simulation Configuration. For example, the following is a message field I
>>>>> got from DAS 4.0.
>>>>>
>>>>> Simulation configuration : {"sources":[{"timeStampInterva
>>>>> l":"5","simulationType":"RANDOM_DATA_SIMULATION","attributeC
>>>>> onfiguration":[{"length":"10","type":"PRIMITIVE_BASED"},{"mi
>>>>> n":"3","max":"3","precision":"2","type":"PRIMITIVE_B
>>>>> ASED"},{"min":"300","max":"300","type":"PRIMITIVE_BASED"}],"
>>>>> streamName":"FooStream","siddhiAppName":"TestSiddhiApp"}],"
>>>>> properties":{"timestampStartTime":"1488615136958","simulatio
>>>>> nName":"simulationPrimitive","timeInterval":"1000","
>>>>> timestampEndTime":null,"noOfEvents":"8"}}
>>>>>
>>>>> In the above, Simulation configuration should be within inverted
>>>>> commas, such as "Simulation Configuration" to properly support JSON
>>>>> parsing. (tested with standard JSON parser of Python3)
>>>>>
>>>>> P.s. I am using DAS 4.0, latest version from master branch.
>>>>>
>>>>> Kind Regards,
>>>>> --
>>>>> *Madhawa Vidanapathirana*
>>>>> Student
>>>>> Department of Computer Science and Engineering
>>>>> University of Moratuwa
>>>>> Sri Lanka
>>>>>
>>>>> Mobile: (+94) 716874425 <071%20687%204425>
>>>>> Email: madhawavidanapathir...@gmail.com
>>>>> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94
>>>>>
>>>>
>>&
Re: [Dev] [GSOC][DAS][DEV] Incorrect response from DAS 4.0 Event Simulator
Hi,
Small correction to my previous mail, actually I was using *GET* http://
:/simulation/feed/{simulationName}, and got the
mentioned response from it. I was *not* using /simulation/single endpoint.
Any help you can provide is most welcome!
On Wed, Jul 5, 2017 at 9:41 AM, Sriskandarajah Suhothayan <s...@wso2.com>
wrote:
> I don't think you can send a simulation config by calling http://
> :/simulation/single/
>
> @Mohan/Ramindu can you guide him on the API of DAS 4.0 Event Simulation
>
> On Tue, Jul 4, 2017 at 9:48 PM, Madhawa Vidanapathirana <
> madhawavidanapathir...@gmail.com> wrote:
>
>> Hi,
>>
>> I am currently working on developing a Python Client for DAS 4.0 Event
>> Simulator as a part of my GSOC project with WSO2.
>>
>> When I used the REST endpoint *GET* http://:/s
>> imulation/single/{simulationName}, I get a JSON response with an
>> incorrect field value.
>>
>> The JSON response consist of two string fields "status" and "message"
>> where the value of "message" is an *invalid JSON text* describing a
>> Simulation Configuration. For example, the following is a message field I
>> got from DAS 4.0.
>>
>> Simulation configuration : {"sources":[{"timeStampInterva
>> l":"5","simulationType":"RANDOM_DATA_SIMULATION","attri
>> buteConfiguration":[{"length":"10","type":"PRIMITIVE_BASED"}
>> ,{"min":"3","max":"3","precision":"2","type":"PRIMIT
>> IVE_BASED"},{"min":"300","max":"300","type":"PRIMITIVE_
>> BASED"}],"streamName":"FooStream","siddhiAppName":"
>> TestSiddhiApp"}],"properties":{"timestampStartTime":"1488615
>> 136958","simulationName":"simulationPrimitive","timeInterval
>> ":"1000","timestampEndTime":null,"noOfEvents":"8"}}
>>
>> In the above, Simulation configuration should be within inverted commas,
>> such as "Simulation Configuration" to properly support JSON parsing.
>> (tested with standard JSON parser of Python3)
>>
>> P.s. I am using DAS 4.0, latest version from master branch.
>>
>> Kind Regards,
>> --
>> *Madhawa Vidanapathirana*
>> Student
>> Department of Computer Science and Engineering
>> University of Moratuwa
>> Sri Lanka
>>
>> Mobile: (+94) 716874425 <071%20687%204425>
>> Email: madhawavidanapathir...@gmail.com
>> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94
>>
>
>
>
> --
>
> *S. Suhothayan*
> Associate Director / Architect
> *WSO2 Inc. *http://wso2.com
> * <http://wso2.com/>*
> lean . enterprise . middleware
>
>
> *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog:
> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter:
> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in:
> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
>
--
*Madhawa Vidanapathirana*
Student
Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka
Mobile: (+94) 716874425
Email: madhawavidanapathir...@gmail.com
Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [GSOC][DAS][DEV] Incorrect response from DAS 4.0 Event Simulator
Hi,
I am currently working on developing a Python Client for DAS 4.0 Event
Simulator as a part of my GSOC project with WSO2.
When I used the REST endpoint *GET* http://
:/simulation/single/{simulationName}, I get a JSON
response with an incorrect field value.
The JSON response consist of two string fields "status" and "message" where
the value of "message" is an *invalid JSON text* describing a Simulation
Configuration. For example, the following is a message field I got from DAS
4.0.
Simulation configuration :
{"sources":[{"timeStampInterval":"5","simulationType":"RANDOM_DATA_SIMULATION","attributeConfiguration":[{"length":"10","type":"PRIMITIVE_BASED"},{"min":"3","max":"3","precision":"2","type":"PRIMITIVE_BASED"},{"min":"300","max":"300","type":"PRIMITIVE_BASED"}],"streamName":"FooStream","siddhiAppName":"TestSiddhiApp"}],"properties":{"timestampStartTime":"1488615136958","simulationName":"simulationPrimitive","timeInterval":"1000","timestampEndTime":null,"noOfEvents":"8"}}
In the above, Simulation configuration should be within inverted commas,
such as "Simulation Configuration" to properly support JSON parsing.
(tested with standard JSON parser of Python3)
P.s. I am using DAS 4.0, latest version from master branch.
Kind Regards,
--
*Madhawa Vidanapathirana*
Student
Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka
Mobile: (+94) 716874425
Email: madhawavidanapathir...@gmail.com
Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Siddhi] [Bug] [GSoC] Issue in releaseBreakPoint of Siddhi Debugger
Hi,
I wrote the following code snippet on releaseBreakPoint feature of
siddhiDebugger (Siddhi4.0.0-M5-SNAPSHOT) but the breakpoint doesn't get
released.
*Am I doing something wrong here? Or is it a bug with Siddhi Debugger since
its still in development?*
> siddhiDebugger.acquireBreakPoint("query 1", SiddhiDebugger.QueryTerminal.IN);
>
> inputHandler.send(new Object[]{"WSO2", 50f, 60});
> //Debugger Callback is triggered twice as expected
>
> siddhiDebugger.releaseBreakPoint("query 1", SiddhiDebugger.QueryTerminal.IN);
>
> inputHandler.send(new Object[]{"WSO2", 70f, 40});
>
> //Debugger Callback is triggered twice. (Not expected)
>
>
Thanks and Regards,
Madhawa
--
*Madhawa Vidanapathirana*
Student
Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka
Mobile: (+94) 716874425
Email: madhawavidanapathir...@gmail.com
Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi, I have started working on debugger wrapping. So far I have made progress through first two test cases at [1]. However, the code is failing in test case 3. *This is because of python crashing with following error when callback events are fired from non python created threads. The issue affects not only the debugger but other callbacks such as StreamCallback and QueryCallback.* > Fatal Python error: take_gil: NULL tstate This error appear only in Python versions 3.4+. The code works fine when I tested with Python 3.3 and below. Furthermore, the error doesn't appear in any Python version when the debugger is connected. During further investigation of error, I found the documented bug [2] of Python which affect Python 3.4+ in similar manner. So far, a possible solution we have is to use a single python created thread to transfer callbacks from Java side to Python. For this purpose, we can use a queue (in java) to hold callback events triggered from java and a single (python created) thread to transfer the events in queue to python. However, this approach might have some performance issues. Can I know your opinion on this approach? (So far I have not implemented this approach) Furthermore, I have opened an issue in pyjnius github [3] (the API I use to communicate between Java and Python) on this matter. It might also be possible to fix the issue from pyjnius side using some of the suggestions available in [2] and [4]. I will look into this approach as well. [1] - https://github.com/wso2/siddhi/blob/79608b6aea4fbd99bb08cf64493c8b4144bc32e4/modules/siddhi-core/src/test/java/org/wso2/siddhi/core/debugger/TestDebugger.java [2] - https://bugs.python.org/issue20891 [3] - https://github.com/kivy/pyjnius/issues/276 [4] - https://bugs.python.org/issue19576 Thanks and Regards, Madhawa On Thu, May 25, 2017 at 5:32 AM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > Great, you can do the debugger now, he said after finishing the debugger > work, work on wrap event simulator . > > Regards > Suho > > On Wed, May 24, 2017 at 6:19 PM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> >> I have updated the README.md file. Will let you know when I have progress >> with debugger. >> >> Thanks >> Madhawa >> >> On Mon, May 22, 2017 at 12:41 PM, Grainier Perera <grain...@wso2.com> >> wrote: >> >>> Hi Madhawa, >>> >>> I went through your impl and it works great. Try to improve the test >>> cases and documentation (README.md on git) when you get a time. >>> >>> Furthermore, I have added Event simulator REST API endpoints to the doc >>> that you shared earlier. After getting debugger to work, try to wrap event >>> simulator endpoints as well. You can refer to [1] for the documentation on >>> them. >>> >>> [1] https://docs.wso2.com/display/DAS400/Simulating+Events >>> >>> Regards, >>> Grainier. >>> >>> On Sun, May 21, 2017 at 6:00 PM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I started working on the native wrapper. So far, have the very basic >>>> functionality working for Siddhi 3.1 and Siddhi 4.0. >>>> I am maintaining my code at the repo [1]. >>>> >>>> Next step is getting the Siddhi debugger working. I will let you know >>>> when it is done. >>>> >>>> [1] - https://github.com/madhawav/SiddhiCEPPythonAPI >>>> >>>> Thanks, >>>> Madhawa >>>> >>>> >>>> On Fri, May 19, 2017 at 12:47 PM, Sriskandarajah Suhothayan < >>>> s...@wso2.com> wrote: >>>> >>>>> Sure we'll look into that. >>>>> >>>>> As the immediate next step can you make finish the work on native >>>>> Siddhi working with python. >>>>> Make sure Siddhi debugger also works. >>>>> >>>>> Regards >>>>> Suho >>>>> >>>>> On Fri, May 19, 2017 at 11:45 AM, Madhawa Vidanapathirana < >>>>> madhawavidanapathir...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I have updated the shared doc [1] by adding "List of Admin Services >>>>>> to be used for DAS 3.1". Feel free to add-in your suggestions as well. >>>>>> >>>>>> Also, are their any documentation available on specific Admin >>>>>> Services APIs I have mentioned in doc? Such as a Reference Guide >>>>>>
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi, I have updated the README.md file. Will let you know when I have progress with debugger. Thanks Madhawa On Mon, May 22, 2017 at 12:41 PM, Grainier Perera <grain...@wso2.com> wrote: > Hi Madhawa, > > I went through your impl and it works great. Try to improve the test cases > and documentation (README.md on git) when you get a time. > > Furthermore, I have added Event simulator REST API endpoints to the doc > that you shared earlier. After getting debugger to work, try to wrap event > simulator endpoints as well. You can refer to [1] for the documentation on > them. > > [1] https://docs.wso2.com/display/DAS400/Simulating+Events > > Regards, > Grainier. > > On Sun, May 21, 2017 at 6:00 PM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> >> I started working on the native wrapper. So far, have the very basic >> functionality working for Siddhi 3.1 and Siddhi 4.0. >> I am maintaining my code at the repo [1]. >> >> Next step is getting the Siddhi debugger working. I will let you know >> when it is done. >> >> [1] - https://github.com/madhawav/SiddhiCEPPythonAPI >> >> Thanks, >> Madhawa >> >> >> On Fri, May 19, 2017 at 12:47 PM, Sriskandarajah Suhothayan < >> s...@wso2.com> wrote: >> >>> Sure we'll look into that. >>> >>> As the immediate next step can you make finish the work on native Siddhi >>> working with python. >>> Make sure Siddhi debugger also works. >>> >>> Regards >>> Suho >>> >>> On Fri, May 19, 2017 at 11:45 AM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I have updated the shared doc [1] by adding "List of Admin Services to >>>> be used for DAS 3.1". Feel free to add-in your suggestions as well. >>>> >>>> Also, are their any documentation available on specific Admin Services >>>> APIs I have mentioned in doc? Such as a Reference Guide describing the >>>> methods and parameters of individual Admin Services APIs. I am already >>>> aware of the general documentation on Admin Services available at [2] >>>> >>>> [1] - https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt >>>> 2JHh9RJya2VdHlHOTl4/edit?usp=sharing >>>> [2] - https://docs.wso2.com/display/DAS310/Calling+Admin+Services+ >>>> from+Apps >>>> >>>> Thanks, >>>> Madhawa >>>> >>>> On Tue, May 9, 2017 at 11:11 AM, Sriskandarajah Suhothayan < >>>> s...@wso2.com> wrote: >>>> >>>>> +1 for the approach. >>>>> We will add the classes >>>>> >>>>> On Tue, May 9, 2017 at 12:05 AM Madhawa Vidanapathirana < >>>>> madhawavidanapathir...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I will look into REST side also then. Already found good APIs to work >>>>>> with Native Calls and SOAP. >>>>>> >>>>>> I am also trying to come up with a list of classes of Siddhi Java >>>>>> Library that should be exposed via Python API. I don't think its >>>>>> required >>>>>> to wrap the internal classes since their functionality is not directly >>>>>> used >>>>>> by Siddhi Java Library users. >>>>>> >>>>>> I will update the list of classes to be wrapped at link below. Feel >>>>>> free to add in your suggestions as well. >>>>>> https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt >>>>>> 2JHh9RJya2VdHlHOTl4/edit?usp=sharing >>>>>> >>>>>> Thanks and Regards, >>>>>> Madhawa >>>>>> >>>>>> >>>>>> On Sun, May 7, 2017 at 11:26 PM, Sriskandarajah Suhothayan < >>>>>> s...@wso2.com> wrote: >>>>>> >>>>>>> Siddhi 3.x is compatible with DAS 3.1, and Siddhi 4.x is >>>>>>> compatible with DAS 4.0 which we are still working on. >>>>>>> >>>>>>> Siddhi APIs does not drastically change from 3.x to 4.x, >>>>>>> DAS 3.1 uses SOAP and DAS 4.0 uses HTTP/REST APIs >>>>>>> >>>>>>> So apart from native APIs, if you have figured out a way to use REST >>>>>&g
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi, I started working on the native wrapper. So far, have the very basic functionality working for Siddhi 3.1 and Siddhi 4.0. I am maintaining my code at the repo [1]. Next step is getting the Siddhi debugger working. I will let you know when it is done. [1] - https://github.com/madhawav/SiddhiCEPPythonAPI Thanks, Madhawa On Fri, May 19, 2017 at 12:47 PM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > Sure we'll look into that. > > As the immediate next step can you make finish the work on native Siddhi > working with python. > Make sure Siddhi debugger also works. > > Regards > Suho > > On Fri, May 19, 2017 at 11:45 AM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> >> I have updated the shared doc [1] by adding "List of Admin Services to be >> used for DAS 3.1". Feel free to add-in your suggestions as well. >> >> Also, are their any documentation available on specific Admin Services >> APIs I have mentioned in doc? Such as a Reference Guide describing the >> methods and parameters of individual Admin Services APIs. I am already >> aware of the general documentation on Admin Services available at [2] >> >> [1] - https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt >> 2JHh9RJya2VdHlHOTl4/edit?usp=sharing >> [2] - https://docs.wso2.com/display/DAS310/Calling+Admin+Services+ >> from+Apps >> >> Thanks, >> Madhawa >> >> On Tue, May 9, 2017 at 11:11 AM, Sriskandarajah Suhothayan <s...@wso2.com >> > wrote: >> >>> +1 for the approach. >>> We will add the classes >>> >>> On Tue, May 9, 2017 at 12:05 AM Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I will look into REST side also then. Already found good APIs to work >>>> with Native Calls and SOAP. >>>> >>>> I am also trying to come up with a list of classes of Siddhi Java >>>> Library that should be exposed via Python API. I don't think its required >>>> to wrap the internal classes since their functionality is not directly used >>>> by Siddhi Java Library users. >>>> >>>> I will update the list of classes to be wrapped at link below. Feel >>>> free to add in your suggestions as well. >>>> https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt >>>> 2JHh9RJya2VdHlHOTl4/edit?usp=sharing >>>> >>>> Thanks and Regards, >>>> Madhawa >>>> >>>> >>>> On Sun, May 7, 2017 at 11:26 PM, Sriskandarajah Suhothayan < >>>> s...@wso2.com> wrote: >>>> >>>>> Siddhi 3.x is compatible with DAS 3.1, and Siddhi 4.x is >>>>> compatible with DAS 4.0 which we are still working on. >>>>> >>>>> Siddhi APIs does not drastically change from 3.x to 4.x, >>>>> DAS 3.1 uses SOAP and DAS 4.0 uses HTTP/REST APIs >>>>> >>>>> So apart from native APIs, if you have figured out a way to use REST >>>>> and SOAP we are good enough. >>>>> >>>>> Regards >>>>> Suho >>>>> >>>>> On Sun, May 7, 2017 at 12:00 PM, Madhawa Vidanapathirana < >>>>> madhawavidanapathir...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> Need bit more clarity on what versions of products we should build >>>>>> on. >>>>>> >>>>>> Are we developing on DAS 3.1 (as mentioned in beginning of mail >>>>>> thread) or 4.0 (mentioned in previous mail) ? >>>>>> Also, what version of WSO2 CEP? >>>>>> >>>>>> According to my understanding so far, we are developing on Siddhi >>>>>> Java Library 4.0. >>>>>> >>>>>> Thanks and Regards, >>>>>> Madhawa >>>>>> >>>>>> On Sat, May 6, 2017 at 1:27 PM, Mohanadarshan Vivekanandalingam < >>>>>> mo...@wso2.com> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Sat, May 6, 2017 at 9:06 AM, Sriskandarajah Suhothayan < >>>>>>> s...@wso2.com> wrote: >>>>>>> >>>>>>>> @Mohan on DAS 4.0 do we have similar services like admin services >>>>>>>> at the worker? >>>>>>>> >>>>>>>>
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi, I have updated the shared doc [1] by adding "List of Admin Services to be used for DAS 3.1". Feel free to add-in your suggestions as well. Also, are their any documentation available on specific Admin Services APIs I have mentioned in doc? Such as a Reference Guide describing the methods and parameters of individual Admin Services APIs. I am already aware of the general documentation on Admin Services available at [2] [1] - https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt2JHh9RJya2VdHlHOTl4/edit?usp=sharing [2] - https://docs.wso2.com/display/DAS310/Calling+Admin+Services+from+Apps Thanks, Madhawa On Tue, May 9, 2017 at 11:11 AM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > +1 for the approach. > We will add the classes > > On Tue, May 9, 2017 at 12:05 AM Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> >> I will look into REST side also then. Already found good APIs to work >> with Native Calls and SOAP. >> >> I am also trying to come up with a list of classes of Siddhi Java Library >> that should be exposed via Python API. I don't think its required to wrap >> the internal classes since their functionality is not directly used by >> Siddhi Java Library users. >> >> I will update the list of classes to be wrapped at link below. Feel free >> to add in your suggestions as well. >> https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt2JHh9 >> RJya2VdHlHOTl4/edit?usp=sharing >> >> Thanks and Regards, >> Madhawa >> >> >> On Sun, May 7, 2017 at 11:26 PM, Sriskandarajah Suhothayan <s...@wso2.com >> > wrote: >> >>> Siddhi 3.x is compatible with DAS 3.1, and Siddhi 4.x is compatible with >>> DAS 4.0 which we are still working on. >>> >>> Siddhi APIs does not drastically change from 3.x to 4.x, >>> DAS 3.1 uses SOAP and DAS 4.0 uses HTTP/REST APIs >>> >>> So apart from native APIs, if you have figured out a way to use REST and >>> SOAP we are good enough. >>> >>> Regards >>> Suho >>> >>> On Sun, May 7, 2017 at 12:00 PM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi, >>>> Need bit more clarity on what versions of products we should build on. >>>> >>>> Are we developing on DAS 3.1 (as mentioned in beginning of mail thread) >>>> or 4.0 (mentioned in previous mail) ? >>>> Also, what version of WSO2 CEP? >>>> >>>> According to my understanding so far, we are developing on Siddhi Java >>>> Library 4.0. >>>> >>>> Thanks and Regards, >>>> Madhawa >>>> >>>> On Sat, May 6, 2017 at 1:27 PM, Mohanadarshan Vivekanandalingam < >>>> mo...@wso2.com> wrote: >>>> >>>>> >>>>> >>>>> On Sat, May 6, 2017 at 9:06 AM, Sriskandarajah Suhothayan < >>>>> s...@wso2.com> wrote: >>>>> >>>>>> @Mohan on DAS 4.0 do we have similar services like admin services at >>>>>> the worker? >>>>>> >>>>>> Shall we come up with the exact list of apis that we need to have ? >>>>>> So he can also incorporate them. >>>>>> >>>>> >>>>> Yes, I have already listed some apis in [1].. Will get the finalized >>>>> list soon and share with Madhawa.. >>>>> >>>>> [1] https://docs.google.com/spreadsheets/d/ >>>>> 1m0sh4DLABCFzCBmjEXtVTrRGM0Mc6lvyYQP6rI99zhQ/edit#gid=0 >>>>> >>>>> Thanks, >>>>> Mohan >>>>> >>>>> >>>>>> >>>>>> Regards >>>>>> Suho >>>>>> >>>>>> On Fri, May 5, 2017 at 9:16 PM Mohanadarshan Vivekanandalingam < >>>>>> mo...@wso2.com> wrote: >>>>>> >>>>>>> [Adding other project mentors] >>>>>>> >>>>>>> On Fri, May 5, 2017 at 5:52 PM, Madhawa Vidanapathirana < >>>>>>> madhawavidanapathir...@gmail.com> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> Thank you for accepting my proposal for Project "Python API for >>>>>>>> Siddhi CEP" in GSoC. >>>>>>>> >>>>>>>> The original proposal submitted by myself is available at [1]. >>>>>>>>
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi, I will look into REST side also then. Already found good APIs to work with Native Calls and SOAP. I am also trying to come up with a list of classes of Siddhi Java Library that should be exposed via Python API. I don't think its required to wrap the internal classes since their functionality is not directly used by Siddhi Java Library users. I will update the list of classes to be wrapped at link below. Feel free to add in your suggestions as well. https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt2JHh9RJya2VdHlHOTl4/edit?usp=sharing Thanks and Regards, Madhawa On Sun, May 7, 2017 at 11:26 PM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > Siddhi 3.x is compatible with DAS 3.1, and Siddhi 4.x is compatible with > DAS 4.0 which we are still working on. > > Siddhi APIs does not drastically change from 3.x to 4.x, > DAS 3.1 uses SOAP and DAS 4.0 uses HTTP/REST APIs > > So apart from native APIs, if you have figured out a way to use REST and > SOAP we are good enough. > > Regards > Suho > > On Sun, May 7, 2017 at 12:00 PM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> Need bit more clarity on what versions of products we should build on. >> >> Are we developing on DAS 3.1 (as mentioned in beginning of mail thread) >> or 4.0 (mentioned in previous mail) ? >> Also, what version of WSO2 CEP? >> >> According to my understanding so far, we are developing on Siddhi Java >> Library 4.0. >> >> Thanks and Regards, >> Madhawa >> >> On Sat, May 6, 2017 at 1:27 PM, Mohanadarshan Vivekanandalingam < >> mo...@wso2.com> wrote: >> >>> >>> >>> On Sat, May 6, 2017 at 9:06 AM, Sriskandarajah Suhothayan <s...@wso2.com >>> > wrote: >>> >>>> @Mohan on DAS 4.0 do we have similar services like admin services at >>>> the worker? >>>> >>>> Shall we come up with the exact list of apis that we need to have ? So >>>> he can also incorporate them. >>>> >>> >>> Yes, I have already listed some apis in [1].. Will get the finalized >>> list soon and share with Madhawa.. >>> >>> [1] https://docs.google.com/spreadsheets/d/1m0sh4DLABCFzCBmj >>> EXtVTrRGM0Mc6lvyYQP6rI99zhQ/edit#gid=0 >>> >>> Thanks, >>> Mohan >>> >>> >>>> >>>> Regards >>>> Suho >>>> >>>> On Fri, May 5, 2017 at 9:16 PM Mohanadarshan Vivekanandalingam < >>>> mo...@wso2.com> wrote: >>>> >>>>> [Adding other project mentors] >>>>> >>>>> On Fri, May 5, 2017 at 5:52 PM, Madhawa Vidanapathirana < >>>>> madhawavidanapathir...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> Thank you for accepting my proposal for Project "Python API for >>>>>> Siddhi CEP" in GSoC. >>>>>> >>>>>> The original proposal submitted by myself is available at [1]. >>>>>> >>>>>> Progress made so far is as follows. >>>>>> >>>>>>1. Figured out a good technique to access JAVA APIs from Python >>>>>>via Native Calls. >>>>>>- Pyjnius Framework supports both method calls and callbacks >>>>>> between Python and Java. >>>>>>2. Has wrapped the basic functionality of Siddhi CEP Java Library >>>>>>using Python in prototype implementations [2]. >>>>>>3. Currently in the process of figuring out a good method to >>>>>>communicate with Admin Services from Python. >>>>>> - Zeep API [3] seems to be a good solution. It supports SSL as >>>>>> well. I have already managed to authenticate and invoke some >>>>>> methods of >>>>>> WSO2 DAS through this API. >>>>>> >>>>>> During the community bonding period, my plan is to gain more clarity >>>>>> on expected architecture of the system such as what sort of a public >>>>>> interface would be suitable for the Python API. I also hope to learn more >>>>>> on Admin Services Interface of WSO2 DAS. >>>>>> >>>>>> Would you like to see any changes in the proposal? Shall I proceed as >>>>>> per the plan their? >>>>>> >>>>>> [1] - https://drive.google.com/file/d/0B7wIuEzJseiwUF9xWGFRUnQyMWc >>>>>
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi, Need bit more clarity on what versions of products we should build on. Are we developing on DAS 3.1 (as mentioned in beginning of mail thread) or 4.0 (mentioned in previous mail) ? Also, what version of WSO2 CEP? According to my understanding so far, we are developing on Siddhi Java Library 4.0. Thanks and Regards, Madhawa On Sat, May 6, 2017 at 1:27 PM, Mohanadarshan Vivekanandalingam < mo...@wso2.com> wrote: > > > On Sat, May 6, 2017 at 9:06 AM, Sriskandarajah Suhothayan <s...@wso2.com> > wrote: > >> @Mohan on DAS 4.0 do we have similar services like admin services at the >> worker? >> >> Shall we come up with the exact list of apis that we need to have ? So he >> can also incorporate them. >> > > Yes, I have already listed some apis in [1].. Will get the finalized list > soon and share with Madhawa.. > > [1] https://docs.google.com/spreadsheets/d/1m0sh4DLABCFzCBmjEXtVTrRGM0Mc6 > lvyYQP6rI99zhQ/edit#gid=0 > > Thanks, > Mohan > > >> >> Regards >> Suho >> >> On Fri, May 5, 2017 at 9:16 PM Mohanadarshan Vivekanandalingam < >> mo...@wso2.com> wrote: >> >>> [Adding other project mentors] >>> >>> On Fri, May 5, 2017 at 5:52 PM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi, >>>> Thank you for accepting my proposal for Project "Python API for Siddhi >>>> CEP" in GSoC. >>>> >>>> The original proposal submitted by myself is available at [1]. >>>> >>>> Progress made so far is as follows. >>>> >>>>1. Figured out a good technique to access JAVA APIs from Python via >>>>Native Calls. >>>>- Pyjnius Framework supports both method calls and callbacks >>>> between Python and Java. >>>>2. Has wrapped the basic functionality of Siddhi CEP Java Library >>>>using Python in prototype implementations [2]. >>>>3. Currently in the process of figuring out a good method to >>>>communicate with Admin Services from Python. >>>> - Zeep API [3] seems to be a good solution. It supports SSL as >>>> well. I have already managed to authenticate and invoke some methods >>>> of >>>> WSO2 DAS through this API. >>>> >>>> During the community bonding period, my plan is to gain more clarity on >>>> expected architecture of the system such as what sort of a public interface >>>> would be suitable for the Python API. I also hope to learn more on Admin >>>> Services Interface of WSO2 DAS. >>>> >>>> Would you like to see any changes in the proposal? Shall I proceed as >>>> per the plan their? >>>> >>>> [1] - https://drive.google.com/file/d/0B7wIuEzJseiwUF9xWGFRUnQyMWc >>>> /view?usp=sharing >>>> [2] - https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyj >>>> nius_Prototype_Wrap_Python2_3 >>>> [3] - http://docs.python-zeep.org/en/master/ >>>> >>>> Thanks and Regards, >>>> >>>> Madhawa >>>> >>>> On Tue, Apr 4, 2017 at 1:52 PM, Sriskandarajah Suhothayan < >>>> s...@wso2.com> wrote: >>>> >>>>> Great >>>>> >>>>> Suho >>>>> >>>>> On Tue, Apr 4, 2017 at 11:10 AM, Madhawa Vidanapathirana < >>>>> madhawavidanapathir...@gmail.com> wrote: >>>>> >>>>>> Hi Suho, >>>>>> >>>>>> I have submitted the final proposal through GSoC Dashboard. Thank you >>>>>> for all the support given. >>>>>> >>>>>> Looking forward for a great GSoC with WSO2. >>>>>> >>>>>> Regards, >>>>>> Madhawa >>>>>> >>>>>> >>>>>> On Monday, March 27, 2017, Madhawa Vidanapathirana < >>>>>> madhawavidanapathir...@gmail.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I have shared the finalized draft proposal via the Google Summer of >>>>>>> Code Web Portal. Kindly let me know if any changes are required. >>>>>>> Hoping to submit the final proposal with changes based on your >>>>>>> feedback. >>>>>>> >>>>>>> Regards, >>>>>>> Madhawa
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi, Thank you for accepting my proposal for Project "Python API for Siddhi CEP" in GSoC. The original proposal submitted by myself is available at [1]. Progress made so far is as follows. 1. Figured out a good technique to access JAVA APIs from Python via Native Calls. - Pyjnius Framework supports both method calls and callbacks between Python and Java. 2. Has wrapped the basic functionality of Siddhi CEP Java Library using Python in prototype implementations [2]. 3. Currently in the process of figuring out a good method to communicate with Admin Services from Python. - Zeep API [3] seems to be a good solution. It supports SSL as well. I have already managed to authenticate and invoke some methods of WSO2 DAS through this API. During the community bonding period, my plan is to gain more clarity on expected architecture of the system such as what sort of a public interface would be suitable for the Python API. I also hope to learn more on Admin Services Interface of WSO2 DAS. Would you like to see any changes in the proposal? Shall I proceed as per the plan their? [1] - https://drive.google.com/file/d/0B7wIuEzJseiwUF9xWGFRUnQyMWc /view?usp=sharing [2] - https://github.com/madhawav/CEP-Python-Wraps/tree/master/ Pyjnius_Prototype_Wrap_Python2_3 [3] - http://docs.python-zeep.org/en/master/ Thanks and Regards, Madhawa On Tue, Apr 4, 2017 at 1:52 PM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > Great > > Suho > > On Tue, Apr 4, 2017 at 11:10 AM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi Suho, >> >> I have submitted the final proposal through GSoC Dashboard. Thank you for >> all the support given. >> >> Looking forward for a great GSoC with WSO2. >> >> Regards, >> Madhawa >> >> >> On Monday, March 27, 2017, Madhawa Vidanapathirana < >> madhawavidanapathir...@gmail.com> wrote: >> >>> Hi, >>> >>> I have shared the finalized draft proposal via the Google Summer of Code >>> Web Portal. Kindly let me know if any changes are required. >>> Hoping to submit the final proposal with changes based on your feedback. >>> >>> Regards, >>> Madhawa >>> >>> >>> On Fri, Mar 24, 2017 at 4:15 PM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> Good news. >>>> >>>> Requested a release from Pyjnius Developer Team [1] and managed to get >>>> a new release [2] to Python Package Index (PIP). Therefore, we no longer >>>> have to develop their library from GitHub code. >>>> We can simply consider it as a dependency which gets auto installed >>>> when our final product is deployed. >>>> >>>> [1] - https://github.com/kivy/pyjnius/issues/189#issuecomment-288750222 >>>> [2] - https://pypi.python.org/pypi/pyjnius/1.1.1 >>>> >>>> Pyjnius is a library which can be used for calling Java methods from >>>> Python and obtaining callback responses. It uses native method calls. >>>> >>>> Regards, >>>> Madhawa >>>> >>>> On Thu, Mar 23, 2017 at 1:48 AM, Sriskandarajah Suhothayan < >>>> s...@wso2.com> wrote: >>>> >>>>> Good to know that it worked :) >>>>> >>>>> Regards >>>>> Suho >>>>> >>>>> On Wed, Mar 22, 2017 at 11:24 PM, Madhawa Vidanapathirana < >>>>> madhawavidanapathir...@gmail.com> wrote: >>>>> >>>>>> Hi Suho, >>>>>> >>>>>> Got the prototype working with Python 3 as well. Refer the link below >>>>>> for sources. >>>>>> >>>>>> https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyj >>>>>> nius_Prototype_Wrap_Python2_3 >>>>>> >>>>>> This version works with both Python 2.7 and 3.x. (Tested on 2.7 and >>>>>> 3.5). Uses native calls via Pyjnius API. >>>>>> >>>>>> Please note: When you are installing Pyjnius from source, don't use >>>>>> the same local copy of source files for both Python2 and Python3. The >>>>>> install scripts of Pyjnius leaves temporary files that make subsequent >>>>>> installs on a different version of Python fail. >>>>>> >>>>>> Regards, >>>>>> Madhawa >>>>>> >>>>>> >>>>>> O
[Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi Suho, I have submitted the final proposal through GSoC Dashboard. Thank you for all the support given. Looking forward for a great GSoC with WSO2. Regards, Madhawa On Monday, March 27, 2017, Madhawa Vidanapathirana < madhawavidanapathir...@gmail.com <javascript:_e(%7B%7D,'cvml','madhawavidanapathir...@gmail.com');>> wrote: > Hi, > > I have shared the finalized draft proposal via the Google Summer of Code > Web Portal. Kindly let me know if any changes are required. > Hoping to submit the final proposal with changes based on your feedback. > > Regards, > Madhawa > > > On Fri, Mar 24, 2017 at 4:15 PM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> >> Good news. >> >> Requested a release from Pyjnius Developer Team [1] and managed to get a >> new release [2] to Python Package Index (PIP). Therefore, we no longer have >> to develop their library from GitHub code. >> We can simply consider it as a dependency which gets auto installed when >> our final product is deployed. >> >> [1] - https://github.com/kivy/pyjnius/issues/189#issuecomment-288750222 >> [2] - https://pypi.python.org/pypi/pyjnius/1.1.1 >> >> Pyjnius is a library which can be used for calling Java methods from >> Python and obtaining callback responses. It uses native method calls. >> >> Regards, >> Madhawa >> >> On Thu, Mar 23, 2017 at 1:48 AM, Sriskandarajah Suhothayan <s...@wso2.com >> > wrote: >> >>> Good to know that it worked :) >>> >>> Regards >>> Suho >>> >>> On Wed, Mar 22, 2017 at 11:24 PM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi Suho, >>>> >>>> Got the prototype working with Python 3 as well. Refer the link below >>>> for sources. >>>> >>>> https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyj >>>> nius_Prototype_Wrap_Python2_3 >>>> >>>> This version works with both Python 2.7 and 3.x. (Tested on 2.7 and >>>> 3.5). Uses native calls via Pyjnius API. >>>> >>>> Please note: When you are installing Pyjnius from source, don't use the >>>> same local copy of source files for both Python2 and Python3. The install >>>> scripts of Pyjnius leaves temporary files that make subsequent installs on >>>> a different version of Python fail. >>>> >>>> Regards, >>>> Madhawa >>>> >>>> >>>> On Mon, Mar 20, 2017 at 12:44 PM, Madhawa Vidanapathirana < >>>> madhawavidanapathir...@gmail.com> wrote: >>>> >>>>> Hi Suho, >>>>> >>>>> Installation via PIP can be done. I will add it to Project Proposal. >>>>> >>>>> Regards, >>>>> Madhawa >>>>> >>>>> On Mon, Mar 20, 2017 at 11:25 AM, Sriskandarajah Suhothayan < >>>>> s...@wso2.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Sun, Mar 19, 2017 at 4:02 PM, Madhawa Vidanapathirana < >>>>>> madhawavidanapathir...@gmail.com> wrote: >>>>>> >>>>>>> Hi Suho, >>>>>>> >>>>>>> Going ahead with the proposal, few questions crossed my mind. >>>>>>> >>>>>>>1. You mentioned previously that WSO2 DAS should also be >>>>>>>supported. What sort of interactions are expected with WSO2 DAS? >>>>>>>1. Should publishing events to WSO2 DAS from Python Siddhi API >>>>>>> supported? >>>>>>> 2. Should deploying of Siddhi Queries to WSO2 DAS through >>>>>>> Python Siddhi API be supported? >>>>>>> 3. Any other expectations? >>>>>>> >>>>>>> >>>>>> For the integration with DAS we can use HTTP calls and deploy Siddhi >>>>>> queries and send events to that, we should also start a server from the >>>>>> python side to receive events from DAS and print them. >>>>>> >>>>>> We can work on the details of that after the proposal. >>>>>> >>>>>> One more thing to add, can we also implement Siddhi (the project you >>>>>> will be creating) to be installed via pip ? >>>>>> >>>>>> Regards >>>>&
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi, I have shared the finalized draft proposal via the Google Summer of Code Web Portal. Kindly let me know if any changes are required. Hoping to submit the final proposal with changes based on your feedback. Regards, Madhawa On Fri, Mar 24, 2017 at 4:15 PM, Madhawa Vidanapathirana < madhawavidanapathir...@gmail.com> wrote: > Hi, > > Good news. > > Requested a release from Pyjnius Developer Team [1] and managed to get a > new release [2] to Python Package Index (PIP). Therefore, we no longer have > to develop their library from GitHub code. > We can simply consider it as a dependency which gets auto installed when > our final product is deployed. > > [1] - https://github.com/kivy/pyjnius/issues/189#issuecomment-288750222 > [2] - https://pypi.python.org/pypi/pyjnius/1.1.1 > > Pyjnius is a library which can be used for calling Java methods from > Python and obtaining callback responses. It uses native method calls. > > Regards, > Madhawa > > On Thu, Mar 23, 2017 at 1:48 AM, Sriskandarajah Suhothayan <s...@wso2.com> > wrote: > >> Good to know that it worked :) >> >> Regards >> Suho >> >> On Wed, Mar 22, 2017 at 11:24 PM, Madhawa Vidanapathirana < >> madhawavidanapathir...@gmail.com> wrote: >> >>> Hi Suho, >>> >>> Got the prototype working with Python 3 as well. Refer the link below >>> for sources. >>> >>> https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyj >>> nius_Prototype_Wrap_Python2_3 >>> >>> This version works with both Python 2.7 and 3.x. (Tested on 2.7 and >>> 3.5). Uses native calls via Pyjnius API. >>> >>> Please note: When you are installing Pyjnius from source, don't use the >>> same local copy of source files for both Python2 and Python3. The install >>> scripts of Pyjnius leaves temporary files that make subsequent installs on >>> a different version of Python fail. >>> >>> Regards, >>> Madhawa >>> >>> >>> On Mon, Mar 20, 2017 at 12:44 PM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi Suho, >>>> >>>> Installation via PIP can be done. I will add it to Project Proposal. >>>> >>>> Regards, >>>> Madhawa >>>> >>>> On Mon, Mar 20, 2017 at 11:25 AM, Sriskandarajah Suhothayan < >>>> s...@wso2.com> wrote: >>>> >>>>> >>>>> >>>>> On Sun, Mar 19, 2017 at 4:02 PM, Madhawa Vidanapathirana < >>>>> madhawavidanapathir...@gmail.com> wrote: >>>>> >>>>>> Hi Suho, >>>>>> >>>>>> Going ahead with the proposal, few questions crossed my mind. >>>>>> >>>>>>1. You mentioned previously that WSO2 DAS should also be >>>>>>supported. What sort of interactions are expected with WSO2 DAS? >>>>>>1. Should publishing events to WSO2 DAS from Python Siddhi API >>>>>> supported? >>>>>> 2. Should deploying of Siddhi Queries to WSO2 DAS through >>>>>> Python Siddhi API be supported? >>>>>> 3. Any other expectations? >>>>>> >>>>>> >>>>> For the integration with DAS we can use HTTP calls and deploy Siddhi >>>>> queries and send events to that, we should also start a server from the >>>>> python side to receive events from DAS and print them. >>>>> >>>>> We can work on the details of that after the proposal. >>>>> >>>>> One more thing to add, can we also implement Siddhi (the project you >>>>> will be creating) to be installed via pip ? >>>>> >>>>> Regards >>>>> Suho >>>>> >>>>> If any of above can be considered as "optional", indicate them as well. >>>>>> >>>>>> Regards, >>>>>> Madhawa >>>>>> >>>>>> On Sat, Mar 18, 2017 at 9:00 PM, Sriskandarajah Suhothayan < >>>>>> s...@wso2.com> wrote: >>>>>> >>>>>>> For the initial cut this looks good, please go ahead with the >>>>>>> proposal. Let's check some other alternatives and start the development. >>>>>>> >>>>>>> Regards >>>>>>> Suho >>>>>>> >>>>>>> On
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi, Good news. Requested a release from Pyjnius Developer Team [1] and managed to get a new release [2] to Python Package Index (PIP). Therefore, we no longer have to develop their library from GitHub code. We can simply consider it as a dependency which gets auto installed when our final product is deployed. [1] - https://github.com/kivy/pyjnius/issues/189#issuecomment-288750222 [2] - https://pypi.python.org/pypi/pyjnius/1.1.1 Pyjnius is a library which can be used for calling Java methods from Python and obtaining callback responses. It uses native method calls. Regards, Madhawa On Thu, Mar 23, 2017 at 1:48 AM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > Good to know that it worked :) > > Regards > Suho > > On Wed, Mar 22, 2017 at 11:24 PM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi Suho, >> >> Got the prototype working with Python 3 as well. Refer the link below for >> sources. >> >> https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyj >> nius_Prototype_Wrap_Python2_3 >> >> This version works with both Python 2.7 and 3.x. (Tested on 2.7 and 3.5). >> Uses native calls via Pyjnius API. >> >> Please note: When you are installing Pyjnius from source, don't use the >> same local copy of source files for both Python2 and Python3. The install >> scripts of Pyjnius leaves temporary files that make subsequent installs on >> a different version of Python fail. >> >> Regards, >> Madhawa >> >> >> On Mon, Mar 20, 2017 at 12:44 PM, Madhawa Vidanapathirana < >> madhawavidanapathir...@gmail.com> wrote: >> >>> Hi Suho, >>> >>> Installation via PIP can be done. I will add it to Project Proposal. >>> >>> Regards, >>> Madhawa >>> >>> On Mon, Mar 20, 2017 at 11:25 AM, Sriskandarajah Suhothayan < >>> s...@wso2.com> wrote: >>> >>>> >>>> >>>> On Sun, Mar 19, 2017 at 4:02 PM, Madhawa Vidanapathirana < >>>> madhawavidanapathir...@gmail.com> wrote: >>>> >>>>> Hi Suho, >>>>> >>>>> Going ahead with the proposal, few questions crossed my mind. >>>>> >>>>>1. You mentioned previously that WSO2 DAS should also be >>>>>supported. What sort of interactions are expected with WSO2 DAS? >>>>>1. Should publishing events to WSO2 DAS from Python Siddhi API >>>>> supported? >>>>> 2. Should deploying of Siddhi Queries to WSO2 DAS through >>>>> Python Siddhi API be supported? >>>>> 3. Any other expectations? >>>>> >>>>> >>>> For the integration with DAS we can use HTTP calls and deploy Siddhi >>>> queries and send events to that, we should also start a server from the >>>> python side to receive events from DAS and print them. >>>> >>>> We can work on the details of that after the proposal. >>>> >>>> One more thing to add, can we also implement Siddhi (the project you >>>> will be creating) to be installed via pip ? >>>> >>>> Regards >>>> Suho >>>> >>>> If any of above can be considered as "optional", indicate them as well. >>>>> >>>>> Regards, >>>>> Madhawa >>>>> >>>>> On Sat, Mar 18, 2017 at 9:00 PM, Sriskandarajah Suhothayan < >>>>> s...@wso2.com> wrote: >>>>> >>>>>> For the initial cut this looks good, please go ahead with the >>>>>> proposal. Let's check some other alternatives and start the development. >>>>>> >>>>>> Regards >>>>>> Suho >>>>>> >>>>>> On Sat, Mar 18, 2017 at 1:01 PM, Madhawa Vidanapathirana < >>>>>> madhawavidanapathir...@gmail.com> wrote: >>>>>> >>>>>>> Hi Suho, >>>>>>> >>>>>>> You can find the python version of test case written using Pyjnius >>>>>>> in below link. >>>>>>> https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyj >>>>>>> nius%20Prototype%20Wrap >>>>>>> Instructions on building the code is also given their. >>>>>>> >>>>>>> During development, I noticed following disadvantages of Pyjnius API >>>>>>> >>>>>>>- Not compatib
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi Suho, Got the prototype working with Python 3 as well. Refer the link below for sources. https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyjnius_Prototype_Wrap_Python2_3 This version works with both Python 2.7 and 3.x. (Tested on 2.7 and 3.5). Uses native calls via Pyjnius API. Please note: When you are installing Pyjnius from source, don't use the same local copy of source files for both Python2 and Python3. The install scripts of Pyjnius leaves temporary files that make subsequent installs on a different version of Python fail. Regards, Madhawa On Mon, Mar 20, 2017 at 12:44 PM, Madhawa Vidanapathirana < madhawavidanapathir...@gmail.com> wrote: > Hi Suho, > > Installation via PIP can be done. I will add it to Project Proposal. > > Regards, > Madhawa > > On Mon, Mar 20, 2017 at 11:25 AM, Sriskandarajah Suhothayan <s...@wso2.com > > wrote: > >> >> >> On Sun, Mar 19, 2017 at 4:02 PM, Madhawa Vidanapathirana < >> madhawavidanapathir...@gmail.com> wrote: >> >>> Hi Suho, >>> >>> Going ahead with the proposal, few questions crossed my mind. >>> >>>1. You mentioned previously that WSO2 DAS should also be supported. >>>What sort of interactions are expected with WSO2 DAS? >>>1. Should publishing events to WSO2 DAS from Python Siddhi API >>> supported? >>> 2. Should deploying of Siddhi Queries to WSO2 DAS through Python >>> Siddhi API be supported? >>> 3. Any other expectations? >>> >>> >> For the integration with DAS we can use HTTP calls and deploy Siddhi >> queries and send events to that, we should also start a server from the >> python side to receive events from DAS and print them. >> >> We can work on the details of that after the proposal. >> >> One more thing to add, can we also implement Siddhi (the project you will >> be creating) to be installed via pip ? >> >> Regards >> Suho >> >> If any of above can be considered as "optional", indicate them as well. >>> >>> Regards, >>> Madhawa >>> >>> On Sat, Mar 18, 2017 at 9:00 PM, Sriskandarajah Suhothayan < >>> s...@wso2.com> wrote: >>> >>>> For the initial cut this looks good, please go ahead with the proposal. >>>> Let's check some other alternatives and start the development. >>>> >>>> Regards >>>> Suho >>>> >>>> On Sat, Mar 18, 2017 at 1:01 PM, Madhawa Vidanapathirana < >>>> madhawavidanapathir...@gmail.com> wrote: >>>> >>>>> Hi Suho, >>>>> >>>>> You can find the python version of test case written using Pyjnius in >>>>> below link. >>>>> https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyj >>>>> nius%20Prototype%20Wrap >>>>> Instructions on building the code is also given their. >>>>> >>>>> During development, I noticed following disadvantages of Pyjnius API >>>>> >>>>>- Not compatible with Python 3.x. >>>>>- There are no stable releases. However, the code available in >>>>>master branch is relatively stable. >>>>>- Difficult to configure. It is required to develop the library >>>>>from source. This would make it difficult to distribute an API >>>>> developed on >>>>>Pyjnius. >>>>>- There are no evidence that a proper release would be done soon. >>>>> >>>>> However, Pyjnius supports callback of events from Java to Python. >>>>> Additionally, it is easier to develop using Pyjnius ones it is configured. >>>>> >>>>> So, I had a looked at some of the other options as well. >>>>> >>>>> Java Bridge >>>>> >>>>> *Advantages* >>>>> >>>>>- Has stable releases available through Python Package Index. (pip) >>>>> >>>>> *Disadvantages* >>>>> >>>>>- No direct call-back mechanism to receive events from Java side. >>>>>It is possible to execute Python scripts in Java but those scripts >>>>> would >>>>>not be in same context as Python Host App. >>>>>- Comparatively harder to develop on but it is manageable. >>>>> >>>>> Py4J >>>>> >>>>> The main difference in Py4J is that it uses socket connectio
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi Suho, Installation via PIP can be done. I will add it to Project Proposal. Regards, Madhawa On Mon, Mar 20, 2017 at 11:25 AM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > > > On Sun, Mar 19, 2017 at 4:02 PM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi Suho, >> >> Going ahead with the proposal, few questions crossed my mind. >> >>1. You mentioned previously that WSO2 DAS should also be supported. >>What sort of interactions are expected with WSO2 DAS? >>1. Should publishing events to WSO2 DAS from Python Siddhi API >> supported? >> 2. Should deploying of Siddhi Queries to WSO2 DAS through Python >> Siddhi API be supported? >> 3. Any other expectations? >> >> > For the integration with DAS we can use HTTP calls and deploy Siddhi > queries and send events to that, we should also start a server from the > python side to receive events from DAS and print them. > > We can work on the details of that after the proposal. > > One more thing to add, can we also implement Siddhi (the project you will > be creating) to be installed via pip ? > > Regards > Suho > > If any of above can be considered as "optional", indicate them as well. >> >> Regards, >> Madhawa >> >> On Sat, Mar 18, 2017 at 9:00 PM, Sriskandarajah Suhothayan <s...@wso2.com >> > wrote: >> >>> For the initial cut this looks good, please go ahead with the proposal. >>> Let's check some other alternatives and start the development. >>> >>> Regards >>> Suho >>> >>> On Sat, Mar 18, 2017 at 1:01 PM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi Suho, >>>> >>>> You can find the python version of test case written using Pyjnius in >>>> below link. >>>> https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyj >>>> nius%20Prototype%20Wrap >>>> Instructions on building the code is also given their. >>>> >>>> During development, I noticed following disadvantages of Pyjnius API >>>> >>>>- Not compatible with Python 3.x. >>>>- There are no stable releases. However, the code available in >>>>master branch is relatively stable. >>>>- Difficult to configure. It is required to develop the library >>>>from source. This would make it difficult to distribute an API >>>> developed on >>>>Pyjnius. >>>>- There are no evidence that a proper release would be done soon. >>>> >>>> However, Pyjnius supports callback of events from Java to Python. >>>> Additionally, it is easier to develop using Pyjnius ones it is configured. >>>> >>>> So, I had a looked at some of the other options as well. >>>> >>>> Java Bridge >>>> >>>> *Advantages* >>>> >>>>- Has stable releases available through Python Package Index. (pip) >>>> >>>> *Disadvantages* >>>> >>>>- No direct call-back mechanism to receive events from Java side. >>>>It is possible to execute Python scripts in Java but those scripts >>>> would >>>>not be in same context as Python Host App. >>>>- Comparatively harder to develop on but it is manageable. >>>> >>>> Py4J >>>> >>>> The main difference in Py4J is that it uses socket connections to >>>> communicate with JVM instead of JNI. (secured socket connections are >>>> possible). >>>> >>>> *Advantages* >>>> >>>>- Stable release available through Python Package Index (pip). Easy >>>>to configure. >>>>- Can connect to an already running Java application (with Py4J) >>>>and communicate with it. (Thus, can be used to communicate with a >>>> running >>>>instance of WSO2 CEP) >>>>- Supports callback events. >>>>- Well maintained documentation. Active project. >>>> >>>> *Disadvantages* >>>> >>>>- Would require a work-around to avoid clashing between socket >>>>connection ports when concurrent applications use the API. >>>> >>>> As of now, I feel Py4J is the most suitable option. However, I am yet >>>> to look at some other options available such as JPy and JCC.
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi Suho, Going ahead with the proposal, few questions crossed my mind. 1. You mentioned previously that WSO2 DAS should also be supported. What sort of interactions are expected with WSO2 DAS? 1. Should publishing events to WSO2 DAS from Python Siddhi API supported? 2. Should deploying of Siddhi Queries to WSO2 DAS through Python Siddhi API be supported? 3. Any other expectations? If any of above can be considered as "optional", indicate them as well. Regards, Madhawa On Sat, Mar 18, 2017 at 9:00 PM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > For the initial cut this looks good, please go ahead with the proposal. > Let's check some other alternatives and start the development. > > Regards > Suho > > On Sat, Mar 18, 2017 at 1:01 PM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi Suho, >> >> You can find the python version of test case written using Pyjnius in >> below link. >> https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyj >> nius%20Prototype%20Wrap >> Instructions on building the code is also given their. >> >> During development, I noticed following disadvantages of Pyjnius API >> >>- Not compatible with Python 3.x. >>- There are no stable releases. However, the code available in master >>branch is relatively stable. >>- Difficult to configure. It is required to develop the library from >>source. This would make it difficult to distribute an API developed on >>Pyjnius. >>- There are no evidence that a proper release would be done soon. >> >> However, Pyjnius supports callback of events from Java to Python. >> Additionally, it is easier to develop using Pyjnius ones it is configured. >> >> So, I had a looked at some of the other options as well. >> >> Java Bridge >> >> *Advantages* >> >>- Has stable releases available through Python Package Index. (pip) >> >> *Disadvantages* >> >>- No direct call-back mechanism to receive events from Java side. It >>is possible to execute Python scripts in Java but those scripts would not >>be in same context as Python Host App. >>- Comparatively harder to develop on but it is manageable. >> >> Py4J >> >> The main difference in Py4J is that it uses socket connections to >> communicate with JVM instead of JNI. (secured socket connections are >> possible). >> >> *Advantages* >> >>- Stable release available through Python Package Index (pip). Easy >>to configure. >>- Can connect to an already running Java application (with Py4J) and >>communicate with it. (Thus, can be used to communicate with a running >>instance of WSO2 CEP) >>- Supports callback events. >>- Well maintained documentation. Active project. >> >> *Disadvantages* >> >>- Would require a work-around to avoid clashing between socket >>connection ports when concurrent applications use the API. >> >> As of now, I feel Py4J is the most suitable option. However, I am yet to >> look at some other options available such as JPy and JCC. >> >> Regards, >> >> Madhawa >> >> On Wed, Mar 15, 2017 at 11:10 PM, Sriskandarajah Suhothayan < >> s...@wso2.com> wrote: >> >>> Great, do also start working on writing the project proposal. >>> >>> Regards >>> Suho >>> >>> On Wed, Mar 15, 2017 at 10:58 PM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi Suho, >>>> Progress made so far is managed to write a python version of test case >>>> you suggested using Pyjnius [1] [2]. >>>> Pyjnius is capable of handling method calls and callbacks to/from JAVA >>>> via JNI. >>>> >>>> I will send the code here after I properly arrange it into a prototype >>>> API. >>>> >>>> [1] - https://pyjnius.readthedocs.io/en/latest/index.html >>>> [2] - https://github.com/kivy/pyjnius/blob/master/docs/source/index.rst >>>> >>>> Regards, >>>> Madhawa >>>> >>>> On Wed, Mar 15, 2017 at 1:11 AM, Sriskandarajah Suhothayan < >>>> s...@wso2.com> wrote: >>>> >>>>> As the first step focus on building APIs such that we can write the >>>>> following test case[1] in python. >>>>> >>>>> [1]https://github.com/wso2/siddhi/blob/master/modules/siddhi >>&
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi Suho, You can find the python version of test case written using Pyjnius in below link. https://github.com/madhawav/CEP-Python-Wraps/tree/master/Pyjnius%20Prototype%20Wrap Instructions on building the code is also given their. During development, I noticed following disadvantages of Pyjnius API - Not compatible with Python 3.x. - There are no stable releases. However, the code available in master branch is relatively stable. - Difficult to configure. It is required to develop the library from source. This would make it difficult to distribute an API developed on Pyjnius. - There are no evidence that a proper release would be done soon. However, Pyjnius supports callback of events from Java to Python. Additionally, it is easier to develop using Pyjnius ones it is configured. So, I had a looked at some of the other options as well. Java Bridge *Advantages* - Has stable releases available through Python Package Index. (pip) *Disadvantages* - No direct call-back mechanism to receive events from Java side. It is possible to execute Python scripts in Java but those scripts would not be in same context as Python Host App. - Comparatively harder to develop on but it is manageable. Py4J The main difference in Py4J is that it uses socket connections to communicate with JVM instead of JNI. (secured socket connections are possible). *Advantages* - Stable release available through Python Package Index (pip). Easy to configure. - Can connect to an already running Java application (with Py4J) and communicate with it. (Thus, can be used to communicate with a running instance of WSO2 CEP) - Supports callback events. - Well maintained documentation. Active project. *Disadvantages* - Would require a work-around to avoid clashing between socket connection ports when concurrent applications use the API. As of now, I feel Py4J is the most suitable option. However, I am yet to look at some other options available such as JPy and JCC. Regards, Madhawa On Wed, Mar 15, 2017 at 11:10 PM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > Great, do also start working on writing the project proposal. > > Regards > Suho > > On Wed, Mar 15, 2017 at 10:58 PM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi Suho, >> Progress made so far is managed to write a python version of test case >> you suggested using Pyjnius [1] [2]. >> Pyjnius is capable of handling method calls and callbacks to/from JAVA >> via JNI. >> >> I will send the code here after I properly arrange it into a prototype >> API. >> >> [1] - https://pyjnius.readthedocs.io/en/latest/index.html >> [2] - https://github.com/kivy/pyjnius/blob/master/docs/source/index.rst >> >> Regards, >> Madhawa >> >> On Wed, Mar 15, 2017 at 1:11 AM, Sriskandarajah Suhothayan <s...@wso2.com >> > wrote: >> >>> As the first step focus on building APIs such that we can write the >>> following test case[1] in python. >>> >>> [1]https://github.com/wso2/siddhi/blob/master/modules/siddhi >>> -samples/quick-start-samples/src/main/java/org/wso2/siddhi/s >>> ample/SimpleFilterSample.java >>> >>> Regards >>> Suho >>> >>> On Tue, Mar 14, 2017 at 9:55 AM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi, >>>> Thank you for your quick reply. >>>> >>>> Since directly using Siddhi Library is the more general case, I'll >>>> first focus on it. >>>> >>>> 1) I am thinking about following the same structure in JAVA API, >>>> centered around Siddhi Manager. Any opinions on this? >>>> 2) Any idea on extent to which lower level/internal components should >>>> be exposed? (e.g. - Exposing "StreamDefinition" class in addition to >>>> creating stream via Siddhi query using >>>> "siddhiManager.createExecutionPlanRuntime"). >>>> I have heard that it is usually discouraged to use lower level components >>>> instead of the query approach. >>>> >>>> Will try to send you a prototype covering basic functionality through >>>> Siddhi Java API, before making the proposal for entire project. >>>> >>>> Madhawa >>>> >>>> On Mon, Mar 13, 2017 at 9:53 PM, Sriskandarajah Suhothayan < >>>> s...@wso2.com> wrote: >>>> >>>>> >>>>> >>>>> On Sun, Mar 12, 2017 at 12:37 PM, Madhawa Vidanapathirana < >>>>> madhawavidanapathir...@gmail.com> wrote: >>>>>
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi Suho, Progress made so far is managed to write a python version of test case you suggested using Pyjnius [1] [2]. Pyjnius is capable of handling method calls and callbacks to/from JAVA via JNI. I will send the code here after I properly arrange it into a prototype API. [1] - https://pyjnius.readthedocs.io/en/latest/index.html [2] - https://github.com/kivy/pyjnius/blob/master/docs/source/index.rst Regards, Madhawa On Wed, Mar 15, 2017 at 1:11 AM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > As the first step focus on building APIs such that we can write the > following test case[1] in python. > > [1]https://github.com/wso2/siddhi/blob/master/modules/ > siddhi-samples/quick-start-samples/src/main/java/org/wso2/siddhi/sample/ > SimpleFilterSample.java > > Regards > Suho > > On Tue, Mar 14, 2017 at 9:55 AM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi, >> Thank you for your quick reply. >> >> Since directly using Siddhi Library is the more general case, I'll first >> focus on it. >> >> 1) I am thinking about following the same structure in JAVA API, centered >> around Siddhi Manager. Any opinions on this? >> 2) Any idea on extent to which lower level/internal components should be >> exposed? (e.g. - Exposing "StreamDefinition" class in addition to creating >> stream via Siddhi query using "siddhiManager.createExecutionPlanRuntime"). >> I have heard that it is usually discouraged to use lower level components >> instead of the query approach. >> >> Will try to send you a prototype covering basic functionality through >> Siddhi Java API, before making the proposal for entire project. >> >> Madhawa >> >> On Mon, Mar 13, 2017 at 9:53 PM, Sriskandarajah Suhothayan <s...@wso2.com >> > wrote: >> >>> >>> >>> On Sun, Mar 12, 2017 at 12:37 PM, Madhawa Vidanapathirana < >>> madhawavidanapathir...@gmail.com> wrote: >>> >>>> Hi. >>>> >>>> I am an undergraduate from Department of Computer Science and >>>> Engineering, University of Moratuwa. I recently completed my internship at >>>> WSO2 working with the Support Team on the project WSO2 Support Knowledge >>>> Base. >>>> >>>> I am interested on GSOC Project* "Proposal 16: Python API for Siddhi >>>> CEP"*. My internship project at WSO2 was almost entirely done using >>>> Python. Additionally, I used Py4J Framework to interface certain parts of >>>> the project to JAVA APIs. Furthermore, I have a certain amount of exposure >>>> with Siddhi/CEP through the WHACK project I took part. >>>> >>>> I went through the provided details in WSO2 GSOC 2017 Project List page >>>> and I am interested to know some more details. >>>> >>>>1. What version of CEP/Siddhi should be used by the API? >>>> >>>> You need to support the latest released version of Siddhi and DAS which >>> is in DAS 3.1 and also for the latest Siddhi (4.0) >>> >>>> >>>>1. In the description, does "Service APIs" refer to "Admin Services >>>>API" which is usually used by Admin Panel to communicate with CEP? >>>> >>>> Yes, to deploy the queries and to send and receive events >>> >>>> >>>>1. Should the Siddhi Python API require WSO2 CEP to be running in >>>>order to make Python API usable? >>>> >>>> Not necessay it should both work with the running CEP/DAS and use >>> Siddhi library in the ohter cases. >>> >>>> >>>>1. Is the Python API expected to do configuring of Siddhi CEP, >>>>streaming events to/from Siddhi CEP, or both? >>>> >>>> Yes in terms of queries. >>> >>> >>> >>>> Thank You >>>> >>>> >>>> -- >>>> *Madhawa Vidanapathirana* >>>> Student >>>> Department of Computer Science and Engineering >>>> University of Moratuwa >>>> Sri Lanka >>>> >>>> Mobile: (+94) 716874425 <071%20687%204425> >>>> Email: madhawavidanapathir...@gmail.com >>>> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 >>>> >>> >>> >>> >>> -- >>> >>> *S. Suhothayan* >>> Associate Director / Architect & Team Lead of WSO2 Complex Event >>> Pro
Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi, Thank you for your quick reply. Since directly using Siddhi Library is the more general case, I'll first focus on it. 1) I am thinking about following the same structure in JAVA API, centered around Siddhi Manager. Any opinions on this? 2) Any idea on extent to which lower level/internal components should be exposed? (e.g. - Exposing "StreamDefinition" class in addition to creating stream via Siddhi query using "siddhiManager.createExecutionPlanRuntime"). I have heard that it is usually discouraged to use lower level components instead of the query approach. Will try to send you a prototype covering basic functionality through Siddhi Java API, before making the proposal for entire project. Madhawa On Mon, Mar 13, 2017 at 9:53 PM, Sriskandarajah Suhothayan <s...@wso2.com> wrote: > > > On Sun, Mar 12, 2017 at 12:37 PM, Madhawa Vidanapathirana < > madhawavidanapathir...@gmail.com> wrote: > >> Hi. >> >> I am an undergraduate from Department of Computer Science and >> Engineering, University of Moratuwa. I recently completed my internship at >> WSO2 working with the Support Team on the project WSO2 Support Knowledge >> Base. >> >> I am interested on GSOC Project* "Proposal 16: Python API for Siddhi >> CEP"*. My internship project at WSO2 was almost entirely done using >> Python. Additionally, I used Py4J Framework to interface certain parts of >> the project to JAVA APIs. Furthermore, I have a certain amount of exposure >> with Siddhi/CEP through the WHACK project I took part. >> >> I went through the provided details in WSO2 GSOC 2017 Project List page >> and I am interested to know some more details. >> >>1. What version of CEP/Siddhi should be used by the API? >> >> You need to support the latest released version of Siddhi and DAS which > is in DAS 3.1 and also for the latest Siddhi (4.0) > >> >>1. In the description, does "Service APIs" refer to "Admin Services >>API" which is usually used by Admin Panel to communicate with CEP? >> >> Yes, to deploy the queries and to send and receive events > >> >>1. Should the Siddhi Python API require WSO2 CEP to be running in >>order to make Python API usable? >> >> Not necessay it should both work with the running CEP/DAS and use Siddhi > library in the ohter cases. > >> >>1. Is the Python API expected to do configuring of Siddhi CEP, >>streaming events to/from Siddhi CEP, or both? >> >> Yes in terms of queries. > > > >> Thank You >> >> >> -- >> *Madhawa Vidanapathirana* >> Student >> Department of Computer Science and Engineering >> University of Moratuwa >> Sri Lanka >> >> Mobile: (+94) 716874425 <071%20687%204425> >> Email: madhawavidanapathir...@gmail.com >> Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 >> > > > > -- > > *S. Suhothayan* > Associate Director / Architect & Team Lead of WSO2 Complex Event Processor > *WSO2 Inc. *http://wso2.com > * <http://wso2.com/>* > lean . enterprise . middleware > > > *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog: > http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: > http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: > http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* > -- *Madhawa Vidanapathirana* Student Department of Computer Science and Engineering University of Moratuwa Sri Lanka Mobile: (+94) 716874425 Email: madhawavidanapathir...@gmail.com Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP
Hi. I am an undergraduate from Department of Computer Science and Engineering, University of Moratuwa. I recently completed my internship at WSO2 working with the Support Team on the project WSO2 Support Knowledge Base. I am interested on GSOC Project* "Proposal 16: Python API for Siddhi CEP"*. My internship project at WSO2 was almost entirely done using Python. Additionally, I used Py4J Framework to interface certain parts of the project to JAVA APIs. Furthermore, I have a certain amount of exposure with Siddhi/CEP through the WHACK project I took part. I went through the provided details in WSO2 GSOC 2017 Project List page and I am interested to know some more details. 1. What version of CEP/Siddhi should be used by the API? 2. In the description, does "Service APIs" refer to "Admin Services API" which is usually used by Admin Panel to communicate with CEP? 3. Should the Siddhi Python API require WSO2 CEP to be running in order to make Python API usable? 4. Is the Python API expected to do configuring of Siddhi CEP, streaming events to/from Siddhi CEP, or both? Thank You -- *Madhawa Vidanapathirana* Student Department of Computer Science and Engineering University of Moratuwa Sri Lanka Mobile: (+94) 716874425 Email: madhawavidanapathir...@gmail.com Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
