Re: [Architecture] Are we missing a common EmailSenderService

+1 for this, Just go through the "email-verification" component. Implementation and config load for the email are there already. *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * * * email: **hars...@wso2.com* * cell: +94 71 5186770* * twitter: *

Re: [Architecture] Proposed code repository restructuring & move to GitHub

Hi, I have updated the component List doc with the components needs to remove from Git for Identity Server. Following will be removed. - user-stores - profile-mgt - xkms Thanks, On Tue, Jan 21, 2014 at 11:22 AM, Eranda Sooriyabandara wrote: > Hi all, > Doc for final component structure. > >

Re: [Architecture] [Dev] Proposed code repository restructuring & move to GitHub

On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed wrote: > On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah < > kishant...@wso2.com> wrote: > >> Yes, we don't need to separately say "service-stubs", it should be under >> the components level as just another component. >> > > Initially we

Re: [Architecture] [Dev] Proposed code repository restructuring & move to GitHub

Hi Shariq, Yeah, we may not needed those to be build again and again. So let's add related stubs to service-stubs directory in each repo. thanks Eranda On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed wrote: > On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah < > kishant...@wso2.com> w

Re: [Architecture] Are we missing a common EmailSenderService

Yes Harsha, there is an email verification service ( for confirming user) , but not a common service to send emails. But still we do have the methods for building the configuration, etc. If you look at the given reference in my initial mail, you will see that we have used those to complete the serv

Re: [Architecture] [Dev] Proposed code repository restructuring & move to GitHub

On Tue, Jan 21, 2014 at 2:42 PM, Eranda Sooriyabandara wrote: > Hi Shariq, > Yeah, we may not needed those to be build again and again. So let's add > related stubs to service-stubs directory in each repo. > Yea lets structure it that way. > > thanks > Eranda > > > On Tue, Jan 21, 2014 at 12:51

Re: [Architecture] [Dev] Proposed code repository restructuring & move to GitHub

Hi All Please find the updated governance component in [1]. thanks Eranda [1]. https://github.com/wso2/carbon-governance On Tue, Jan 21, 2014 at 2:56 PM, Shariq Muhammed wrote: > On Tue, Jan 21, 2014 at 2:42 PM, Eranda Sooriyabandara wrote: > >> Hi Shariq, >> Yeah, we may not needed those to

Re: [Architecture] Are we missing a common EmailSenderService

Yes, I just mentioned about the code implementation is available in that module. It is not published as a common service. :). *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * * * email: **hars...@wso2.com* * cell: +94 71 5186770* * twitter: **ht

Re: [Architecture] Are we missing a common EmailSenderService

Actually in CEP we have a common mechanism to send notifications using EventFormatter and OutputEventAdaptor. With this we can send any type of Notification. You can simply install this features and integrate with them to send Email/SMS May be you can use these components and implement an easy to

Re: [Architecture] [Dev] Proposed code repository restructuring & move to GitHub

How about WSO2 Commons projects, E.g Siddhi ? Currently its in commons and under dependencies/commons Where should we have this? I believe projects like Siddhi also need to be top level repos may be "commons-siddhi" and it don't need be in dependencies/commons anymore. WDYT? Suho On Tue, Jan

Re: [Architecture] Are we missing a common EmailSenderService

In that case we have to fix that. Suho On Tue, Jan 21, 2014 at 3:15 PM, Harsha Thirimanna wrote: > Yes, I just mentioned about the code implementation is available in that > module. It is not published as a common service. :). > > > *Harsha Thirimanna* > Senior Software Engineer; WSO2, Inc.;

[Architecture] Developer Studio 3.5.0 RC 1 Released!

Hi All, We have WSO2 Developer Studio 3.5.0 RC 1 ready to be downloaded at [1]. Installed eclipse distributions available at [2]. This release includes following bug fixes. Bug Fixes - [TOOLS-2312 ] - Complex Endpoint editor does not open when doub

Re: [Architecture] Invitation: APIM Progress update @ Mon Jan 20 11:30pm - Tue Jan 21, 2014 12:30am (samee...@wso2.com)

Hi all, Following is the meeting notes of $ Subject. Participants : APIM team, Store team ( Ruchira, SameeraM, Tanya ), Rajeeva, Venura *UI related modifications* 1. Modify the look and feel of "Asset details" page as of that of APIM - Fix the UI issues - Expand the applicatio

Re: [Architecture] Invitation: APIM Progress update @ Mon Jan 20 11:30pm - Tue Jan 21, 2014 12:30am (samee...@wso2.com)

Hi, Addition to Tanya's notes,following features/improvements noted as we expect to complete from ES side [sorry,if I repeat few..],while Sameera is working on adding APIM related custom pages and functionalties Features expecting from Store 1) Signup page need to extend with ability to prov

Re: [Architecture] Are we missing a common EmailSenderService

