Re: [Dev] [Orbit] Please merge PR for spark-mllib_2.10 version 1.4.1.wso2v3

[Manoj Kumara]

Seems its an authorization issue with the server based on the error log.

*Manoj Kumara*
WSO2 Inc. *| **lean. enterprise. middleware.*
*Mobile:* +94 713 448188

On Tue, Jul 26, 2016 at 12:07 PM, Maheshika Goonetilleke  wrote:

> Hi Manoj
>
> Came across the following error
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
> on project spark-mllib_2.10: Failed to deploy artifacts: Could not transfer
> artifact org.wso2.orbit.org.apache.spark:spark-mllib_2.10:jar:1.4.1.wso2v3
> from/to wso2.releases (
> http://maven.wso2.org/nexus/content/repositories/releases/): Failed to
> transfer file:
> http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/orbit/org/apache/spark/spark-mllib_2.10/1.4.1.wso2v3/spark-mllib_2.10-1.4.1.wso2v3.jar.
> Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project spark-mllib_2.10: Failed to deploy artifacts:
> Could not transfer artifact
> org.wso2.orbit.org.apache.spark:spark-mllib_2.10:jar:1.4.1.wso2v3 from/to
> wso2.releases (http://maven.wso2.org/nexus/content/repositories/releases/):
> Failed to transfer file:
> http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/orbit/org/apache/spark/spark-mllib_2.10/1.4.1.wso2v3/spark-mllib_2.10-1.4.1.wso2v3.jar.
> Return code is: 401, ReasonPhrase: Unauthorized.
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:606)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
> deploy artifacts: Could not transfer artifact
> org.wso2.orbit.org.apache.spark:spark-mllib_2.10:jar:1.4.1.wso2v3 from/to
> wso2.releases (http://maven.wso2.org/nexus/content/repositories/releases/):
> Failed to transfer file:
> http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/orbit/org/apache/spark/spark-mllib_2.10/1.4.1.wso2v3/spark-mllib_2.10-1.4.1.wso2v3.jar.
> Return code is: 401, ReasonPhrase: Unauthorized.
>
> at
> org.apache.maven.plugin.deploy.DeployMojo.deployProject(DeployMojo.java:284)
>
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:169)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>
> ... 19 more
>
> Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
> Failed to deploy artifacts: Could not transfer artifact
> org.wso2.orbit.org.apache.spark:spark-mllib_2.10:jar:1.4.1.wso2v3 from/to
> wso2.releases (http://maven.wso2.org/nexus/content/repositories/releases/):
> Failed to transfer file:
> http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/orbit/org/apache/spark/spark-mllib_2.10/1.4.1.wso2v3/spark-mllib_2.10-1.4.1.wso2v3.jar.
> Return code is: 401, ReasonPhrase: Unauthorized.
>
> at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:141)
>
> at
> org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:171)
>
> at
> org.apache.maven.plugin.deploy.DeployMojo.deployProject(DeployMojo.java:250)
>
> ... 22 more
>
> Caused by: org.sonatype.aether.deployment.DeploymentException: Failed to
> d

Re: [Dev] [Orbit] Please merge PR for spark-mllib_2.10 version 1.4.1.wso2v3

[Maheshika Goonetilleke]

Hi Manoj

Came across the following error

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
on project spark-mllib_2.10: Failed to deploy artifacts: Could not transfer
artifact org.wso2.orbit.org.apache.spark:spark-mllib_2.10:jar:1.4.1.wso2v3
from/to wso2.releases (
http://maven.wso2.org/nexus/content/repositories/releases/): Failed to
transfer file:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/orbit/org/apache/spark/spark-mllib_2.10/1.4.1.wso2v3/spark-mllib_2.10-1.4.1.wso2v3.jar.
Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
(default-deploy) on project spark-mllib_2.10: Failed to deploy artifacts:
Could not transfer artifact
org.wso2.orbit.org.apache.spark:spark-mllib_2.10:jar:1.4.1.wso2v3 from/to
wso2.releases (http://maven.wso2.org/nexus/content/repositories/releases/):
Failed to transfer file:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/orbit/org/apache/spark/spark-mllib_2.10/1.4.1.wso2v3/spark-mllib_2.10-1.4.1.wso2v3.jar.
Return code is: 401, ReasonPhrase: Unauthorized.

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)

at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)

Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to deploy
artifacts: Could not transfer artifact
org.wso2.orbit.org.apache.spark:spark-mllib_2.10:jar:1.4.1.wso2v3 from/to
wso2.releases (http://maven.wso2.org/nexus/content/repositories/releases/):
Failed to transfer file:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/orbit/org/apache/spark/spark-mllib_2.10/1.4.1.wso2v3/spark-mllib_2.10-1.4.1.wso2v3.jar.
Return code is: 401, ReasonPhrase: Unauthorized.

at
org.apache.maven.plugin.deploy.DeployMojo.deployProject(DeployMojo.java:284)

at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:169)

at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)

... 19 more

Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Failed to deploy artifacts: Could not transfer artifact
org.wso2.orbit.org.apache.spark:spark-mllib_2.10:jar:1.4.1.wso2v3 from/to
wso2.releases (http://maven.wso2.org/nexus/content/repositories/releases/):
Failed to transfer file:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/orbit/org/apache/spark/spark-mllib_2.10/1.4.1.wso2v3/spark-mllib_2.10-1.4.1.wso2v3.jar.
Return code is: 401, ReasonPhrase: Unauthorized.

at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:141)

at
org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:171)

at
org.apache.maven.plugin.deploy.DeployMojo.deployProject(DeployMojo.java:250)

... 22 more

Caused by: org.sonatype.aether.deployment.DeploymentException: Failed to
deploy artifacts: Could not transfer artifact
org.wso2.orbit.org.apache.spark:spark-mllib_2.10:jar:1.4.1.wso2v3 from/to
wso2.releases (http://maven.wso2.org/nexus/content/repositories/releases/):
Failed to transfer file:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/orbit/org/apache/spark/spark-mllib_2.10/1.4.1.wso2v3/spark-mllib_2.10-1.4.1.wso2v3.jar.
Return code is: 401, ReasonPhrase: Unauthorized.

at
or

Re: [Dev] Encoding issue in JSPs

[Farasath Ahamed]

+ Kishanthan, Johann

Farasath Ahamed
Software Engineer, WSO2 Inc.; http://wso2.com
Mobile: +94777603866
Blog: blog.farazath.com
Twitter: @farazath619 




On Tue, Jul 26, 2016 at 11:22 AM, Farasath Ahamed 
wrote:

> Hi,
>
> I am sending some UTF-8 encoded texts from a form to a JSP(ajax
> processor). In the JSP I read the request parameters using,
>
> String emailSubject = request.getParameter("emailSubject");
> String emailBody = request.getParameter("emailBody");
> String emailFooter = request.getParameter("emailFooter");
>
> This scenario works fine with IS 5.3.0-M1 which is based on 4.4.5 kernel.
> But when I run the same code without any changes on IS 5.3.0-M3 which is
> based on 4.4.7 encoding doesn't seem to work.
>
> Appreciate your help to find the root cause.
>
>
> Thanks,
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Akila Ravihansa Perera]

[+1] Stable - Go ahead and release

1. Verified the License Headers with RAT Tool.
2. Checked distribution.
3. Tested wso2esb-4.9.0 using default and puppet provisioning

On Tue, Jul 26, 2016 at 11:17 AM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi All,
>
> I have tested the following.
>
> 1. Verified the License Headers with RAT Tool.
> 2. Checked distribution.
> 3. Test following product with puppet provisioning.
>
>- APIM 1.10.0
>- AS 5.3.0
>- BPS 3.5.0
>- BRS 2.2.0
>- CEP 4.0.0
>
>
>
> On Tue, Jul 26, 2016 at 11:14 AM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have tested the following.
>>
>> 1. Verified the License Headers with RAT Tool.
>> 2. Checked distribution.
>> 3. Test following product with puppet provisioning.
>>
>>
>>
>> On Mon, Jul 25, 2016 at 10:30 PM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> [+1] Stable - Go ahead and release
>>>
>>> Verified the following:
>>> 1. Distribution
>>> 2. License Headers
>>> 3. Built following products docker images with puppet provisioning for
>>> Mesos platform and tested basic functionalities:
>>>
>>>
>>>- WSO2 ES 2.0.0 (Distributed setup)
>>>-  WSO2 ESB 4.9.0 (Distributed setup)
>>>-  WSO2 MB 3.1.0
>>>-  WSO2 IS 5.1.0
>>>-  WSO2 IS KM 5.1.0
>>>
>>> Thanks.
>>>
>>> On Fri, Jul 22, 2016 at 9:27 PM, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
 Hi Devs,

 This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
 release.

 *This release fixes the following issues:*

 https://wso2.org/jira/issues/?filter=13159

 *Tag to be voted upon:*

 https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1

 *Source and distribution packages:*

 https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1

 Please download, test, and vote. The README file under the distribution
 contains guide and instructions on how to try it out locally.

 [+] Stable - Go ahead and release

 [-] Broken - Do not release (explain why)



 This vote will be open for 72 hours or as needed.

 Regards,
 WSO2 PaaS team


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Thanuja Uruththirakodeeswaran
>>> Software Engineer
>>> WSO2 Inc.;http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 774363167
>>>
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Thanks and Regards,*
>> Anuruddha Lanka Liyanarachchi
>> Software Engineer - WSO2
>> Mobile : +94 (0) 712762611
>> Tel  : +94 112 145 345
>> a nurudd...@wso2.com
>>
>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

Blog: http://ravihansa3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Orbit] Please merge PR for spark-mllib_2.10 version 1.4.1.wso2v3

[Manoj Kumara]

Merged the PR.

@Maheshika, can you release it.

Regards,
Manoj

*Manoj Kumara*
WSO2 Inc. *| **lean. enterprise. middleware.*
*Mobile:* +94 713 448188

On Tue, Jul 26, 2016 at 9:22 AM, Supun Sethunga  wrote:

> Hi Manoj,
>
> Did the changes as per the comment. Can you please review it?
>
> Thanks,
> Supun
>
> On Mon, Jul 25, 2016 at 6:25 PM, Manoj Kumara  wrote:
>
>> Hi Supun,
>>
>> Added a comment. Please resolve that.
>>
>> Regards,
>> manoj
>>
>> *Manoj Kumara*
>> WSO2 Inc. *| **lean. enterprise. middleware.*
>> *Mobile:* +94 713 448188
>>
>> On Mon, Jul 25, 2016 at 5:23 PM, Supun Sethunga  wrote:
>>
>>> Hi Carbon Team,
>>>
>>> Can you please review and merge PR[1]? This is a fix for [2].
>>>
>>> [1] https://github.com/wso2/orbit/pull/222
>>> [2] https://wso2.org/jira/browse/CEP-1471
>>>
>>> Regards,
>>> Supun
>>>
>>> --
>>> *Supun Sethunga*
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> http://wso2.com/
>>> lean | enterprise | middleware
>>> Mobile : +94 716546324
>>> Blog: http://supunsetunga.blogspot.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> *Supun Sethunga*
> Senior Software Engineer
> WSO2, Inc.
> http://wso2.com/
> lean | enterprise | middleware
> Mobile : +94 716546324
> Blog: http://supunsetunga.blogspot.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Encoding issue in JSPs

[Farasath Ahamed]

Hi,

I am sending some UTF-8 encoded texts from a form to a JSP(ajax processor).
In the JSP I read the request parameters using,

String emailSubject = request.getParameter("emailSubject");
String emailBody = request.getParameter("emailBody");
String emailFooter = request.getParameter("emailFooter");

This scenario works fine with IS 5.3.0-M1 which is based on 4.4.5 kernel.
But when I run the same code without any changes on IS 5.3.0-M3 which is
based on 4.4.7 encoding doesn't seem to work.

Appreciate your help to find the root cause.


