date:20160726

Re: [Dev] Error with Secured/Encrypted VFS Transport Credentials on ESB500Beta2

2016-07-26 Thread Chaminda Jayawardena

Hi Rajith,

This is worked when I used a keystore with 1024 keysize. I will verify with
2048 bit keystore with the next release.

I noticed following warning in the logs while server startup even though
the param exists.

*[2016-07-26 12:22:12,199]  WARN - PollTableEntry transport.vfs.FileURI
parameter is missing in the proxy service configuration*

And when I put *"BC" *param in axis2.xml, getting below
exception[1] while server startup. Better to fix these two.

And following information mentioned in the jira should be corrected.
When we use ciphertool for encryption, it is not needed to put
*security.provider*  parameter either in axis2.xml or in the proxy service.

*[1]*
*[2016-07-26 12:22:15,166] ERROR - VFSTransportListener Unexpected error
when configuring service StockQuoteProxy for the VFS transport. It will be
disabled for this transport and marked as faulty.*
*java.lang.IllegalArgumentException: Illegal group reference*
* at java.util.regex.Matcher.appendReplacement(Matcher.java:857)*
* at java.util.regex.Matcher.replaceFirst(Matcher.java:1004)*
* at
org.apache.synapse.transport.vfs.PollTableEntry.decryptIfRequired(PollTableEntry.java:701)*
* at
org.apache.synapse.transport.vfs.PollTableEntry.loadConfiguration(PollTableEntry.java:414)*
* at
org.apache.axis2.transport.base.AbstractTransportListenerEx.startListeningForService(AbstractTransportListenerEx.java:153)*
* at
org.apache.axis2.transport.base.AbstractTransportListener.internalStartListeningForService(AbstractTransportListener.java:213)*
* at
org.apache.axis2.transport.base.AbstractTransportListener$2.serviceAdded(AbstractTransportListener.java:126)*
* at
org.apache.axis2.transport.base.tracker.AxisServiceTracker.serviceAdded(AxisServiceTracker.java:212)*
* at
org.apache.axis2.transport.base.tracker.AxisServiceTracker.start(AxisServiceTracker.java:188)*
* at
org.apache.axis2.transport.base.AbstractTransportListener.start(AbstractTransportListener.java:178)*
* at
org.apache.axis2.transport.base.AbstractTransportListenerEx.start(AbstractTransportListenerEx.java:83)*
* at
org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:168)*
* at
org.apache.axis2.engine.ListenerManager.startSystem(ListenerManager.java:186)*
* at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:165)*
* 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
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.throttling.agent.internal.ThrottlingAgentServiceComponent.registerThrottlingAgent(ThrottlingAgentServiceComponent.java:123)*
* at
org.wso2.carbon.throttling.agent.internal.ThrottlingAgentServiceComponent.activate(ThrottlingAgentServiceComponent.java:100)*
* at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
* at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
* at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
* at java.lang.reflect.Method.invoke(Method.java:483)*
* 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.BundleContextImp

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

2016-07-26 Thread Imesh Gunaratne

Hi,

+1 for the release, I verified following:

   - Built and verified following Docker images using default provisioning
   scheme:
  - wso2am:1.10.0, wso2as:5.3.0, wso2bps:3.5.1, wso2brs:2.2.0,
  wso2cep:4.1.0, wso2das:3.0.1, wso2dss:3.5.0, wso2es:2.0, wso2esb:4.9.0,
  wso2greg:5.1.0, wso2is:5.1.0, wso2mb:.3.1.0
   - Verified license headers using RAT tool
   - Verified README files
   - Docker version used: 1.12.0-rc4

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
>
>


-- 
*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

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

2016-07-26 Thread Thanuja Uruththirakodeeswaran

[+1] Stable - Go ahead and release

Verified the following:

   1. Distribution
   2. License Headers using RAT plugin
   3. README files
   4. Verified following products with docker images built with puppet
   provisioning for Mesos platform and tested basic functionalities:


   - WSO2 ES 2.0.0 (Distributed setup)
   - WSO2 AS 5.3.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
   - WSO2 APIM 1.10.0

5. Tested above products in Mesos platform with secure vault
enabled.
6. Tested SSO configuration with WSO2 IS 5.1.0 as identity provider
and WSO2 ESB 4.9.0 and WSO2 AS 5.3.0 as service providers.

Thanks.

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
>
>


-- 
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] Fwd: Releasing an update for DevS kernel 4.1.0

2016-07-26 Thread Kavith Lokuhewage

Hi Viraj,

Please send the PR with the fix to master branch. We will release the
update for 4.1.0.

Thanks,

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


On Fri, Jul 22, 2016 at 3:47 PM, Viraj Rajaguru  wrote:

>
> -- Forwarded message --
> From: Viraj Rajaguru 
> Date: Fri, Jul 22, 2016 at 3:46 PM
> Subject: Releasing an update for DevS kernel 4.1.0
> To: Jasintha Dasanayake , Kavith Lokuhewage <
> kav...@wso2.com>, Susinda Perera , Sohani Weerasinghe <
> soh...@wso2.com>, Nuwan Pallewela , Chanaka Fernando <
> chana...@wso2.com>, Jagath Sisirakumara Ariyarathne 
>
>
> Hi DevS kernel team,
>
> We faced an issue while deploying CAR files when webContextRoot is enabled
> in carbon.xml. See the public Jira[1]. This needs to be fixed in
> "devstudio-tooling-platform". Can we have this fix as an update for Kernel
> 4.1.0 since this is a blocker for ESB tolling release. Fix is attached to
> the jira.
>
> BTW, is there any 4.1.0 update branch so that we can send pull requests?
>
> Thanks,
> Viraj.
>
> [1] - https://wso2.org/jira/browse/DEVTOOLESB-637
> --
> Viraj Rajaguru
> Associate Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>
>
>
> --
> Viraj Rajaguru
> Associate Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>
> ___
> 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] Please vote for WSO2 Developer Studio Kernel 4.2.0 RC2