+1 for having a common email sender. I have seen in one support issue related to IS whether we can send emails when registering tenants, adding users to tenants etc. This scenario is valid for the whole products stack. Gayan Dhanuska Software Engineer http://wso2.com/ Lean Enterprise Middleware M

Re: [Architecture] Are we missing a common EmailSenderService

I believe the easy approach is to get the code from CEP Email Output Adaptor and Email-verification code and create a simple E-mail sender service. This service can then be used by both CEP Email Output Adaptor and Email-verification. In this process please keep in mind the performance aspects an

Re: [Architecture] Are we missing a common EmailSenderService

I think with this effort we can also remove the axis2 SMTP transport bindings. Suho On Tue, Jan 21, 2014 at 5:48 PM, Sriskandarajah Suhothayan wrote: > I believe the easy approach is to get the code from CEP Email Output > Adaptor and Email-verification code and create a simple E-mail sender >

Re: [Architecture] [Dev] Proposed code repository restructuring & move to GitHub

On Tue, Jan 21, 2014 at 3:34 PM, Sriskandarajah Suhothayan wrote: > How about WSO2 Commons projects, E.g Siddhi ? > > Currently its in commons and under dependencies/commons > > Where should we have this? > > I believe projects like Siddhi also need to be top level repos may be > "commons-siddhi"

Re: [Architecture] [Dev] Proposed code repository restructuring & move to GitHub

Hi all, +1 for Sagara's proposal. These projects have a life outside the Carbon Platform. But, we need to find a place to host them. If everything ends up on GitHub should these be in their too? If so, are they a WSO2 repository? Or is it a separate TLP? Thanks, Senaka. On Tue, Jan 21, 2014 at

Re: [Architecture] Proposed code repository restructuring & move to GitHub

Hi all, On Tuesday, January 21, 2014, Senaka Fernando wrote: > Hi all, > > +1 for Sagara's proposal. These projects have a life outside the Carbon > Platform. But, we need to find a place to host them. If everything ends up > on GitHub should these be in their too? If so, are they a WSO2 reposit

Re: [Architecture] [Dev] Proposed code repository restructuring & move to GitHub

On Wed, Jan 22, 2014 at 7:28 AM, Eranda Sooriyabandara wrote: > Hi all, > > > On Tuesday, January 21, 2014, Senaka Fernando wrote: > >> Hi all, >> >> +1 for Sagara's proposal. These projects have a life outside the Carbon >> Platform. But, we need to find a place to host them. If everything ends

Re: [Architecture] Should we have one place to define event streams?

I had a chat with Sanjiva as well and here are some of thoughts and a proposal. For high performance case, and when we do know the event definitions beforehand, it is BAD to redefine them every time. So shall we 1) Define all WSO2 inbuilt event definitions in corresponding toolboxes and use them

[Architecture] Fwd: [C5] Repository API/SPI

Shazni Nazeer Senior Software Engineer Mob : +94 715 440 607 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com -- Forwarded message -- From: Kishanthan Thangarajah Date: Wed, Jan 22, 2014 at 11:08 AM Subject: Re: [C5] Repository API/SPI T

Re: [Architecture] [Dev] Proposed code repository restructuring & move to GitHub

Yes most of the commons projects are not under development we can only move the actively developed projects. One suggestion, When looking at the WSO2 org in Git we have lots of junk repos. Are we going to remove then? Or can't we have a separate Git org called "WSO2 Middleware Platform" and have a

Re: [Architecture] CEP UI re-factoring and adding much more functionality

Hi Mohan, +1 for the design. IMO, the in-flow and out-flow UI will be very useful to get an idea about how the events are flowing, which is currently a bit lacking in CEP, I think. Great addition! Will the user be able to sample events generated in the stream UI to test a flow, or will that part

[Architecture] Provide support for self signup for tenants' APIStores

Hi, With current WSO2 APIStore self signup functionality,we do support only for super tenant APIStore. We are planning to extend it to support for tenant users as well. With current signup approach, we do two web service calls as; 1) call "UserSelfRegistrationService" to add the user 2) call "U

Re: [Architecture] [C5] Repository API/SPI

Hi Eranda, In the current context, MountHandler is dependant on the RemoteRegistry. I think we need to retain MountHandler in the kernel. How will be the removal of RemoteRegistry would affect that? regards, Shazni Nazeer Senior Software Engineer Mob : +94 715 440 607 LinkedIn : http://lk.link

Re: [Architecture] CEP UI re-factoring and adding much more functionality

On Wed, Jan 22, 2014 at 11:18 AM, Lasantha Fernando wrote: > Hi Mohan, > > +1 for the design. IMO, the in-flow and out-flow UI will be very useful to > get an idea about how the events are flowing, which is currently a bit > lacking in CEP, I think. Great addition! > > Will the user be able to sam