[Architecture] WSO2 Identity Server 5.1.0 Milestone 5 Released!

WSO2 Identity Server 5.1.0 Milestone 5 Released! Date: 31st July 2015The WSO2 Identity Server team is pleased to announce the 5th Milestone of WSO2 Identity Server 5.1.0. You can download this distribution from https://github.com/wso2/product-is/releases/tag/v5.1.0-m5 Following list [1] contains a

Re: [Architecture] Possible issue with the new GW implementation

Hi all, I think there are two aspects, handling connections and handling requests coming through connections. Basically what happens is Threads in BossGroup accepts the incoming connections and after accepting it. It creates a channel pipelines for each connection and handover accepted connection

Re: [Architecture] Implement File Connector for zip file for WSO2 ESB

Hi Malaka, I will do that one . *Thank youVivekananthan Sivanayagam* *Associate Software Engineer | WSO2* *E:vivekanant...@wso2.com * *M:+94752786138* On Thu, Jul 30, 2015 at 7:55 PM, Malaka Silva wrote: > Looks good. > > Also include a load testing in your plan. > > On Thu, Jul 30, 2015

Re: [Architecture] [GSoC] JMS 2.0 support for WSO2 ESB JMS Inbound Endpoint and JMS Transport

Hi, This is the progress update on my work. For the JMS Delivery Delay feature, I have done the implementation and sent the PR[1]. Currently, working on a sample, to demonstrate it and a integration test. You can find the working repo in here [2]. [1]. https://github.com/wso2/wso2-axis2-transport

Re: [Architecture] Implement File Connector for zip file for WSO2 ESB

Looks good. Also include a load testing in your plan. On Thu, Jul 30, 2015 at 6:49 PM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Introduction > > The File connector > allows you > to connect to different file syste

[Architecture] Implement File Connector for zip file for WSO2 ESB

Introduction The File connector allows you to connect to different file systems and perform various operations with the file systems. The file connector uses the apache commons VFS I/O functionalities to execute operations. File Conne

[Architecture] WSO2 EMM 2.0.0 Milestone - 5 Released

Hi All, WSO2 EMM 2.0.0 Milestone - 5 Released ! This is the fifth milestone of WSO2 EMM version 2.0.0. You can download the milestone at [1]. Milestone - 5 specifically contains following features. New Features Enhancements to policy management framework and compliance monitoring framework

Re: [Architecture] [Connector + Inbound] RSS/Atom feed Connector + Inbound for WSO2 ESB

Looks good On Thu, Jul 30, 2015 at 5:25 PM, Rajjaz Mohammed wrote: > Hi Malaka, > as you mentioned implementation will be polling inbound and Connector for > Atom/RSS feed. i will post diagram soon after study further about Apache > abdera framework working flow. > > here is my Milestone plan >

Re: [Architecture] [Connector + Inbound] RSS/Atom feed Connector + Inbound for WSO2 ESB

Hi Malaka, as you mentioned implementation will be polling inbound and Connector for Atom/RSS feed. i will post diagram soon after study further about Apache abdera framework working flow. here is my Milestone plan https://docs.google.com/a/wso2.com/spreadsheets/d/12wFJ1l0ffkOirvLSzO5A7T4ySiH3pIa

Re: [Architecture] Possible issue with the new GW implementation

Netty 5.x is still in alpha and 4.x is current stable. On Thu, Jul 30, 2015 at 2:32 PM, Afkham Azeez wrote: > Shouldn't we be using Netty 5? > > On Thu, Jul 30, 2015 at 2:26 PM, Ravi Undupitiya wrote: > >> Hi Azeez, >> >> The reason for using a worker for executing engine tasks is to avoid >> u

Re: [Architecture] Possible issue with the new GW implementation

Shouldn't we be using Netty 5? On Thu, Jul 30, 2015 at 2:26 PM, Ravi Undupitiya wrote: > Hi Azeez, > > The reason for using a worker for executing engine tasks is to avoid using > an I/O thread to do the same. AFAIU the pipeline is executed from an I/O > thread. However, we might be able to shar

Re: [Architecture] Possible issue with the new GW implementation

Hi Azeez, The reason for using a worker for executing engine tasks is to avoid using an I/O thread to do the same. AFAIU the pipeline is executed from an I/O thread. However, we might be able to share the existing netty worker pool [1] and place our worker in it. We'll update the code to use this.

Re: [Architecture] Stratos Membership Scheme for Automatically Discovering Carbon Instances in a Carbon Cluster

Hi Sameera, I have completed the initial implementation of the Membership Scheme Extension Model and sent a pull request [1]. I tested this with Application Server 5.3.0-SNAPSHOT distribution. Please review and let me know your thoughts. [1] https://github.com/wso2/carbon4-kernel/pull/355 Thanks