[Architecture] Developer Studio 3.7.0 RC 3 Released!

Hi All, We have WSO2 Developer Studio 3.7.0 RC3 ready to be downloaded at [1] and installed eclipse distributions available at [2]. This release includes following bug fixes, improvements. *Improvement* [TOOLS-2559] https://wso2.org/jira/browse/TOOLS-2559 - App Factory Tools - Add support for

[Architecture] Coordination support for Message Store and Processors

Hi, We need to support $subject. As we support coordination for ESB tasks through ntask integration, we can use the same concept to execute the message processor tasks too. The main objective is to execute a message processor on an elected worker node in a given cluster deployment.

[Architecture] Unwanted application deployment notifications in AppFactory

Hi All, Following is the problem-solution description regards to jira APPFAC-2252 https://wso2.org/jira/browse/APPFAC-2252 *Problem :* AppServer tenant get unloaded when there is no activity for 30mins. When a user deploy an app to this unloaded tenant, it will load and deploy all previously

Re: [Architecture] Unwanted application deployment notifications in AppFactory

Hi Anuruddha, How do we handle a scenario where developer1 click on deploy of 1.0.0 version and at the same time, developer2 click on deploy of 2.0.0 version of same application? AFAIU, both developer1 and developer2 will notice that 1.0.0 and 2.0.0 both deployment messages in App wall. IMO this

Re: [Architecture] Unwanted application deployment notifications in AppFactory

I think this will apply to everything deployed in WSO2 servers. Currently we only have app server based app types only. So Anuruddha remember to change data service path as well (service deployment listener) and you will need to test for all app types. And Dimuthu what's happening to jaggery apps?

Re: [Architecture] Unwanted application deployment notifications in AppFactory

Hi Anuraddha, Need to test with Jaggery apps as well. thanks, dimuthu On Tue, Jul 1, 2014 at 6:03 PM, Danushka Fernando danush...@wso2.com wrote: I think this will apply to everything deployed in WSO2 servers. Currently we only have app server based app types only. So Anuruddha remember to

Re: [Architecture] Unwanted application deployment notifications in AppFactory

What I mentioned was last time remember jaggery app is not an single artifact. Its a folder. So how we can handle md5sum? On Jul 1, 2014 6:07 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Anuraddha, Need to test with Jaggery apps as well. thanks, dimuthu On Tue, Jul 1, 2014 at

Re: [Architecture] Unwanted application deployment notifications in AppFactory

Yes Danushka, if we are going to avoid user deploying the same artifact it will be fine. And +1 for implementing that ( avoid deployment and notify user ) On Tue, Jul 1, 2014 at 6:20 PM, Danushka Fernando danush...@wso2.com wrote: There are two sides to that. But IMO There is no point in

[Architecture] Fixing CApp story for Carbon 4.3.0

Hi All, We recently had a meeting on $subject. Our current story for CApp (Carbon Application) development approach is broken when including application of QoS for services. This was mainly due to the issues we faced with, - the file-based metadata persistence layer for services. - the

Re: [Architecture] Unwanted application deployment notifications in AppFactory

Hi, For the WebApplication there may be some initialization process with the context listeners when it deploy. Because of some reason, developer wants to redeploy the same app to check or redo the initialization process using that context listeners, we are unable to support it if we allow the