Re: [Architecture] [Dev] Common configuration for publishing events from carbon servers to DAS/CEP

Hi Malith, On Fri, Mar 18, 2016 at 11:42 AM, Malith Dhanushka wrote: > > > On Fri, Mar 18, 2016 at 11:38 AM, Kishanthan Thangarajah < > kishant...@wso2.com> wrote: > >> This new change is only for OSGi based servers in the platform right? Are >> there any changes for standalone data publishing A

Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines

I think for a major release such as 5.0, its quite important to get this kind of major limitations fixed (this has been raised in several occasions AFAIR) Lets spend sometime and evaluate the effort involves with this. For Connectors, if this introduce any issues, we have to fix them and re-releas

[Architecture] OSGi ServiceLoader for Carbon

Hi all, The Carbon uses Apache Aries SPI-Fly Dynamic Weaving[1] bundle to mediate the Java ServiceLoader mechanism in the OSGi environment[2]. In order to work the API bundles (Bundles that uses Java ServceLoader to find the implementation classes) the SPI-Fly mediator bundle should start 1st befo

[Architecture] [Ann] WSO2 App Cloud 3.0.0-Alpha Released!

WSO2 App Cloud 3.0.0-Alpha Release WSO2 App Cloud team is pleased to announce the release of version 3.0.0-Alpha of the WSO2 App Cloud. WSO2 App Cloud is a multi-tenant, elastic and self-service enterprise platform that enables hosting applications written in multiple languages on multiple runtim

[Architecture] WSO2 Carbon Feature Plugin 2.0.1 Released

*WSO2 Carbon Feature Plugin 2.0.1 Released* The Carbon team is pleased to announce the release of Carbon Feature Plugin 2.0.1. It is now available to download from here . *Improvements and Bug fixes* https://wso2.org/jira/issues/?f

Re: [Architecture] [Dev] [C5] Must Inject CarbonServerInfo when writing OSGi Test Cases

On Mon, Apr 11, 2016 at 4:47 PM, Nilmini Perera wrote: > Updated the doc [1]. Hope this will do. Let me know if anything is > incorrect. > Looks good. Thanks Nilmini. > > [1] https://docs.wso2.com/display/Carbon500/In-Container+OSGi+Testing > > Thanks, > Nilmini > > On Fri, Apr 8, 2016 at 12:13

Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines

Hi all, Current script mediator implementation depends on apache-commons-bsf-3.0 to get the script engines for Rhino, Ruby, Groovy and Jython [1][2]. However, moving forward if we are to support newer Rhino and Nashorn (for Java 8) we can directly use these engines or any other implementation of o

Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines

@PrabathAR - Can you give us more details on this please? Inside Rhino engine, we can set optimization levels[1] which change the behavior of the engine. Default level is 0 and no optimizations are performed, but we can set this level in between -1 and 9 for the different optimizations. We can set

Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines

We have to check if all use cases are supported if we are going to upgrade or going for an alternative solutions. Also some connectors are heavily using script mediator. IMO we should not plan to do this for the immediate release. On Mon, Apr 11, 2016 at 12:34 PM, Vanjikumaran Sivajothy wrote:

Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines

With JDK 8, there is an in-build JS engine called Nashorn. Isn't that worth to leverage the JS support by using native implementation to JDK 8? [1] http://www.oracle.com/technetwork/articles/java/jf14-nashorn-2126515.html On Sun, Apr 10, 2016 at 11:57 PM, Malaka Silva wrote: > PrabathAR has al