Thanks,
Farasath Ahamed
Software Engineer, WSO2 Inc.; http://wso2.com
Mobile: +94777603866
Blog: blog.farazath.com
Twitter: @farazath619 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Anuruddha Liyanarachchi]

Hi All,

I have tested the following.

1. Verified the License Headers with RAT Tool.
2. Checked distribution.
3. Test following product with puppet provisioning.

   - APIM 1.10.0
   - AS 5.3.0
   - BPS 3.5.0
   - BRS 2.2.0
   - CEP 4.0.0



On Tue, Jul 26, 2016 at 11:14 AM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi All,
>
> I have tested the following.
>
> 1. Verified the License Headers with RAT Tool.
> 2. Checked distribution.
> 3. Test following product with puppet provisioning.
>
>
>
> On Mon, Jul 25, 2016 at 10:30 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> [+1] Stable - Go ahead and release
>>
>> Verified the following:
>> 1. Distribution
>> 2. License Headers
>> 3. Built following products docker images with puppet provisioning for
>> Mesos platform and tested basic functionalities:
>>
>>
>>- WSO2 ES 2.0.0 (Distributed setup)
>>-  WSO2 ESB 4.9.0 (Distributed setup)
>>-  WSO2 MB 3.1.0
>>-  WSO2 IS 5.1.0
>>-  WSO2 IS KM 5.1.0
>>
>> Thanks.
>>
>> On Fri, Jul 22, 2016 at 9:27 PM, Anuruddha Liyanarachchi <
>> anurudd...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
>>> release.
>>>
>>> *This release fixes the following issues:*
>>>
>>> https://wso2.org/jira/issues/?filter=13159
>>>
>>> *Tag to be voted upon:*
>>>
>>> https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1
>>>
>>> *Source and distribution packages:*
>>>
>>> https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1
>>>
>>> Please download, test, and vote. The README file under the distribution
>>> contains guide and instructions on how to try it out locally.
>>>
>>> [+] Stable - Go ahead and release
>>>
>>> [-] Broken - Do not release (explain why)
>>>
>>>
>>>
>>> This vote will be open for 72 hours or as needed.
>>>
>>> Regards,
>>> WSO2 PaaS team
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>



-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Anuruddha Liyanarachchi]

Hi All,

I have tested the following.

1. Verified the License Headers with RAT Tool.
2. Checked distribution.
3. Test following product with puppet provisioning.



On Mon, Jul 25, 2016 at 10:30 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> [+1] Stable - Go ahead and release
>
> Verified the following:
> 1. Distribution
> 2. License Headers
> 3. Built following products docker images with puppet provisioning for
> Mesos platform and tested basic functionalities:
>
>
>- WSO2 ES 2.0.0 (Distributed setup)
>-  WSO2 ESB 4.9.0 (Distributed setup)
>-  WSO2 MB 3.1.0
>-  WSO2 IS 5.1.0
>-  WSO2 IS KM 5.1.0
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 9:27 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
>> release.
>>
>> *This release fixes the following issues:*
>>
>> https://wso2.org/jira/issues/?filter=13159
>>
>> *Tag to be voted upon:*
>>
>> https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1
>>
>> *Source and distribution packages:*
>>
>> https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1
>>
>> Please download, test, and vote. The README file under the distribution
>> contains guide and instructions on how to try it out locally.
>>
>> [+] Stable - Go ahead and release
>>
>> [-] Broken - Do not release (explain why)
>>
>>
>>
>> This vote will be open for 72 hours or as needed.
>>
>> Regards,
>> WSO2 PaaS team
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Enable debug logs for proxies and apis

[Udara Liyanage]

Hi Elilmatha,

1) I want to enable it for every proxy and api, otherwise we have to add
log4j configs every time we add a proxy and api which is not practical
where there are 10+ proxies

2) Below is my api config and log4j config. Still debug logs are not
printed.

http://ws.apache.org/ns/synapse"; name="*getUsers*"
context="/users">
   
  
 

 
 

 

  
  
   



# Configure the service logger at INFO level. Writes only
run-time/mediation-time audit messages
log4j.category.SERVICE_LOGGER.*getUsers*=DEBUG, SERVICE_APPENDER
log4j.additivity.SERVICE_LOGGER=false
log4j.appender.SERVICE_APPENDER=org.apache.log4j.RollingFileAppender
#log4j.appender.SERVICE_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-service${instance.log}.log
log4j.appender.SERVICE_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-
*get-users*${instance.log}.log
log4j.appender.SERVICE_APPENDER.MaxFileSize=1000KB
log4j.appender.SERVICE_APPENDER.MaxBackupIndex=10
log4j.appender.SERVICE_APPENDER.layout=org.apache.log4j.PatternLayout
log4j.appender.SERVICE_APPENDER.layout.ConversionPattern=%d{ISO8601}
[%X{ip}-%X{host}] [%t] %5p %c{1} %m%n

On Tue, Jul 26, 2016 at 10:17 AM, Elilmatha Sivanesan 
wrote:

> Hi Udara,
>
> Can you try by adding the following entries into your log4j.properties
> file ,In this way, you might need to add separate blocks of configuration
> for all configured proxies.(assumes a proxy service named TestProxy):
>
> log4j.category.SERVICE_LOGGER.TestProxy= 
> DEBUG,PROXY_APPENDERlog4j.additivity.PROXY_APPENDER=falselog4j.appender.PROXY_APPENDER=org.apache.log4j.DailyRollingFileAppenderlog4j.appender.PROXY_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-test-proxy${instance.log}.loglog4j.appender.PROXY_APPENDER.Append=truelog4j.appender.PROXY_APPENDER.layout=org.apache.log4j.PatternLayoutlog4j.appender.PROXY_APPENDER.layout.ConversionPattern=%d{HH:mm:ss,SSS}
>  [%X{ip}-%X{host}] [%t] %5p %c{1} %m%
>
>
> Thanks
>
> On Tue, Jul 26, 2016 at 9:33 AM, Udara Liyanage  wrote:
>
>> Hi,
>>
>> I want to set some logs to debug in log mediator. When I set log category
>> to DEBUG and enable DEBUG in SERVICE_LOGGER, I don't see any logs in any of
>> the file inside logs folder. How do we enable debug logs for APIs and
>> proxies?
>>
>>  
>> 
>>  
>>  
>> 
>>  
>>
>> log4j.category.SERVICE_LOGGER=*DEBUG*, SERVICE_APPENDER
>> log4j.additivity.SERVICE_LOGGER=false
>> log4j.appender.SERVICE_APPENDER=org.apache.log4j.RollingFileAppender
>>
>> log4j.appender.SERVICE_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-service${instance.log}.log
>>
>> log4j.appender.SERVICE_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-get-users${instance.log}.log
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> Blog: http://udaraliyanage.wordpress.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *S.Elilmatha*
> Software Engineer,
>
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> Mobile 0779842221.
>
>


-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

Blog: http://udaraliyanage.wordpress.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC2

[Anuruddha Liyanarachchi]

Hi All,

Verified the following:

1. Verified the License with the RAT plugin
2. DSS 3.5.0 - Tested default and distributed setup in mesos platform, with
clustering.
3. ESB 4.9.0 - Worker manager setup in mesos platform with clustering.
4. AS 5.3.0 - Tested on default platform.

*[x] Stable - Go ahead and release*

On Mon, Jul 25, 2016 at 6:39 PM, Pubudu Gunatilaka  wrote:

> Hi Devs,
>
> This is the second release candidate (RC2) of WSO2 Puppet Modules 2.1.0
> release. Please download, verify, and vote. Voting will be open for 72
> hours or as needed.
>
> This release fixes following issues:
> https://wso2.org/jira/browse/PMODULES-16?filter=13155
>
> ​Source and binary distribution files:
> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2
>
> The tag to be voted upon:
> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2
>
> Release verification guide:
> https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment
>
> Refer modules README files for more details.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> Thank you,
> WSO2 PaaS Team.
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: GSOC2016: [ML][CEP] Predictive analytic with online data for WSO2 Machine Learner

[Nirmal Fernando]

Hi Mahesh,

What's the status of the project?

On Thu, Jul 14, 2016 at 10:28 AM, Mahesh Dananjaya <
dananjayamah...@gmail.com> wrote:

> Hi Maheshakya,
> I am building and running samoa to see its functionality. In samoa still
> we have limited supports in algorithms. Samoa supports only classification
> and clustering with streams. It also use kind of StreamProcessor, like the
> one we use in StreamProcessor extension.  I was getting started with Samoa
> referring to this page [1]. Then i ran couple of examples to identified the
> flow. Samoa use hadoop framework instead spark for distribution. But i am
> using it in a local mode. When i see the Samoa core there is only limited
> algorithms. IMO if we are going to use Samoa we  have to limit the
> functionality and algorithms [2]. When i go to developer corner in [3], it
> seems to be something like CEP extension that we are using currenlty. SO in
> Samoa though the algorihtms are limited, they have implemented streaming
> support for them. Therefore if we integrate it into CEP we have to look for
> how to handle streams and algorithms in Samoa side. Is it good for your
> side to have both hadoop and spark running background.thank you.
> regards,
> Mahesh.
>
> [1] https://samoa.incubator.apache.org/documentation/Home.html
> [2]
> https://samoa.incubator.apache.org/documentation/api/current/index.html
>
>
> On Wed, Jun 22, 2016 at 11:51 AM, Mahesh Dananjaya <
> dananjayamah...@gmail.com> wrote:
>
>> Hi Maheshakya,
>> can i give external data sources like data from database , data from HDFS
>> to generate events in the cep event simulator rather than giving a file. i
>> saw "Switch to upload file for simulation" in the input Data By Data Source
>> in  the event simulator. How can i feed data real time from other sources
>> or directly as data generating from remote server as JSON or etc... What
>> format the database should be.This is just for my knowledge.thank you.
>> regards,
>> Mahesh.
>>
>> On Wed, Jun 22, 2016 at 10:59 AM, Mahesh Dananjaya <
>> dananjayamah...@gmail.com> wrote:
>>
>>> Hi Nirmal,
>>> *This is what i have done so far in the GSOC2016,*
>>>
>>>- prior research before SGD (Stochastic Gradient Descent)
>>>optimization techniques and mini-batch processing
>>>- Getting familiar and writing extensions to siddhi
>>>- Wrote a Stream Processor extensions for streaming application and
>>>machine learning algorithms (Linear Regression,KMeans & Logistic 
>>> Regression)
>>>- Developed a Streaming Linear Regression class for periodically
>>>retrain models as mini batch processing with SGD
>>>- Extend the functionality for Moving Window Mini Batch Processing
>>>with SGD providing windowShift which control data horizon and data
>>>obsolescences
>>>- Performance evaluation of the implementation
>>>- Adding Streaming Linear Regression class and Stream Processor
>>>extension to carbon-ml
>>>
>>>
>>> *As a next step,*
>>>
>>>- Adding Persisting temporal models for applications such as
>>>prediction
>>>- complete Streaming Kmeans clustering and Logistic Regression
>>>classes
>>>- Improve batching and streaming mechanisms
>>>- improve visualization(optional)
>>>- and writing examples and documentation
>>>
>>> regards,
>>>
>>> Mahesh.
>>>
>>> On Wed, Jun 22, 2016 at 10:28 AM, Maheshakya Wijewardena <
>>> mahesha...@wso2.com> wrote:
>>>
 Sorry, you need to put the returned values of the function into the
 output stream

 from LinRegInput#ml:streamlinreg(1, 2, 4, 100, 0.0001, 1.0, 0.95,
 salary, rbi, walks, strikeouts, errors)



 *select mseinsert into LinregOutput;*
 or

 from LinRegInput#ml:streamlinreg(1, 2, 4, 100, 0.0001, 1.0, 0.95,
 salary, rbi, walks, strikeouts, errors)
 select *
 insert into LinregOutput;

 where LinregOutput stream definition contains all attributes: mse,
 intercept, beta1, 

 On Wed, Jun 22, 2016 at 10:24 AM, Maheshakya Wijewardena <
 mahesha...@wso2.com> wrote:

> Hi Mahesh,
>
> In your output stream, you need to list all the attributes that are
> returned from the streamlinreg function: mse, intercept, beta1, 
> Can you try that?
>
> On Wed, Jun 22, 2016 at 10:06 AM, Mahesh Dananjaya <
> dananjayamah...@gmail.com> wrote:
>
>> Hi Maheshakya,
>> This is the full query i used.
>>
>> @Import('LinRegInput:1.0.0')
>>
>> define stream LinRegInput (salary double, rbi double, walks double,
>> strikeouts double, errors double);
>>
>> @Export('LinRegOutput:1.0.0')
>>
>> define stream LinregOutput (mse double);
>>
>> from LinRegInput#ml:streamlinreg(1, 2, 4, 100, 0.0001, 1.0, 0.95,
>> salary, rbi, walks, strikeouts, errors)
>>
>> select *
>> insert into mse;
>>
>> but i am sending [mse,intercept,beta1betap] as a outputData
>> Object[]. SO h

Re: [Dev] [ESB] Enable debug logs for proxies and apis

[Elilmatha Sivanesan]

Hi Udara,

Can you try by adding the following entries into your log4j.properties file
,In this way, you might need to add separate blocks of configuration for
all configured proxies.(assumes a proxy service named TestProxy):

log4j.category.SERVICE_LOGGER.TestProxy=
DEBUG,PROXY_APPENDERlog4j.additivity.PROXY_APPENDER=falselog4j.appender.PROXY_APPENDER=org.apache.log4j.DailyRollingFileAppenderlog4j.appender.PROXY_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-test-proxy${instance.log}.loglog4j.appender.PROXY_APPENDER.Append=truelog4j.appender.PROXY_APPENDER.layout=org.apache.log4j.PatternLayoutlog4j.appender.PROXY_APPENDER.layout.ConversionPattern=%d{HH:mm:ss,SSS}
[%X{ip}-%X{host}] [%t] %5p %c{1} %m%


Thanks

On Tue, Jul 26, 2016 at 9:33 AM, Udara Liyanage  wrote:

> Hi,
>
> I want to set some logs to debug in log mediator. When I set log category
> to DEBUG and enable DEBUG in SERVICE_LOGGER, I don't see any logs in any of
> the file inside logs folder. How do we enable debug logs for APIs and
> proxies?
>
>  
> 
>  
>  
> 
>  
>
> log4j.category.SERVICE_LOGGER=*DEBUG*, SERVICE_APPENDER
> log4j.additivity.SERVICE_LOGGER=false
> log4j.appender.SERVICE_APPENDER=org.apache.log4j.RollingFileAppender
>
> log4j.appender.SERVICE_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-service${instance.log}.log
>
> log4j.appender.SERVICE_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-get-users${instance.log}.log
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> Blog: http://udaraliyanage.wordpress.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*S.Elilmatha*
Software Engineer,

WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

Mobile 0779842221.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PC] Setting permission for all the roles when state transitions take place in life cycles

[Yasima Dewmini]

Hi,

Thank you Madawa.

Regards,
Yasima.

On Tue, Jul 26, 2016 at 9:46 AM, Madawa Soysa  wrote:

> Hi,
>
> AFAIK in order to execute an action based on a lifecycle state change, you
> need to use a lifecycle executor. You can find the information about
> standard executors in [1]
> .
> Also, you can implement a custom executor as well. The following article
> [2]
> 
> and blog post [3]
> 
> gives a good explanation about adding custom lifecycle executors.
>
>
> [1] -
> https://docs.wso2.com/display/Governance520/Supported+Standard+Executors
> [2] -
> http://wso2.com/library/articles/2015/07/wso2-governance-registry-governance-framework-extension-points/
> [3] -
> http://sencs.blogspot.com/2016/05/how-to-write-simple-g-reg-lifecycle.html
>
> On Fri, Jul 22, 2016 at 4:41 PM, Yasima Dewmini  wrote:
>
>> Hi,
>>
>> I need to set permission for all the roles including user defined roles,
>> when state transitions take place in life cycles. How can I achieve this?
>> And also admin can edit a process when that process is in retired state.
>> I need to avoid that scenario also.
>>
>> Any thought regarding this is appreciated.
>>
>> The life cycle is as follows.
>>
>> > class="org.wso2.jaggery.scxml.aspects.JaggeryTravellingPermissionLifeCycle">
>> 
>> 
>> http://www.w3.org/2005/07/scxml";
>>version="1.0"
>>initialstate="Development">
>> 
>> 
>> 
>> > class="org.wso2.jaggery.scxml.generic.GenericExecutor">
>> >
>> value="http://www.wso2.org/projects/registry/actions/get"/>
>> >
>> value="http://www.wso2.org/projects/registry/actions/add"/>
>> >
>> value="http://www.wso2.org/projects/registry/actions/delete"/>
>> > value="authorize"/>
>>
>> >
>> value="Internal/private_{asset_author}:+get,-add,+delete,-authorize"/>
>> >
>> value="Internal/everyone:+get,-add,-delete,-authorize"/>
>> >
>> value="Internal/publisher:+get,+add,+delete,+authorize"/>
>> >
>> value="system/wso2.anonymous.role:+get,-add,-delete,-authorize" />
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> > class="org.wso2.jaggery.scxml.generic.GenericExecutor">
>> >
>> value="http://www.wso2.org/projects/registry/actions/get"/>
>> >
>> value="http://www.wso2.org/projects/registry/actions/add"/>
>> >
>> value="http://www.wso2.org/projects/registry/actions/delete"/>
>> > value="authorize"/>
>>
>> >
>> value="Internal/private_{asset_author}:+get,-add,-delete,-authorize"/>
>> >
>> value="Internal/everyone:+get,-add,-delete,-authorize"/>
>> >
>> value="Internal/publisher:+get,+add,+delete,+authorize"/>
>> >
>> value="system/wso2.anonymous.role:+get,-add,-delete,-authorize" />
>> 
>> 
>> 
>> > roles="Internal/publisher,admin"/>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> > class="org.wso2.jaggery.scxml.generic.GenericExecutor">
>> >
>> value="http://www.wso2.org/projects/registry/actions/get"/>
>> >
>> value="http://www.wso2.org/projects/registry/actions/add"/>
>>  

Re: [Dev] [PC] Setting permission for all the roles when state transitions take place in life cycles

[Madawa Soysa]

Hi,

AFAIK in order to execute an action based on a lifecycle state change, you
need to use a lifecycle executor. You can find the information about
standard executors in [1]
.
Also, you can implement a custom executor as well. The following article [2]

and blog post [3]

gives a good explanation about adding custom lifecycle executors.


[1] -
https://docs.wso2.com/display/Governance520/Supported+Standard+Executors
[2] -
http://wso2.com/library/articles/2015/07/wso2-governance-registry-governance-framework-extension-points/
[3] -
http://sencs.blogspot.com/2016/05/how-to-write-simple-g-reg-lifecycle.html

On Fri, Jul 22, 2016 at 4:41 PM, Yasima Dewmini  wrote:

> Hi,
>
> I need to set permission for all the roles including user defined roles,
> when state transitions take place in life cycles. How can I achieve this?
> And also admin can edit a process when that process is in retired state. I
> need to avoid that scenario also.
>
> Any thought regarding this is appreciated.
>
> The life cycle is as follows.
>
>  class="org.wso2.jaggery.scxml.aspects.JaggeryTravellingPermissionLifeCycle">
> 
> 
> http://www.w3.org/2005/07/scxml";
>version="1.0"
>initialstate="Development">
> 
> 
> 
>  class="org.wso2.jaggery.scxml.generic.GenericExecutor">
> 
> value="http://www.wso2.org/projects/registry/actions/get"/>
> 
> value="http://www.wso2.org/projects/registry/actions/add"/>
> 
> value="http://www.wso2.org/projects/registry/actions/delete"/>
>  value="authorize"/>
>
> 
> value="Internal/private_{asset_author}:+get,-add,+delete,-authorize"/>
> 
> value="Internal/everyone:+get,-add,-delete,-authorize"/>
> 
> value="Internal/publisher:+get,+add,+delete,+authorize"/>
> 
> value="system/wso2.anonymous.role:+get,-add,-delete,-authorize" />
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.wso2.jaggery.scxml.generic.GenericExecutor">
> 
> value="http://www.wso2.org/projects/registry/actions/get"/>
> 
> value="http://www.wso2.org/projects/registry/actions/add"/>
> 
> value="http://www.wso2.org/projects/registry/actions/delete"/>
>  value="authorize"/>
>
> 
> value="Internal/private_{asset_author}:+get,-add,-delete,-authorize"/>
> 
> value="Internal/everyone:+get,-add,-delete,-authorize"/>
> 
> value="Internal/publisher:+get,+add,+delete,+authorize"/>
> 
> value="system/wso2.anonymous.role:+get,-add,-delete,-authorize" />
> 
> 
> 
>  roles="Internal/publisher,admin"/>
> 
> 
> 
> 
> 
> 
> 
>  class="org.wso2.jaggery.scxml.generic.GenericExecutor">
> 
> value="http://www.wso2.org/projects/registry/actions/get"/>
> 
> value="http://www.wso2.org/projects/registry/actions/add"/>
> 
> value="http://www.wso2.org/projects/registry/actions/delete"/>
>  value="authorize"/>
>
> 

[Dev] [ESB] Enable debug logs for proxies and apis

[Udara Liyanage]

Hi,

I want to set some logs to debug in log mediator. When I set log category
to DEBUG and enable DEBUG in SERVICE_LOGGER, I don't see any logs in any of
the file inside logs folder. How do we enable debug logs for APIs and
proxies?

 

 
 

 

log4j.category.SERVICE_LOGGER=*DEBUG*, SERVICE_APPENDER
log4j.additivity.SERVICE_LOGGER=false
log4j.appender.SERVICE_APPENDER=org.apache.log4j.RollingFileAppender
log4j.appender.SERVICE_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-service${instance.log}.log
log4j.appender.SERVICE_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-get-users${instance.log}.log

-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

Blog: http://udaraliyanage.wordpress.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Orbit] Please merge PR for spark-mllib_2.10 version 1.4.1.wso2v3

[Supun Sethunga]

Hi Manoj,

Did the changes as per the comment. Can you please review it?

Thanks,
Supun

On Mon, Jul 25, 2016 at 6:25 PM, Manoj Kumara  wrote:

> Hi Supun,
>
> Added a comment. Please resolve that.
>
> Regards,
> manoj
>
> *Manoj Kumara*
> WSO2 Inc. *| **lean. enterprise. middleware.*
> *Mobile:* +94 713 448188
>
> On Mon, Jul 25, 2016 at 5:23 PM, Supun Sethunga  wrote:
>
>> Hi Carbon Team,
>>
>> Can you please review and merge PR[1]? This is a fix for [2].
>>
>> [1] https://github.com/wso2/orbit/pull/222
>> [2] https://wso2.org/jira/browse/CEP-1471
>>
>> Regards,
>> Supun
>>
>> --
>> *Supun Sethunga*
>> Senior Software Engineer
>> WSO2, Inc.
>> http://wso2.com/
>> lean | enterprise | middleware
>> Mobile : +94 716546324
>> Blog: http://supunsetunga.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
*Supun Sethunga*
Senior Software Engineer
WSO2, Inc.
http://wso2.com/
lean | enterprise | middleware
Mobile : +94 716546324
Blog: http://supunsetunga.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC2016-Contact Development Team Feature

[Nathiesha Maddage]

Hi Kavith,

I accepted the invitation.

Thanks and regards
Nathiesha

On Mon, Jul 25, 2016 at 8:42 PM, Kavith Lokuhewage  wrote:

> Hi Nathiesha,
>
> I have sent the invitation for the meeting at 2pm-3pm on 28/07/2016 [1].
>
> Thanks,
>
> [1] https://goo.gl/PLEWQd
>
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Mon, Jul 25, 2016 at 8:13 PM, Nathiesha Maddage <
> nathieshamadd...@gmail.com> wrote:
>
>> Hi Kavith,
>>
>> How about Thursday evening, for the meeting? I am free after 1 pm.
>>
>> Thank you for the examples. I was going to refactor the code by
>> introducing the interfaces as you suggested during the mid evaluation. But
>> I was not sure how to do that. I will try to change the code as given in
>> the examples before the next meeting.
>>
>> I think it is good to start converting the project to a maven project as
>> only a few weeks remaining to finalize the project. We can discuss about
>> that during the meeting.
>>
>> Thanks and regards
>>
>> Nathiesha
>>
>> On Mon, Jul 25, 2016 at 3:10 PM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi Nathiesha,
>>>
>>> I noticed that there are some more pending tasks to restructure the code
>>> base as per the discussion we had during last code review. Just putting
>>> them down here again, so that you are able to go through again and complete
>>> any missing parts.
>>>
>>> *Introduce interfaces for the each sub component  to decouple main
>>> controller logic from implementation specific things*
>>>
>>> For example, right now, the controller class (ErrorReporter) is hardly
>>> coupled with EmailSender and RemoteJiraConnector. We can think latter two
>>> as error report publishers and introduce an interface called ErrorPublisher
>>> as below.
>>>
>>> public interface ErrorPublisher{
>>> void publish(ReportGenerator reportGen) throws IOException;
>>> }
>>>
>>> And then EmailSender and RemoreJiraConnector classes can be refactored
>>> like below.
>>>
>>> public class EmailPublisher implements ErrorPublisher{
>>>
>>>  void init () throws IOException{
>>>//init : read preferences for SMTP connection params
>>>  }
>>>
>>> // implement publish method
>>> void publish(ReportGenerator reportGen) throws IOException{
>>> init();
>>>//send mail
>>> }
>>> }
>>>
>>> public class JiraPublisher implements ErrorPublisher{
>>>
>>>  void init () throws IOException{
>>>   //init : read preferences for JIRA resp API connection params
>>>  }
>>>
>>>// implement publish method
>>>void publish(ReportGenerator reportGen) throws IOException{
>>>init();
>>>   //post to JIRA api and create issue
>>>}
>>> }
>>>
>>> Finally refactor ErrorReporter class to use only ErrorPublisher
>>> interface. Further more, introduce methods to bind/unbind error publishers.
>>>
>>> public class ErrorReporter {
>>> Map registeredPublishers;
>>>
>>> public void addPublisher (String id, ErrorPublisher publisher){
>>>registeredPublishers.put(id,publisher);
>>>}
>>>
>>>   public void reportError(){
>>>  //iterate over all publishers
>>>  // and call  publish() method
>>>   }
>>> }
>>>
>>> (We can further ErrorReporter class by using OSGI services to let other
>>> devstudio plugins to contribute publishers as needed - we can do that later
>>> as time permits)
>>>
>>> For another example, currently you have used a class
>>> called ReportGenerator to generate the report in plain text and directly
>>> used that generator inside main controller. Instead, you can introduce an
>>> interface called ReportGenerator and create a class called
>>> TextReportGenerator and move the code there - and decouple main controller
>>> and let other people add report generators later (say an HTML report
>>> generator) as needed. It can be done in same manner as above example I have
>>> provided .
>>>
>>> Once you do above restructuring, we can further improve the code to use
>>> OSGI services to decouple these components even further.
>>>
>>> Finally, I think it is time for us to convert the project to a maven
>>> project and use tycho maven plugins for building it. I can assist you with
>>> this task - let's discuss this furthermore during the call. The main
>>> requirement here is to make this project directly mergable to developer
>>> studio repository. Since we are now reaching to the final weeks of GSOC
>>> coding period, I think we should concentrate a little more on this task.
>>>
>>> Please a suggest a time for the meeting so we are able to discuss
>>> these in-detail.
>>>
>>> Thanks,
>>>
>>> *Kavith Lokuhewage*
>>> Senior Software Engineer
>>> WSO2 Inc. - http://wso2.com
>>> lean . enterprise . middleware
>>> Mobile - +94779145123
>>> Linkedin 

Re: [Dev] [DEV][carbon-metrics] Issue with timer stats

[Indika Sampath]

On Tue, Jul 26, 2016 at 12:39 AM, Isuru Perera  wrote:

> Hi Indika,
>
> Yes, this is a known issue when using the exponentially-decaying reservoir
> and when we see the problem clearly when we display the data in a time
> series chart.
>
> In order to provide a solution, we need to implement a different reservoir
> for metrics and we can use a project like HdrHistogram [1]. I'm planning to
> include a new reservoir implementation in Carbon Metrics 2.1.0, which is
> based on Carbon Kernel 5.1.0.
>
> Do you want this problem to be fixed in Carbon 4.x based release?
>
Yes. Because we are going to release analytics-mb along with message broker
3.2.0 which is based on carbon 4.x.

>
> [1] https://github.com/HdrHistogram/HdrHistogram
>
> On Mon, Jul 25, 2016 at 7:13 PM, Indika Sampath  wrote:
>
>> Hi Isuru,
>>
>> We were encounter there is an issue with timer stats in carbon-metrics
>> due to its default reservoir which is exponentially decaying reservoir. As
>> per the doc, it says A histogram with an exponentially decaying reservoir
>> produces quantiles which are representative of (roughly) the last five
>> minutes of data. Same issue mentioned in links [1][2] as well and they have
>> provided some workaround to mitigate the issue. It would be great if you
>> could provide a fix for this?
>>
>> [1] http://taint.org/2014/01/16/145944a.html
>> [2] https://blog.filippo.io/understanding-metrics
>>
>> Cheers!
>>
>> --
>> Indika Sampath
>> Senior Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Phone: +94 716 424 744
>> Blog: http://indikasampath.blogspot.com/
>>
>>
>
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][carbon-metrics] Issue with timer stats

[Isuru Perera]

Hi Indika,

Yes, this is a known issue when using the exponentially-decaying reservoir
and when we see the problem clearly when we display the data in a time
series chart.

In order to provide a solution, we need to implement a different reservoir
for metrics and we can use a project like HdrHistogram [1]. I'm planning to
include a new reservoir implementation in Carbon Metrics 2.1.0, which is
based on Carbon Kernel 5.1.0.

Do you want this problem to be fixed in Carbon 4.x based release?

[1] https://github.com/HdrHistogram/HdrHistogram

On Mon, Jul 25, 2016 at 7:13 PM, Indika Sampath  wrote:

> Hi Isuru,
>
> We were encounter there is an issue with timer stats in carbon-metrics due
> to its default reservoir which is exponentially decaying reservoir. As per
> the doc, it says A histogram with an exponentially decaying reservoir
> produces quantiles which are representative of (roughly) the last five
> minutes of data. Same issue mentioned in links [1][2] as well and they have
> provided some workaround to mitigate the issue. It would be great if you
> could provide a fix for this?
>
> [1] http://taint.org/2014/01/16/145944a.html
> [2] https://blog.filippo.io/understanding-metrics
>
> Cheers!
>
> --
> Indika Sampath
> Senior Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 716 424 744
> Blog: http://indikasampath.blogspot.com/
>
>


-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] XML String to Balana Node conversion

[Farasath Ahamed]

HI Manujith,

You can get the required Node/Element argument to be passed to
Balana Attributes Object using a code segment like below,

