Re: [Dev] [ML] Wrangler Integration

Sure. Ill send the document and the PR Thanks, Danula On Fri, Sep 4, 2015 at 9:01 AM, Nirmal Fernando wrote: > Also please send a PR to our repos. > > On Fri, Sep 4, 2015 at 8:59 AM, Nirmal Fernando wrote: > >> Thanks Danula. >> >> ML team like to do the

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3

Hi ESB team, CXF_WS_RM type is not available in type drop down list in new inbound endpoint page of management console in ESB RC3 pack. And reported through jira[1]. [1].https://wso2.org/jira/browse/ESBJAVA-4171 Nayomi Dayarathne *Software Engineer-QA* Mobile : +94 (0) 775246619

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

Hi Raj, Thanks for pointing this out. I have now added the jinja2 dependency to configurator module and removed from PCA. [1] [1] https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/configurator/manifests/init.pp#L32 On Sat, Sep 5, 2015 at 3:14 PM, Rajkumar

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

How about this for apim integration? APIM has dipsync use case. KM needs the same userstore to be shared with. In a distributed setup which has both Greg and APIM nodes(may be multiple KM, GW as well), what would be the suggestion? On Fri, Sep 4, 2015 at 3:23 PM, Sagara Gunathunga

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

Hi Chaminda, APIM 1.9.1 will be used as GW and KM nodes. Since it is based on carbon 4.2.0, this won't be an issue. Regards, Chandana How about this for apim integration? APIM has dipsync use case. KM needs the same userstore to be shared with. In a distributed setup which has both Greg and

Re: [Dev] [ESB Inbound Endpoint UI] Parameter Display Name Changes in UI

Looks good with the change. Did you check the functionality afterwards? On Sat, Sep 5, 2015 at 12:29 PM, Rajjaz Mohammed wrote: > Hi Dev, > I'm working on Jira Issue[1] so please Check inbound endpoint Display > Names [2] . > UI Will Look Like [3] > > [1]

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3

Hi Nayomi, This feature has been separated from the ESB and available as an installable feature due to conflict with AS feature installation. Please find the p2-repo [1]. [1] https://drive.google.com/a/wso2.com/file/d/0B8Lypp0TU4cmWnRMVHBJRUZBblk/view?usp=sharing On Sat, Sep 5, 2015 at 5:20 PM,

[Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

Hi, I think python-pip & jinja2 should be installed by configurator puppet module, not by python agent. I am using vagrant, puppet and configurator to setup my development environment, but I am not using python agent. Since $subject is not done, I had to modify configurator puppet module. It

[Dev] [ESB Inbound Endpoint UI] Parameter Display Name Changes in UI

Hi Dev, I'm working on Jira Issue[1] so please Check inbound endpoint Display Names [2] . UI Will Look Like [3] [1] https://wso2.org/jira/browse/ESBJAVA-4075 [2] interval=Interval sequential=Sequential coordination=Coordination inbound.http.port=Http Port inbound.worker.pool.size.core=Number

Re: [Dev] [ESB Inbound Endpoint UI] Parameter Display Name Changes in UI

Yes, i checked malaka. Its work fine. On 5 Sep 2015 13:27, "Malaka Silva" wrote: > Looks good with the change. Did you check the functionality afterwards? > > On Sat, Sep 5, 2015 at 12:29 PM, Rajjaz Mohammed wrote: > >> Hi Dev, >> I'm working on Jira Issue[1]

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

Hi Raj, I think we should not remove python-pip from PCA module since those dependencies should be installed for PCA to function. @Anuruddha: I still see that jinja2 is packed from PCA module [1]. Shall we move this to configurator module? [1]

Re: [Dev] Downloadin wso2 product with ERROR 403: Forbidden.

Hi Jorge, You have to download the product via wso2.com website. On Sat, Sep 5, 2015 at 8:14 PM, Jorge wrote: > Hi folks, > When I try to download any wso2 product I find this error: > > > Resolving product-dist.wso2.com (product-dist.wso2.com)... 204.232.230.14 >

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3

Adding Buddhima On Sat, Sep 5, 2015 at 5:33 PM, Chanaka Fernando wrote: > Hi Nayomi, > > This feature has been separated from the ESB and available as an > installable feature due to conflict with AS feature installation. Please > find the p2-repo [1]. > > [1] >

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3

Hi Nayomi, Since CXF RM Inbound is install via a feature, it's not possible to integrate with UI dropdown. So you need to add it as a Custom Inbound. Please refer following post: https://buddhimawijeweera.wordpress.com/2015/09/05/reliable-messaging-with-wso2-esb/ Thanks, On Sat, Sep 5, 2015 at

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3

Please fix the folder permission in bin, lib, repository, resources, samples. Thanks, Deependra. On Fri, Sep 4, 2015 at 2:09 AM, Ravindra Ranwala wrote: > Hi Devs, > > WSO2 ESB 4.9.0 RC3 Release Vote > > This release fixes the following issues: >

Re: [Dev] Downloadin wso2 product with ERROR 403: Forbidden.

Hi Nirmal. So I cannot use a plugin in Firefox like DownThemAll to download your product after get the download url from your page? I try this right now and the 403 error appear. Jorge. De: Nirmal Fernando [mailto:nir...@wso2.com] Enviado el: sábado, 5 de septiembre de 2015 11:01

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3

Hi Buddhima, Please update the documentation with the relevant information. On Sat, Sep 5, 2015 at 7:03 PM, Nayomi Dayarathne wrote: > Hi, > > Appreciate if u can inform such changes when sharing new > packs..:)..:)..Therefore please make it update on ESB 4.9.0 document too.