2016-07-26 Thread Kavith Lokuhewage

Hi Prakhash,

I have submitted security scan reports as per the guide-lines.

@All,

We are closing this vote now and will proceed with Developer Studio Kernel
4.2.0 release.

Thanks,

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

On Fri, Jul 22, 2016 at 11:17 AM, Prakhash Sivakumar 
wrote:

> Sorry :
> s/Sohani/Kavith/g
>
> On Fri, Jul 22, 2016 at 11:14 AM, Prakhash Sivakumar 
> wrote:
>
>> Hi Sohani,
>>
>> We couldn't find the security report for this. Please provide that as
>> instructed in "Enforcing Security Scanning Before Product Releases"
>>
>> Thanks
>>
>>
>> On Fri, Jul 22, 2016 at 10:34 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested the updater tool functionality including the issue
>>> reported at [1].
>>>
>>> My vote is +1
>>>
>>> [1] https://wso2.org/jira/browse/TOOLS-3436
>>>
>>> Thanks,
>>> Sohani
>>>
>>> Sohani Weerasinghe
>>> Senior Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Wed, Jul 20, 2016 at 10:07 PM, Kavith Lokuhewage 
>>> wrote:
>>>
 Hello Devs,

 Please vote for the second release candidate for WSO2 Developer Studio
 Kernel 4.2.0.

 P2 repository and RCP products of WSO2 developer Studio kernel 4.2.0
 RC2 is available here

 .

 Source and Tag Location to be voted upon is available here

 .

 With the 4.2.0 release, WSO2 Developer Studio kernel also provides an
 Eclipse RCP based distribution - further reducing the size.

 We have also introduced a web based dashboard for Developer Studio to
 enhance user experience.

 Also the XULRunner is embedded to maintain an unbroken user experience
 in WSO2 Developer Studio on windows platform - when using web technologies.

 We have also fixed a few bugs.

  - https://wso2.org/jira/browse/DEVTOOLESB-441
  - https://wso2.org/jira/browse/TOOLS-3423

 For the second release candidate, we have identified and fixed a major
 blocker for automatic updater in kernel.

 - https://wso2.org/jira/browse/TOOLS-3436

 Vote will be open for 72 hours or as needed. Please vote as follows.

1. [+] Stable - go ahead and release
2. [-]  Broken - do not release (please explain why)

 Thanks,

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

>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Prakhash Sivakumar
>> Software Engineer | WSO2 Inc
>> Platform Security Team
>> Mobile : +94771510080
>> Blog : https://medium.com/@PrakhashS
>>
>
>
>
> --
> Prakhash Sivakumar
> Software Engineer | WSO2 Inc
> Platform Security Team
> Mobile : +94771510080
> Blog : https://medium.com/@PrakhashS
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

2016-07-26 Thread Sajith Ravindra

H Manoj,

Did the changes. Please check.

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

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


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

> 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

[Dev] [ML] Making the server port configurable in the ML samples

2016-07-26 Thread Niranda Perera

Hi Nirmal,

When I run the ML samples, I found out that SERVER_PORT is not configurable
as of the current impl [1]. Is there any way where we could adjust the port
offset in the samples?

If not, I created a PR to make it configurable, following the same approach
for SERVER_PORT. Please review it and merge it. :-)

Best

[1]
https://github.com/wso2/product-ml/blob/master/modules/samples/server.conf
[2] https://github.com/wso2/product-ml/pull/307
-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please vote for WSO2 Developer Studio Kernel 4.2.0 RC2

2016-07-26 Thread Prakhash Sivakumar

Hi Kavith,

Got the report.

Thanks

On Tue, Jul 26, 2016 at 2:22 PM, Kavith Lokuhewage  wrote:

> Hi Prakhash,
>
> I have submitted security scan reports as per the guide-lines.
>
> @All,
>
> We are closing this vote now and will proceed with Developer Studio Kernel
> 4.2.0 release.
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Fri, Jul 22, 2016 at 11:17 AM, Prakhash Sivakumar 
> wrote:
>
>> Sorry :
>> s/Sohani/Kavith/g
>>
>> On Fri, Jul 22, 2016 at 11:14 AM, Prakhash Sivakumar 
>> wrote:
>>
>>> Hi Sohani,
>>>
>>> We couldn't find the security report for this. Please provide that as
>>> instructed in "Enforcing Security Scanning Before Product Releases"
>>>
>>> Thanks
>>>
>>>
>>> On Fri, Jul 22, 2016 at 10:34 AM, Sohani Weerasinghe 
>>> wrote:
>>>
 Hi All,

 I have tested the updater tool functionality including the issue
 reported at [1].

 My vote is +1

 [1] https://wso2.org/jira/browse/TOOLS-3436

 Thanks,
 Sohani

 Sohani Weerasinghe
 Senior Software Engineer
 WSO2, Inc: http://wso2.com

 Mobile  : +94 716439774
 Blog :http://christinetechtips.blogspot.com/
 Twitter  : https://twitter.com/sohanichristine

 On Wed, Jul 20, 2016 at 10:07 PM, Kavith Lokuhewage 
 wrote:

