Re: [Architecture] APIM Supporting additional endpoint types

2013-10-02 Thread Joseph Fonseka
Hi Sanjiva Jo does this also address secured endpoints? E.g. basic auth secured or > WSSec-UT or other (as long as its supported by the ESB)? > The plan is to add most of the Endpoint configuration to the Publisher UI without over complicating it. So I guess we can handle WSSec-UT as well and ba

Re: [Architecture] [Dev] Why we are refactoring the CarbonContext API Usage in the Carbon platform?

2013-10-02 Thread Sanjiva Weerawarana
Sameera isn't CarbonContext.getCurrentContext() supposed to return the context associated with the current thread??? On Tue, Oct 1, 2013 at 11:45 AM, Sameera Jayasoma wrote: > Hi Folks, > > Some of you may be wondering why we are doing this change now. The > simplest reason is, to ensure the co

Re: [Architecture] APIM Supporting additional endpoint types

2013-10-02 Thread Sanjiva Weerawarana
On Wed, Oct 2, 2013 at 2:50 PM, Joseph Fonseka wrote: > In the current APIM we only support Address endpoint type. So we are >> planing to include other endpoint types which are supported by the ESB. >> >> Following are the other endpoint types >> >>Address Endpoint >>

Re: [Architecture] Changes to CEP 3.0.0 to improve usablity

2013-10-02 Thread Mohanadarshan Vivekanandalingam
Hi, On Wed, Oct 2, 2013 at 9:06 PM, Lasantha Fernando wrote: >>> Hi all, The following changes were proposed to CEP 3.0.0 to improve the usability of CEP. 1) EventStream UI is the central place to store all the event streams. Event stream management will be dec

Re: [Architecture] Changes to CEP 3.0.0 to improve usablity

2013-10-02 Thread Srinath Perera
On Wed, Oct 2, 2013 at 11:36 PM, Lasantha Fernando wrote: > Hi Srinath, > > > On 2 October 2013 21:25, Srinath Perera wrote: > >> Hi Lasantha, >> >> >> On Wed, Oct 2, 2013 at 9:06 PM, Lasantha Fernando wrote: >> >>> Hi all, >>> >>> The following changes were proposed to CEP 3.0.0 to improve the >

Re: [Architecture] [Dev] WSO2 Message Broker 2.1.1 - Alpha Released!

2013-10-02 Thread Shammi Jayasinghe
Hi Isuru, Yes, We will support it with the version 3.0.0. Please find the road map of MB [1] [1]https://redmine.wso2.com/projects/wso2-mb/roadmap Thanks Shammi On Wed, Oct 2, 2013 at 9:52 PM, Isuru Perera wrote: > Any plans to support AMQP 1.0? > > > On Wed, Oct 2, 2013 at 9:26 PM, Ishara Pr

Re: [Architecture] Changes to CEP 3.0.0 to improve usablity

2013-10-02 Thread Lasantha Fernando
Hi Srinath, On 2 October 2013 21:25, Srinath Perera wrote: > Hi Lasantha, > > > On Wed, Oct 2, 2013 at 9:06 PM, Lasantha Fernando wrote: > >> Hi all, >> >> The following changes were proposed to CEP 3.0.0 to improve the usability >> of CEP. >> >> 1) EventStream UI is the central place to store

Re: [Architecture] Changes to CEP 3.0.0 to improve usablity

2013-10-02 Thread Sriskandarajah Suhothayan
On Wed, Oct 2, 2013 at 8:55 AM, Srinath Perera wrote: > Hi Lasantha, > > > On Wed, Oct 2, 2013 at 9:06 PM, Lasantha Fernando wrote: > >> Hi all, >> >> The following changes were proposed to CEP 3.0.0 to improve the usability >> of CEP. >> >> 1) EventStream UI is the central place to store all the

Re: [Architecture] [Dev] WSO2 Message Broker 2.1.1 - Alpha Released!

2013-10-02 Thread Isuru Perera
Any plans to support AMQP 1.0? On Wed, Oct 2, 2013 at 9:26 PM, Ishara Premadasa wrote: > *WSO2 Message Broker 2.1.1- Alpha Released!* > > WSO2 MB team is pleased to announce the 2.1.1- Alpha release of the WSO2 > Message Broker. > > WSO2 Message Broker 2.1.1, JMS message broker backed up with t

[Architecture] [Dev] WSO2 Message Broker 2.1.1 - Alpha Released!

2013-10-02 Thread Ishara Premadasa
*WSO2 Message Broker 2.1.1- Alpha Released!* WSO2 MB team is pleased to announce the 2.1.1- Alpha release of the WSO2 Message Broker. WSO2 Message Broker 2.1.1, JMS message broker backed up with the wso2 distributed message brokering engine "Andes" is compliant with AMQP 0-91 version. The new alp

Re: [Architecture] Changes to CEP 3.0.0 to improve usablity

2013-10-02 Thread Srinath Perera
Hi Lasantha, On Wed, Oct 2, 2013 at 9:06 PM, Lasantha Fernando wrote: > Hi all, > > The following changes were proposed to CEP 3.0.0 to improve the usability > of CEP. > > 1) EventStream UI is the central place to store all the event streams. > Event stream management will be decoupled from the

[Architecture] Changes to CEP 3.0.0 to improve usablity

2013-10-02 Thread Lasantha Fernando
Hi all, The following changes were proposed to CEP 3.0.0 to improve the usability of CEP. 1) EventStream UI is the central place to store all the event streams. Event stream management will be decoupled from the EB/EF/EP components and a separate component will be created to manage event streams.

[Architecture] Discussion on Depsync based on MB

2013-10-02 Thread Srinath Perera
Participants: Sanjiva, Sameera, Shankar, Lakmal, Azeez, + Stratos team Stratos will use JMS, that path is cleared We will look at persistant subscription in Hazecast. If not we need to move to MB. We need lightweight MB regardless - DB based MB - HCast without ZK We will switching to Git and d

Re: [Architecture] OAuth2 Scope and Resource Owner Validation

2013-10-02 Thread Prabath Siriwardena
+1 Currently IS and API-M use two different services for token validation. So - lets get rid-of this code duplication first and then work on the improvements... Thanks & regards, -Prabath On Wed, Oct 2, 2013 at 11:05 AM, Johann Nallathamby wrote: > Currently the OAuth2 scopes and resource ow

Re: [Architecture] APIM Supporting additional endpoint types

2013-10-02 Thread Joseph Fonseka
Forwarding mail to Architecture from dev. On Wed, Oct 2, 2013 at 2:12 PM, Joseph Fonseka wrote: > > Hi > > In the current APIM we only support Address endpoint type. So we are > planing to include other endpoint types which are supported by the ESB. > > Following are the other endpoint types > >

Re: [Architecture] Ordering Window and Debug Status for CEP

2013-10-02 Thread Sriskandarajah Suhothayan
On Mon, Sep 30, 2013 at 4:37 AM, Srinath Perera wrote: > Like to propose two new features for CEP > > 1) New Window that collect data, order them by a given ID (including > timestamp), and then re-emit them to the pipeline down stream in a batch > style periodically. This us useful for event reor