try {
DocumentBuilderFactory documentBuilderFactory =
IdentityUtil.getSecuredDocumentBuilderFactory();

DocumentBuilder docBuilder = documentBuilderFactory.newDocumentBuilder();
ByteArrayInputStream is = new
ByteArrayInputStream(xacmlRequestString.getBytes());

// parse and build the document.

Document document = docBuilder.parse(is);
Element element = document.getDocumentElement();

// use the element in the Balana constructor


} catch (ParserConfigurationException | UnmarshallingException |
IOException | SAXException e) {
throw new SAMLSSOException("Error in unmarshalling SAML Request
from the encoded String", e);

}



Thanks,


Farasath Ahamed
Software Engineer, WSO2 Inc.; http://wso2.com
Mobile: +94777603866
Blog: blog.farazath.com
Twitter: @farazath619 




On Mon, Jul 25, 2016 at 10:40 PM, Manujith Pallewatte  wrote:

> Hi all,
>
> As a part of the REST API for IS AZaaS, i'm in the process of parsing JSON
> XACML 3.0 requests into the Balana RequestCtx Objects [1], thus allowing me
> to directly evaluate them using the engine. In that process, according to
> the JSON profile of XACML 3.0 [2], it is stated that the content section of
>  request should be converted sent as either a Base64 string or escaped XML
> String.
>
> By that the XML String is obtained, yet the Balana Attributes object [3]
> only accepts type 'Node' as content. Thus I'm in search for a way of
> parsing a XML String to Balana Node object, hopefully using an existing
> method in the engine.
>
> Please let me know if there's any or any pointers I can work on.
>
> Thank You
> Best Regards,
> Manujith
>
>
> [1]
> https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/ctx/xacml3/RequestCtx.java
> [2]
> http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html
> [3]
> https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/xacml3/Attributes.java
>
> --
>
>
>
> Manujith Pallewatte
> [image: https://]about.me/manzzup
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Private constructor of Balana MultiRequests

[Manujith Pallewatte]

Hi all,

As a part of the ongoing REST API for IS AZaaS, I'm in need of creating
MultiRequests objects [1] from a given JSON String. But when checked with
source, MultiRequests class has only 1 constructor which is private. Please
explain if it needs to be private and if so, any mechanism through which I
can instantiate a MultiRequests object without using the getInstance method
(Since it requires an XML node which I donot posses)

Thank You
Best Regards,
Manujith

-- 



Manujith Pallewatte
[image: https://]about.me/manzzup

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS] XML String to Balana Node conversion

[Manujith Pallewatte]

Hi all,

As a part of the REST API for IS AZaaS, i'm in the process of parsing JSON
XACML 3.0 requests into the Balana RequestCtx Objects [1], thus allowing me
to directly evaluate them using the engine. In that process, according to
the JSON profile of XACML 3.0 [2], it is stated that the content section of
 request should be converted sent as either a Base64 string or escaped XML
String.

By that the XML String is obtained, yet the Balana Attributes object [3]
only accepts type 'Node' as content. Thus I'm in search for a way of
parsing a XML String to Balana Node object, hopefully using an existing
method in the engine.

Please let me know if there's any or any pointers I can work on.

Thank You
Best Regards,
Manujith


[1]
https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/ctx/xacml3/RequestCtx.java
[2]
http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html
[3]
https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/xacml3/Attributes.java

-- 



Manujith Pallewatte
[image: https://]about.me/manzzup

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Thanuja Uruththirakodeeswaran]

[+1] Stable - Go ahead and release

Verified the following:
1. Distribution
2. License Headers
3. Built following products docker images with puppet provisioning for
Mesos platform and tested basic functionalities:


   - WSO2 ES 2.0.0 (Distributed setup)
   -  WSO2 ESB 4.9.0 (Distributed setup)
   -  WSO2 MB 3.1.0
   -  WSO2 IS 5.1.0
   -  WSO2 IS KM 5.1.0

Thanks.

On Fri, Jul 22, 2016 at 9:27 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi Devs,
>
> This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
> release.
>
> *This release fixes the following issues:*
>
> https://wso2.org/jira/issues/?filter=13159
>
> *Tag to be voted upon:*
>
> https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1
>
> *Source and distribution packages:*
>
> https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1
>
> Please download, test, and vote. The README file under the distribution
> contains guide and instructions on how to try it out locally.
>
> [+] Stable - Go ahead and release
>
> [-] Broken - Do not release (explain why)
>
>
>
> This vote will be open for 72 hours or as needed.
>
> Regards,
> WSO2 PaaS team
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

mobile: +94 774363167


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Tharindu Dharmarathna]

Verified AM Docker files

*[x] Stable - Go ahead and release*

On Mon, Jul 25, 2016 at 7:09 PM, Isuru Haththotuwa  wrote:

> Verified the following:
>
> 1. API Manager 1.10.0
>
>- built the images for default and distributed profiles (api-store
>api-publisher api-key-manager gateway-manager) with puppet provisioning
>mechanism form mesos platform
>
>  2. ESB 4.9.0
>
>- built the images for default profile with default provisioning system
>- ran a smoke test
>- uses stop.sh script to terminate and delete the container
>
> 3. CEP 4.0.0
>
>- built the images for default profile with default provisioning system
>- ran a smoke test
>- uses stop.sh script to terminate and delete the container
>
> 4. DAS 3.0.1
>
>- built the images for default profile with default provisioning system
>- ran a smoke test
>- uses stop.sh script to terminate and delete the container
>
> 5. Verified the License with the RAT plugin
>
> *[x] Stable - Go ahead and release*
>
> On Fri, Jul 22, 2016 at 9:27 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
>> release.
>>
>> *This release fixes the following issues:*
>>
>> https://wso2.org/jira/issues/?filter=13159
>>
>> *Tag to be voted upon:*
>>
>> https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1
>>
>> *Source and distribution packages:*
>>
>> https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1
>>
>> Please download, test, and vote. The README file under the distribution
>> contains guide and instructions on how to try it out locally.
>>
>> [+] Stable - Go ahead and release
>>
>> [-] Broken - Do not release (explain why)
>>
>>
>>
>> This vote will be open for 72 hours or as needed.
>>
>> Regards,
>> WSO2 PaaS team
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Tharindu Dharmarathna*Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94779109091*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC2016-Contact Development Team Feature

[Kavith Lokuhewage]

Hi Nathiesha,

I have sent the invitation for the meeting at 2pm-3pm on 28/07/2016 [1].

Thanks,

[1] https://goo.gl/PLEWQd


*Kavith Lokuhewage*
Senior Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +94779145123
Linkedin   Twitter


On Mon, Jul 25, 2016 at 8:13 PM, Nathiesha Maddage <
nathieshamadd...@gmail.com> wrote:

> Hi Kavith,
>
> How about Thursday evening, for the meeting? I am free after 1 pm.
>
> Thank you for the examples. I was going to refactor the code by
> introducing the interfaces as you suggested during the mid evaluation. But
> I was not sure how to do that. I will try to change the code as given in
> the examples before the next meeting.
>
> I think it is good to start converting the project to a maven project as
> only a few weeks remaining to finalize the project. We can discuss about
> that during the meeting.
>
> Thanks and regards
>
> Nathiesha
>
> On Mon, Jul 25, 2016 at 3:10 PM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> I noticed that there are some more pending tasks to restructure the code
>> base as per the discussion we had during last code review. Just putting
>> them down here again, so that you are able to go through again and complete
>> any missing parts.
>>
>> *Introduce interfaces for the each sub component  to decouple main
>> controller logic from implementation specific things*
>>
>> For example, right now, the controller class (ErrorReporter) is hardly
>> coupled with EmailSender and RemoteJiraConnector. We can think latter two
>> as error report publishers and introduce an interface called ErrorPublisher
>> as below.
>>
>> public interface ErrorPublisher{
>> void publish(ReportGenerator reportGen) throws IOException;
>> }
>>
>> And then EmailSender and RemoreJiraConnector classes can be refactored
>> like below.
>>
>> public class EmailPublisher implements ErrorPublisher{
>>
>>  void init () throws IOException{
>>//init : read preferences for SMTP connection params
>>  }
>>
>> // implement publish method
>> void publish(ReportGenerator reportGen) throws IOException{
>> init();
>>//send mail
>> }
>> }
>>
>> public class JiraPublisher implements ErrorPublisher{
>>
>>  void init () throws IOException{
>>   //init : read preferences for JIRA resp API connection params
>>  }
>>
>>// implement publish method
>>void publish(ReportGenerator reportGen) throws IOException{
>>init();
>>   //post to JIRA api and create issue
>>}
>> }
>>
>> Finally refactor ErrorReporter class to use only ErrorPublisher
>> interface. Further more, introduce methods to bind/unbind error publishers.
>>
>> public class ErrorReporter {
>> Map registeredPublishers;
>>
>> public void addPublisher (String id, ErrorPublisher publisher){
>>registeredPublishers.put(id,publisher);
>>}
>>
>>   public void reportError(){
>>  //iterate over all publishers
>>  // and call  publish() method
>>   }
>> }
>>
>> (We can further ErrorReporter class by using OSGI services to let other
>> devstudio plugins to contribute publishers as needed - we can do that later
>> as time permits)
>>
>> For another example, currently you have used a class
>> called ReportGenerator to generate the report in plain text and directly
>> used that generator inside main controller. Instead, you can introduce an
>> interface called ReportGenerator and create a class called
>> TextReportGenerator and move the code there - and decouple main controller
>> and let other people add report generators later (say an HTML report
>> generator) as needed. It can be done in same manner as above example I have
>> provided .
>>
>> Once you do above restructuring, we can further improve the code to use
>> OSGI services to decouple these components even further.
>>
>> Finally, I think it is time for us to convert the project to a maven
>> project and use tycho maven plugins for building it. I can assist you with
>> this task - let's discuss this furthermore during the call. The main
>> requirement here is to make this project directly mergable to developer
>> studio repository. Since we are now reaching to the final weeks of GSOC
>> coding period, I think we should concentrate a little more on this task.
>>
>> Please a suggest a time for the meeting so we are able to discuss
>> these in-detail.
>>
>> Thanks,
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +94779145123
>> Linkedin 
>> Twitter 
>>
>> On Mon, Jul 25, 2016 at 2:11 PM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi Nathiesha,
>>>
>>> There were some changes done to preference API since Eclipse Mars. I
>>> suspect that the root cause for the issue should be it. I

Re: [Dev] GSoC2016-Contact Development Team Feature

[Nathiesha Maddage]

Hi Kavith,

How about Thursday evening, for the meeting? I am free after 1 pm.

Thank you for the examples. I was going to refactor the code by introducing
the interfaces as you suggested during the mid evaluation. But I was not
sure how to do that. I will try to change the code as given in the examples
before the next meeting.

I think it is good to start converting the project to a maven project as
only a few weeks remaining to finalize the project. We can discuss about
that during the meeting.

Thanks and regards

Nathiesha

On Mon, Jul 25, 2016 at 3:10 PM, Kavith Lokuhewage  wrote:

> Hi Nathiesha,
>
> I noticed that there are some more pending tasks to restructure the code
> base as per the discussion we had during last code review. Just putting
> them down here again, so that you are able to go through again and complete
> any missing parts.
>
> *Introduce interfaces for the each sub component  to decouple main
> controller logic from implementation specific things*
>
> For example, right now, the controller class (ErrorReporter) is hardly
> coupled with EmailSender and RemoteJiraConnector. We can think latter two
> as error report publishers and introduce an interface called ErrorPublisher
> as below.
>
> public interface ErrorPublisher{
> void publish(ReportGenerator reportGen) throws IOException;
> }
>
> And then EmailSender and RemoreJiraConnector classes can be refactored
> like below.
>
> public class EmailPublisher implements ErrorPublisher{
>
>  void init () throws IOException{
>//init : read preferences for SMTP connection params
>  }
>
> // implement publish method
> void publish(ReportGenerator reportGen) throws IOException{
> init();
>//send mail
> }
> }
>
> public class JiraPublisher implements ErrorPublisher{
>
>  void init () throws IOException{
>   //init : read preferences for JIRA resp API connection params
>  }
>
>// implement publish method
>void publish(ReportGenerator reportGen) throws IOException{
>init();
>   //post to JIRA api and create issue
>}
> }
>
> Finally refactor ErrorReporter class to use only ErrorPublisher interface.
> Further more, introduce methods to bind/unbind error publishers.
>
> public class ErrorReporter {
> Map registeredPublishers;
>
> public void addPublisher (String id, ErrorPublisher publisher){
>registeredPublishers.put(id,publisher);
>}
>
>   public void reportError(){
>  //iterate over all publishers
>  // and call  publish() method
>   }
> }
>
> (We can further ErrorReporter class by using OSGI services to let other
> devstudio plugins to contribute publishers as needed - we can do that later
> as time permits)
>
> For another example, currently you have used a class
> called ReportGenerator to generate the report in plain text and directly
> used that generator inside main controller. Instead, you can introduce an
> interface called ReportGenerator and create a class called
> TextReportGenerator and move the code there - and decouple main controller
> and let other people add report generators later (say an HTML report
> generator) as needed. It can be done in same manner as above example I have
> provided .
>
> Once you do above restructuring, we can further improve the code to use
> OSGI services to decouple these components even further.
>
> Finally, I think it is time for us to convert the project to a maven
> project and use tycho maven plugins for building it. I can assist you with
> this task - let's discuss this furthermore during the call. The main
> requirement here is to make this project directly mergable to developer
> studio repository. Since we are now reaching to the final weeks of GSOC
> coding period, I think we should concentrate a little more on this task.
>
> Please a suggest a time for the meeting so we are able to discuss
> these in-detail.
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Mon, Jul 25, 2016 at 2:11 PM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> There were some changes done to preference API since Eclipse Mars. I
>> suspect that the root cause for the issue should be it. I will go through
>> the changes we did in Developer Studio to fix issues with new pref API and
>> confirm you whether it is the root cause or not.
>>
>> Meanwhile, please suggest a time for another meeting this week - probably
>> on Thursday or Friday. We will go through the complete implementation to
>> verify that everything is in order.
>> I went through the code and have some comments too. I will put them in
>> github it self.
>>
>> Thanks,
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +94779145123
>> 

[Dev] [DEV][carbon-metrics] Issue with timer stats

[Indika Sampath]

Hi Isuru,

We were encounter there is an issue with timer stats in carbon-metrics due
to its default reservoir which is exponentially decaying reservoir. As per
the doc, it says A histogram with an exponentially decaying reservoir
produces quantiles which are representative of (roughly) the last five
minutes of data. Same issue mentioned in links [1][2] as well and they have
provided some workaround to mitigate the issue. It would be great if you
could provide a fix for this?

[1] http://taint.org/2014/01/16/145944a.html
[2] https://blog.filippo.io/understanding-metrics

Cheers!

-- 
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [C5] [CAAS] On Authentication: Invoking loginContext.login() returns LoginException of CNF for UsernamePasswordLoginModule

[Rasika Perera]

Hi All,

I am trying to invoke basic authentication with CAAS. I have installed
"org.wso2.carbon.security.caas.feature" and imported following packages;

org.wso2.carbon.security.caas.api.*,
org.wso2.carbon.kernel.context,
org.wso2.carbon.messaging

Further I have added config location into the startup script;

-Djava.security.auth.login.config="$CARBON_HOME/conf/security/carbon-jaas.config"\

My code snippet is as below (based on JAAS sample[1]);

PrivilegedCarbonContext.destroyCurrentContext();
CarbonMessage carbonMessage = new DefaultCarbonMessage();
carbonMessage.setHeader("Authorization", "Basic " + Base64.getEncoder()
.encodeToString("admin:admin".getBytes())
);

ProxyCallbackHandler callbackHandler = new ProxyCallbackHandler(carbonMessage);
LoginContext loginContext = new LoginContext("CarbonSecurityConfig",
callbackHandler);
loginContext.login();

​I am getting following error at the line "loginContext.login()";

Caused by: javax.security.auth.login.LoginException: unable to find
LoginModule class:
org.wso2.carbon.security.caas.api.module.UsernamePasswordLoginModule
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:794)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:587)
at
org.wso2.carbon.uuf.sample.simpleauth.bundle.SimpleAuthHandler.authenticate(SimpleAuthHandler.java:45)

Further I have found this occurs when LoginContext is trying load the class
"UsernamePasswordLoginModule" using Bootstrap class loader.

Any thoughts on how to fix this issue?