> Hello Devs,
>
> Please vote for the second release candidate for WSO2 Developer Studio
> Kernel 4.2.0.
>
> P2 repository and RCP products of WSO2 developer Studio kernel 4.2.0
> RC2 is available here
> 
> .
>
> Source and Tag Location to be voted upon is available here
> 
> .
>
> With the 4.2.0 release, WSO2 Developer Studio kernel also provides an
> Eclipse RCP based distribution - further reducing the size.
>
> We have also introduced a web based dashboard for Developer Studio to
> enhance user experience.
>
> Also the XULRunner is embedded to maintain an unbroken user experience
> in WSO2 Developer Studio on windows platform - when using web 
> technologies.
>
> We have also fixed a few bugs.
>
>  - https://wso2.org/jira/browse/DEVTOOLESB-441
>  - https://wso2.org/jira/browse/TOOLS-3423
>
> For the second release candidate, we have identified and fixed a major
> blocker for automatic updater in kernel.
>
> - https://wso2.org/jira/browse/TOOLS-3436
>
> Vote will be open for 72 hours or as needed. Please vote as follows.
>
>1. [+] Stable - go ahead and release
>2. [-]  Broken - do not release (please explain why)
>
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>


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


>>>
>>>
>>> --
>>> Prakhash Sivakumar
>>> Software Engineer | WSO2 Inc
>>> Platform Security Team
>>> Mobile : +94771510080
>>> Blog : https://medium.com/@PrakhashS
>>>
>>
>>
>>
>> --
>> Prakhash Sivakumar
>> Software Engineer | WSO2 Inc
>> Platform Security Team
>> Mobile : +94771510080
>> Blog : https://medium.com/@PrakhashS
>>
>
>


-- 
Prakhash Sivakumar
Software Engineer | WSO2 Inc
Platform Security Team
Mobile : +94771510080
Blog : https://medium.com/@PrakhashS
___
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

2016-07-26 Thread Maheshika Goonetilleke

Hi Manoj

Done, deployed successfully.

On Tue, Jul 26, 2016 at 12:24 PM, Manoj Kumara  wrote:

> 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 <
> mahesh...@wso2.com> 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.plugi

Re: [Dev] [ML] Making the server port configurable in the ML samples

2016-07-26 Thread Nirmal Fernando

Thanks, Niranda ! Merged it.

On Tue, Jul 26, 2016 at 2:33 PM, Niranda Perera  wrote:

> Hi Nirmal,
>
> When I run the ML samples, I found out that SERVER_PORT is not
> configurable as of the current impl [1]. Is there any way where we could
> adjust the port offset in the samples?
>
> If not, I created a PR to make it configurable, following the same
> approach for SERVER_PORT. Please review it and merge it. :-)
>
> Best
>
> [1]
> https://github.com/wso2/product-ml/blob/master/modules/samples/server.conf
> [2] https://github.com/wso2/product-ml/pull/307
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>

-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.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

2016-07-26 Thread Supun Sethunga

Thanks Manoj and Maheshika!

On Tue, Jul 26, 2016 at 2:46 PM, Maheshika Goonetilleke 
wrote:

> Hi Manoj
>
> Done, deployed successfully.
>
> On Tue, Jul 26, 2016 at 12:24 PM, Manoj Kumara  wrote:
>
>> 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 <
>> mahesh...@wso2.com> 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/s

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

2016-07-26 Thread Manujith Pallewatte

Hi Farasath,

Above code works perfectly! Thankx alot for the help.

Manujith

On Tue, Jul 26, 2016 at 12:32 AM, Farasath Ahamed 
wrote:

> 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 <
> manujith...@gmail.com> 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
>>
>>
>


-- 



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

2016-07-26 Thread Anuruddha Liyanarachchi

Hi All,

Thank you for taking your time to test and verify WSO2 Dockerfiles
 1.2.0 RC1.

The vote is been closed now. The vote passes with 8 'stable' votes and no
votes for 'broken'.
It will now be prepared for the release of WSO2 Dockerfiles 1.2.0.

On Tue, Jul 26, 2016 at 1:05 PM, Imesh Gunaratne  wrote:

> Hi,
>
> +1 for the release, I verified following:
>
>- Built and verified following Docker images using default
>provisioning scheme:
>   - wso2am:1.10.0, wso2as:5.3.0, wso2bps:3.5.1, wso2brs:2.2.0,
>   wso2cep:4.1.0, wso2das:3.0.1, wso2dss:3.5.0, wso2es:2.0, wso2esb:4.9.0,
>   wso2greg:5.1.0, wso2is:5.1.0, wso2mb:.3.1.0
>- Verified license headers using RAT tool
>- Verified README files
>- Docker version used: 1.12.0-rc4
>
> 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
>>
>>
>
>
> --
> *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
>
>


-- 
*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] [Orbit] Adding Storm 0.9.6 orbit bundle

2016-07-26 Thread Manoj Kumara

Merged the PR.

Regards,
Manoj

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

On Tue, Jul 26, 2016 at 2:28 PM, Sajith Ravindra  wrote:

> H Manoj,
>
> Did the changes. Please check.
>
> Thanks
> *,Sajith Ravindra*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273550
> blog: http://sajithr.blogspot.com/
> 
>
> On Mon, Jul 25, 2016 at 5:31 PM, Manoj Kumara  wrote:
>
>> 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] [Orbit] Adding Storm 0.9.6 orbit bundle

2016-07-26 Thread Sajith Ravindra

@Mahesika, could you please release it.

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

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


On Tue, Jul 26, 2016 at 3:30 PM, Manoj Kumara  wrote:

> Merged the PR.
>
> Regards,
> Manoj
>
> *Manoj Kumara*
> WSO2 Inc. *| **lean. enterprise. middleware.*
> *Mobile:* +94 713 448188
>
> On Tue, Jul 26, 2016 at 2:28 PM, Sajith Ravindra  wrote:
>
>> H Manoj,
>>
>> Did the changes. Please check.
>>
>> Thanks
>> *,Sajith Ravindra*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 2273550
>> blog: http://sajithr.blogspot.com/
>> 
>>
>> On Mon, Jul 25, 2016 at 5:31 PM, Manoj Kumara  wrote:
>>
>>> 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] [Orbit] Adding Storm 0.9.6 orbit bundle