Re: [Dev] [MB] Prioritize requirements for MB

Sure will discuss in detail, also somethings to add in relation to MQTT, - Clean session false (similar to durable subscriptions in AMQP) - Retain (persist a given message and distribute for new subscriptions) - Also QoS levels should be mixed (i.e if published at QoS 1 and subscribed with

[Dev] Downloadin wso2 product with ERROR 403: Forbidden.

Hi folks, When I try to download any wso2 product I find this error: Resolving product-dist.wso2.com (product-dist.wso2.com)... 204.232.230.14 Connecting to product-dist.wso2.com (product-dist.wso2.com)|204.232.230.14|:80... connected. HTTP request sent, awaiting response... 403 Forbidden ERROR

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3

Hi, Appreciate if u can inform such changes when sharing new packs..:)..:)..Therefore please make it update on ESB 4.9.0 document too. :) Nayomi Dayarathne *Software Engineer-QA* Mobile : +94 (0) 775246619 <+94+(0)+775246619> *nay...@wso2.com * On Sat, Sep 5, 2015 at 6:07

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3

Hi Chanaka, I've updated the doc. mentioning about installing from feature repo, and sample config. Thanks, On Sat, Sep 5, 2015 at 8:00 PM, Chanaka Fernando wrote: > Hi Buddhima, > > Please update the documentation with the relevant information. > > On Sat, Sep 5, 2015 at

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

Hi Raj, Yes, I meant python-pip should not be removed from PCA module but should be installed for configurator as well. I think it should be redefined for configurator module since python-pip is not a compulsory package. We can use Java agent without it. Thanks. On Sun, Sep 6, 2015 at 6:17 AM,

[Dev] [Private PaaS] Set JAVA_HOME as part of java installation via puppet

Hi, I think we need to do $Subject. Thanks, Raj. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org

Re: [Dev] [ESB] Security policy availability in ESB490

Hi Chanaka, Just noticed that even though we do not recommend to apply security policy application via the UI, a user may tend to create a "Secured proxy" via the esb console (may be for test purpose) since it is still available. If such secured proxy is created then he will be in a state of

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

On Sun, Sep 6, 2015 at 7:45 AM, Akila Ravihansa Perera wrote: > Hi Raj, > > I think we should not remove python-pip from PCA module since those > dependencies should be installed for PCA to function. > ​In the very similar way, python-pip should be installed for configurator

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

It is ok to redefined the python-pip module in configurator module since currently it is used in PCA and configurator only. But this might be a issue with other python libraries as well if that commonly used among the python modules.Also if there is several python modules exists we need to

Re: [Dev] [Private PaaS] Set JAVA_HOME as part of java installation via puppet

Hi Raj, I have done $subject. On Sun, Sep 6, 2015 at 9:37 AM, Rajkumar Rajaratnam wrote: > Hi, > > I think we need to do $Subject. > > Thanks, > Raj. > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Software Engineer, WSO2 > > Mobile : +94777568639 >

Re: [Dev] [Private PaaS] Set JAVA_HOME as part of java installation via puppet

Great. Thanks Anuruddha! On Sun, Sep 6, 2015 at 5:21 PM, Anuruddha Liyanarachchi wrote: > Hi Raj, > > I have done $subject. > > On Sun, Sep 6, 2015 at 9:37 AM, Rajkumar Rajaratnam > wrote: > >> Hi, >> >> I think we need to do $Subject. >> >> Thanks, >>

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

Hi, IMO we can define 'python-dev', 'python-pip' libraries in stratos base since they are required by configurator which is a mandatory module. Therefore, In configurator module we can inlcude jinja2; In PCA module we can include PCA related python dependencies