Re: [Architecture] Custom AS specific WebApp configuration file for web applications

Adding DevStudio folks so that they can track this change. On Mon, Jul 6, 2015 at 2:20 PM, Kishanthan Thangarajah wrote: > Hi Sameera, > > We need to show that this file is specific to web-applications deployed on > AS and/or any other servers with webapp-mgt + CRE features right? > > So can we

Re: [Architecture] Proposal: C5 with MB (topic) based artifact distribution and topology management

On Thu, Jul 9, 2015 at 10:41 AM, Srinath Perera wrote: > If we only support MQTT only in light weight one, that should be possible. > > +1, MQTT is enough for our communications. > On Thu, Jul 9, 2015 at 10:38 AM, Afkham Azeez wrote: > >> Ramith what would involve making a really lightweight M

Re: [Architecture] Proposal: C5 with MB (topic) based artifact distribution and topology management

If we only support MQTT only in light weight one, that should be possible. On Thu, Jul 9, 2015 at 10:38 AM, Afkham Azeez wrote: > Ramith what would involve making a really lightweight MB? It would have a > lot of benefits. Like the lightweight Netty based JAXRS engine which is > performing a who

Re: [Architecture] Proposal: C5 with MB (topic) based artifact distribution and topology management

On Thu, Jul 9, 2015 at 10:16 AM, Ramith Jayasinghe wrote: > can't we make the single node work without having to go through topics etc? > and topic based artifact distribution mechanism get enabled only if > clustering is enabled? > > IMO, we should used same mechanism to both single and cluster

Re: [Architecture] Proposal: C5 with MB (topic) based artifact distribution and topology management

Ramith what would involve making a really lightweight MB? It would have a lot of benefits. Like the lightweight Netty based JAXRS engine which is performing a whole lot better than stock JAXRS as well as consuming less memory, it would be very useful to have a lightweight MB which can run on C5.

Re: [Architecture] Deploying an ESB Connector with a cApp?

Hi Malaka, As you noted, I will test for possible scenarios. Thank you. On Thu, Jul 9, 2015 at 10:10 AM, Malaka Silva wrote: > Hi Shakila, > > Good Progress on this. > > Let's verify some scenario similar to following, > >1. Include more that one connector. >2. Use the connector inside

Re: [Architecture] Proposal: C5 with MB (topic) based artifact distribution and topology management

can't we make the single node work without having to go through topics etc? and topic based artifact distribution mechanism get enabled only if clustering is enabled? On Thu, Jul 9, 2015 at 8:40 AM, Srinath Perera wrote: > Overall look good. > > How would the single node version work? Does it e

Re: [Architecture] Deploying an ESB Connector with a cApp?

Hi Shakila, Good Progress on this. Let's verify some scenario similar to following, 1. Include more that one connector. 2. Use the connector inside a proxy service, Api and sequence that are included in the same capp. On Wed, Jul 8, 2015 at 6:23 PM, Shakila Sivagnanarajah wrote: > H

Re: [Architecture] Proposal: C5 with MB (topic) based artifact distribution and topology management

Overall look good. How would the single node version work? Does it embed MB? Kernel, are we using JMS as message interface or wrap it in our own interface? --Srinath On Thu, Jul 2, 2015 at 3:49 PM, Lakmal Warusawithana wrote: > Hi, > > Had initial discussion with Azeez and Carbon team about

Re: [Architecture] [ESB] Guaranteed message delivery capability to the MSMP

[Adding missing images] Hi All. We had an internal review on the retry mechanism design and Please find below for the points discussed during the review. - If we enable guaranteed delivery for the message producer, a separate failover message store and a message processor[1] have been cre

Re: [Architecture] [ESB] Guaranteed message delivery capability to the MSMP

Hi All. We had an internal review on the retry mechanism design and Please find below for the points discussed during the review. - If we enable guaranteed delivery for the message producer, a separate failover message store and a message processor[1] have been created initially.Failove

[Architecture] WSO2 Data Analytics Server 3.0.0 Beta Released!

Hi all, The WSO2 DAS team is pleased to announce the beta release of WSO2 DAS 3.0.0. The distribution is available for download here . The release includes the following bug fixes, improvements, and tasks: Bug Fixes - [BAM-

Re: [Architecture] Deploying an ESB Connector with a cApp?

Hi all, I have done the connector deployment from CApp. Thank you On Wed, Jul 8, 2015 at 10:25 AM, Shakila Sivagnanarajah wrote: > Hi all, > > Please find the CApp [1]. > > This is my progress: > > 1. I added the connector zip in to the CApp as an artifact and specified > the artifact type as

Re: [Architecture] HTTP Inbound Endpoint - Dispatching logic

Hi All, We had a review on the implementation done for supporting the filtering logic. Please find below the points discussed during the review. - Exposing all the API/Proxy through the ports which we are creating inbound endpoints may affect the existing customers in a confusing manner.