2016-07-26 Thread Maheshika Goonetilleke

Hi Sajith

Deployed successfully.

On Tue, Jul 26, 2016 at 3:34 PM, Sajith Ravindra  wrote:

> @Mahesika, could you please release it.
>
> Thanks
> *,Sajith Ravindra*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273550
> blog: http://sajithr.blogspot.com/
> 
>
> On Tue, Jul 26, 2016 at 3:30 PM, Manoj Kumara  wrote:
>
>> Merged the PR.
>>
>> Regards,
>> Manoj
>>
>> *Manoj Kumara*
>> WSO2 Inc. *| **lean. enterprise. middleware.*
>> *Mobile:* +94 713 448188
>>
>> On Tue, Jul 26, 2016 at 2:28 PM, Sajith Ravindra 
>> wrote:
>>
>>> H Manoj,
>>>
>>> Did the changes. Please check.
>>>
>>> Thanks
>>> *,Sajith Ravindra*
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 77 2273550
>>> blog: http://sajithr.blogspot.com/
>>> 
>>>
>>> On Mon, Jul 25, 2016 at 5:31 PM, Manoj Kumara  wrote:
>>>
 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
>
>

>>>
>>
>


-- 

Thanks & Best Regards,

Maheshika Goonetilleke
Senior Engineering Process Coordinator

*WSO2 Inc*
*email   : mahesh...@wso2.com *
*mobile : +94 773 596707*
*www: :http://wso2.com *lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

2016-07-26 Thread Sajith Ravindra

Thanks, Mahesika.

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

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


On Tue, Jul 26, 2016 at 3:41 PM, Maheshika Goonetilleke 
wrote:

> Hi Sajith
>
> Deployed successfully.
>
> On Tue, Jul 26, 2016 at 3:34 PM, Sajith Ravindra  wrote:
>
>> @Mahesika, could you please release it.
>>
>> Thanks
>> *,Sajith Ravindra*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 2273550
>> blog: http://sajithr.blogspot.com/
>> 
>>
>> On Tue, Jul 26, 2016 at 3:30 PM, Manoj Kumara  wrote:
>>
>>> Merged the PR.
>>>
>>> Regards,
>>> Manoj
>>>
>>> *Manoj Kumara*
>>> WSO2 Inc. *| **lean. enterprise. middleware.*
>>> *Mobile:* +94 713 448188
>>>
>>> On Tue, Jul 26, 2016 at 2:28 PM, Sajith Ravindra 
>>> wrote:
>>>
 H Manoj,

 Did the changes. Please check.

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

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

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

> 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
>>
>>
>

>>>
>>
>
>
> --
>
> Thanks & Best Regards,
>
> Maheshika Goonetilleke
> Senior Engineering Process Coordinator
>
> *WSO2 Inc*
> *email   : mahesh...@wso2.com *
> *mobile : +94 773 596707 <%2B94%20773%20596707>*
> *www: :http://wso2.com *lean . enterprise . middleware
>
>
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error with Secured/Encrypted VFS Transport Credentials on ESB500Beta2

2016-07-26 Thread Rajith Vitharana

Hi Chaminda,

On Tue, Jul 26, 2016 at 12:35 PM, Chaminda Jayawardena 
wrote:

> Hi Rajith,
>
> This is worked when I used a keystore with 1024 keysize. I will verify
> with 2048 bit keystore with the next release.
>
> I noticed following warning in the logs while server startup even though
> the param exists.
>
> *[2016-07-26 12:22:12,199]  WARN - PollTableEntry transport.vfs.FileURI
> parameter is missing in the proxy service configuration*
>
As I remember this happens when trying to initialize transports in
axis2.xml, which means this won't happen for proxy services(even if you
don't have any vfs proxy, this will get printed if you enable vfs transport
from axis2.xml)

>
> And when I put *" name="security.provider">BC" *param in axis2.xml, getting
> below exception[1] while server startup. Better to fix these two.
>
> And following information mentioned in the jira should be corrected.
> When we use ciphertool for encryption, it is not needed to put
> *security.provider*  parameter either in axis2.xml or in the proxy
> service.
>
I think this is expected behavior because if you won't use BC to encrypt
username:password part then you can't use BC for decryption. Because you
can't decrypt passwords with BC which are encrypted without BC.

Thanks,

>
> *[1]*
> *[2016-07-26 12:22:15,166] ERROR - VFSTransportListener Unexpected error
> when configuring service StockQuoteProxy for the VFS transport. It will be
> disabled for this transport and marked as faulty.*
> *java.lang.IllegalArgumentException: Illegal group reference*
> * at java.util.regex.Matcher.appendReplacement(Matcher.java:857)*
> * at java.util.regex.Matcher.replaceFirst(Matcher.java:1004)*
> * at
> org.apache.synapse.transport.vfs.PollTableEntry.decryptIfRequired(PollTableEntry.java:701)*
> * at
> org.apache.synapse.transport.vfs.PollTableEntry.loadConfiguration(PollTableEntry.java:414)*
> * at
> org.apache.axis2.transport.base.AbstractTransportListenerEx.startListeningForService(AbstractTransportListenerEx.java:153)*
> * at
> org.apache.axis2.transport.base.AbstractTransportListener.internalStartListeningForService(AbstractTransportListener.java:213)*
> * at
> org.apache.axis2.transport.base.AbstractTransportListener$2.serviceAdded(AbstractTransportListener.java:126)*
> * at
> org.apache.axis2.transport.base.tracker.AxisServiceTracker.serviceAdded(AxisServiceTracker.java:212)*
> * at
> org.apache.axis2.transport.base.tracker.AxisServiceTracker.start(AxisServiceTracker.java:188)*
> * at
> org.apache.axis2.transport.base.AbstractTransportListener.start(AbstractTransportListener.java:178)*
> * at
> org.apache.axis2.transport.base.AbstractTransportListenerEx.start(AbstractTransportListenerEx.java:83)*
> * at
> org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:168)*
> * at
> org.apache.axis2.engine.ListenerManager.startSystem(ListenerManager.java:186)*
> * at
> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:165)*
> * 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
> 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.throttling.agent.internal.ThrottlingAgentServiceComponent.registerThrottlingAgent(ThrottlingAgentServiceComponent.java:123)*
> * at
> org.wso2.carbon.throttling.agent.internal.ThrottlingAgentServiceComponent.activate(ThrottlingAgentServiceComponent.java:100)*
> * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
> * at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
> * at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
> * at java.lang.reflect.Method.invoke(Method.java:483)*
> * at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)*
> * at
> org.eclipse.e

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