[1]
https://github.com/wso2/carbon-security/blob/master/tests/osgi-tests/src/test/java/org/wso2/carbon/security/caas/test/osgi/JAASTests.java
-- 
With Regards,

*Rasika Perera*
Software Engineer
LinkedIn: http://lk.linkedin.com/in/rasika90

[image: wso2-signature-general.png] 

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Isuru Haththotuwa]

Verified the following:

1. API Manager 1.10.0

   - built the images for default and distributed profiles (api-store
   api-publisher api-key-manager gateway-manager) with puppet provisioning
   mechanism form mesos platform

 2. ESB 4.9.0

   - built the images for default profile with default provisioning system
   - ran a smoke test
   - uses stop.sh script to terminate and delete the container

3. CEP 4.0.0

   - built the images for default profile with default provisioning system
   - ran a smoke test
   - uses stop.sh script to terminate and delete the container

4. DAS 3.0.1

   - built the images for default profile with default provisioning system
   - ran a smoke test
   - uses stop.sh script to terminate and delete the container

5. Verified the License with the RAT plugin

*[x] Stable - Go ahead and release*

On Fri, Jul 22, 2016 at 9:27 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi Devs,
>
> This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
> release.
>
> *This release fixes the following issues:*
>
> https://wso2.org/jira/issues/?filter=13159
>
> *Tag to be voted upon:*
>
> https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1
>
> *Source and distribution packages:*
>
> https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1
>
> Please download, test, and vote. The README file under the distribution
> contains guide and instructions on how to try it out locally.
>
> [+] Stable - Go ahead and release
>
> [-] Broken - Do not release (explain why)
>
>
>
> This vote will be open for 72 hours or as needed.
>
> Regards,
> WSO2 PaaS team
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Dimuthu De Lanerolle]

[+] Stable - Go ahead and release

Tested & Verified following wso2 products.
- WSO2 APIM
- WSO2 AS

Regards


On Mon, Jul 25, 2016 at 5:21 PM, Pubudu Gunatilaka  wrote:

> Hi,
>
> *[+] Stable - Go ahead and release*
>
> Verified following.
>
> 1. Distribution
> 2. License Headers
> 3. Tested following products
>-  WSO2 AM
>-  WSO2 AS
>-  WSO2 Greg
>-  WSO2 CEP
>-  WSO2 BPS
>
> Thank you!
>
> On Sat, Jul 23, 2016 at 3:31 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi Akila,
>>
>> Thanks for pointing out, I have fixed the mater branch pom versions with
>> commit [1].
>>
>> [1]
>> https://github.com/wso2/dockerfiles/commit/0cd9b7ae445fdd5ce8754e28352e28b30106401f
>>
>> On Sat, Jul 23, 2016 at 11:59 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Anuruddha,
>>>
>>> The pom version in master branch should always be a SNAPSHOT version [1].
>>>
>>> Thanks.
>>>
>>> On Fri, Jul 22, 2016 at 9:27 PM, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
 Hi Devs,

 This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
 release.

 *This release fixes the following issues:*

 https://wso2.org/jira/issues/?filter=13159

 *Tag to be voted upon:*

 https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1

 *Source and distribution packages:*

 https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1

 Please download, test, and vote. The README file under the distribution
 contains guide and instructions on how to try it out locally.

 [+] Stable - Go ahead and release

 [-] Broken - Do not release (explain why)



 This vote will be open for 72 hours or as needed.

 Regards,
 WSO2 PaaS team


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>
>>
>>
>> --
>> *Thanks and Regards,*
>> Anuruddha Lanka Liyanarachchi
>> Software Engineer - WSO2
>> Mobile : +94 (0) 712762611
>> Tel  : +94 112 145 345
>> a nurudd...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dimuthu De Lanerolle
Software Engineer
WSO2 Inc.
lean . enterprise . middlewear.
http://wso2.com/
Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC2

[Pubudu Gunatilaka]

Hi Devs,

This is the second release candidate (RC2) of WSO2 Puppet Modules 2.1.0
release. Please download, verify, and vote. Voting will be open for 72
hours or as needed.

This release fixes following issues:
https://wso2.org/jira/browse/PMODULES-16?filter=13155

​Source and binary distribution files:
https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2

The tag to be voted upon:
https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2

Release verification guide:
https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment

Refer modules README files for more details.

Please vote as follows.
[+] Stable - go ahead and release
[-]  Broken - do not release (please explain why)

Thank you,
WSO2 PaaS Team.

-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Orbit] Please merge PR for spark-mllib_2.10 version 1.4.1.wso2v3

[Manoj Kumara]

Hi Supun,

Added a comment. Please resolve that.

Regards,
manoj

*Manoj Kumara*
WSO2 Inc. *| **lean. enterprise. middleware.*
*Mobile:* +94 713 448188

On Mon, Jul 25, 2016 at 5:23 PM, Supun Sethunga  wrote:

> Hi Carbon Team,
>
> Can you please review and merge PR[1]? This is a fix for [2].
>
> [1] https://github.com/wso2/orbit/pull/222
> [2] https://wso2.org/jira/browse/CEP-1471
>
> Regards,
> Supun
>
> --
> *Supun Sethunga*
> Senior Software Engineer
> WSO2, Inc.
> http://wso2.com/
> lean | enterprise | middleware
> Mobile : +94 716546324
> Blog: http://supunsetunga.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Supporting secure vault capability in all Inbound Endpoint parameters

[Nuwan Wimalasekara]

Hi
In ESB 5.0.0, wso2:vault-lookup('alias') expression can be used in all
inbound endpoint parameters. even in registry resource text, valut-lookup()
expression can be used and set resource as the parameter value.

Parameter value  need to be encrypted and store with a alias and retrieve
the actual value in your ESB  inbound configuration as below

{wso2:vault-lookup('my.password')}
OR


[1] https://wso2.org/jira/browse/ESBJAVA-4715
[2] https://github.com/wso2/wso2-synapse/pull/608

Thanks,
Nuwanw

-- 
Nuwan Wimalasekara
Associate Technical Lead
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC1

[Pubudu Gunatilaka]

Hi,

We are aborting the vote as we found issues with license headers. Will
start another vote soon.

Thank you!

On Mon, Jul 25, 2016 at 3:55 PM, Thushara Ranawaka 
wrote:

> Hi Everyone,
>
> Tested the default deployment for G-Reg 5.1.0/5.2.0 and went through
> configuration and found no blocking issues.
>
> [X] Stable - Go ahead and release
>
> Thanks,
> Thushara.
>
>
> On Sun, Jul 24, 2016 at 7:41 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi Akila,
>>
>> Thanks for pointing this. I have fixed this in commit [1].
>>
>> Thanks.
>>
>> [1].
>> https://github.com/wso2/puppet-modules/commit/71a52d16f3b1d765f911d0ce197f627c36c513a6
>>
>>
>> On Sat, Jul 23, 2016 at 11:58 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Pubudu,
>>>
>>> The pom version in master branch should always be a SNAPSHOT version [1].
>>>
>>> [1] https://github.com/wso2/puppet-modules/blob/master/pom.xml#L24
>>>
>>> Thanks.
>>>
>>> On Fri, Jul 22, 2016 at 10:04 PM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Devs,

 This is the first release candidate (RC1) of WSO2 Puppet Modules 2.1.0
 release. Please download, verify, and vote. Voting will be open for 72
 hours or as needed.

 This release fixes following issues:

 https://wso2.org/jira/browse/PMODULES-16?filter=13155

 ​Source and binary distribution files:

 https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc1

 The tag to be voted upon:

 https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc1

 Release verification guide:


 https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment

 Refer modules README files for more details.

 Please vote as follows.

 [+] Stable - go ahead and release

 [-]  Broken - do not release (please explain why)

 Thank you,
 WSO2 PaaS Team.

 --
 *Pubudu Gunatilaka*
 Committer and PMC Member - Apache Stratos
 Software Engineer
 WSO2, Inc.: http://wso2.com
 mobile : +94774078049 <%2B94772207163>


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks,
> Thushara Kasun Ranawaka
> Software Engineer
> WSO2 Inc.;  
> lean.enterprise.middleware
> Mobile : *+94 (0) 773438949 <%2B94%20%280%29%20773438949>*
> *thusha...@wso2.com *
>
>
>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Orbit] Adding Storm 0.9.6 orbit bundle

[Manoj Kumara]

Added some comments. Please check.

Regards,
Manoj

*Manoj Kumara*
WSO2 Inc. *| **lean. enterprise. middleware.*
*Mobile:* +94 713 448188

On Mon, Jul 25, 2016 at 2:41 PM, Sajith Ravindra  wrote:

> Hi Kernal team,
>
> Can you please review and merge the pull request
> https://github.com/wso2/orbit/pull/221 to add the new strom version 0.9.6.
>
> Thanks
> *,Sajith Ravindra*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273550
> blog: http://sajithr.blogspot.com/
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [GSoC Dockerfiles] Issues with setting up Kubernetes using Vagrant

[Imesh Gunaratne]

Hi Abhishek,

How can we build your latest code in [1]?
[1] https://github.com/abhishek0198/test-framework.git

Thanks

On Wed, Jul 20, 2016 at 11:12 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi Imesh,
>
> Thanks a lot for the instructions, I will try the setup on OSX itself once
> I am done with the smoke tests.
>
> - Abhishek
>
>
> On Wednesday, July 20, 2016, Imesh Gunaratne  wrote:
>
>> Hi Abhishek,
>>
>> On Wed, Jul 20, 2016 at 9:49 AM, Abhishek Tiwari <
>> abhishek.tiwari0...@gmail.com> wrote:
>>
>>> Hi Mentors,
>>>
>>> I have been working on setting up Kubernetes cluster using vagrant and
>>> docker using [1]. I ran into multiple issues (coreos download taking hours,
>>> nfsd not being setup etc), however, those got resolved.
>>>
>>
>> ​Can you please execute following to ssh into the master node and check
>> the system log?
>>
>> vagrant ssh master
>> journalctl -f​
>>
>>
>>>
>>> Now, when I launch the setup using run.sh, I get this error [2]. I tried
>>> wiping out everything (vagrant destroy -f) and restart the whole process
>>> again, I get the same issue.
>>>
>>> One thing to note is, my host os is Mac and I use VirtualBox for
>>> development, so essentially I have virtualbox setup inside virtualbox. I
>>> don't think it should matter, but would like to get other people's opinion
>>> on this.
>>>
>>
>> ​This works on OSX.​
>>
>>
>>>
>>> While this issue gets resolved, I am planning to complete another
>>> milestone to add smoke tests for ESB and MB. I feel like, I should complete
>>> the test workflow for default platform before moving to Kubernetes, since
>>> the latter involves a lot of new technologies, more moving parts and other
>>> unknowns. I do plan to address Kubernetes testing, but would like to do
>>> that once default platform test workflow is complete. Thoughts?
>>>
>>
>> ​+1
>>
>> If [1] does not work for you, please try following:
>> http://kubernetes.io/docs/getting-started-guides/vagrant/
>>
>> Thanks​
>>
>>
>>>
>>> Thanks,
>>> Abhishek
>>>
>>> [1]. https://github.com/imesh/kubernetes-vagrant-setup
>>> [2].
>>> master: Waiting for machine to boot. This may take a few minutes...
>>> master: SSH address: 127.0.0.1:
>>> master: SSH username: core
>>> master: SSH auth method: private key
>>>
>>> Timed out while waiting for the machine to boot. This means that
>>> Vagrant was unable to communicate with the guest machine within
>>> the configured ("config.vm.boot_timeout" value) time period.
>>>
>>>
>>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> lean. enterprise. middleware
>>
>>


-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoT] Registering devices using API

[Dumidu Handakumbura]

Hi IoT Team,

In EMM you can register android devices using POST /devices resource(it is
also found in the swagger def). When going through IoT device-mgt swagger
def[1] I didn't find such a resource. How can I get devices
registered/enrolled purely using API? Please provide steps.


[1] - https://localhost:9443/api/device-mgt/v1.0/swagger.yaml