2016-07-26 Thread Mahesh Dananjaya

Hi Nirmal,
I am in the middle of trying some options to connect samoa with cep for
prediction. There are couple of options.Since there are lack of
documentation and lack of support from the samoa dev email list, Thing is
that i have to go through all the project to implement even a small
topology on my own. I am implementing samoa example topologies for our
exact goal. But i think this is something large in scope. I am in the
middle of converting cep siddhi event streams into some samoa streams and
convert result samoa streams back to cep streams. I am writing couple of
examples for that. Sorry for not updating by email, But i have putting my
examples into my gsoc repository [1]. I will push latest changes to couple
of modules. I was discussing wit the Maheshakaya to arrange meeting with
team next thursday or friday.Please let me know a convenient day. looking
forward to some of the advices from you there. This integration can be
done, but it will take some time for that, because i have to go through all
samoa things.
 ANyway i could connect samoa output streams with the custom stream outside
it [2]. Connecting the custom streams to samoa streams is challenging. I
have couple of options that can be used without exploiting samoa
architecture. I will discuss with you guys when i will be meeting you.
Anyway i think i have already implemented our intial goal with spark. will
try to finish Samoa thing as soon as i can.thank you.
regards,
Mahesh.

P.s: If anyone having knowledge on WEKA or MOA streams and instance, it
will be very helpful.because what i am doing now is converting cep events
into samoa Instance and feed it to the stream.
[1]
https://github.com/dananjayamahesh/GSOC2016/tree/master/gsoc/samoa/streaming
[2]
https://github.com/dananjayamahesh/GSOC2016/tree/master/gsoc/samoa/streaming/src/main/java/org/gsoc/samoa/streaming

On Tue, Jul 26, 2016 at 10:25 AM, Nirmal Fernando  wrote:

> 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

[Dev] WSO2 Dockerfiles 1.2.0 Released !

2016-07-26 Thread Anuruddha Liyanarachchi

WSO2 PaaS team is pleased to announce the release of *WSO2 Dockerfiles
1.2.0*


WSO2 Dockerfiles 1.2.0 is the successor of 1.1.0.

*The main changes for this release:*

   -

   Created a WSO2 base image with the common packages installed.
   -

   Validated the profile and platform before building the Docker image.
   -

   Added a SVN Docker image.
   -

   Changed all ENTRYPOINTs in all Dockerfiles to use the exec form.
   -

   Added a script to push the Docker images to a specified registry.
   -

   Added the wso2cep init extension scripts.
   -

   Included the net-tools package into the wso2base image.
   -

   Added debug support for WSO2 servers.
   -

   Replaced localMemberPort with dynamic proxy port for the Mesos platform.
   -

   Added the platform name as a postfix to the Docker image name.
   -

   Introduced artifacts folder
   -

   Append host node IP to symlink path to create a unique path across a
   cluster in Mesos platform 


*Release artifacts:*

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

*Documentation:*

https://docs.wso2.com/display/DF120/WSO2+Dockerfiles+Documentation


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

*Known Issues:*

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

-- 

Regards,
WSO2 PaaS team
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

2016-07-26 Thread Thanuja Jayasinghe

Hi Rasika,

This issue happens when 'carbon-security-caas' module does not activate
properly. Can you debug the code [1], and check whether activate method is
getting called.

[1] -
https://github.com/wso2/carbon-security/blob/master/components/org.wso2.carbon.security.caas/src/main/java/org/wso2/carbon/security/caas/internal/CarbonSecurityComponent.java#L80

Thanks,

On Mon, Jul 25, 2016 at 7:09 PM, Rasika Perera  wrote:

> 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
>



-- 
*Thanuja Lakmal*
Senior Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94715979891 +94758009992
___
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

2016-07-26 Thread Maheshakya Wijewardena

Hi Nirmal,

Please refer to thread "GSOC2016: [ML][CEP] [SAMOA]Predictive analytic with
online data for WSO2 Machine Learner-Samoa Integration".

Best regards.

On Tue, Jul 26, 2016 at 5:05 PM, Mahesh Dananjaya  wrote:

> Hi Nirmal,
> I am in the middle of trying some options to connect samoa with cep for
> prediction. There are couple of options.Since there are lack of
> documentation and lack of support from the samoa dev email list, Thing is
> that i have to go through all the project to implement even a small
> topology on my own. I am implementing samoa example topologies for our
> exact goal. But i think this is something large in scope. I am in the
> middle of converting cep siddhi event streams into some samoa streams and
> convert result samoa streams back to cep streams. I am writing couple of
> examples for that. Sorry for not updating by email, But i have putting my
> examples into my gsoc repository [1]. I will push latest changes to couple
> of modules. I was discussing wit the Maheshakaya to arrange meeting with
> team next thursday or friday.Please let me know a convenient day. looking
> forward to some of the advices from you there. This integration can be
> done, but it will take some time for that, because i have to go through all
> samoa things.
>  ANyway i could connect samoa output streams with the custom stream
> outside it [2]. Connecting the custom streams to samoa streams is
> challenging. I have couple of options that can be used without exploiting
> samoa architecture. I will discuss with you guys when i will be meeting
> you. Anyway i think i have already implemented our intial goal with spark.
> will try to finish Samoa thing as soon as i can.thank you.
> regards,
> Mahesh.
>
> P.s: If anyone having knowledge on WEKA or MOA streams and instance, it
> will be very helpful.because what i am doing now is converting cep events
> into samoa Instance and feed it to the stream.
> [1]
> https://github.com/dananjayamahesh/GSOC2016/tree/master/gsoc/samoa/streaming
> [2]
> https://github.com/dananjayamahesh/GSOC2016/tree/master/gsoc/samoa/streaming/src/main/java/org/gsoc/samoa/streaming
>
> On Tue, Jul 26, 2016 at 10:25 AM, Nirmal Fernando  wrote:
>
>> 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 W

Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0

2016-07-26 Thread Viraj Rajaguru

Hi Kavith,

Sent a pull request[1].

Thanks,
Viraj.

[1] - https://github.com/wso2/devstudio-tooling-platform/pull/1

On Tue, Jul 26, 2016 at 2:17 PM, Kavith Lokuhewage  wrote:

> Hi Viraj,
>
> Please send the PR with the fix to master branch. We will release the
> update for 4.1.0.
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Fri, Jul 22, 2016 at 3:47 PM, Viraj Rajaguru  wrote:
>
>>
>> -- Forwarded message --
>> From: Viraj Rajaguru 
>> Date: Fri, Jul 22, 2016 at 3:46 PM
>> Subject: Releasing an update for DevS kernel 4.1.0
>> To: Jasintha Dasanayake , Kavith Lokuhewage <
>> kav...@wso2.com>, Susinda Perera , Sohani Weerasinghe <
>> soh...@wso2.com>, Nuwan Pallewela , Chanaka Fernando <
>> chana...@wso2.com>, Jagath Sisirakumara Ariyarathne 
>>
>>
>> Hi DevS kernel team,
>>
>> We faced an issue while deploying CAR files when webContextRoot is
>> enabled in carbon.xml. See the public Jira[1]. This needs to be fixed in
>> "devstudio-tooling-platform". Can we have this fix as an update for Kernel
>> 4.1.0 since this is a blocker for ESB tolling release. Fix is attached to
>> the jira.
>>
>> BTW, is there any 4.1.0 update branch so that we can send pull requests?
>>
>> Thanks,
>> Viraj.
>>
>> [1] - https://wso2.org/jira/browse/DEVTOOLESB-637
>> --
>> Viraj Rajaguru
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>>
>>
>> --
>> Viraj Rajaguru
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0

2016-07-26 Thread Viraj Rajaguru

Thanks Kavith !

On Tue, Jul 26, 2016 at 8:08 PM, Kavith Lokuhewage  wrote:

> Hi Viraj,
>
> I will prepare platform update and let you know once it is published.
>
> Thanks,
>
> On 26 Jul 2016 8:02 p.m., "Viraj Rajaguru"  wrote:
>
>> Hi Kavith,
>>
>> Sent a pull request[1].
>>
>> Thanks,
>> Viraj.
>>
>> [1] - https://github.com/wso2/devstudio-tooling-platform/pull/1
>>
>> On Tue, Jul 26, 2016 at 2:17 PM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi Viraj,
>>>
>>> Please send the PR with the fix to master branch. We will release the
>>> update for 4.1.0.
>>>
>>> Thanks,
>>>
>>> *Kavith Lokuhewage*
>>> Senior Software Engineer
>>> WSO2 Inc. - http://wso2.com
>>> lean . enterprise . middleware
>>> Mobile - +94779145123
>>> Linkedin 
>>> Twitter 
>>>
>>> On Fri, Jul 22, 2016 at 3:47 PM, Viraj Rajaguru  wrote:
>>>

 -- Forwarded message --
 From: Viraj Rajaguru 
 Date: Fri, Jul 22, 2016 at 3:46 PM
 Subject: Releasing an update for DevS kernel 4.1.0
 To: Jasintha Dasanayake , Kavith Lokuhewage <
 kav...@wso2.com>, Susinda Perera , Sohani
 Weerasinghe , Nuwan Pallewela ,
 Chanaka Fernando , Jagath Sisirakumara Ariyarathne <
 jaga...@wso2.com>


 Hi DevS kernel team,

 We faced an issue while deploying CAR files when webContextRoot is
 enabled in carbon.xml. See the public Jira[1]. This needs to be fixed in
 "devstudio-tooling-platform". Can we have this fix as an update for Kernel
 4.1.0 since this is a blocker for ESB tolling release. Fix is attached to
 the jira.

 BTW, is there any 4.1.0 update branch so that we can send pull requests?

 Thanks,
 Viraj.

 [1] - https://wso2.org/jira/browse/DEVTOOLESB-637
 --
 Viraj Rajaguru
 Associate Technical Lead
 WSO2 Inc. : http://wso2.com

 Mobile: +94 77 3683068






 --
 Viraj Rajaguru
 Associate Technical Lead
 WSO2 Inc. : http://wso2.com

 Mobile: +94 77 3683068




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


>>>
>>
>>
>> --
>> Viraj Rajaguru
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>


-- 
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0

2016-07-26 Thread Kavith Lokuhewage