Thanks,

-- 
*Dumidu Handakumbura*
Software Engineer
WSO2 Inc; http://www.wso2.com/.
Mobile;
*+9406740 *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Orbit] Please merge PR for spark-mllib_2.10 version 1.4.1.wso2v3

[Supun Sethunga]

Hi Carbon Team,

Can you please review and merge PR[1]? This is a fix for [2].

[1] https://github.com/wso2/orbit/pull/222
[2] https://wso2.org/jira/browse/CEP-1471

Regards,
Supun

-- 
*Supun Sethunga*
Senior Software Engineer
WSO2, Inc.
http://wso2.com/
lean | enterprise | middleware
Mobile : +94 716546324
Blog: http://supunsetunga.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Pubudu Gunatilaka]

Hi,

*[+] Stable - Go ahead and release*

Verified following.

1. Distribution
2. License Headers
3. Tested following products
   -  WSO2 AM
   -  WSO2 AS
   -  WSO2 Greg
   -  WSO2 CEP
   -  WSO2 BPS

Thank you!

On Sat, Jul 23, 2016 at 3:31 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi Akila,
>
> Thanks for pointing out, I have fixed the mater branch pom versions with
> commit [1].
>
> [1]
> https://github.com/wso2/dockerfiles/commit/0cd9b7ae445fdd5ce8754e28352e28b30106401f
>
> On Sat, Jul 23, 2016 at 11:59 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Anuruddha,
>>
>> The pom version in master branch should always be a SNAPSHOT version [1].
>>
>> Thanks.
>>
>> On Fri, Jul 22, 2016 at 9:27 PM, Anuruddha Liyanarachchi <
>> anurudd...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
>>> release.
>>>
>>> *This release fixes the following issues:*
>>>
>>> https://wso2.org/jira/issues/?filter=13159
>>>
>>> *Tag to be voted upon:*
>>>
>>> https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1
>>>
>>> *Source and distribution packages:*
>>>
>>> https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1
>>>
>>> Please download, test, and vote. The README file under the distribution
>>> contains guide and instructions on how to try it out locally.
>>>
>>> [+] Stable - Go ahead and release
>>>
>>> [-] Broken - Do not release (explain why)
>>>
>>>
>>>
>>> This vote will be open for 72 hours or as needed.
>>>
>>> Regards,
>>> WSO2 PaaS team
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB Tooling] Improvement needed for operators that manipulates values using both input and configuration

[Chathurika De Silva]

Hi Nuwan

Awesome. Thank You

Best Regards
Erandi

On Mon, Jul 25, 2016 at 5:05 PM, Nuwan Pallewela  wrote:

> Hi Chathurika,
>
> Yes. We have discussed it and going to do it[1]. We will provide a
> editable drop down with the configuration need to provide to select the
> input and operator description in the configure dialog about it.
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-655
>
> Thanks,
> Nuwan
>
> On Mon, Jul 25, 2016 at 4:36 PM, Chathurika De Silva  > wrote:
>
>> Hi
>>
>> It was observed that the operators which manipulates values using both
>> the configuration and the inputs always takes the configured value as the
>> preceded one when both ways are present. According to the discussion in [1]
>> the user has to keep the default values in the configuration as it is to
>> make the values from the input to take precedence for the manipulation.
>>
>> In data mapper there are multiple operators that behave similarly and
>> currently the user should be either knowledgable or find out by reading
>> documentation which is an extra effort.
>>
>> In order to solve this, can we have an instruction wording in the
>> operator it self, so that the user will know how to use it directly. Since
>> this is a common improvement for most of the operators, it would be ideal
>> if this is done for this release itself.
>>
>> WDYT?
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-643
>>
>> Thank you
>> Erandi
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB Tooling] Improvement needed for operators that manipulates values using both input and configuration

[Nuwan Pallewela]

Hi Chathurika,

Yes. We have discussed it and going to do it[1]. We will provide a editable
drop down with the configuration need to provide to select the input and
operator description in the configure dialog about it.

[1] https://wso2.org/jira/browse/DEVTOOLESB-655

Thanks,
Nuwan

On Mon, Jul 25, 2016 at 4:36 PM, Chathurika De Silva 
wrote:

> Hi
>
> It was observed that the operators which manipulates values using both the
> configuration and the inputs always takes the configured value as the
> preceded one when both ways are present. According to the discussion in [1]
> the user has to keep the default values in the configuration as it is to
> make the values from the input to take precedence for the manipulation.
>
> In data mapper there are multiple operators that behave similarly and
> currently the user should be either knowledgable or find out by reading
> documentation which is an extra effort.
>
> In order to solve this, can we have an instruction wording in the operator
> it self, so that the user will know how to use it directly. Since this is a
> common improvement for most of the operators, it would be ideal if this is
> done for this release itself.
>
> WDYT?
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-643
>
> Thank you
> Erandi
>
> --
> *Chathurika Erandi*
> Senior Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][ESB Tooling] Improvement needed for operators that manipulates values using both input and configuration

[Chathurika De Silva]

Hi

It was observed that the operators which manipulates values using both the
configuration and the inputs always takes the configured value as the
preceded one when both ways are present. According to the discussion in [1]
the user has to keep the default values in the configuration as it is to
make the values from the input to take precedence for the manipulation.

In data mapper there are multiple operators that behave similarly and
currently the user should be either knowledgable or find out by reading
documentation which is an extra effort.

In order to solve this, can we have an instruction wording in the operator
it self, so that the user will know how to use it directly. Since this is a
common improvement for most of the operators, it would be ideal if this is
done for this release itself.

WDYT?

[1] https://wso2.org/jira/browse/DEVTOOLESB-643

Thank you
Erandi

-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC1

[Thushara Ranawaka]

Hi Everyone,

Tested the default deployment for G-Reg 5.1.0/5.2.0 and went through
configuration and found no blocking issues.

[X] Stable - Go ahead and release

Thanks,
Thushara.


On Sun, Jul 24, 2016 at 7:41 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi Akila,
>
> Thanks for pointing this. I have fixed this in commit [1].
>
> Thanks.
>
> [1].
> https://github.com/wso2/puppet-modules/commit/71a52d16f3b1d765f911d0ce197f627c36c513a6
>
>
> On Sat, Jul 23, 2016 at 11:58 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Pubudu,
>>
>> The pom version in master branch should always be a SNAPSHOT version [1].
>>
>> [1] https://github.com/wso2/puppet-modules/blob/master/pom.xml#L24
>>
>> Thanks.
>>
>> On Fri, Jul 22, 2016 at 10:04 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the first release candidate (RC1) of WSO2 Puppet Modules 2.1.0
>>> release. Please download, verify, and vote. Voting will be open for 72
>>> hours or as needed.
>>>
>>> This release fixes following issues:
>>>
>>> https://wso2.org/jira/browse/PMODULES-16?filter=13155
>>>
>>> ​Source and binary distribution files:
>>>
>>> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc1
>>>
>>> The tag to be voted upon:
>>>
>>> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc1
>>>
>>> Release verification guide:
>>>
>>>
>>> https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment
>>>
>>> Refer modules README files for more details.
>>>
>>> Please vote as follows.
>>>
>>> [+] Stable - go ahead and release
>>>
>>> [-]  Broken - do not release (please explain why)
>>>
>>> Thank you,
>>> WSO2 PaaS Team.
>>>
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks,
Thushara Kasun Ranawaka
Software Engineer
WSO2 Inc.;  
lean.enterprise.middleware
Mobile : *+94 (0) 773438949*
*thusha...@wso2.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC2016-Contact Development Team Feature

[Kavith Lokuhewage]

Hi Nathiesha,

I noticed that there are some more pending tasks to restructure the code
base as per the discussion we had during last code review. Just putting
them down here again, so that you are able to go through again and complete
any missing parts.

*Introduce interfaces for the each sub component  to decouple main
controller logic from implementation specific things*

For example, right now, the controller class (ErrorReporter) is hardly
coupled with EmailSender and RemoteJiraConnector. We can think latter two
as error report publishers and introduce an interface called ErrorPublisher
as below.

public interface ErrorPublisher{
void publish(ReportGenerator reportGen) throws IOException;
}

And then EmailSender and RemoreJiraConnector classes can be refactored like
below.

public class EmailPublisher implements ErrorPublisher{

 void init () throws IOException{
   //init : read preferences for SMTP connection params
 }

// implement publish method
void publish(ReportGenerator reportGen) throws IOException{
init();
   //send mail
}
}

public class JiraPublisher implements ErrorPublisher{

 void init () throws IOException{
  //init : read preferences for JIRA resp API connection params
 }

   // implement publish method
   void publish(ReportGenerator reportGen) throws IOException{
   init();
  //post to JIRA api and create issue
   }
}

Finally refactor ErrorReporter class to use only ErrorPublisher interface.
Further more, introduce methods to bind/unbind error publishers.

public class ErrorReporter {
Map registeredPublishers;

public void addPublisher (String id, ErrorPublisher publisher){
   registeredPublishers.put(id,publisher);
   }

  public void reportError(){
 //iterate over all publishers
 // and call  publish() method
  }
}

(We can further ErrorReporter class by using OSGI services to let other
devstudio plugins to contribute publishers as needed - we can do that later
as time permits)

For another example, currently you have used a class called ReportGenerator
to generate the report in plain text and directly used that generator
inside main controller. Instead, you can introduce an interface called
ReportGenerator and create a class called TextReportGenerator and move the
code there - and decouple main controller and let other people add report
generators later (say an HTML report generator) as needed. It can be done
in same manner as above example I have provided .

Once you do above restructuring, we can further improve the code to use
OSGI services to decouple these components even further.

Finally, I think it is time for us to convert the project to a maven
project and use tycho maven plugins for building it. I can assist you with
this task - let's discuss this furthermore during the call. The main
requirement here is to make this project directly mergable to developer
studio repository. Since we are now reaching to the final weeks of GSOC
coding period, I think we should concentrate a little more on this task.

Please a suggest a time for the meeting so we are able to discuss
these in-detail.

Thanks,

*Kavith Lokuhewage*
Senior Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +94779145123
Linkedin   Twitter


On Mon, Jul 25, 2016 at 2:11 PM, Kavith Lokuhewage  wrote:

> Hi Nathiesha,
>
> There were some changes done to preference API since Eclipse Mars. I
> suspect that the root cause for the issue should be it. I will go through
> the changes we did in Developer Studio to fix issues with new pref API and
> confirm you whether it is the root cause or not.
>
> Meanwhile, please suggest a time for another meeting this week - probably
> on Thursday or Friday. We will go through the complete implementation to
> verify that everything is in order.
> I went through the code and have some comments too. I will put them in
> github it self.
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Wed, Jul 20, 2016 at 10:20 AM, Nathiesha Maddage <
> nathieshamadd...@gmail.com> wrote:
>
>> Hi all,
>>
>> I started unit testing with InfoCollector and Startup Classes, and
>> created a few unit tests using JUnit.
>>
>> Regarding the progress of the project, I am currently working on the
>> ReportArchive module. The ReportArchive module currently displays all the
>> sent error reports to the user in a window, and I am  working on adding a
>> context menu option for each error report to inquire the current status of
>> the issue.
>>
>> Regarding the Preference page, I tried creating a Input Dialog, that
>> would open up for the very first time the plugin  reports an

Re: [Dev] EventPublisherConfigurationException at IS 5.2.0 Snapshot Startup

[Dulanja Liyanage]

Ah okay. I will try with an later JDK. Thanks!

On Mon, Jul 25, 2016 at 12:12 PM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:

> This seems to be a JDK issue and fixed in later updates as per :
> https://bugs.openjdk.java.net/browse/JDK-8059803
>
> We are using a system property to get the OS name which - System.
> getProperty("os.name")
>
> On Fri, Jul 22, 2016 at 8:00 AM, Dulanja Liyanage 
> wrote:
>
>> Also, Kernel Team, I wonder why the correct Windows version cannot be
>> identified. Mine is a 10 but identified as 8.1. Could we please check on
>> that?
>>
>> TID: [-1234] [] [2016-07-22 07:36:38,101]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
>> Windows 8.1 6.3, amd64
>> TID: [-1234] [] [2016-07-22 07:36:38,105]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
>> C:\Program Files\Java\jdk1.7.0_80\jre
>> TID: [-1234] [] [2016-07-22 07:36:38,108]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
>> 1.7.0_80
>> TID: [-1234] [] [2016-07-22 07:36:38,110]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
>> Java HotSpot(TM) 64-Bit Server VM 24.80-b11,Oracle Corporation
>> TID: [-1234] [] [2016-07-22 07:36:38,114]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
>> D:\packs\WSO2IS~1.0-S\bin\..
>> TID: [-1234] [] [2016-07-22 07:36:38,116]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
>> D:\packs\WSO2IS~1.0-S\bin\..\tmp
>> TID: [-1234] [] [2016-07-22 07:36:38,119]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
>> dulanja, en-US, Asia/Colombo
>> TID: [-1234] [] [2016-07-22 07:36:38,233]  WARN
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  The
>> running OS : Windows 8.1 is not a tested Operating System for running WSO2
>> Carbon
>>
>>
>> On Fri, Jul 22, 2016 at 7:55 AM, Dulanja Liyanage 
>> wrote:
>>
>>> Hi All,
>>>
>>> Getting the following error at the server startup:
>>>
>>> TID: [-1234] [] [2016-07-22 07:37:16,240] ERROR
>>>
>>> {org.wso2.carbon.event.publisher.core.EventPublisherDeployer}
>>>
>>> - Error, Event Publisher not deployed and in inactive state, Error while
>>> deleting the Event Publisher : Illegal char <:> at index 2:
>>> /D:/packs/WSO2IS~1.0-S/bin/../repository/deployment/server/\eventpublishers
>>> org.wso2.carbon.event.publisher.core.exception.EventPublisherConfigurationException:
>>> Error while deleting the Event Publisher : Illegal char <:> at index 2:
>>> /D:/packs/WSO2IS~1.0-S/bin/../repository/deployment/server/\eventpublishers
>>> at
>>> org.wso2.carbon.event.publisher.core.internal.util.helper.EventPublisherConfigurationFilesystemInvoker.delete(EventPublisherConfigurationFilesystemInvoker.java:131)
>>> at
>>> org.wso2.carbon.event.publisher.core.EventPublisherDeployer.processDeployment(EventPublisherDeployer.java:177)
>>> at
>>> org.wso2.carbon.event.publisher.core.EventPublisherDeployer.deploy(EventPublisherDeployer.java:83)
>>> at
>>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>>> at
>>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
>>> at
>>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>>> at
>>> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:135)
>>> at
>>> org.wso2.carbon.core.CarbonAxisConfigurator.deployServices(CarbonAxisConfigurator.java:567)
>>> at
>>> org.wso2.carbon.core.internal.DeploymentServerStartupObserver.completingServerStartup(DeploymentServerStartupObserver.java:51)
>>> at
>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.notifyBefore(CarbonCoreServiceComponent.java:238)
>>> at
>>> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:185)
>>> at
>>> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:288)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>> at
>>> or

[Dev] [Orbit] Adding Storm 0.9.6 orbit bundle

[Sajith Ravindra]

Hi Kernal team,

Can you please review and merge the pull request
https://github.com/wso2/orbit/pull/221 to add the new strom version 0.9.6.

Thanks
*,Sajith Ravindra*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 77 2273550
blog: http://sajithr.blogspot.com/

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error while starting-up DAS 3.0.1 with -Dsetup option

[Malintha Adikari]

Hi,

I am getting $subject  when I use -Dsetup option. Do I have to
provide "identity/h2.sql"
file ?

[2016-07-25 13:54:37,878] ERROR
{org.wso2.carbon.identity.core.internal.IdentityCoreServiceComponent} -
 Error occurred while populating identity configuration properties
org.wso2.carbon.identity.base.IdentityRuntimeException: Error occurred
while executing SQL script for creating identity database
at
org.wso2.carbon.identity.base.IdentityRuntimeException.error(IdentityRuntimeException.java:162)
at
org.wso2.carbon.identity.core.persistence.IdentityDBInitializer.executeSQLScript(IdentityDBInitializer.java:273)
at
org.wso2.carbon.identity.core.persistence.IdentityDBInitializer.createIdentityDatabase(IdentityDBInitializer.java:141)
at
org.wso2.carbon.identity.core.persistence.JDBCPersistenceManager.initializeDatabase(JDBCPersistenceManager.java:112)
at
org.wso2.carbon.identity.core.internal.IdentityCoreServiceComponent.activate(IdentityCoreServiceComponent.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:514)
at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(S

Re: [Dev] GSoC2016-Contact Development Team Feature

[Kavith Lokuhewage]

Hi Nathiesha,

There were some changes done to preference API since Eclipse Mars. I
suspect that the root cause for the issue should be it. I will go through
the changes we did in Developer Studio to fix issues with new pref API and
confirm you whether it is the root cause or not.

Meanwhile, please suggest a time for another meeting this week - probably
on Thursday or Friday. We will go through the complete implementation to
verify that everything is in order.
I went through the code and have some comments too. I will put them in
github it self.

Thanks,

*Kavith Lokuhewage*
Senior Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +94779145123
Linkedin   Twitter


On Wed, Jul 20, 2016 at 10:20 AM, Nathiesha Maddage <
nathieshamadd...@gmail.com> wrote:

> Hi all,
>
> I started unit testing with InfoCollector and Startup Classes, and created
> a few unit tests using JUnit.
>
> Regarding the progress of the project, I am currently working on the
> ReportArchive module. The ReportArchive module currently displays all the
> sent error reports to the user in a window, and I am  working on adding a
> context menu option for each error report to inquire the current status of
> the issue.
>
> Regarding the Preference page, I tried creating a Input Dialog, that would
> open up for the very first time the plugin  reports an error to the user.
> This dialog would ask the user to fill  values to compulsory fields like
> Jira Username and Password, and it would store these values in the
> preference page as well, for future use.
>
> I tried to save the user entered values in Input dialog, to the preference
> page using Activator.getDefault().getPreferenceStore().setValue() method.
> This method would set the user entered values in respective fields of the
> preference page, but that is just temporary. These values disappear from
> the preference page the next time I run it. Only the default set values by
> the code and the values that I enter in the preference page there itself
> would retain permanently. I tried to fix this for a couple of days and
> tried almost every solution I could find in the internet regarding this.
>
> Have you encountered a situation like this where you have to set the
> values in preference page through code? Any idea whether this is possible
> and if so how to do it would be of big help!
>
> Best regards
>
> Nathiesha
>
>
> On Thu, Jul 7, 2016 at 6:31 AM, Nathiesha Maddage <
> nathieshamadd...@gmail.com> wrote:
>
>> Hi all,
>>
>> Regarding the current status of the project, I am working on the
>> development of the report Archive module, where the user can view the
>> previously sent error reports and also the current status of those issues.
>> Meanwhile I thought to look into the testing part of the project as well.
>> Is their any special testing framework used in Developer Studio testing,
>> that I need to adopt? I though to use JUnit. Is it OK?
>>
>> Regards
>>
>> Nathiesha
>>
>> On Tue, Jun 28, 2016 at 9:34 AM, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I downloaded and tried running the Data Analytics Server . Currently I
>>> am going through the DAS documentation and the REST API. Is it possible to
>>> post data using the REST API? As I noticed, it only allows to retrieve data
>>> from the DAS.
>>>
>>> Thanks and regards
>>>
>>> Nathiesha
>>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016: Proposal 7

[Dinanjana Gunaratne]

Hi Kasun,
Currently our solution has following capabilities.
Monitoring memory and CPU loads
Monitoring request load
Monitoring responsiveness of ESB.
Creating thread and heap dumps
Creating a report
Storing request count and relevant details in Derby embedded db
When any adverse effect taking place on esb this variables can indicate
that. Currently we are monitoring those aspects in an event based system.
Each event can be configured by the user by changing parameters in
respective config files. So when an anomaly detected by those monitors
respective event will be triggered. This will result in logging the event
in a report. Also thread dumps heap dumps will be collected according to
users specifications. We can schedule a demo on Wednesday preferably in the
night since I have an interview on the same day. I will confirm it once I
discuss this with my mentors

On Jul 25, 2016 9:30 AM, "Kasun Indrasiri"  wrote:

> What's the current state of this project? Shall we do a end to end demo on
> what you have done so far?
>
> On Tue, Jun 21, 2016 at 6:24 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Here are the minutes of the review meeting we had yesterda
>> y
>>  -Some code refactoring was suggested. Reducing use of static variables
>> and static methods was suggested.
>>  -As the next milestone adding user configurable esb issue reporting
>> suggested. This will change the current implementation to event   base
>> implementation.There will be pre defined events for monitoring tool.
>>   -E.g Out of memory event
>>  Configurable options :Memory threshold
>>  Outcomes (heap dumps,thread
>> dumps)
>>  Frequency of extracting dumps
>>
>> - Creating a class diagram
>>
>>
>>
>> On Wed, Jun 1, 2016 at 10:13 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Hello all,
>>>
>>> Progress of the tool so far
>>>
>>> The tool can be deployed in a remote machine to monitor ESB instance. It
>>> connects to MBanServer of the targeted machine through RMI. Currently it
>>> monitors memory usage, CPU usage and Network traffic of the ESB. Network
>>> traffic details are gathered through PassThruHttpSender/receiver mbeans.
>>> These metrics values are queried periodically. Period can be defined on a
>>> property file under the resources folder inside the working dir. There are
>>> three threads running inside the tool.
>>>
>>> Thread 1: Periodically query memory and operating system mbeans to find
>>> out about heap memory usage & cpu load avearge
>>>Threshold values for max memory usage and max cpu load
>>> average can be set on the property file. So is the period.
>>>If memory usage exceeds this max value heap dump will be
>>> automatically generated on the remote ESB Home. User can
>>>  specify any location. By default it will be created on ESB home. If the
>>> average CPU load exceeds the max value the Threaddump will
>>> be generated inside the tool. Location to thread dumps to be saved can be
>>> specified by the user. Each time a heapdump requested a
>>> seperate thread will be created to handle it.
>>>
>>> Thread 2: Periodically monitors network traffic from
>>> PassThruHTTPSender/receiver mbeans. As we discussed earlier network details
>>>are persisted to an embedded derby db. Period can be set.
>>>
>>> Thread 3: This handles persistence services. Period can be set.
>>>
>>> Name of the heap dumps are created as this "HeapDump "
>>> +date.toString().replaceAll(":","")+".bin"
>>> Name of the thread dumps are created as this  "ThreadDump"+new
>>> Date().toString().replaceAll(":","")+".txt"
>>>
>>> Let me know if I got it right :)
>>>
>>>
>>> On Mon, May 30, 2016 at 7:30 PM, Dinanjana Gunaratne <
>>> dinanjanagunara...@gmail.com> wrote:
>>>
 Thanks Viraj
 On May 30, 2016 7:23 PM, "Viraj Senevirathne"  wrote:

> 
> org.apache.synapse
> synapse-nhttp-transport
> 
>
> On Sun, May 29, 2016 at 9:19 AM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Hello all,
>> I am facing a problem when trying to create a proxy object. I
>> couldn't find correct maven dependency to get class
>> org.apache.synapse.transport.passthru.jmx.TransportView. Can you
>> direct me to the correct dependency.
>>
>>
>> On Sat, May 14, 2016 at 8:46 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Dear all,
>>> I have added DynamicReports (which is an implementation based on
>>> Jasper reports) as the reporting framework for the Flight recorder. It
>>> would be great if I can have wso2 license headers for refactor. Direct 
>>> me
>>> for IntelliJ headers. All changes can be seen here [1]
>>> 
>>>
>>> [1 ]https://github.com/dina