Hi Viraj,

I will prepare platform update and let you know once it is published.

Thanks,

On 26 Jul 2016 8:02 p.m., "Viraj Rajaguru"  wrote:

> Hi Kavith,
>
> Sent a pull request[1].
>
> Thanks,
> Viraj.
>
> [1] - https://github.com/wso2/devstudio-tooling-platform/pull/1
>
> On Tue, Jul 26, 2016 at 2:17 PM, Kavith Lokuhewage 
> wrote:
>
>> Hi Viraj,
>>
>> Please send the PR with the fix to master branch. We will release the
>> update for 4.1.0.
>>
>> Thanks,
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +94779145123
>> Linkedin 
>> Twitter 
>>
>> On Fri, Jul 22, 2016 at 3:47 PM, Viraj Rajaguru  wrote:
>>
>>>
>>> -- Forwarded message --
>>> From: Viraj Rajaguru 
>>> Date: Fri, Jul 22, 2016 at 3:46 PM
>>> Subject: Releasing an update for DevS kernel 4.1.0
>>> To: Jasintha Dasanayake , Kavith Lokuhewage <
>>> kav...@wso2.com>, Susinda Perera , Sohani Weerasinghe
>>> , Nuwan Pallewela , Chanaka Fernando <
>>> chana...@wso2.com>, Jagath Sisirakumara Ariyarathne 
>>>
>>>
>>> Hi DevS kernel team,
>>>
>>> We faced an issue while deploying CAR files when webContextRoot is
>>> enabled in carbon.xml. See the public Jira[1]. This needs to be fixed in
>>> "devstudio-tooling-platform". Can we have this fix as an update for Kernel
>>> 4.1.0 since this is a blocker for ESB tolling release. Fix is attached to
>>> the jira.
>>>
>>> BTW, is there any 4.1.0 update branch so that we can send pull requests?
>>>
>>> Thanks,
>>> Viraj.
>>>
>>> [1] - https://wso2.org/jira/browse/DEVTOOLESB-637
>>> --
>>> Viraj Rajaguru
>>> Associate Technical Lead
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile: +94 77 3683068
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Viraj Rajaguru
>>> Associate Technical Lead
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile: +94 77 3683068
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Viraj Rajaguru
> Associate Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

2016-07-26 Thread Rasika Perera

Hi Thanuja,

This issue got resolved by updating version into 1.0.0-m2. Now I am
getting BundleContext is null exception.

java.lang.IllegalStateException: BundleContext is null.
> at
> org.wso2.carbon.security.caas.internal.CarbonSecurityDataHolder.getBundleContext(CarbonSecurityDataHolder.java:125)
> at
> org.wso2.carbon.security.caas.api.util.CarbonSecurityUtils.getCallbackHandlers(CarbonSecurityUtils.java:39)
> at
> org.wso2.carbon.security.caas.api.ProxyCallbackHandler.handle(ProxyCallbackHandler.java:65)
> at
> javax.security.auth.login.LoginContext$SecureCallbackHandler$1.run(LoginContext.java:939)
> at
> javax.security.auth.login.LoginContext$SecureCallbackHandler$1.run(LoginContext.java:936)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> javax.security.auth.login.LoginContext$SecureCallbackHandler.handle(LoginContext.java:936)
> at
> org.wso2.carbon.security.caas.api.module.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:103)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at javax.security.auth.login.LoginContext.invoke(LoginContext.java:755)
> 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.authenticateByCaas(SimpleAuthHandler.java:60)


When debugging found that CarbonSecurityComponent's @Activate method[1] is
not invoked by OSGi. Then checked bundles on osgi console,  both fragment
and bundle is Active.

   79|Active|4|org.wso2.carbon.security.caas (1.0.0.m2)
>80|Resolved   |1|org.wso2.carbon.security.caas.boot (1.0.0.m2)


Any thoughts on resolving this issue?

[1]
https://github.com/wso2/carbon-security/blob/release-1.0.0-m2/components/org.wso2.carbon.security.caas/src/main/java/org/wso2/carbon/security/caas/internal/CarbonSecurityComponent.java#L80

On Tue, Jul 26, 2016 at 6:18 PM, Thanuja Jayasinghe 
wrote:

> Hi Rasika,
>
> This issue happens when 'carbon-security-caas' module does not activate
> properly. Can you debug the code [1], and check whether activate method is
> getting called.
>
> [1] -
> https://github.com/wso2/carbon-security/blob/master/components/org.wso2.carbon.security.caas/src/main/java/org/wso2/carbon/security/caas/internal/CarbonSecurityComponent.java#L80
>
> Thanks,
>
> On Mon, Jul 25, 2016 at 7:09 PM, Rasika Perera  wrote:
>
>> 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?
>>
>>

[Dev] [VOTE] Release WSO2 Mesos Artifacts 1.0.0 RC1

2016-07-26 Thread Pubudu Gunatilaka

Hi Devs,

This is the first release candidate (RC1) of WSO2 Mesos Artifacts 1.0.0.

Please download, test and vote. Please refer the README files under each
product for details on testing the artifacts.

Source & binary distribution files:
https://github.com/wso2/mesos-artifacts/releases/tag/v1.0.0-rc1

Maven staging repo:
https://maven.wso2.org/nexus/content/repositories/orgwso2carbonmesosartifacts-1000/

The tag to be voted upon:
https://github.com/wso2/mesos-artifacts/releases/tag/v1.0.0-rc1

Mesos Artifacts Documentation:
https://docs.wso2.com/display/MA100/Home

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

[+] Stable - go ahead and release
[-] Broken - do not release (explain why)


Regards,
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] [GSOC 16] Initial Project Progress

2016-07-26 Thread Osura Rathnayake

Hi All,

Following are the meeting notes of the hangout we had on 25th of July, 2016.

*Centralized logging*

Azure Log Analytics provides centralized logging which facilitates the
users to get logs from a given location in a VM, to a centralized location
so that they can analyse and query those logs as they need.
*next task - Documentation in terms of a blog post or webinar

*Auto scaling*

Auto scaling is achieved through scale sets in Azure. Scale set is a set of
VMs and auto scaling rules that defines auto scale metrics & actions and
the specification of the VMs.

*Limitations - Azure portal doesn't support addition of auto scale rules,
it only allows to add a simple scale set with a given number of instances.
Whereas azure CLI, Powershell and REST API supports full functionality.

I have added the template to the github repo which I used to create the
auto scale settings which includes the ability to add a custom VM image and
auto scale rules. When you deploy from this template you should give the
URI of the VM image. you can edit auto scale rules using CLI, Power shell
or REST API. Azure Resource Explorer  can be
used if you choose REST API to modify.

*next tasks - 1) Have to figure out a way to pass application and user data
such as usernames and passwords of database, to the VM image through the
template. 2) Documentaion

*Load balancing*

Following are some key terms you need to know.

· Backend pool: This is a pool of virtual machines that share the
traffic

· Probe: The load balancer can probe the health of the various
server instances. When a probe fails to respond, the load balancer stops
sending new connections to the unhealthy instances. Existing connections
are not impacted.

· Availability set: when you have a set of virtual machines for the
same purpose, azure recommends to add them to an availability set.

We can add load balancing rules such that requests coming from a given URL
 are shared among the VMs in backend pool. if we configure the load
balancer with auto scaling, VMs in the scale set can be added to the
backend pool so if the auto scale rules are met, it can scale in or out.

*next tasks - 1)  research more about Probe and service health checking. 2)
 documentation 3) How to automate the whole deployment process.

[1] https://github.com/osuran/Azure-templates

Thank you,

On Mon, Jul 25, 2016 at 11:46 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Thank you. That will solve the issue.
>
> On Mon, Jul 25, 2016 at 11:44 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> If you need any customizations/configurations done at the VM startup, you
>> can use /etc/rc.local script to do it. Also, if you define the JAVA_HOME in
>> a system wide bashrc file at /etc/bash.bashrc it won't get deleted when the
>> user home is removed.
>>
>>
>> On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> You can only capture a generalized VM image, so when it's being
>>> generalized, all of the data in '/home' is erased. Since .bashrc is also in
>>> '/home/', it's also erased. Only the data that are not
>>> in '/home' is preserved.
>>>
>>> Okay I will try out these steps.
>>>
>>> Thanks,
>>>
>>> On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne 
>>> wrote:
>>>
 Hi Osura,

 On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> I could successfully configure auto scaling with a VM which has a WSO2
> application server installed in it. When capturing a VM, it first get
> deallocated and then generalized.
>

 I'm sorry I did not get this. Can you please elaborate this further?

> So the Java home set in .bashrc is gone in the captured image of the
> VM. So I had to reset the Java home and also I had to manually start the
> server after the startup of the VM.
>

 I think you are trying to create a VM image from a running VM
 instance and try to reuse that. Can you please try following:

1. Create a VM instance from Ubuntu 14.04 VM image
2. Extract JDK 1.7 (JAVA_HOME) and the WSO2 server distribution
(CARBON_HOME) to /opt/ directory.
3. Write a brash script (init.sh) to start the WSO2 server by
invoking CARBON_HOME/bin/wso2server.sh
4. Update /etc/rc.local to invoke the above bash script; init.sh
5. Create a VM image of this VM instance.

 Thanks

 Is there any method developed in WSO2 to overcome this situation?
>
> thanks,
>
> On Thu, Jul 21, 2016 at 5:10 PM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> That time is fine by me.
>>
>> thanks,
>>
>> On Thu, Jul 21, 2016 at 3:44 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Men

[Dev] [Jaggerry][BPS] Check user permission using jaggery user.User not working for tenants

2016-07-26 Thread Milinda Perera

Hi,

We are checking the user permission in jaggery in following way:

function isUserAuthorized(username, permission, action, bpsUrl){
var carbon = require('carbon'),
process = require('process'),
srv = new carbon.server.Server({url: bpsUrl}),
tenantId = carbon.server.tenantId(),
userManager = new carbon.user.UserManager(srv, tenantId),
user = new carbon.user.User(userManager, username);
return user.isAuthorized(permission, action);
}

it works perfectly fine for super tenant but get false for tenant users
even they have relevant permission.

Thanks,
Milinda

-- 
Milinda Perera
Software Engineer;
WSO2 Inc. http://wso2.com ,
Mobile: (+94) 714 115 032
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error with Secured/Encrypted VFS Transport Credentials on ESB500Beta2

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

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

Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0

Re: [Dev] Please vote for WSO2 Developer Studio Kernel 4.2.0 RC2

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

[Dev] [ML] Making the server port configurable in the ML samples

Re: [Dev] Please vote for WSO2 Developer Studio Kernel 4.2.0 RC2

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

Re: [Dev] [ML] Making the server port configurable in the ML samples

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

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

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

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

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

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

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

Re: [Dev] Error with Secured/Encrypted VFS Transport Credentials on ESB500Beta2

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

[Dev] WSO2 Dockerfiles 1.2.0 Released !

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

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

Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0

Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0

Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0

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

[Dev] [VOTE] Release WSO2 Mesos Artifacts 1.0.0 RC1

Re: [Dev] [GSOC 16] Initial Project Progress

[Dev] [Jaggerry][BPS] Check user permission using jaggery user.User not working for tenants

29 matches

Site Navigation

Mail list logo

Footer information