Re: [Dev] Enabling security with user name token

2015-10-14 Thread Rajith Vitharana
Hi Hasintha,

We are using carbon-identity 4.5.6

@Firzan we are using [1] as the policy file which contains the element you
mentioned above.

[1] -
http://svn.wso2.org/repos/wso2/people/isuruu/qos/synapse-configs/default/local-entries/p1.xml

Thanks,

On Wed, Oct 14, 2015 at 5:12 PM, Hasintha Indrajee 
wrote:

> Can you please tell me the carbon-identity version you are using ?
>
> On Wed, Oct 14, 2015 at 3:04 PM, Rajith Vitharana 
> wrote:
>
>> + Asela
>>
>> On Wed, Oct 14, 2015 at 1:13 PM, Rajith Vitharana 
>> wrote:
>>
>>> Hi,
>>>
>>> I have enabled security in DSS service specifying the policy file (roles
>>> included in the policy). But when invoking the service with username
>>> password, it throws below exception.
>>>
>>> java.lang.ClassCastException: org.apache.axiom.om.impl.dom.ElementImpl
>>> cannot be cast to org.apache.axiom.soap.SOAPHeaderBlock
>>> at
>>> org.wso2.carbon.security.pox.POXSecurityHandler.isSOAPWithoutSecHeader(POXSecurityHandler.java:362)
>>> at
>>> org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:102)
>>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>> at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:515)
>>> at
>>> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:433)
>>> at
>>> org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:398)
>>> at
>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:188)
>>> at
>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>> at
>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at
>>> org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSRFPreventionFilter.java:88)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at
>>> org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRLFPreventionFilter.java:59)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at
>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at
>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>>> at
>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>>> at
>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
>>> at
>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
>>> at
>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>> at
>>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
>>> at
>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
>>> at
>>> 

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 4

2015-10-14 Thread Kavith Lokuhewage
Hi Devs,

Thank you for testing and verifying the WSO2 Developer Studio 3.8.0 RC4. We
are closing this vote now. This vote has passed with 5 +1s and 0 -1s.
Therefore we are proceeding with the WSO2 Developer Studio 3.8.0 release.

5 +1s
0  -1s

Thank you and Regards,
WSO2 Developer Studio team

On Wed, Oct 14, 2015 at 9:25 AM, Kavith Lokuhewage  wrote:

> Hi Devs,
>
> Please vote for the fourth release candidate of WSO2 Developer Studio
> 3.8.0.
>
> This release fixes following issues.
> https://wso2.org/jira/issues/?filter=12453
>
> Please download, test and vote. Vote will be open for 72 hours or as
> needed.
>
> Sources, binary distribution and pre-installed eclipse distributions:
> http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC4/
>
> The tag to be voted upon:
> https://github.com/wso2/developer-studio/tree/v3.8.0-RC4
>
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (explain why)
>
> Thanks and Regards,
> DevStudio Team
>
> --
> *Kavith Lokuhewage*
> Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +9477-9-145-123 | +9471-455-6-401
> Linkedin 
> Twitter 
>



-- 
*Kavith Lokuhewage*
Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +9477-9-145-123 | +9471-455-6-401
Linkedin   Twitter

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


[Dev] Null pointer exception from api gateway component when logging as the tenant-admin

2015-10-14 Thread Harshan Liyanage
Hi all,

I'm getting the below exception when logging as the tenant-admin (latest
EMM build). We are using org.wso2.carbon.apimgt.gateway.feature.group
version 4.3.0-SNAPSHOT at the moment.

Could please someone from APIM team can shed a light on this issue?

[2015-10-14 23:00:18,924] hars...@wso2.com [1] [MDM] WARN
{org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Could not
create
/home/harshan/development/cdm/wso2mdm-2.0.0-SNAPSHOT/repository/tenants/1/synapse-configs/default/sequences
[2015-10-14 23:00:18,925] hars...@wso2.com [1] [MDM]ERROR
{org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Error
while reading API manager specific synapse
sequencesjava.io.FileNotFoundException: File
'/home/harshan/development/cdm/wso2mdm-2.0.0-SNAPSHOT/repository/resources/apim-synapse-config/_auth_failure_handler_.xml'
does not exist
[2015-10-14 23:00:18,927] hars...@wso2.com [1] [MDM]ERROR
{org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Couldn't
serialise the initial synapse configuration for the domain : wso2.com
java.lang.NullPointerException
at
org.apache.synapse.config.xml.MultiXMLConfigurationSerializer.serializeSequence(MultiXMLConfigurationSerializer.java:470)
at
org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator.createTenantSynapseConfigHierarchy(TenantServiceCreator.java:234)
at
org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator.createdConfigurationContext(TenantServiceCreator.java:141)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:357)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:148)
at
org.wso2.carbon.core.services.util.CarbonAuthenticationUtil.onSuccessAdminLogin(CarbonAuthenticationUtil.java:134)
at
org.wso2.carbon.core.services.authentication.AuthenticationAdmin.login(AuthenticationAdmin.java:117)
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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
at
org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient.login(AuthenticationAdminClient.java:64)
at
org.wso2.carbon.ui.DefaultCarbonAuthenticator.doAuthentication(DefaultCarbonAuthenticator.java:119)
at
org.wso2.carbon.ui.AbstractCarbonUIAuthenticator.handleSecurity(AbstractCarbonUIAuthenticator.java:218)
at
org.wso2.carbon.ui.BasicAuthUIAuthenticator.authenticate(BasicAuthUIAuthenticator.java:83)
at
org.wso2.carbon.ui.CarbonUILoginUtil.handleLogin(CarbonUILoginUtil.java:377)
at
org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecuredHttpContext.java:244)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:60)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at

Re: [Dev] [Integration test] testng.xml Reading Error (java.lang.reflect.InvocationTargetException)

2015-10-14 Thread Nuwan Wimalasekara
Hi Rajjaz,

Please check the testng.xml file whether it is in valid format.

Thanks,
Nuwanw

On Wed, Oct 14, 2015 at 12:21 PM, Rajjaz Mohammed  wrote:

> Hi Dev,
> I'm writing a simple integration test [1] but while running the test i'm
> getting the following error[2]. and i attached my pom also. can anyone
> guide on me on this?
>
> [1] https://docs.wso2.com/display/TA430/Writing+a+Test+Case+for+ESB
>
> [2]
> ---
>  T E S T S
> ---
> Forking command line: /bin/sh -c cd
> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target &&
> /home/rajjaz/Documents/jdk1.7.0_79/jre/bin/java -Xms512m -Xmx1024m
> -XX:MaxPermSize=128m -jar
> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefirebooter7361817641598581788.jar
> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefire8778537678578881741tmp
> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefire_06295743703835172308tmp
> org.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: org.apache.maven.surefire.testset.TestSetFailedException: Suite
> file /src/test/resources/testng.xml is not a valid file
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:124)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:89)
> ... 9 more
>
> Results :
>
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 9.685 s
> [INFO] Finished at: 2015-10-14T12:17:26+05:30
> [INFO] Final Memory: 94M/668M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test)
> on project org.wso2.carbon.connector.ejb2X: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The
> forked VM terminated without saying properly goodbye. VM crash or
> System.exit called ? -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test
> (default-test) on project org.wso2.carbon.connector.ejb2X: Execution
> default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The
> forked VM terminated without saying properly goodbye. VM crash or
> System.exit called ?
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 

Re: [Dev] [Integration test] testng.xml Reading Error (java.lang.reflect.InvocationTargetException)

2015-10-14 Thread Nuwan Wimalasekara
Hi Rajjaz,

In your pom file, testng.xml file path is wrong. So surefire can not locate
the testng.xml file defined. Please define relative path to solve this
issue.

/src/test/resources/testng.xml

Above should be corrected as bellow.

*src/test/resources/testng.xml*

Thanks,
Nuwanw

On Wed, Oct 14, 2015 at 12:21 PM, Rajjaz Mohammed  wrote:

> Hi Dev,
> I'm writing a simple integration test [1] but while running the test i'm
> getting the following error[2]. and i attached my pom also. can anyone
> guide on me on this?
>
> [1] https://docs.wso2.com/display/TA430/Writing+a+Test+Case+for+ESB
>
> [2]
> ---
>  T E S T S
> ---
> Forking command line: /bin/sh -c cd
> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target &&
> /home/rajjaz/Documents/jdk1.7.0_79/jre/bin/java -Xms512m -Xmx1024m
> -XX:MaxPermSize=128m -jar
> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefirebooter7361817641598581788.jar
> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefire8778537678578881741tmp
> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefire_06295743703835172308tmp
> org.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: org.apache.maven.surefire.testset.TestSetFailedException: Suite
> file /src/test/resources/testng.xml is not a valid file
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:124)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:89)
> ... 9 more
>
> Results :
>
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 9.685 s
> [INFO] Finished at: 2015-10-14T12:17:26+05:30
> [INFO] Final Memory: 94M/668M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test)
> on project org.wso2.carbon.connector.ejb2X: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The
> forked VM terminated without saying properly goodbye. VM crash or
> System.exit called ? -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test
> (default-test) on project org.wso2.carbon.connector.ejb2X: Execution
> default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The
> forked VM terminated without saying properly goodbye. VM crash or
> System.exit called ?
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
> at 

[Dev] [Integration test] testng.xml Reading Error (java.lang.reflect.InvocationTargetException)

2015-10-14 Thread Rajjaz Mohammed
Hi Dev,
I'm writing a simple integration test [1] but while running the test i'm
getting the following error[2]. and i attached my pom also. can anyone
guide on me on this?

[1] https://docs.wso2.com/display/TA430/Writing+a+Test+Case+for+ESB

[2]
---
 T E S T S
---
Forking command line: /bin/sh -c cd
/home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target &&
/home/rajjaz/Documents/jdk1.7.0_79/jre/bin/java -Xms512m -Xmx1024m
-XX:MaxPermSize=128m -jar
/home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefirebooter7361817641598581788.jar
/home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefire8778537678578881741tmp
/home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefire_06295743703835172308tmp
org.apache.maven.surefire.util.SurefireReflectionException:
java.lang.reflect.InvocationTargetException; nested exception is
java.lang.reflect.InvocationTargetException: null
java.lang.reflect.InvocationTargetException
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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: org.apache.maven.surefire.testset.TestSetFailedException: Suite
file /src/test/resources/testng.xml is not a valid file
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:124)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:89)
... 9 more

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 9.685 s
[INFO] Finished at: 2015-10-14T12:17:26+05:30
[INFO] Final Memory: 94M/668M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test)
on project org.wso2.carbon.connector.ejb2X: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The
forked VM terminated without saying properly goodbye. VM crash or
System.exit called ? -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test
(default-test) on project org.wso2.carbon.connector.ejb2X: Execution
default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The
forked VM terminated without saying properly goodbye. VM crash or
System.exit called ?
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
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:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at

Re: [Dev] [DEV] [IS] [user store] Login failed for user from secondary store when same ldap used for R/W & Read only

2015-10-14 Thread Maduranga Siriwardena
Hi Kavitha,

Have you assigned login permission to the user?

Thanks,
Maduranga.

On Wed, Oct 14, 2015 at 10:09 AM, Kavitha Subramaniyam 
wrote:

> Hi IS team,
>
> I have configured both R/W and Read only LDAP secondary user store manager
> by using same ldap connection and I could not be able to login via user
> created under RW ldap user store. But note that I could view the same user
> under both secondary store's domain (Users & Roles -> List -> select each
> domain and search).
>
> I want to check with you whether the above behavior is expected or not,
> please clarify..
>
> Steps followed:
> - Configure R/W secondary user store - ReadWriteLDAPUserStoreManager -
> using open ldap connectoin 1
> - Configure Read only secondary user store - ReadOnlyLDAPUserStoreManager
> - using open ldap connectoin 1
> - Create a user1 under R/W ldap domain
> - Login by user1
>
> When try to login without domain, log shows as below:
>
> 
> [2015-10-13 16:32:55,232] DEBUG
> {org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager} -  SELECT * FROM
> UM_USER WHERE UM_USER_NAME=? AND UM_TENANT_ID=?
> [2015-10-13 16:32:55,241] DEBUG
> {org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager} -  User userkavirw3
> login attempt. Login success :: false
> [2015-10-13 16:32:55,241] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
>  Authenticating user userkavirw3
> [2015-10-13 16:32:55,241] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
> Using DN uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
> [2015-10-13 16:32:55,252] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
> uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
> authnticated: true
> [2015-10-13 16:32:55,253] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
>  Authorization cache hit. roldap.com/userkavirw3 user is not Authorized
> to perform ui.execute on /permission/admin/login
> [2015-10-13 16:32:55,253]  WARN
> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
> Administrator login attempt 'ROLDAP.COM/userkavirw3[-1234]
> ' at [2015-10-13
> 16:32:55,253+0530]
>
>
> When try to login with domain, log shows as below:
> ---
> [2015-10-13 16:33:14,424] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
>  Authenticating user userkavirw3
> [2015-10-13 16:33:14,425] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
> Using DN uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
> [2015-10-13 16:33:14,458] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
> uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
> authnticated: true
> [2015-10-13 16:33:14,463] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
>  Authorization cache hit. rwldap.com/userkavirw3 user is not Authorized
> to perform ui.execute on /permission/admin/login
> [2015-10-13 16:33:14,463]  WARN
> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
> Administrator login attempt 'RWLDAP.COM/userkavirw3[-1234]
> ' at [2015-10-13
> 16:33:14,463+0530]
>
>
> Thanks & Kind regards,
> --
> Kavitha.S
> *Software Engineer -QA*
> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
> kavi...@wso2.com 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Maduranga Siriwardena
Software Engineer
WSO2 Inc.

email: madura...@wso2.com
mobile: +94718990591
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Can not find defineStream method in Siddhi 3.0.0M1

2015-10-14 Thread Lasantha Fernando
Hi,

You can read more about the syntax and annotations from the SiddhiQL guide.
For stream syntax, please refer to [1]. You can drop the
@config(async='true') annotation in Siddhi-3.0.0 since that is the default
mode and the only mode of processing currently.

[1]
https://docs.wso2.com/display/CEP400/SiddhiQL+Guide+3.0#SiddhiQLGuide3.0-EventStreamDefinition

Thanks,

On 14 October 2015 at 12:00, Lakini Senanayaka  wrote:

> Hi,
>
> I have read the link Lasantha gave me.[1]
>
> Is there any format of writing EventStreams and queries as strings when
> passing them to the createExecutionPlanRuntime method ?
>
> Example:-
> String cseEventStream = "@config(async = 'true') define stream
> cseEventStream (symbol string, price float, volume long);";
>
> I couldn't understand the annotations used to write them.Could you please
> give me a reference to read about them.
>
> [1]
> https://github.com/wso2/siddhi/blob/master/modules/siddhi-core/src/test/java/org/wso2/siddhi/core/query/FilterTestCase.java
>
> Thank you.
>
> On Wed, Oct 14, 2015 at 11:17 AM, Lakini Senanayaka 
> wrote:
>
>> Thank you Lasantha.
>> I'll refer the link which you gave me.
>>
>> On Wed, Oct 14, 2015 at 11:07 AM, Lasantha Fernando 
>> wrote:
>>
>>> Hi Lakini,
>>>
>>> Better use a released version of Siddhi instead of the milestone
>>> version. Siddhi-3.0.0-M1 would have very little of the actual features
>>> implemented since this is the first milestone for the rewrite of Siddhi.
>>> Siddhi-3.0.2 is already released and you can use that version instead.
>>>
>>> Also from Siddhi-3.0.0 onwards, separate methods like defineStream,
>>> defineTable were removed from the API and there is a single API method
>>> createExecutionPlanRuntime() to which you can pass in the complete query,
>>> along with stream definitions, table definitions etc. This was done so that
>>> the user can simply pass in the execution plan just as you would write the
>>> query in CEP, without the API user having to know about different methods
>>> to define different constructs of the language.
>>>
>>> You can refer to the test cases in [1] or any other test case to get a
>>> better idea on how to use the Siddhi library API.
>>>
>>> [1]
>>> https://github.com/wso2/siddhi/blob/master/modules/siddhi-core/src/test/java/org/wso2/siddhi/core/query/FilterTestCase.java
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 14 October 2015 at 10:49, Lakini Senanayaka  wrote:
>>>
 Hi,

  I have used SiddhiQueryapi  3.0.0M1 and SiddhiCore 3.0.0M1 in my
 android project.Now I can create siddhimanager instances.But I don't get
 defineStream,addQuery methods.Instead of that I get defineFunction.But in
 the siddhi user guide there are examples with defineStream method.Could you
 please explain me why is that and guide me how to continue the task.
 PS:I'm using siddhi queries in android.

 Thank you.
 --
 *Intern-Engineering*
 Lakini S.Senanayaka
 Mobile: +94 712295444
 Email: lak...@wso2.com

>>>
>>>
>>>
>>> --
>>> *Lasantha Fernando*
>>> Senior Software Engineer - Data Technologies Team
>>> WSO2 Inc. http://wso2.com
>>>
>>> email: lasan...@wso2.com
>>> mobile: (+94) 71 5247551
>>>
>>
>>
>>
>> --
>> *Intern-Engineering*
>> Lakini S.Senanayaka
>> Mobile: +94 712295444
>> Email: lak...@wso2.com
>>
>
>
>
> --
> *Intern-Engineering*
> Lakini S.Senanayaka
> Mobile: +94 712295444
> Email: lak...@wso2.com
>



-- 
*Lasantha Fernando*
Senior Software Engineer - Data Technologies Team
WSO2 Inc. http://wso2.com

email: lasan...@wso2.com
mobile: (+94) 71 5247551
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Integration test] testng.xml Reading Error (java.lang.reflect.InvocationTargetException)

2015-10-14 Thread Rajjaz Mohammed
Hi this is my testng.xml file

http://testng.org/testng-1.0.dtd; >




















On Wed, Oct 14, 2015 at 12:24 PM, Nuwan Wimalasekara 
wrote:

> Hi Rajjaz,
>
> Please check the testng.xml file whether it is in valid format.
>
> Thanks,
> Nuwanw
>
> On Wed, Oct 14, 2015 at 12:21 PM, Rajjaz Mohammed  wrote:
>
>> Hi Dev,
>> I'm writing a simple integration test [1] but while running the test i'm
>> getting the following error[2]. and i attached my pom also. can anyone
>> guide on me on this?
>>
>> [1] https://docs.wso2.com/display/TA430/Writing+a+Test+Case+for+ESB
>>
>> [2]
>> ---
>>  T E S T S
>> ---
>> Forking command line: /bin/sh -c cd
>> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target &&
>> /home/rajjaz/Documents/jdk1.7.0_79/jre/bin/java -Xms512m -Xmx1024m
>> -XX:MaxPermSize=128m -jar
>> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefirebooter7361817641598581788.jar
>> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefire8778537678578881741tmp
>> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefire_06295743703835172308tmp
>> org.apache.maven.surefire.util.SurefireReflectionException:
>> java.lang.reflect.InvocationTargetException; nested exception is
>> java.lang.reflect.InvocationTargetException: null
>> java.lang.reflect.InvocationTargetException
>> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>> at
>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>> at
>> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
>> Caused by: org.apache.maven.surefire.testset.TestSetFailedException:
>> Suite file /src/test/resources/testng.xml is not a valid file
>> at
>> org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:124)
>> at
>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:89)
>> ... 9 more
>>
>> Results :
>>
>> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>>
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 9.685 s
>> [INFO] Finished at: 2015-10-14T12:17:26+05:30
>> [INFO] Final Memory: 94M/668M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test)
>> on project org.wso2.carbon.connector.ejb2X: Execution default-test of goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The
>> forked VM terminated without saying properly goodbye. VM crash or
>> System.exit called ? -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test
>> (default-test) on project org.wso2.carbon.connector.ejb2X: Execution
>> default-test of goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The
>> forked VM terminated without saying properly goodbye. VM crash or
>> System.exit called ?
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>> 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:116)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>> at
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>   

Re: [Dev] Clarifications on command in DAS analytic migration tool

2015-10-14 Thread Inosh Goonewardena
Hi Nayomi,


On Wed, Oct 14, 2015 at 11:07 AM, Nayomi Dayarathne  wrote:

> Hi DAS team,
>
> I need below clarifications regarding the command that we used to
> migrate data from BAM to DAS using analytic migration tool.
>
>  I used below command to migrate data from a table in BAM to DAS
>
> ./analytics-migrate.sh -serverUrl  -cassandra_Url
>  -serverPort  -columnFamily
>  -analyticTable  -batchSize
> 1000  -tenantId   -1234   -username 
> -password  -cassandraPort 
> -clusterName 
>
> 1. Are there any optional and mandatory parameters in the command ?
>
> Because when we remove  and  parameters and
> run the command, it still migrate data from BAM to DAS.
>

Server URL and server port(CQL port) are no longer needed for migration. So
we can actually remove those properties completely from the command.


>
> 2. If we are migrating data from multiple tables from BAM to DAS, how
> do we define it in the command ?
>

Migrating data from multiple tables is not supported at the moment.

>
>
> Regards,
>
> Nayomi Dayarathne
> Software Engineer-QA
> Mobile : +94 (0) 775246619
> nay...@wso2.com
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
Thanks & Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [DEV] [IS] [user store] Login failed for user from secondary store when same ldap used for R/W & Read only

2015-10-14 Thread Kavitha Subramaniyam
Hi Maduranga,

Yes, I have created a role with admin permission in R/W user store and
assigned to relevant user (here role name: rolekavirw ; user name:
userkavirw2). check the debug log[1]

[1]

[2015-10-14 12:33:08,494] DEBUG
{org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager} -  SELECT * FROM
UM_USER WHERE UM_USER_NAME=? AND UM_TENANT_ID=?
[2015-10-14 12:33:08,501] DEBUG
{org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager} -  User userkavirw2
login attempt. Login success :: false
[2015-10-14 12:33:08,501] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
 Authenticating user userkavirw2
[2015-10-14 12:33:08,501] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Replace
escape characters configured to: true
[2015-10-14 12:33:08,514] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Searching
for user with SearchFilter: (&(objectClass=person)(uid=userkavirw2)) in
SearchBase:
[2015-10-14 12:33:08,514] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Replace
escape characters configured to: true
[2015-10-14 12:33:12,270] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Name in
space for userkavirw2 is
uid=userkavirw2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
[2015-10-14 12:33:12,271] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
 Authenticating with
uid=userkavirw2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
[2015-10-14 12:33:12,302] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
uid=userkavirw2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
authnticated: true
[2015-10-14 12:33:12,303] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 Authorization cache miss for username : roldap.com/userkavirw2 resource
/permission/admin/login action : ui.execute
[2015-10-14 12:33:12,303] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 Allowed roles for the ResourceID: /permission/admin/login Action:
ui.execute
[2015-10-14 12:33:12,304] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
apach.com/role_kavi
[2015-10-14 12:33:12,304] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
admin
[2015-10-14 12:33:12,304] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
rw2/rolekavirw3
[2015-10-14 12:33:12,304] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
rwldap.com/chalitharole
[2015-10-14 12:33:12,304] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
rwldap.com/rolekavirw
[2015-10-14 12:33:12,304] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
secondrole1
[2015-10-14 12:33:12,304] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Roles
which have permission for resource : /permission/admin/login action :
ui.execute
[2015-10-14 12:33:12,305] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  apach.com/role_kavi
[2015-10-14 12:33:12,305] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  admin
[2015-10-14 12:33:12,305] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  rw2/rolekavirw3
[2015-10-14 12:33:12,305] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  rwldap.com/chalitharole
[2015-10-14 12:33:12,305] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  rwldap.com/rolekavirw
[2015-10-14 12:33:12,305] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  secondrole1
[2015-10-14 12:33:12,306] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
ROLDAP.COM/userkavirw2 user is not in role :  apach.com/role_kavi
[2015-10-14 12:33:12,306] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
ROLDAP.COM/userkavirw2 user is not in role :  admin
[2015-10-14 12:33:12,307] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
ROLDAP.COM/userkavirw2 user is not in role :  rw2/rolekavirw3
[2015-10-14 12:33:12,307] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
ROLDAP.COM/userkavirw2 user is not in role :  rwldap.com/chalitharole
[2015-10-14 12:33:12,307] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
ROLDAP.COM/userkavirw2 user is not in role :  rwldap.com/rolekavirw
[2015-10-14 12:33:12,308] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
ROLDAP.COM/userkavirw2 user is not in role :  secondrole1
[2015-10-14 12:33:12,308] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
roldap.com/userkavirw2 user is not Authorized to perform ui.execute on
/permission/admin/login
[2015-10-14 12:33:12,308]  WARN

Re: [Dev] Can not find defineStream method in Siddhi 3.0.0M1

2015-10-14 Thread Lakini Senanayaka
Hi,

I have read the link Lasantha gave me.[1]

Is there any format of writing EventStreams and queries as strings when
passing them to the createExecutionPlanRuntime method ?

Example:-
String cseEventStream = "@config(async = 'true') define stream
cseEventStream (symbol string, price float, volume long);";

I couldn't understand the annotations used to write them.Could you please
give me a reference to read about them.

[1]
https://github.com/wso2/siddhi/blob/master/modules/siddhi-core/src/test/java/org/wso2/siddhi/core/query/FilterTestCase.java

Thank you.

On Wed, Oct 14, 2015 at 11:17 AM, Lakini Senanayaka  wrote:

> Thank you Lasantha.
> I'll refer the link which you gave me.
>
> On Wed, Oct 14, 2015 at 11:07 AM, Lasantha Fernando 
> wrote:
>
>> Hi Lakini,
>>
>> Better use a released version of Siddhi instead of the milestone version.
>> Siddhi-3.0.0-M1 would have very little of the actual features implemented
>> since this is the first milestone for the rewrite of Siddhi. Siddhi-3.0.2
>> is already released and you can use that version instead.
>>
>> Also from Siddhi-3.0.0 onwards, separate methods like defineStream,
>> defineTable were removed from the API and there is a single API method
>> createExecutionPlanRuntime() to which you can pass in the complete query,
>> along with stream definitions, table definitions etc. This was done so that
>> the user can simply pass in the execution plan just as you would write the
>> query in CEP, without the API user having to know about different methods
>> to define different constructs of the language.
>>
>> You can refer to the test cases in [1] or any other test case to get a
>> better idea on how to use the Siddhi library API.
>>
>> [1]
>> https://github.com/wso2/siddhi/blob/master/modules/siddhi-core/src/test/java/org/wso2/siddhi/core/query/FilterTestCase.java
>>
>> Thanks,
>> Lasantha
>>
>> On 14 October 2015 at 10:49, Lakini Senanayaka  wrote:
>>
>>> Hi,
>>>
>>>  I have used SiddhiQueryapi  3.0.0M1 and SiddhiCore 3.0.0M1 in my
>>> android project.Now I can create siddhimanager instances.But I don't get
>>> defineStream,addQuery methods.Instead of that I get defineFunction.But in
>>> the siddhi user guide there are examples with defineStream method.Could you
>>> please explain me why is that and guide me how to continue the task.
>>> PS:I'm using siddhi queries in android.
>>>
>>> Thank you.
>>> --
>>> *Intern-Engineering*
>>> Lakini S.Senanayaka
>>> Mobile: +94 712295444
>>> Email: lak...@wso2.com
>>>
>>
>>
>>
>> --
>> *Lasantha Fernando*
>> Senior Software Engineer - Data Technologies Team
>> WSO2 Inc. http://wso2.com
>>
>> email: lasan...@wso2.com
>> mobile: (+94) 71 5247551
>>
>
>
>
> --
> *Intern-Engineering*
> Lakini S.Senanayaka
> Mobile: +94 712295444
> Email: lak...@wso2.com
>



-- 
*Intern-Engineering*
Lakini S.Senanayaka
Mobile: +94 712295444
Email: lak...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [DEV] [IS] [user store] Login failed for user from secondary store when same ldap used for R/W & Read only

2015-10-14 Thread Darshana Gunawardana
On Wednesday, 14 October 2015, Maduranga Siriwardena 
wrote:

> Hi Kavitha,
>
> Have you assigned login permission to the user?
>

As Maduranga mentioned, user "http://rwldap.com/userkavirw3; doesn't seems
to have given login permission caused this behavior.

Thanks,

>
> Thanks,
> Maduranga.
>
> On Wed, Oct 14, 2015 at 10:09 AM, Kavitha Subramaniyam  > wrote:
>
>> Hi IS team,
>>
>> I have configured both R/W and Read only LDAP secondary user store
>> manager by using same ldap connection and I could not be able to login via
>> user created under RW ldap user store. But note that I could view the same
>> user under both secondary store's domain (Users & Roles -> List -> select
>> each domain and search).
>>
>> I want to check with you whether the above behavior is expected or not,
>> please clarify..
>>
>> Steps followed:
>> - Configure R/W secondary user store - ReadWriteLDAPUserStoreManager -
>> using open ldap connectoin 1
>> - Configure Read only secondary user store - ReadOnlyLDAPUserStoreManager
>> - using open ldap connectoin 1
>> - Create a user1 under R/W ldap domain
>> - Login by user1
>>
>> When try to login without domain, log shows as below:
>>
>> 
>> [2015-10-13 16:32:55,232] DEBUG
>> {org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager} -  SELECT * FROM
>> UM_USER WHERE UM_USER_NAME=? AND UM_TENANT_ID=?
>> [2015-10-13 16:32:55,241] DEBUG
>> {org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager} -  User userkavirw3
>> login attempt. Login success :: false
>> [2015-10-13 16:32:55,241] DEBUG
>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
>>  Authenticating user userkavirw3
>> [2015-10-13 16:32:55,241] DEBUG
>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
>> Using DN uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
>> [2015-10-13 16:32:55,252] DEBUG
>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
>> uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
>> authnticated: true
>> [2015-10-13 16:32:55,253] DEBUG
>> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
>>  Authorization cache hit. roldap.com/userkavirw3 user is not Authorized
>> to perform ui.execute on /permission/admin/login
>> [2015-10-13 16:32:55,253]  WARN
>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
>> Administrator login attempt 'ROLDAP.COM/userkavirw3[-1234]
>> ' at [2015-10-13
>> 16:32:55,253+0530]
>>
>>
>> When try to login with domain, log shows as below:
>>
>> ---
>> [2015-10-13 16:33:14,424] DEBUG
>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
>>  Authenticating user userkavirw3
>> [2015-10-13 16:33:14,425] DEBUG
>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
>> Using DN uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
>> [2015-10-13 16:33:14,458] DEBUG
>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
>> uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
>> authnticated: true
>> [2015-10-13 16:33:14,463] DEBUG
>> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
>>  Authorization cache hit. rwldap.com/userkavirw3 user is not Authorized
>> to perform ui.execute on /permission/admin/login
>> [2015-10-13 16:33:14,463]  WARN
>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
>> Administrator login attempt 'RWLDAP.COM/userkavirw3[-1234]
>> ' at [2015-10-13
>> 16:33:14,463+0530]
>>
>>
>> Thanks & Kind regards,
>> --
>> Kavitha.S
>> *Software Engineer -QA*
>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>> kavi...@wso2.com 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org 
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Maduranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
> email: madura...@wso2.com
> 
> mobile: +94718990591
>


-- 
Regards,


*Darshana Gunawardana*Senior Software Engineer
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Hazelcast Issue - sequence is too small. the current head sequence...

2015-10-14 Thread Sasikala Kottegoda
Hi Hasitha,

Yeah, the default  TopicOverloadPolicy is BLOCK.

Thank you

On Wed, Oct 14, 2015 at 1:06 PM, Hasitha Amal De Silva 
wrote:

> Hi Sasikala,
>
> 2. In case the producing node is attempting an over-write on the buffer,
> hold it until the buffer is processed. (flow control for subscriptions..)
>
> This is provided by default configurations of Hazelcast 'RealiableTopic'
> as per [1]
>
> So the default TopicOverloadPolicy is BLOCK in an overwrite scenario ? if
> not that would be the ideal setting IMO.
>
> Thanks
>
> On Wed, Oct 14, 2015 at 9:53 AM, Sasikala Kottegoda 
> wrote:
>
>> Hi Hasitha,
>>
>> Please find the comments in line for the ways of handling the issue.
>>
>> 1. Come to a default balance between the buffer size (currently 1000) and
>> the TTL value for each item in buffer (seconds) / make this configurable.
>>
>> I don't think there is an impact of the ring buffer size on the
>> expiration of items. Increasing the TTL seems the only solution. But we did
>> not increase this since we needed to avoid the possibility of getting old
>> notifications in the case of a network failure or a crashed node. Making
>> the TTL configurable seems like a good solution.
>>
>> 2. In case the producing node is attempting an over-write on the buffer,
>> hold it until the buffer is processed. (flow control for subscriptions..)
>>
>> This is provided by default configurations of Hazelcast 'RealiableTopic'
>> as per [1]
>>
>> [1]
>> http://docs.hazelcast.org/docs/latest-dev/manual/html/reliabletopic.html#reliable-topic-configuration
>>
>> Thank you
>>
>> On Tue, Oct 13, 2015 at 8:07 PM, Hasitha Amal De Silva > > wrote:
>>
>>> increasing the Time-to-Live value [1] from 1 second to about 30 seconds
>>> got rid of this issue for my scenario. This exception can only occur if the
>>> item is expired or had been rewritten within the buffer as per [2].
>>>
>>> 2 ways to properly handle this as I can think :
>>>
>>> 1. Come to a default balance between the buffer size (currently 1000)
>>> and the TTL value for each item in buffer (seconds) / make this
>>> configurable.
>>> 2. In case the producing node is attempting an over-write on the buffer,
>>> hold it until the buffer is processed. (flow control for subscriptions..)
>>>
>>> For me, the issue was reproduced by creating about 400 durable JMS topic
>>> subscriptions with a ramp time of about 2 seconds from Jmeter.
>>>
>>> [1] : http://blog.hazelcast.com/ringbuffer-data-structure/
>>> [2] :
>>> http://docs.hazelcast.org/docs/3.5/javadoc/com/hazelcast/ringbuffer/StaleSequenceException.html
>>>
>>>
>>>
>>> On Tue, Oct 6, 2015 at 4:47 PM, Hasitha Hiranya 
>>> wrote:
>>>
 Hi Peter,

 We are using Hazelcast in our Message Broker project. We are getting
 following exception when using a iTopic for syncing data.

 Appreciate any idea why this happen? Are we doing something wrong in
 our client application?

 We found code [1] throwing the exception.

 Oct 06, 2015 4:26:44 PM
 com.hazelcast.ringbuffer.impl.operations.ReadManyOperation
 SEVERE: [192.168.1.50]:4000 [wso2.mb.domain] [3.5] sequence:8 is too
 small. The current headSequence is:9
 com.hazelcast.ringbuffer.StaleSequenceException: sequence:8 is too
 small. The current headSequence is:9
 at
 com.hazelcast.ringbuffer.impl.RingbufferContainer.checkBlockableReadSequence(RingbufferContainer.java:176)
 at
 com.hazelcast.ringbuffer.impl.operations.ReadManyOperation.beforeRun(ReadManyOperation.java:55)
 at
 com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:131)
 at
 com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processOperation(OperationThread.java:154)
 at
 com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.process(OperationThread.java:110)
 at
 com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.doRun(OperationThread.java:101)
 at
 com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.run(OperationThread.java:76)


 [1].
 https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/ringbuffer/impl/RingbufferContainer.java

 Thanks

 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* 


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


>>>
>>>
>>> --
>>> Cheers,
>>>
>>> Hasitha Amal De Silva
>>> Software Engineer
>>> Mobile : 0772037426
>>> Blog: http://devnutshell.tumblr.com/
>>> WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )
>>>
>>
>>
>>
>> --
>> Sasikala Kottegoda
>> *Software Engineer*
>> WSO2 Inc., 

Re: [Dev] Enabling security with user name token

2015-10-14 Thread Rajith Vitharana
+ Asela

On Wed, Oct 14, 2015 at 1:13 PM, Rajith Vitharana  wrote:

> Hi,
>
> I have enabled security in DSS service specifying the policy file (roles
> included in the policy). But when invoking the service with username
> password, it throws below exception.
>
> java.lang.ClassCastException: org.apache.axiom.om.impl.dom.ElementImpl
> cannot be cast to org.apache.axiom.soap.SOAPHeaderBlock
> at
> org.wso2.carbon.security.pox.POXSecurityHandler.isSOAPWithoutSecHeader(POXSecurityHandler.java:362)
> at
> org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:102)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
> at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:515)
> at
> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:433)
> at
> org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:398)
> at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:188)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSRFPreventionFilter.java:88)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRLFPreventionFilter.java:59)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
> at
> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
> at
> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
> at
> 

Re: [Dev] [DEV] [IS] [user store] Login failed for user from secondary store when same ldap used for R/W & Read only

2015-10-14 Thread Darshana Gunawardana
There seems to issue with domain handling as per following log,

DEBUG {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
ROLDAP.COM/userkavirw2  user is not in role
:  rwldap.com/rolekavirw


Please raise a JIRA.

Thanks,
Darshana

On Wednesday, 14 October 2015, Darshana Gunawardana 
wrote:

>
>
> On Wednesday, 14 October 2015, Maduranga Siriwardena  > wrote:
>
>> Hi Kavitha,
>>
>> Have you assigned login permission to the user?
>>
>
> As Maduranga mentioned, user "http://rwldap.com/userkavirw3; doesn't
> seems to have given login permission caused this behavior.
>
> Thanks,
>
>>
>> Thanks,
>> Maduranga.
>>
>> On Wed, Oct 14, 2015 at 10:09 AM, Kavitha Subramaniyam 
>> wrote:
>>
>>> Hi IS team,
>>>
>>> I have configured both R/W and Read only LDAP secondary user store
>>> manager by using same ldap connection and I could not be able to login via
>>> user created under RW ldap user store. But note that I could view the same
>>> user under both secondary store's domain (Users & Roles -> List -> select
>>> each domain and search).
>>>
>>> I want to check with you whether the above behavior is expected or not,
>>> please clarify..
>>>
>>> Steps followed:
>>> - Configure R/W secondary user store - ReadWriteLDAPUserStoreManager -
>>> using open ldap connectoin 1
>>> - Configure Read only secondary user store -
>>> ReadOnlyLDAPUserStoreManager - using open ldap connectoin 1
>>> - Create a user1 under R/W ldap domain
>>> - Login by user1
>>>
>>> When try to login without domain, log shows as below:
>>>
>>> 
>>> [2015-10-13 16:32:55,232] DEBUG
>>> {org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager} -  SELECT * FROM
>>> UM_USER WHERE UM_USER_NAME=? AND UM_TENANT_ID=?
>>> [2015-10-13 16:32:55,241] DEBUG
>>> {org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager} -  User userkavirw3
>>> login attempt. Login success :: false
>>> [2015-10-13 16:32:55,241] DEBUG
>>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
>>>  Authenticating user userkavirw3
>>> [2015-10-13 16:32:55,241] DEBUG
>>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
>>> Using DN uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
>>> [2015-10-13 16:32:55,252] DEBUG
>>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
>>> uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
>>> authnticated: true
>>> [2015-10-13 16:32:55,253] DEBUG
>>> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
>>>  Authorization cache hit. roldap.com/userkavirw3 user is not Authorized
>>> to perform ui.execute on /permission/admin/login
>>> [2015-10-13 16:32:55,253]  WARN
>>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
>>> Administrator login attempt 'ROLDAP.COM/userkavirw3[-1234]
>>> ' at [2015-10-13
>>> 16:32:55,253+0530]
>>>
>>>
>>> When try to login with domain, log shows as below:
>>>
>>> ---
>>> [2015-10-13 16:33:14,424] DEBUG
>>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
>>>  Authenticating user userkavirw3
>>> [2015-10-13 16:33:14,425] DEBUG
>>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
>>> Using DN uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
>>> [2015-10-13 16:33:14,458] DEBUG
>>> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
>>> uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
>>> authnticated: true
>>> [2015-10-13 16:33:14,463] DEBUG
>>> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
>>>  Authorization cache hit. rwldap.com/userkavirw3 user is not Authorized
>>> to perform ui.execute on /permission/admin/login
>>> [2015-10-13 16:33:14,463]  WARN
>>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
>>> Administrator login attempt 'RWLDAP.COM/userkavirw3[-1234]
>>> ' at [2015-10-13
>>> 16:33:14,463+0530]
>>>
>>>
>>> Thanks & Kind regards,
>>> --
>>> Kavitha.S
>>> *Software Engineer -QA*
>>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>>> kavi...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Maduranga Siriwardena
>> Software Engineer
>> WSO2 Inc.
>>
>> email: madura...@wso2.com
>> mobile: +94718990591
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com
> *
> *Mobile: +94718566859*Lean . Enterprise . 

Re: [Dev] Hazelcast Issue - sequence is too small. the current head sequence...

2015-10-14 Thread Hasitha Amal De Silva
Hi Sasikala,

2. In case the producing node is attempting an over-write on the buffer,
hold it until the buffer is processed. (flow control for subscriptions..)

This is provided by default configurations of Hazelcast 'RealiableTopic' as
per [1]

So the default TopicOverloadPolicy is BLOCK in an overwrite scenario ? if
not that would be the ideal setting IMO.

Thanks

On Wed, Oct 14, 2015 at 9:53 AM, Sasikala Kottegoda 
wrote:

> Hi Hasitha,
>
> Please find the comments in line for the ways of handling the issue.
>
> 1. Come to a default balance between the buffer size (currently 1000) and
> the TTL value for each item in buffer (seconds) / make this configurable.
>
> I don't think there is an impact of the ring buffer size on the expiration
> of items. Increasing the TTL seems the only solution. But we did not
> increase this since we needed to avoid the possibility of getting old
> notifications in the case of a network failure or a crashed node. Making
> the TTL configurable seems like a good solution.
>
> 2. In case the producing node is attempting an over-write on the buffer,
> hold it until the buffer is processed. (flow control for subscriptions..)
>
> This is provided by default configurations of Hazelcast 'RealiableTopic'
> as per [1]
>
> [1]
> http://docs.hazelcast.org/docs/latest-dev/manual/html/reliabletopic.html#reliable-topic-configuration
>
> Thank you
>
> On Tue, Oct 13, 2015 at 8:07 PM, Hasitha Amal De Silva 
> wrote:
>
>> increasing the Time-to-Live value [1] from 1 second to about 30 seconds
>> got rid of this issue for my scenario. This exception can only occur if the
>> item is expired or had been rewritten within the buffer as per [2].
>>
>> 2 ways to properly handle this as I can think :
>>
>> 1. Come to a default balance between the buffer size (currently 1000) and
>> the TTL value for each item in buffer (seconds) / make this configurable.
>> 2. In case the producing node is attempting an over-write on the buffer,
>> hold it until the buffer is processed. (flow control for subscriptions..)
>>
>> For me, the issue was reproduced by creating about 400 durable JMS topic
>> subscriptions with a ramp time of about 2 seconds from Jmeter.
>>
>> [1] : http://blog.hazelcast.com/ringbuffer-data-structure/
>> [2] :
>> http://docs.hazelcast.org/docs/3.5/javadoc/com/hazelcast/ringbuffer/StaleSequenceException.html
>>
>>
>>
>> On Tue, Oct 6, 2015 at 4:47 PM, Hasitha Hiranya 
>> wrote:
>>
>>> Hi Peter,
>>>
>>> We are using Hazelcast in our Message Broker project. We are getting
>>> following exception when using a iTopic for syncing data.
>>>
>>> Appreciate any idea why this happen? Are we doing something wrong in our
>>> client application?
>>>
>>> We found code [1] throwing the exception.
>>>
>>> Oct 06, 2015 4:26:44 PM
>>> com.hazelcast.ringbuffer.impl.operations.ReadManyOperation
>>> SEVERE: [192.168.1.50]:4000 [wso2.mb.domain] [3.5] sequence:8 is too
>>> small. The current headSequence is:9
>>> com.hazelcast.ringbuffer.StaleSequenceException: sequence:8 is too
>>> small. The current headSequence is:9
>>> at
>>> com.hazelcast.ringbuffer.impl.RingbufferContainer.checkBlockableReadSequence(RingbufferContainer.java:176)
>>> at
>>> com.hazelcast.ringbuffer.impl.operations.ReadManyOperation.beforeRun(ReadManyOperation.java:55)
>>> at
>>> com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:131)
>>> at
>>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processOperation(OperationThread.java:154)
>>> at
>>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.process(OperationThread.java:110)
>>> at
>>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.doRun(OperationThread.java:101)
>>> at
>>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.run(OperationThread.java:76)
>>>
>>>
>>> [1].
>>> https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/ringbuffer/impl/RingbufferContainer.java
>>>
>>> Thanks
>>>
>>> --
>>> *Hasitha Abeykoon*
>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>> *cell:* *+94 719363063*
>>> *blog: **abeykoon.blogspot.com* 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Cheers,
>>
>> Hasitha Amal De Silva
>> Software Engineer
>> Mobile : 0772037426
>> Blog: http://devnutshell.tumblr.com/
>> WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )
>>
>
>
>
> --
> Sasikala Kottegoda
> *Software Engineer*
> WSO2 Inc., http://wso2.com/
> lean. enterprise. middleware
> Mobile: +94 774835928/712792401
>



-- 
Cheers,

Hasitha Amal De Silva
Software Engineer
Mobile : 0772037426
Blog: http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )
___
Dev 

[Dev] where we could find the source of synapse 2.1.2-wso2v8

2015-10-14 Thread Lakshman Udayakantha
Hi,

It is not in [1] and [2].

[1] https://github.com/wso2/wso2-synapse


[2]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/synapse/

is there any other place kept synapse other than above mentioned ones?

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


Re: [Dev] Checkstyle organize imports differently from intelliJ default configuration

2015-10-14 Thread Afkham Azeez
Change your IDEA settings. Checkstyle default organization is better.

On Wed, Oct 14, 2015 at 2:00 PM, Dinusha Boteju  wrote:

> Hi all,
>
> I have integrated checkstyle maven plugin in to the project I work on and
> fixing style issues reported. The checkstyle configuration is taken from
> [1] (The plugin configuration was taken from C5 codebase). However, the
> configuration to organize imports in [1] is different from that of
> intelliJ's default configuration.
>
> If we are to use configuration in [1], then we can configure intelliJ
> accordingly. Otherwise the configuration in [1] needs to be changed.
> Checkstyle configuration which matches the default organize import
> configuration of intelliJ is [2]. Thus I would like to know which one to
> use.
>
> [1] -
> https://raw.githubusercontent.com/wso2/code-quality-tools/master/checkstyle/checkstyle.xml
>
> [2] -
>  
>  
>  
>  
>  
>  
>  
>
> Thanks,
> --
> *Dinusha Boteju*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: dinus...@wso2.com 
> phone:(+94) 776640275 <%28%2B94%29%2039736>
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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


Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 4

2015-10-14 Thread Kavith Lokuhewage
Hi,

I have tested App Factory, API Manager tools and Connector import.
No blockers found.

+1 for the release.

Thanks,

On Wed, Oct 14, 2015 at 10:09 AM, Awanthika Senarath 
wrote:

> Hi
>
> I have tested the following features and bug fixes and the observations
> were positive, hence +1
>
>
>- ESB projects,
>- Registry Projects
>- Data Service Projects
>
>
>
>- Capp projects (creation, deploy, redeploy, removal)
>- Servers (remote/local)
>
>
>
>- Artifact renaming.
>
>
> Regards
> Awanthika
>
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Wed, Oct 14, 2015 at 9:25 AM, Kavith Lokuhewage 
> wrote:
>
>> Hi Devs,
>>
>> Please vote for the fourth release candidate of WSO2 Developer Studio
>> 3.8.0.
>>
>> This release fixes following issues.
>> https://wso2.org/jira/issues/?filter=12453
>>
>> Please download, test and vote. Vote will be open for 72 hours or as
>> needed.
>>
>> Sources, binary distribution and pre-installed eclipse distributions:
>> http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC4/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/developer-studio/tree/v3.8.0-RC4
>>
>>
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>> DevStudio Team
>>
>> --
>> *Kavith Lokuhewage*
>> Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +9477-9-145-123 | +9471-455-6-401
>> Linkedin 
>> Twitter 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
*Kavith Lokuhewage*
Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +9477-9-145-123 | +9471-455-6-401
Linkedin   Twitter

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


Re: [Dev] Can not find defineStream method in Siddhi 3.0.0M1

2015-10-14 Thread Lakini Senanayaka
Hi,

I have created an sample application using Siddhi-3.0.2 in android Studio.

This is my code.

package org.wso2.myapplication3;

import android.os.Bundle;
import android.support.v7.app.ActionBarActivity;
import android.util.Log;
import android.view.Menu;
import android.view.MenuItem;
import android.view.View;
import android.widget.EditText;
import org.wso2.siddhi.core.ExecutionPlanRuntime;
import org.wso2.siddhi.core.SiddhiManager;
import org.wso2.siddhi.core.event.Event;
import org.wso2.siddhi.core.query.output.callback.QueryCallback;
import org.wso2.siddhi.core.stream.input.InputHandler;
import org.wso2.siddhi.core.util.EventPrinter;

public class MainActivity extends ActionBarActivity {

SiddhiManager siddhiManager=new SiddhiManager();
ExecutionPlanRuntime executionPlanRuntime;

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);

//passing the rules to the siddhi

String cseEventStream = "@config(async = 'true') define stream
StockQuoteStream (value double);";
String query = "@info(name = 'query1') from
StockQuoteStream[value>20] insert into HighValueQuotes;";
executionPlanRuntime =
siddhiManager.createExecutionPlanRuntime(cseEventStream + query);
executionPlanRuntime.addCallback("query1", new QueryCallback() {
@Override
public void receive(long timeStamp, Event[] inEvents,
Event[] removeEvents) {
EventPrinter.print(timeStamp, inEvents, removeEvents);
Log.d("app3", "Received event!!");
}
});
}

@Override
public boolean onCreateOptionsMenu(Menu menu) {
// Inflate the menu; this adds items to the action bar if it is present.
getMenuInflater().inflate(R.menu.menu_main, menu);
return true;
}

@Override
public boolean onOptionsItemSelected(MenuItem item) {
// Handle action bar item clicks here. The action bar will
// automatically handle clicks on the Home/Up button, so long
// as you specify a parent activity in AndroidManifest.xml.
int id = item.getItemId();

//noinspection SimplifiableIfStatement
if (id == R.id.action_settings) {
return true;
}

return super.onOptionsItemSelected(item);
}

//passing data to the stream
public void onClick_Button (View v) throws InterruptedException {
EditText t = (EditText) findViewById(R.id.editText);
double value = Double.parseDouble(t.getText().toString());
Log.d("app3",String.valueOf(value));

//send events/data in to stream
InputHandler inputHandler =
executionPlanRuntime.getInputHandler("StockQuoteStream");
executionPlanRuntime.start();
inputHandler.send(new Object[]{value});
executionPlanRuntime.shutdown();
}
}


I have included the log file which I got when I run the app.

10-14 04:28:01.025  16126-16126/? D/dalvikvm﹕ Late-enabling CheckJNI
10-14 04:28:01.073  16126-16126/? I/dalvikvm﹕ Could not find method
org.wso2.siddhi.query.compiler.SiddhiCompiler.parse, referenced from method
org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime
10-14 04:28:01.073  16126-16126/? W/dalvikvm﹕ VFY: unable to resolve static
method 30602: Lorg/wso2/siddhi/query/compiler/SiddhiCompiler;.parse
(Ljava/lang/String;)Lorg/wso2/siddhi/query/api/ExecutionPlan;
10-14 04:28:01.073  16126-16126/? D/dalvikvm﹕ VFY: replacing opcode 0x71 at
0x
10-14 04:28:01.073  16126-16126/? I/dalvikvm﹕ Could not find method
org.wso2.siddhi.query.compiler.SiddhiCompiler.parse, referenced from method
org.wso2.siddhi.core.SiddhiManager.validateExecutionPlan
10-14 04:28:01.073  16126-16126/? W/dalvikvm﹕ VFY: unable to resolve static
method 30602: Lorg/wso2/siddhi/query/compiler/SiddhiCompiler;.parse
(Ljava/lang/String;)Lorg/wso2/siddhi/query/api/ExecutionPlan;
10-14 04:28:01.073  16126-16126/? D/dalvikvm﹕ VFY: replacing opcode 0x71 at
0x
10-14 04:28:01.101  16126-16132/? D/dalvikvm﹕ Debugger has detached; object
registry had 1 entries
10-14 04:28:01.145  16126-16129/? D/dalvikvm﹕ GC_CONCURRENT freed 221K, 3%
free 8960K/9212K, paused 1ms+0ms, total 10ms
10-14 04:28:01.213  16126-16129/? D/dalvikvm﹕ GC_CONCURRENT freed 255K, 4%
free 9091K/9376K, paused 2ms+1ms, total 9ms
10-14 04:28:01.297  16126-16129/? D/dalvikvm﹕ GC_CONCURRENT freed 378K, 5%
free 9100K/9508K, paused 3ms+1ms, total 10ms
10-14 04:28:01.381  16126-16129/? D/dalvikvm﹕ GC_CONCURRENT freed 390K, 5%
free 9096K/9516K, paused 2ms+1ms, total 6ms

This is my dependencies in the gradle file.
dependencies {

compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.android.support:appcompat-v7:22.2.1'
compile files('libs/antlr-runtime_3.2.0.wso2v1.jar')
compile files('libs/antlr_3.2.0.wso2v1.jar')
compile files('libs/stringtemplate-3.2.1.jar')
compile 

Re: [Dev] [DEV] [IS] [user store] Login failed for user from secondary store when same ldap used for R/W & Read only

2015-10-14 Thread Kavitha Subramaniyam
Hi Darshana,

please find the log for login with RW domain.

[2015-10-14 13:25:46,003] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
 Authenticating user userkavirw2
[2015-10-14 13:25:46,004] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
Using DN uid=userkavirw2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
[2015-10-14 13:25:46,009] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
uid=userkavirw2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
authnticated: true
[2015-10-14 13:25:46,009] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 Authorization cache miss for username : rwldap.com/userkavirw2 resource
/permission/admin/login action : ui.execute
[2015-10-14 13:25:46,009] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 Allowed roles for the ResourceID: /permission/admin/login Action:
ui.execute
[2015-10-14 13:25:46,009] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
apach.com/role_kavi
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
admin
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
rw2/rolekavirw3
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
rwldap.com/chalitharole
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
rwldap.com/rolekavirw
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
secondrole1
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Roles
which have permission for resource : /permission/admin/login action :
ui.execute
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  apach.com/role_kavi
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  admin
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  rw2/rolekavirw3
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  rwldap.com/chalitharole
[2015-10-14 13:25:46,010] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  rwldap.com/rolekavirw
[2015-10-14 13:25:46,011] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  secondrole1
[2015-10-14 13:25:46,011] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
RWLDAP.COM/userkavirw2 user is not in role :  apach.com/role_kavi
[2015-10-14 13:25:46,011] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
RWLDAP.COM/userkavirw2 user is not in role :  admin
[2015-10-14 13:25:46,012] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
RWLDAP.COM/userkavirw2 user is not in role :  rw2/rolekavirw3
[2015-10-14 13:25:46,012] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  value
after escaping special characters in userkavirw2 : userkavirw2
[2015-10-14 13:25:46,012] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Escaped DN
value for filter :
[2015-10-14 13:25:46,012] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Do check
whether the user : userkavirw2 is in role: chalitharole
[2015-10-14 13:25:46,013] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Search
filter : (&(objectClass=groupOfNames)(member=))
[2015-10-14 13:25:46,013] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Requesting
attribute: cn
[2015-10-14 13:25:46,018] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Do check
whether the user: userkavirw2 is in role: chalitharole
[2015-10-14 13:25:46,018] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Search
filter: (&(objectClass=groupOfNames)(member=))
[2015-10-14 13:25:46,018] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Requesting
attribute: cn
[2015-10-14 13:25:46,024] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
userkavirw2 NOT in role: chalitharole
[2015-10-14 13:25:46,024] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
RWLDAP.COM/userkavirw2 user is not in role :  rwldap.com/chalitharole
[2015-10-14 13:25:46,025] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  value
after escaping special characters in userkavirw2 : userkavirw2
[2015-10-14 13:25:46,025] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Escaped DN
value for filter :
[2015-10-14 13:25:46,025] DEBUG

Re: [Dev] [DEV] [IS] [user store] Login failed for user from secondary store when same ldap used for R/W & Read only

2015-10-14 Thread Darshana Gunawardana
User: userkavirw2 NOT in role: rolekavirw
[2015-10-14 13:25:46,039] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
RWLDAP.COM/userkavirw2  user is not in role
:  rwldap.com/rolekavirw

So even you added userkavirw2 user to rolekavirw role, it's not picking up
in the runtime.

Can you please check, role list of users in the mgt console and check
whether this particular role is listed to the user.

Thanks,

On Wednesday, 14 October 2015, Kavitha Subramaniyam 
wrote:

> Hi Darshana,
>
> please find the log for login with RW domain.
>
> [2015-10-14 13:25:46,003] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
>  Authenticating user userkavirw2
> [2015-10-14 13:25:46,004] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
> Using DN uid=userkavirw2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
> [2015-10-14 13:25:46,009] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
> uid=userkavirw2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
> authnticated: true
> [2015-10-14 13:25:46,009] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
>  Authorization cache miss for username : rwldap.com/userkavirw2 resource
> /permission/admin/login action : ui.execute
> [2015-10-14 13:25:46,009] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
>  Allowed roles for the ResourceID: /permission/admin/login Action:
> ui.execute
> [2015-10-14 13:25:46,009] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
> apach.com/role_kavi
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
> admin
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
> rw2/rolekavirw3
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
> rwldap.com/chalitharole
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
> rwldap.com/rolekavirw
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
> secondrole1
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Roles
> which have permission for resource : /permission/admin/login action :
> ui.execute
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
> :  apach.com/role_kavi
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
> :  admin
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
> :  rw2/rolekavirw3
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
> :  rwldap.com/chalitharole
> [2015-10-14 13:25:46,010] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
> :  rwldap.com/rolekavirw
> [2015-10-14 13:25:46,011] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
> :  secondrole1
> [2015-10-14 13:25:46,011] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
> RWLDAP.COM/userkavirw2 user is not in role :  apach.com/role_kavi
> [2015-10-14 13:25:46,011] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
> RWLDAP.COM/userkavirw2 user is not in role :  admin
> [2015-10-14 13:25:46,012] DEBUG
> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
> RWLDAP.COM/userkavirw2 user is not in role :  rw2/rolekavirw3
> [2015-10-14 13:25:46,012] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  value
> after escaping special characters in userkavirw2 : userkavirw2
> [2015-10-14 13:25:46,012] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Escaped DN
> value for filter :
> [2015-10-14 13:25:46,012] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Do check
> whether the user : userkavirw2 is in role: chalitharole
> [2015-10-14 13:25:46,013] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Search
> filter : (&(objectClass=groupOfNames)(member=))
> [2015-10-14 13:25:46,013] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Requesting
> attribute: cn
> [2015-10-14 13:25:46,018] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Do check
> whether the user: userkavirw2 is in role: chalitharole
> [2015-10-14 13:25:46,018] DEBUG
> {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Search
> filter: (&(objectClass=groupOfNames)(member=))
> [2015-10-14 13:25:46,018] DEBUG
> 

[Dev] Enabling security with user name token

2015-10-14 Thread Rajith Vitharana
Hi,

I have enabled security in DSS service specifying the policy file (roles
included in the policy). But when invoking the service with username
password, it throws below exception.

java.lang.ClassCastException: org.apache.axiom.om.impl.dom.ElementImpl
cannot be cast to org.apache.axiom.soap.SOAPHeaderBlock
at
org.wso2.carbon.security.pox.POXSecurityHandler.isSOAPWithoutSecHeader(POXSecurityHandler.java:362)
at
org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:102)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:515)
at
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:433)
at
org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:398)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:188)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSRFPreventionFilter.java:88)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRLFPreventionFilter.java:59)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:744)

Do we need to do anything 

[Dev] Checkstyle organize imports differently from intelliJ default configuration

2015-10-14 Thread Dinusha Boteju
Hi all,

I have integrated checkstyle maven plugin in to the project I work on and
fixing style issues reported. The checkstyle configuration is taken from
[1] (The plugin configuration was taken from C5 codebase). However, the
configuration to organize imports in [1] is different from that of
intelliJ's default configuration.

If we are to use configuration in [1], then we can configure intelliJ
accordingly. Otherwise the configuration in [1] needs to be changed.
Checkstyle configuration which matches the default organize import
configuration of intelliJ is [2]. Thus I would like to know which one to
use.

[1] -
https://raw.githubusercontent.com/wso2/code-quality-tools/master/checkstyle/checkstyle.xml

[2] -
 
 
 
 
 
 
 

Thanks,
-- 
*Dinusha Boteju*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: dinus...@wso2.com 
phone:(+94) 776640275 <%28%2B94%29%2039736>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 4

2015-10-14 Thread Susinda Perera
Hi All
I have tested following and no blocking issues found.

ESB, DSS, BPEL, CAPP project creation
ESB artifact creation
Importing connectors
Connector exporter project
All inbound endpoints
APIM perspective - commit/rename/checkout

Thanks
Susinda





On Wed, Oct 14, 2015 at 10:09 AM, Awanthika Senarath 
wrote:

> Hi
>
> I have tested the following features and bug fixes and the observations
> were positive, hence +1
>
>
>- ESB projects,
>- Registry Projects
>- Data Service Projects
>
>
>
>- Capp projects (creation, deploy, redeploy, removal)
>- Servers (remote/local)
>
>
>
>- Artifact renaming.
>
>
> Regards
> Awanthika
>
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Wed, Oct 14, 2015 at 9:25 AM, Kavith Lokuhewage 
> wrote:
>
>> Hi Devs,
>>
>> Please vote for the fourth release candidate of WSO2 Developer Studio
>> 3.8.0.
>>
>> This release fixes following issues.
>> https://wso2.org/jira/issues/?filter=12453
>>
>> Please download, test and vote. Vote will be open for 72 hours or as
>> needed.
>>
>> Sources, binary distribution and pre-installed eclipse distributions:
>> http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC4/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/developer-studio/tree/v3.8.0-RC4
>>
>>
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>> DevStudio Team
>>
>> --
>> *Kavith Lokuhewage*
>> Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +9477-9-145-123 | +9471-455-6-401
>> Linkedin 
>> Twitter 
>>
>> ___
>> 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
>
>


-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [DEV] [IS] [user store] Login failed for user from secondary store when same ldap used for R/W & Read only

2015-10-14 Thread Kavitha Subramaniyam
Hi Darshana/ Maduranga,

I have been checked this scenario in kernal rc2 pack
(wso2is-5.1.0-kernel-4.2.0-SNAPSHOT) and I could not reproduce the same as
it is. Now, user can login to console either with RW/read only domains[1]
or without domain.

So, can I assume that the user (login permission granted) from secondary
user store which same ldap used for R/W & Read only can have permission to
login?

[1]
RW domain
---
[2015-10-14 14:57:33,191] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
 Authenticating user testnew2
[2015-10-14 14:57:33,192] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
Using DN uid=testnew2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
[2015-10-14 14:57:33,203] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
uid=testnew2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
authnticated: true
[2015-10-14 14:57:33,205]  INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
 'RWLDAP.com/testnew2@carbon.super [-1234]' logged in at [2015-10-14
14:57:33,205+0530]
[2015-10-14 14:57:33,209] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 Authorization cache miss for username : RWLDAP.com/testnew2 resource
/permission action : ui.execute
[2015-10-14 14:57:33,209] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 Allowed roles for the ResourceID: /permission Action: ui.execute


read only domain
-
[2015-10-14 15:01:04,319] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
 Authenticating user testnew2
[2015-10-14 15:01:04,320] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
Using DN uid=testnew2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
[2015-10-14 15:01:04,327] DEBUG
{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
uid=testnew2,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
authnticated: true
[2015-10-14 15:01:04,328] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 Authorization cache miss for username : ROLDAP.com/testnew2 resource
/permission/admin/login action : ui.execute
[2015-10-14 15:01:04,328] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 Allowed roles for the ResourceID: /permission/admin/login Action:
ui.execute
[2015-10-14 15:01:04,329] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
INTERNAL/everyone
[2015-10-14 15:01:04,329] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
admin
[2015-10-14 15:01:04,329] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  role:
RWLDAP.COM/glassrole
[2015-10-14 15:01:04,329] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Roles
which have permission for resource : /permission/admin/login action :
ui.execute
[2015-10-14 15:01:04,329] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  INTERNAL/everyone
[2015-10-14 15:01:04,329] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  admin
[2015-10-14 15:01:04,329] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Role
:  RWLDAP.COM/glassrole
[2015-10-14 15:01:04,330] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 ROLDAP.com/testnew2 user is in role :  INTERNAL/everyone
[2015-10-14 15:01:04,332]  INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
 'ROLDAP.com/testnew2@carbon.super [-1234]' logged in at [2015-10-14
15:01:04,331+0530]
[2015-10-14 15:01:04,335] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 Authorization cache miss for username : ROLDAP.com/testnew2 resource
/permission action : ui.execute
[2015-10-14 15:01:04,336] DEBUG
{org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
 Allowed roles for the ResourceID: /permission Action: ui.execute


Thanks & Kind regards,



On Wed, Oct 14, 2015 at 2:10 PM, Kavitha Subramaniyam 
wrote:

> PFA for role list of user.
>
>
> Thanks,
> Kavitha.
>
> On Wed, Oct 14, 2015 at 1:50 PM, Darshana Gunawardana 
> wrote:
>
>> User: userkavirw2 NOT in role: rolekavirw
>> [2015-10-14 13:25:46,039] DEBUG
>> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
>> RWLDAP.COM/userkavirw2  user is not in
>> role :  rwldap.com/rolekavirw
>>
>> So even you added userkavirw2 user to rolekavirw role, it's not picking
>> up in the runtime.
>>
>> Can you please check, role list of users in the mgt console and check
>> whether this particular role is listed to the user.
>>
>> Thanks,
>>
>> On Wednesday, 14 October 2015, Kavitha Subramaniyam 
>> wrote:
>>
>>> Hi Darshana,
>>>
>>> please find the log for login with RW domain.
>>>
>>> 

Re: [Dev] [DEV] [IS] [user store] Login failed for user from secondary store when same ldap used for R/W & Read only

2015-10-14 Thread Darshana Gunawardana
And it seems you do not pr used the domain name when authenticating in the
last case. Can you login providing the domain of the RW userstore and share
the log.

On Wednesday, 14 October 2015, Darshana Gunawardana 
wrote:

> There seems to issue with domain handling as per following log,
>
> DEBUG {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
>  ROLDAP.COM/userkavirw2  user is not in
> role :  rwldap.com/rolekavirw
>
>
> Please raise a JIRA.
>
> Thanks,
> Darshana
>
> On Wednesday, 14 October 2015, Darshana Gunawardana  > wrote:
>
>>
>>
>> On Wednesday, 14 October 2015, Maduranga Siriwardena 
>> wrote:
>>
>>> Hi Kavitha,
>>>
>>> Have you assigned login permission to the user?
>>>
>>
>> As Maduranga mentioned, user "http://rwldap.com/userkavirw3; doesn't
>> seems to have given login permission caused this behavior.
>>
>> Thanks,
>>
>>>
>>> Thanks,
>>> Maduranga.
>>>
>>> On Wed, Oct 14, 2015 at 10:09 AM, Kavitha Subramaniyam >> > wrote:
>>>
 Hi IS team,

 I have configured both R/W and Read only LDAP secondary user store
 manager by using same ldap connection and I could not be able to login via
 user created under RW ldap user store. But note that I could view the same
 user under both secondary store's domain (Users & Roles -> List -> select
 each domain and search).

 I want to check with you whether the above behavior is expected or not,
 please clarify..

 Steps followed:
 - Configure R/W secondary user store - ReadWriteLDAPUserStoreManager -
 using open ldap connectoin 1
 - Configure Read only secondary user store -
 ReadOnlyLDAPUserStoreManager - using open ldap connectoin 1
 - Create a user1 under R/W ldap domain
 - Login by user1

 When try to login without domain, log shows as below:

 
 [2015-10-13 16:32:55,232] DEBUG
 {org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager} -  SELECT * FROM
 UM_USER WHERE UM_USER_NAME=? AND UM_TENANT_ID=?
 [2015-10-13 16:32:55,241] DEBUG
 {org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager} -  User userkavirw3
 login attempt. Login success :: false
 [2015-10-13 16:32:55,241] DEBUG
 {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
  Authenticating user userkavirw3
 [2015-10-13 16:32:55,241] DEBUG
 {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
 Using DN uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
 [2015-10-13 16:32:55,252] DEBUG
 {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
 uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
 authnticated: true
 [2015-10-13 16:32:55,253] DEBUG
 {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
  Authorization cache hit. roldap.com/userkavirw3 user is not
 Authorized to perform ui.execute on /permission/admin/login
 [2015-10-13 16:32:55,253]  WARN
 {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
 Administrator login attempt 'ROLDAP.COM/userkavirw3[-1234]
 ' at [2015-10-13
 16:32:55,253+0530]


 When try to login with domain, log shows as below:

 ---
 [2015-10-13 16:33:14,424] DEBUG
 {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -
  Authenticating user userkavirw3
 [2015-10-13 16:33:14,425] DEBUG
 {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  Cache hit.
 Using DN uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl
 [2015-10-13 16:33:14,458] DEBUG
 {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} -  User:
 uid=userkavirw3,ou=People,ou=WSO2,o=Opensource,dc=ITIndustry,dc=sl is
 authnticated: true
 [2015-10-13 16:33:14,463] DEBUG
 {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -
  Authorization cache hit. rwldap.com/userkavirw3 user is not
 Authorized to perform ui.execute on /permission/admin/login
 [2015-10-13 16:33:14,463]  WARN
 {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
 Administrator login attempt 'RWLDAP.COM/userkavirw3[-1234]
 ' at [2015-10-13
 16:33:14,463+0530]


 Thanks & Kind regards,
 --
 Kavitha.S
 *Software Engineer -QA*
 Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
 kavi...@wso2.com

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

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 4

2015-10-14 Thread Sajith Dimal
Hi All.

I tested main use cases of the following scenarios and found no issues:

   1.

   Analytics project creation.
   2.

   Analytics artifacts (Execution-plan, Stream, Receiver, Publisher)
   creation.
   3.

   Analytics artifact rename.
   4.

   CAPP project creation and deploy for Analytics project.

+1 for the release.

Thanks.

On Wed, Oct 14, 2015 at 2:53 PM, Susinda Perera  wrote:

> Hi All
> I have tested following and no blocking issues found.
>
> ESB, DSS, BPEL, CAPP project creation
> ESB artifact creation
> Importing connectors
> Connector exporter project
> All inbound endpoints
> APIM perspective - commit/rename/checkout
>
> Thanks
> Susinda
>
>
>
>
>
> On Wed, Oct 14, 2015 at 10:09 AM, Awanthika Senarath 
> wrote:
>
>> Hi
>>
>> I have tested the following features and bug fixes and the observations
>> were positive, hence +1
>>
>>
>>- ESB projects,
>>- Registry Projects
>>- Data Service Projects
>>
>>
>>
>>- Capp projects (creation, deploy, redeploy, removal)
>>- Servers (remote/local)
>>
>>
>>
>>- Artifact renaming.
>>
>>
>> Regards
>> Awanthika
>>
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> On Wed, Oct 14, 2015 at 9:25 AM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> Please vote for the fourth release candidate of WSO2 Developer Studio
>>> 3.8.0.
>>>
>>> This release fixes following issues.
>>> https://wso2.org/jira/issues/?filter=12453
>>>
>>> Please download, test and vote. Vote will be open for 72 hours or as
>>> needed.
>>>
>>> Sources, binary distribution and pre-installed eclipse distributions:
>>> http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC4/
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/developer-studio/tree/v3.8.0-RC4
>>>
>>>
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards,
>>> DevStudio Team
>>>
>>> --
>>> *Kavith Lokuhewage*
>>> Software Engineer
>>> WSO2 Inc. - http://wso2.com
>>> lean . enterprise . middleware
>>> Mobile - +9477-9-145-123 | +9471-455-6-401
>>> Linkedin 
>>> Twitter 
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards

*Sajith Dimal*
Software Engineer - Intern
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

Email: saji...@wso2.com
Mobile: +94 783101496 <94783101496>
LinkedIn: https://lk.linkedin.com/pub/sajith-dimal/b8/1b1/25b

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


Re: [Dev] Can not find defineStream method in Siddhi 3.0.0M1

2015-10-14 Thread Lasantha Fernando
Hi,

I tried the above same Siddhi query in Java and it is working fine for me.

I think you mentioned that the main activity interface was not loading
properly with the above Siddhi instance creation logic. Can you move the
siddhi manager instantiation and the execution plan runtime creation logic
also to the onClick_Button method for now and see whether the interface
gets loaded?

Also, if possible, please increase the logs so that you can track better
where the code gets hit. Can you debug the above application in Android
Studio and determine how much memory is getting allocated for Siddhi?

Thanks,
Lasantha

On 14 October 2015 at 17:11, Lakini Senanayaka  wrote:

> Hi,
>
> Now I'm getting log like,
>
> 10-14 07:38:18.9705362-5362/org.wso2.myapplication3 D/dalvikvm﹕
> Late-enabling CheckJNI
> 10-14 07:38:19.0745362-5362/org.wso2.myapplication3 D/dalvikvm﹕
> GC_FOR_ALLOC freed 290K, 4% free 9019K/9336K, paused 3ms, total 7ms
>
> My app is not working yet.If you have any suggestions please share with me.
>
> Thank You.
>
> On Wed, Oct 14, 2015 at 4:43 PM, Lasantha Fernando 
> wrote:
>
>> Hi Lakini,
>>
>> Please include siddhi-query-compiler-3.0.2.jar to your dependencies as
>> well.
>>
>> Thanks,
>> Lasantha
>>
>> On 14 October 2015 at 15:07, Lakini Senanayaka  wrote:
>>
>>> Hi,
>>>
>>> I have created an sample application using Siddhi-3.0.2 in android
>>> Studio.
>>>
>>> This is my code.
>>>
>>> package org.wso2.myapplication3;
>>>
>>> import android.os.Bundle;
>>> import android.support.v7.app.ActionBarActivity;
>>> import android.util.Log;
>>> import android.view.Menu;
>>> import android.view.MenuItem;
>>> import android.view.View;
>>> import android.widget.EditText;
>>> import org.wso2.siddhi.core.ExecutionPlanRuntime;
>>> import org.wso2.siddhi.core.SiddhiManager;
>>> import org.wso2.siddhi.core.event.Event;
>>> import org.wso2.siddhi.core.query.output.callback.QueryCallback;
>>> import org.wso2.siddhi.core.stream.input.InputHandler;
>>> import org.wso2.siddhi.core.util.EventPrinter;
>>>
>>> public class MainActivity extends ActionBarActivity {
>>>
>>> SiddhiManager siddhiManager=new SiddhiManager();
>>> ExecutionPlanRuntime executionPlanRuntime;
>>>
>>> @Override
>>> protected void onCreate(Bundle savedInstanceState) {
>>> super.onCreate(savedInstanceState);
>>> setContentView(R.layout.activity_main);
>>>
>>> //passing the rules to the siddhi
>>>
>>> String cseEventStream = "@config(async = 'true') define stream 
>>> StockQuoteStream (value double);";
>>> String query = "@info(name = 'query1') from 
>>> StockQuoteStream[value>20] insert into HighValueQuotes;";
>>> executionPlanRuntime = 
>>> siddhiManager.createExecutionPlanRuntime(cseEventStream + query);
>>> executionPlanRuntime.addCallback("query1", new QueryCallback() {
>>> @Override
>>> public void receive(long timeStamp, Event[] inEvents, Event[] 
>>> removeEvents) {
>>> EventPrinter.print(timeStamp, inEvents, removeEvents);
>>> Log.d("app3", "Received event!!");
>>> }
>>> });
>>> }
>>>
>>> @Override
>>> public boolean onCreateOptionsMenu(Menu menu) {
>>> // Inflate the menu; this adds items to the action bar if it is 
>>> present.
>>> getMenuInflater().inflate(R.menu.menu_main, menu);
>>> return true;
>>> }
>>>
>>> @Override
>>> public boolean onOptionsItemSelected(MenuItem item) {
>>> // Handle action bar item clicks here. The action bar will
>>> // automatically handle clicks on the Home/Up button, so long
>>> // as you specify a parent activity in AndroidManifest.xml.
>>> int id = item.getItemId();
>>>
>>> //noinspection SimplifiableIfStatement
>>> if (id == R.id.action_settings) {
>>> return true;
>>> }
>>>
>>> return super.onOptionsItemSelected(item);
>>> }
>>>
>>> //passing data to the stream
>>> public void onClick_Button (View v) throws InterruptedException {
>>> EditText t = (EditText) findViewById(R.id.editText);
>>> double value = Double.parseDouble(t.getText().toString());
>>> Log.d("app3",String.valueOf(value));
>>>
>>> //send events/data in to stream
>>> InputHandler inputHandler = 
>>> executionPlanRuntime.getInputHandler("StockQuoteStream");
>>> executionPlanRuntime.start();
>>> inputHandler.send(new Object[]{value});
>>> executionPlanRuntime.shutdown();
>>> }
>>> }
>>>
>>>
>>> I have included the log file which I got when I run the app.
>>>
>>> 10-14 04:28:01.025  16126-16126/? D/dalvikvm﹕ Late-enabling CheckJNI
>>> 10-14 04:28:01.073  16126-16126/? I/dalvikvm﹕ Could not find method
>>> org.wso2.siddhi.query.compiler.SiddhiCompiler.parse, referenced from method
>>> 

Re: [Dev] Can not find defineStream method in Siddhi 3.0.0M1

2015-10-14 Thread Lakini Senanayaka
Hi,

Now I'm getting log like,

10-14 07:38:18.9705362-5362/org.wso2.myapplication3 D/dalvikvm﹕
Late-enabling CheckJNI
10-14 07:38:19.0745362-5362/org.wso2.myapplication3 D/dalvikvm﹕
GC_FOR_ALLOC freed 290K, 4% free 9019K/9336K, paused 3ms, total 7ms

My app is not working yet.If you have any suggestions please share with me.

Thank You.

On Wed, Oct 14, 2015 at 4:43 PM, Lasantha Fernando 
wrote:

> Hi Lakini,
>
> Please include siddhi-query-compiler-3.0.2.jar to your dependencies as
> well.
>
> Thanks,
> Lasantha
>
> On 14 October 2015 at 15:07, Lakini Senanayaka  wrote:
>
>> Hi,
>>
>> I have created an sample application using Siddhi-3.0.2 in android Studio.
>>
>> This is my code.
>>
>> package org.wso2.myapplication3;
>>
>> import android.os.Bundle;
>> import android.support.v7.app.ActionBarActivity;
>> import android.util.Log;
>> import android.view.Menu;
>> import android.view.MenuItem;
>> import android.view.View;
>> import android.widget.EditText;
>> import org.wso2.siddhi.core.ExecutionPlanRuntime;
>> import org.wso2.siddhi.core.SiddhiManager;
>> import org.wso2.siddhi.core.event.Event;
>> import org.wso2.siddhi.core.query.output.callback.QueryCallback;
>> import org.wso2.siddhi.core.stream.input.InputHandler;
>> import org.wso2.siddhi.core.util.EventPrinter;
>>
>> public class MainActivity extends ActionBarActivity {
>>
>> SiddhiManager siddhiManager=new SiddhiManager();
>> ExecutionPlanRuntime executionPlanRuntime;
>>
>> @Override
>> protected void onCreate(Bundle savedInstanceState) {
>> super.onCreate(savedInstanceState);
>> setContentView(R.layout.activity_main);
>>
>> //passing the rules to the siddhi
>>
>> String cseEventStream = "@config(async = 'true') define stream 
>> StockQuoteStream (value double);";
>> String query = "@info(name = 'query1') from 
>> StockQuoteStream[value>20] insert into HighValueQuotes;";
>> executionPlanRuntime = 
>> siddhiManager.createExecutionPlanRuntime(cseEventStream + query);
>> executionPlanRuntime.addCallback("query1", new QueryCallback() {
>> @Override
>> public void receive(long timeStamp, Event[] inEvents, Event[] 
>> removeEvents) {
>> EventPrinter.print(timeStamp, inEvents, removeEvents);
>> Log.d("app3", "Received event!!");
>> }
>> });
>> }
>>
>> @Override
>> public boolean onCreateOptionsMenu(Menu menu) {
>> // Inflate the menu; this adds items to the action bar if it is 
>> present.
>> getMenuInflater().inflate(R.menu.menu_main, menu);
>> return true;
>> }
>>
>> @Override
>> public boolean onOptionsItemSelected(MenuItem item) {
>> // Handle action bar item clicks here. The action bar will
>> // automatically handle clicks on the Home/Up button, so long
>> // as you specify a parent activity in AndroidManifest.xml.
>> int id = item.getItemId();
>>
>> //noinspection SimplifiableIfStatement
>> if (id == R.id.action_settings) {
>> return true;
>> }
>>
>> return super.onOptionsItemSelected(item);
>> }
>>
>> //passing data to the stream
>> public void onClick_Button (View v) throws InterruptedException {
>> EditText t = (EditText) findViewById(R.id.editText);
>> double value = Double.parseDouble(t.getText().toString());
>> Log.d("app3",String.valueOf(value));
>>
>> //send events/data in to stream
>> InputHandler inputHandler = 
>> executionPlanRuntime.getInputHandler("StockQuoteStream");
>> executionPlanRuntime.start();
>> inputHandler.send(new Object[]{value});
>> executionPlanRuntime.shutdown();
>> }
>> }
>>
>>
>> I have included the log file which I got when I run the app.
>>
>> 10-14 04:28:01.025  16126-16126/? D/dalvikvm﹕ Late-enabling CheckJNI
>> 10-14 04:28:01.073  16126-16126/? I/dalvikvm﹕ Could not find method
>> org.wso2.siddhi.query.compiler.SiddhiCompiler.parse, referenced from method
>> org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime
>> 10-14 04:28:01.073  16126-16126/? W/dalvikvm﹕ VFY: unable to resolve
>> static method 30602: Lorg/wso2/siddhi/query/compiler/SiddhiCompiler;.parse
>> (Ljava/lang/String;)Lorg/wso2/siddhi/query/api/ExecutionPlan;
>> 10-14 04:28:01.073  16126-16126/? D/dalvikvm﹕ VFY: replacing opcode 0x71
>> at 0x
>> 10-14 04:28:01.073  16126-16126/? I/dalvikvm﹕ Could not find method
>> org.wso2.siddhi.query.compiler.SiddhiCompiler.parse, referenced from method
>> org.wso2.siddhi.core.SiddhiManager.validateExecutionPlan
>> 10-14 04:28:01.073  16126-16126/? W/dalvikvm﹕ VFY: unable to resolve
>> static method 30602: Lorg/wso2/siddhi/query/compiler/SiddhiCompiler;.parse
>> (Ljava/lang/String;)Lorg/wso2/siddhi/query/api/ExecutionPlan;
>> 10-14 04:28:01.073  16126-16126/? D/dalvikvm﹕ VFY: replacing opcode 0x71
>> at 0x
>> 

Re: [Dev] Can not find defineStream method in Siddhi 3.0.0M1

2015-10-14 Thread Lasantha Fernando
Hi Lakini,

Please include siddhi-query-compiler-3.0.2.jar to your dependencies as well.

Thanks,
Lasantha

On 14 October 2015 at 15:07, Lakini Senanayaka  wrote:

> Hi,
>
> I have created an sample application using Siddhi-3.0.2 in android Studio.
>
> This is my code.
>
> package org.wso2.myapplication3;
>
> import android.os.Bundle;
> import android.support.v7.app.ActionBarActivity;
> import android.util.Log;
> import android.view.Menu;
> import android.view.MenuItem;
> import android.view.View;
> import android.widget.EditText;
> import org.wso2.siddhi.core.ExecutionPlanRuntime;
> import org.wso2.siddhi.core.SiddhiManager;
> import org.wso2.siddhi.core.event.Event;
> import org.wso2.siddhi.core.query.output.callback.QueryCallback;
> import org.wso2.siddhi.core.stream.input.InputHandler;
> import org.wso2.siddhi.core.util.EventPrinter;
>
> public class MainActivity extends ActionBarActivity {
>
> SiddhiManager siddhiManager=new SiddhiManager();
> ExecutionPlanRuntime executionPlanRuntime;
>
> @Override
> protected void onCreate(Bundle savedInstanceState) {
> super.onCreate(savedInstanceState);
> setContentView(R.layout.activity_main);
>
> //passing the rules to the siddhi
>
> String cseEventStream = "@config(async = 'true') define stream 
> StockQuoteStream (value double);";
> String query = "@info(name = 'query1') from 
> StockQuoteStream[value>20] insert into HighValueQuotes;";
> executionPlanRuntime = 
> siddhiManager.createExecutionPlanRuntime(cseEventStream + query);
> executionPlanRuntime.addCallback("query1", new QueryCallback() {
> @Override
> public void receive(long timeStamp, Event[] inEvents, Event[] 
> removeEvents) {
> EventPrinter.print(timeStamp, inEvents, removeEvents);
> Log.d("app3", "Received event!!");
> }
> });
> }
>
> @Override
> public boolean onCreateOptionsMenu(Menu menu) {
> // Inflate the menu; this adds items to the action bar if it is 
> present.
> getMenuInflater().inflate(R.menu.menu_main, menu);
> return true;
> }
>
> @Override
> public boolean onOptionsItemSelected(MenuItem item) {
> // Handle action bar item clicks here. The action bar will
> // automatically handle clicks on the Home/Up button, so long
> // as you specify a parent activity in AndroidManifest.xml.
> int id = item.getItemId();
>
> //noinspection SimplifiableIfStatement
> if (id == R.id.action_settings) {
> return true;
> }
>
> return super.onOptionsItemSelected(item);
> }
>
> //passing data to the stream
> public void onClick_Button (View v) throws InterruptedException {
> EditText t = (EditText) findViewById(R.id.editText);
> double value = Double.parseDouble(t.getText().toString());
> Log.d("app3",String.valueOf(value));
>
> //send events/data in to stream
> InputHandler inputHandler = 
> executionPlanRuntime.getInputHandler("StockQuoteStream");
> executionPlanRuntime.start();
> inputHandler.send(new Object[]{value});
> executionPlanRuntime.shutdown();
> }
> }
>
>
> I have included the log file which I got when I run the app.
>
> 10-14 04:28:01.025  16126-16126/? D/dalvikvm﹕ Late-enabling CheckJNI
> 10-14 04:28:01.073  16126-16126/? I/dalvikvm﹕ Could not find method
> org.wso2.siddhi.query.compiler.SiddhiCompiler.parse, referenced from method
> org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime
> 10-14 04:28:01.073  16126-16126/? W/dalvikvm﹕ VFY: unable to resolve
> static method 30602: Lorg/wso2/siddhi/query/compiler/SiddhiCompiler;.parse
> (Ljava/lang/String;)Lorg/wso2/siddhi/query/api/ExecutionPlan;
> 10-14 04:28:01.073  16126-16126/? D/dalvikvm﹕ VFY: replacing opcode 0x71
> at 0x
> 10-14 04:28:01.073  16126-16126/? I/dalvikvm﹕ Could not find method
> org.wso2.siddhi.query.compiler.SiddhiCompiler.parse, referenced from method
> org.wso2.siddhi.core.SiddhiManager.validateExecutionPlan
> 10-14 04:28:01.073  16126-16126/? W/dalvikvm﹕ VFY: unable to resolve
> static method 30602: Lorg/wso2/siddhi/query/compiler/SiddhiCompiler;.parse
> (Ljava/lang/String;)Lorg/wso2/siddhi/query/api/ExecutionPlan;
> 10-14 04:28:01.073  16126-16126/? D/dalvikvm﹕ VFY: replacing opcode 0x71
> at 0x
> 10-14 04:28:01.101  16126-16132/? D/dalvikvm﹕ Debugger has detached;
> object registry had 1 entries
> 10-14 04:28:01.145  16126-16129/? D/dalvikvm﹕ GC_CONCURRENT freed 221K, 3%
> free 8960K/9212K, paused 1ms+0ms, total 10ms
> 10-14 04:28:01.213  16126-16129/? D/dalvikvm﹕ GC_CONCURRENT freed 255K, 4%
> free 9091K/9376K, paused 2ms+1ms, total 9ms
> 10-14 04:28:01.297  16126-16129/? D/dalvikvm﹕ GC_CONCURRENT freed 378K, 5%
> free 9100K/9508K, paused 3ms+1ms, total 10ms
> 10-14 04:28:01.381  16126-16129/? D/dalvikvm﹕ GC_CONCURRENT freed 390K, 5%
> 

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 4

2015-10-14 Thread Nuwan Pallewela
Hi All,

I have tested following areas,

   - ESB basic fuctionalities
   - App Server service classes
   - Registry Resources
   - CApp creation and deployments in servers
   - Connector importing and removing
   - Servers

No blocking issues found. So +1

On Wed, Oct 14, 2015 at 3:30 PM, Sajith Dimal  wrote:

> Hi All.
>
> I tested main use cases of the following scenarios and found no issues:
>
>1.
>
>Analytics project creation.
>2.
>
>Analytics artifacts (Execution-plan, Stream, Receiver, Publisher)
>creation.
>3.
>
>Analytics artifact rename.
>4.
>
>CAPP project creation and deploy for Analytics project.
>
> +1 for the release.
>
> Thanks.
>
> On Wed, Oct 14, 2015 at 2:53 PM, Susinda Perera  wrote:
>
>> Hi All
>> I have tested following and no blocking issues found.
>>
>> ESB, DSS, BPEL, CAPP project creation
>> ESB artifact creation
>> Importing connectors
>> Connector exporter project
>> All inbound endpoints
>> APIM perspective - commit/rename/checkout
>>
>> Thanks
>> Susinda
>>
>>
>>
>>
>>
>> On Wed, Oct 14, 2015 at 10:09 AM, Awanthika Senarath 
>> wrote:
>>
>>> Hi
>>>
>>> I have tested the following features and bug fixes and the observations
>>> were positive, hence +1
>>>
>>>
>>>- ESB projects,
>>>- Registry Projects
>>>- Data Service Projects
>>>
>>>
>>>
>>>- Capp projects (creation, deploy, redeploy, removal)
>>>- Servers (remote/local)
>>>
>>>
>>>
>>>- Artifact renaming.
>>>
>>>
>>> Regards
>>> Awanthika
>>>
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>> On Wed, Oct 14, 2015 at 9:25 AM, Kavith Lokuhewage 
>>> wrote:
>>>
 Hi Devs,

 Please vote for the fourth release candidate of WSO2 Developer Studio
 3.8.0.

 This release fixes following issues.
 https://wso2.org/jira/issues/?filter=12453

 Please download, test and vote. Vote will be open for 72 hours or as
 needed.

 Sources, binary distribution and pre-installed eclipse distributions:

 http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC4/

 The tag to be voted upon:
 https://github.com/wso2/developer-studio/tree/v3.8.0-RC4


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

 Thanks and Regards,
 DevStudio Team

 --
 *Kavith Lokuhewage*
 Software Engineer
 WSO2 Inc. - http://wso2.com
 lean . enterprise . middleware
 Mobile - +9477-9-145-123 | +9471-455-6-401
 Linkedin 
 Twitter 

 ___
 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
>>>
>>>
>>
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>> Mobile:(+94)716049075
>> Blog: susinda.blogspot.com
>> WSO2 Inc. http://wso2.com/
>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards
>
> *Sajith Dimal*
> Software Engineer - Intern
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: saji...@wso2.com
> Mobile: +94 783101496 <94783101496>
> LinkedIn: https://lk.linkedin.com/pub/sajith-dimal/b8/1b1/25b
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*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


Re: [Dev] [Orbit] [BRS] Upgrade jxl, dools, Joda-time and Revamp group IDs of jsr94, janino for BRS

2015-10-14 Thread Milinda Perera
Hi,

Updated suggestions, Please review and merge.

Thanks,
Milinda

On Tue, Oct 13, 2015 at 11:48 AM, Milinda Perera  wrote:

> Hi Aruna,
>
> Will update suggestions, test BRS and let you know ASAP.
>
> Thanks,
> Milinda
>
> On Tue, Oct 13, 2015 at 11:28 AM, Aruna Karunarathna 
> wrote:
>
>> Hi Milinda,
>>
>> I have added some comments to your PR. Can you please check them?.
>>
>> Regards,
>> Aruna
>>
>> On Tue, Oct 13, 2015 at 12:31 AM, Milinda Perera 
>> wrote:
>>
>>> Hi,
>>>
>>> Please review and merge PR : https://github.com/wso2/orbit/pull/139
>>>
>>> Please refer following information about the changes and upgrades:
>>>
>>> *jsr94*
>>> 
>>> jsr94 used by BRS.
>>> Currently jsr94 in located in SVN orrbit [1] with groupID "jsr94.wso2"
>>> which does not match to current WSO2 orbit groupID naming convention. So
>>> with next release of BRS we decided to move it from SVN to GIT with current
>>> orbit naming convention
>>>
>>> New groupId : org.wso2.orbit.jsr94
>>> artifactId : jsr94
>>>
>>>
>>> *janino*
>>> 
>>> janino used by BRS.
>>> Same as jsr94 it also located in SVN orrbit [2] with groupID
>>> "janino.wso2" which also not match with current WSO2 orbit groupID naming
>>> convention. So with next release of BRS we decided to move it from SVN to
>>> GIT with current orbit naming convention
>>>
>>> New groupId : org.wso2.orbit.org.codehaus.janino
>>> artifactId : janino
>>>
>>> *jxl*
>>> 
>>> jxl used by BRS.
>>> same as above it also located in SVN orbit [3] with groupID "jxl.wso2"
>>> which also not match with current WSO2 orbit groupID naming convention. So
>>> with next release of BRS we decided to move it from SVN to GIT with current
>>> orbit naming convention.
>>>
>>> And also with this there is a version upgrade of jxl from 2.6.8 to 2.6.12
>>>
>>> New groupId : org.wso2.orbit.net.sourceforge.jexcelapi
>>> artifactId : jxl
>>>
>>> *joda-time*
>>> ===
>>> This orbit [4] also with groupID "joda-time.wso2" which also not match
>>> with current WSO2 orbit groupID naming convention. For next release of BRS,
>>> need version upgrade 1.6.0 to 2.8.2 with proper orbit groupID naming
>>> convention
>>>
>>> New groupId : org.wso2.orbit.joda-time
>>> artifactId : joda-time
>>>
>>> *dools*
>>> 
>>> Version upgrade from 6.0.1 to 6.3.0.
>>> GroupID also revamped to match current convention
>>>
>>> New groupId : org.wso2.orbit.org.drools
>>> artifactId : drools
>>>
>>>
>>>
>>> [1] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jsr94/
>>> [2] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/janino
>>> [3] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jxl/
>>> [4]
>>> https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/joda-time
>>>
>>> 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
>>>
>>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *| Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.wso2.com
>>
>>
>
>
>
> --
> Milinda Perera
> Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>


-- 
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] Enabling security with user name token

2015-10-14 Thread Hasintha Indrajee
Can you please tell me the carbon-identity version you are using ?

On Wed, Oct 14, 2015 at 3:04 PM, Rajith Vitharana  wrote:

> + Asela
>
> On Wed, Oct 14, 2015 at 1:13 PM, Rajith Vitharana 
> wrote:
>
>> Hi,
>>
>> I have enabled security in DSS service specifying the policy file (roles
>> included in the policy). But when invoking the service with username
>> password, it throws below exception.
>>
>> java.lang.ClassCastException: org.apache.axiom.om.impl.dom.ElementImpl
>> cannot be cast to org.apache.axiom.soap.SOAPHeaderBlock
>> at
>> org.wso2.carbon.security.pox.POXSecurityHandler.isSOAPWithoutSecHeader(POXSecurityHandler.java:362)
>> at
>> org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:102)
>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>> at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:515)
>> at
>> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:433)
>> at
>> org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:398)
>> at
>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:188)
>> at
>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSRFPreventionFilter.java:88)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRLFPreventionFilter.java:59)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>> at
>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
>> at
>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
>> at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
>> at
>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
>> at
>> 

Re: [Dev] Enabling security with user name token

2015-10-14 Thread Firzhan Naqash
Hi Rajith,

This is related to permission issue from your policy file.

We also encountered same issue some times ago and later figured out we were
missing the following configuration in the policy file

 http://www.wso2.org/products/carbon/security;>

admin,sys-admin





Regards,
Firzhan


-- 
*Firzhan Naqash*
Senior Software Engineer - Integration Platform Team
WSO2 Inc. http://wso2.com

email: firz...@wso2.com 
mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
blog: http://firzhanblogger.blogspot.com/
  *
*twitter: https://twitter.com/firzhan007  |
linked-in: **https://www.linkedin.com/in/firzhan
*

On Wed, Oct 14, 2015 at 5:12 PM, Hasintha Indrajee 
wrote:

> Can you please tell me the carbon-identity version you are using ?
>
> On Wed, Oct 14, 2015 at 3:04 PM, Rajith Vitharana 
> wrote:
>
>> + Asela
>>
>> On Wed, Oct 14, 2015 at 1:13 PM, Rajith Vitharana 
>> wrote:
>>
>>> Hi,
>>>
>>> I have enabled security in DSS service specifying the policy file (roles
>>> included in the policy). But when invoking the service with username
>>> password, it throws below exception.
>>>
>>> java.lang.ClassCastException: org.apache.axiom.om.impl.dom.ElementImpl
>>> cannot be cast to org.apache.axiom.soap.SOAPHeaderBlock
>>> at
>>> org.wso2.carbon.security.pox.POXSecurityHandler.isSOAPWithoutSecHeader(POXSecurityHandler.java:362)
>>> at
>>> org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:102)
>>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>> at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:515)
>>> at
>>> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:433)
>>> at
>>> org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:398)
>>> at
>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:188)
>>> at
>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>> at
>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at
>>> org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSRFPreventionFilter.java:88)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at
>>> org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRLFPreventionFilter.java:59)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at
>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at
>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>>> at
>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>>> at
>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
>>> at
>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
>>> at
>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
>>> at
>>> 

Re: [Dev] [Orbit] [BRS] Upgrade jxl, dools, Joda-time and Revamp group IDs of jsr94, janino for BRS

2015-10-14 Thread Aruna Karunarathna
This is merged.

@Maheshika can you host these bundles please?

Regards,
Aruna

On Wed, Oct 14, 2015 at 4:56 PM, Milinda Perera  wrote:

> Hi,
>
> Updated suggestions, Please review and merge.
>
> Thanks,
> Milinda
>
> On Tue, Oct 13, 2015 at 11:48 AM, Milinda Perera 
> wrote:
>
>> Hi Aruna,
>>
>> Will update suggestions, test BRS and let you know ASAP.
>>
>> Thanks,
>> Milinda
>>
>> On Tue, Oct 13, 2015 at 11:28 AM, Aruna Karunarathna 
>> wrote:
>>
>>> Hi Milinda,
>>>
>>> I have added some comments to your PR. Can you please check them?.
>>>
>>> Regards,
>>> Aruna
>>>
>>> On Tue, Oct 13, 2015 at 12:31 AM, Milinda Perera 
>>> wrote:
>>>
 Hi,

 Please review and merge PR : https://github.com/wso2/orbit/pull/139

 Please refer following information about the changes and upgrades:

 *jsr94*
 
 jsr94 used by BRS.
 Currently jsr94 in located in SVN orrbit [1] with groupID "jsr94.wso2"
 which does not match to current WSO2 orbit groupID naming convention. So
 with next release of BRS we decided to move it from SVN to GIT with current
 orbit naming convention

 New groupId : org.wso2.orbit.jsr94
 artifactId : jsr94


 *janino*
 
 janino used by BRS.
 Same as jsr94 it also located in SVN orrbit [2] with groupID
 "janino.wso2" which also not match with current WSO2 orbit groupID naming
 convention. So with next release of BRS we decided to move it from SVN to
 GIT with current orbit naming convention

 New groupId : org.wso2.orbit.org.codehaus.janino
 artifactId : janino

 *jxl*
 
 jxl used by BRS.
 same as above it also located in SVN orbit [3] with groupID "jxl.wso2"
 which also not match with current WSO2 orbit groupID naming convention. So
 with next release of BRS we decided to move it from SVN to GIT with current
 orbit naming convention.

 And also with this there is a version upgrade of jxl from 2.6.8 to
 2.6.12

 New groupId : org.wso2.orbit.net.sourceforge.jexcelapi
 artifactId : jxl

 *joda-time*
 ===
 This orbit [4] also with groupID "joda-time.wso2" which also not match
 with current WSO2 orbit groupID naming convention. For next release of BRS,
 need version upgrade 1.6.0 to 2.8.2 with proper orbit groupID naming
 convention

 New groupId : org.wso2.orbit.joda-time
 artifactId : joda-time

 *dools*
 
 Version upgrade from 6.0.1 to 6.3.0.
 GroupID also revamped to match current convention

 New groupId : org.wso2.orbit.org.drools
 artifactId : drools



 [1] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jsr94/
 [2] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/janino
 [3] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jxl/
 [4]
 https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/joda-time

 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


>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *| Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.wso2.com
>>>
>>>
>>
>>
>>
>> --
>> Milinda Perera
>> Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>
>
> --
> Milinda Perera
> Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>


-- 

*Aruna Sujith Karunarathna *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.2 RC2

2015-10-14 Thread Isura Karunaratne
Hi,

This issue is fixed in [1].


Thanks
isura


[1] https://wso2.org/jira/browse/CARBON-15517


On Wed, Oct 14, 2015 at 11:25 AM, Johann Nallathamby 
wrote:

> Hi Isura,
>
> Can you look into this issue urgently. I remember you fixing an issue
> related to this.
>
> Thanks.
>
> On Wed, Oct 14, 2015 at 7:16 AM, Indika Sampath  wrote:
>
>> Hi All,
>>
>> I debug code of our and found issue. It seems implementation of some API
>> changed in user-core. Let me explain the flow.
>>
>> Our queue/topic creation has two call.
>>
>> 1. We create internal role when adding queue and assign
>> "changePermission", "publish", "consume"  permissions to it. Which means
>> that, user who created particular queue can update permission, publish or
>> consume.
>>
>> - Below code line used to get internal role name:
>>
>> UserCoreUtil.addInternalDomainName(QUEUE_ROLE_PREFIX +
>> queueName.replace(".","-").replace("/", "-"))
>>
>> result = {java.lang.String@10289}"*Internal/Q_userQueue*"
>> value = {char[21]@10290}
>> hash = 0
>> hash32 = 0
>>
>> - assign permission as below:
>>
>> userStoreManager.addRole(roleName, user, null);
>> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>> PERMISSION_CHANGE_PERMISSION);
>> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>> TreeNode.Permission.CONSUME.toString().toLowerCase());
>> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>> TreeNode.Permission.PUBLISH.toString().toLowerCase());
>>
>> 2. User can select some other role listed in in queue add page. He can
>> select these role when adding queue or later by updating queue. So in
>> update permission we checked whether any of user's role has above assign
>> change permission.
>>
>> - get role list of user:
>>
>> userRealm.getUserStoreManager().getRoleListOfUser(loggedInUser)
>>
>> result = {java.lang.String[3]@9689}
>> [0] = {java.lang.String@9690}"*Internal/Q_userQueue*"
>> [1] = {java.lang.String@9691}"Internal/everyone"
>> [2] = {java.lang.String@9692}"role1"
>>
>> - check whether any of role has change permission
>>
>> for (String userRole : userRoles) {
>> if
>> (userRealm.getAuthorizationManager().isRoleAuthorized(userRole, queueID,
>> PERMISSION_CHANGE_PERMISSION)) {
>> isUserHasChangePermission = true;
>> }
>> }
>>
>> Issue is above check false for all roles. But we assigned change
>> permission to *Internal/Q_userQueue*  role when creating queue.
>>
>> 3. Next I evaluate below code line to check whether which role has change
>> permission to queueID. Result is as below:
>>
>> userRealm.getAuthorizationManager().getAllowedRolesForResource(queueID,
>> PERMISSION_CHANGE_PERMISSION)
>>
>> result = {java.lang.String[1]@9694}
>> [0] = {java.lang.String@9686}"*INTERNAL/Q_userQueue*"
>>
>> Result has different role name. We created role name called
>> *Internal/Q_userQueue* and assign permissions but it has created with
>> different name *INTERNAL/Q_userQueue* and assign permission.
>>
>> Please have look into this because it is blocking issue to our
>> implementation.
>>
>> Cheers!
>>
>>
>> On Tue, Oct 13, 2015 at 5:22 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Was this issue found in 4.4.2 RC1 too?
>>>
>>> On Tue, Oct 13, 2015 at 4:58 PM, Sasikala Kottegoda 
>>> wrote:
>>>
 Hi Manuri,

 We tested MB 3.0.0 with this release and our scenario of queue creation
 fails after giving a permission denied error. The scenario is as follows:

 1. Create a user "user1" with a role assigned with permission to create
 queues.
 2. Login from "user1" and try to create a queue, we get a permission
 denied error.

 When creating a queue the following happens from our code.

 1. We create an internal role for the queue and assign it to the
 current user with permissions assigned.

 userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
   
 PERMISSION_CHANGE_PERMISSION);

 2. Next, we create the queue and update permissions for the queue. In this 
 step, we check if the current user has permissions to change the queue.

 String[] userRoles = 
 userRealm.getUserStoreManager().getRoleListOfUser(loggedInUser);
 for (String userRole : userRoles) {
 if (userRealm.getAuthorizationManager().isRoleAuthorized(
 userRole, queueID, PERMISSION_CHANGE_PERMISSION)) {
 isUserHasChangePermission = true;
 }
 }

 At this stage, *'*(userRealm.getAuthorizationManager().isRoleAuthorized(
 userRole, queueID, PERMISSION_CHANGE_PERMISSION))' false 
 implying that any of roles assigned to the user do not have permissions to 
 change the queue, thus not allowing the user to create the 

Re: [Dev] [EMM]Issue in Policy Monitoring Service

2015-10-14 Thread Dilshan Edirisuriya
Once we get the monitoring response back we need to update it to completed
state. For other operations what we do is to set the status manually. For
this I think we can update the status at the policy core level?

On Wed, Oct 14, 2015 at 6:20 PM, Hasunie Adikari  wrote:

> Hi All,
>
> There is a issue in Policy monitoring task.Service add monitor operation
> to the DM_OPERATION Table without considering the status of the MONITOR
> operation in the DM_ENROLLMENT_OPERATION_MAPPING.
> It should not be a proper behavior.Monitor operation should add new
> Monitor operation to the table, If existing MONITOR operation status has
> changed in to the COMPLETED status.
> Task need to be checked status of the existing one.Before adding to new
> MONITOR operation.
>
>
> ​
> ​
>
>
> --
> *Hasunie Adikari*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
> blog http://hasuniea.blogspot.com
> Mobile:+94715139495
>



-- 
Dilshan Edirisuriya
Senior Software Engineer - WSO2
Mob: + 94 777878905
http://wso2.com/
https://www.linkedin.com/profile/view?id=50486426
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [EMM]Issue in Policy Monitoring Service

2015-10-14 Thread Geeth Munasinghe
Hi all,

I am looking in to this,  Will update soon.

Thanks
Geeth


*G. K. S. Munasinghe*
*Senior Software Engineer,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226

On Wed, Oct 14, 2015 at 4:36 PM, Dilshan Edirisuriya 
wrote:

> Once we get the monitoring response back we need to update it to completed
> state. For other operations what we do is to set the status manually. For
> this I think we can update the status at the policy core level?
>
> On Wed, Oct 14, 2015 at 6:20 PM, Hasunie Adikari  wrote:
>
>> Hi All,
>>
>> There is a issue in Policy monitoring task.Service add monitor operation
>> to the DM_OPERATION Table without considering the status of the MONITOR
>> operation in the DM_ENROLLMENT_OPERATION_MAPPING.
>> It should not be a proper behavior.Monitor operation should add new
>> Monitor operation to the table, If existing MONITOR operation status has
>> changed in to the COMPLETED status.
>> Task need to be checked status of the existing one.Before adding to new
>> MONITOR operation.
>>
>>
>> ​
>> ​
>>
>>
>> --
>> *Hasunie Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>> blog http://hasuniea.blogspot.com
>> Mobile:+94715139495
>>
>
>
>
> --
> Dilshan Edirisuriya
> Senior Software Engineer - WSO2
> Mob: + 94 777878905
> http://wso2.com/
> https://www.linkedin.com/profile/view?id=50486426
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Null pointer exception from api gateway component when logging as the tenant-admin

2015-10-14 Thread Uvindra Dias Jayasinha
Hi Harsha,

This seems to be happening because you dont have the default sequences that
are shipped with the APIM pack. When you login to the tenant for the first
time the sequence are copied over to that tenant space, but you dont have
these in the MDM pack. The Error and Warning above the NPE also shows that
this is the case.

We have not handled the scenario where the gateway feature would be used in
when an actual synapse gateway does not exist. We need to validate the
gateway type and only carry this step out if the gateway type is synapse to
avoid the NPE.

On 14 October 2015 at 23:07, Harshan Liyanage  wrote:

> Hi all,
>
> I'm getting the below exception when logging as the tenant-admin (latest
> EMM build). We are using org.wso2.carbon.apimgt.gateway.feature.group
> version 4.3.0-SNAPSHOT at the moment.
>
> Could please someone from APIM team can shed a light on this issue?
>
> [2015-10-14 23:00:18,924] hars...@wso2.com [1] [MDM] WARN
> {org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Could not
> create
> /home/harshan/development/cdm/wso2mdm-2.0.0-SNAPSHOT/repository/tenants/1/synapse-configs/default/sequences
> [2015-10-14 23:00:18,925] hars...@wso2.com [1] [MDM]ERROR
> {org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Error
> while reading API manager specific synapse
> sequencesjava.io.FileNotFoundException: File
> '/home/harshan/development/cdm/wso2mdm-2.0.0-SNAPSHOT/repository/resources/apim-synapse-config/_auth_failure_handler_.xml'
> does not exist
> [2015-10-14 23:00:18,927] hars...@wso2.com [1] [MDM]ERROR
> {org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Couldn't
> serialise the initial synapse configuration for the domain : wso2.com
> java.lang.NullPointerException
> at
> org.apache.synapse.config.xml.MultiXMLConfigurationSerializer.serializeSequence(MultiXMLConfigurationSerializer.java:470)
> at
> org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator.createTenantSynapseConfigHierarchy(TenantServiceCreator.java:234)
> at
> org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator.createdConfigurationContext(TenantServiceCreator.java:141)
> at
> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:357)
> at
> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:148)
> at
> org.wso2.carbon.core.services.util.CarbonAuthenticationUtil.onSuccessAdminLogin(CarbonAuthenticationUtil.java:134)
> at
> org.wso2.carbon.core.services.authentication.AuthenticationAdmin.login(AuthenticationAdmin.java:117)
> 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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
> at
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
> at
> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
> at
> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
> at
> org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient.login(AuthenticationAdminClient.java:64)
> at
> org.wso2.carbon.ui.DefaultCarbonAuthenticator.doAuthentication(DefaultCarbonAuthenticator.java:119)
> at
> org.wso2.carbon.ui.AbstractCarbonUIAuthenticator.handleSecurity(AbstractCarbonUIAuthenticator.java:218)
> at
> org.wso2.carbon.ui.BasicAuthUIAuthenticator.authenticate(BasicAuthUIAuthenticator.java:83)
> at
> org.wso2.carbon.ui.CarbonUILoginUtil.handleLogin(CarbonUILoginUtil.java:377)
> at
> org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecuredHttpContext.java:244)
> at
> 

Re: [Dev] Null pointer exception from api gateway component when logging as the tenant-admin

2015-10-14 Thread Amila De Silva
Hi Uvindra,

IIRC TenantServiceCreator ( the task which deploys synapse artifacts upon a
TenantLoading) is only registered, if the Gateway type is Synapse. If we
 set it to None, then that task should not get registered.

On Thursday, October 15, 2015, Uvindra Dias Jayasinha 
wrote:

> Hi Harsha,
>
> This seems to be happening because you dont have the default sequences
> that are shipped with the APIM pack. When you login to the tenant for the
> first time the sequence are copied over to that tenant space, but you dont
> have these in the MDM pack. The Error and Warning above the NPE also shows
> that this is the case.
>
> We have not handled the scenario where the gateway feature would be used
> in when an actual synapse gateway does not exist. We need to validate the
> gateway type and only carry this step out if the gateway type is synapse to
> avoid the NPE.
>
> On 14 October 2015 at 23:07, Harshan Liyanage  > wrote:
>
>> Hi all,
>>
>> I'm getting the below exception when logging as the tenant-admin (latest
>> EMM build). We are using org.wso2.carbon.apimgt.gateway.feature.group
>> version 4.3.0-SNAPSHOT at the moment.
>>
>> Could please someone from APIM team can shed a light on this issue?
>>
>> [2015-10-14 23:00:18,924] hars...@wso2.com
>>  [1] [MDM] WARN
>> {org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Could not
>> create
>> /home/harshan/development/cdm/wso2mdm-2.0.0-SNAPSHOT/repository/tenants/1/synapse-configs/default/sequences
>> [2015-10-14 23:00:18,925] hars...@wso2.com
>>  [1] [MDM]ERROR
>> {org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Error
>> while reading API manager specific synapse
>> sequencesjava.io.FileNotFoundException: File
>> '/home/harshan/development/cdm/wso2mdm-2.0.0-SNAPSHOT/repository/resources/apim-synapse-config/_auth_failure_handler_.xml'
>> does not exist
>> [2015-10-14 23:00:18,927] hars...@wso2.com
>>  [1] [MDM]ERROR
>> {org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Couldn't
>> serialise the initial synapse configuration for the domain : wso2.com
>> java.lang.NullPointerException
>> at
>> org.apache.synapse.config.xml.MultiXMLConfigurationSerializer.serializeSequence(MultiXMLConfigurationSerializer.java:470)
>> at
>> org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator.createTenantSynapseConfigHierarchy(TenantServiceCreator.java:234)
>> at
>> org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator.createdConfigurationContext(TenantServiceCreator.java:141)
>> at
>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:357)
>> at
>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:148)
>> at
>> org.wso2.carbon.core.services.util.CarbonAuthenticationUtil.onSuccessAdminLogin(CarbonAuthenticationUtil.java:134)
>> at
>> org.wso2.carbon.core.services.authentication.AuthenticationAdmin.login(AuthenticationAdmin.java:117)
>> 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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>> at
>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>> at
>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>> at
>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
>> at
>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
>> at
>> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>> at
>> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>> at
>> org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
>> at
>> 

Re: [Dev] Null pointer exception from api gateway component when logging as the tenant-admin

2015-10-14 Thread Uvindra Dias Jayasinha
Ok, to confirm what Amila is saying, Harsha can you check the value of the
** element in the api-manager.xml of MDM? The value should be
*None*.



On 15 October 2015 at 10:05, Amila De Silva  wrote:

> Hi Uvindra,
>
> IIRC TenantServiceCreator ( the task which deploys synapse artifacts upon
> a TenantLoading) is only registered, if the Gateway type is Synapse. If we
>  set it to None, then that task should not get registered.
>
>
> On Thursday, October 15, 2015, Uvindra Dias Jayasinha 
> wrote:
>
>> Hi Harsha,
>>
>> This seems to be happening because you dont have the default sequences
>> that are shipped with the APIM pack. When you login to the tenant for the
>> first time the sequence are copied over to that tenant space, but you dont
>> have these in the MDM pack. The Error and Warning above the NPE also shows
>> that this is the case.
>>
>> We have not handled the scenario where the gateway feature would be used
>> in when an actual synapse gateway does not exist. We need to validate the
>> gateway type and only carry this step out if the gateway type is synapse to
>> avoid the NPE.
>>
>> On 14 October 2015 at 23:07, Harshan Liyanage  wrote:
>>
>>> Hi all,
>>>
>>> I'm getting the below exception when logging as the tenant-admin (latest
>>> EMM build). We are using org.wso2.carbon.apimgt.gateway.feature.group
>>> version 4.3.0-SNAPSHOT at the moment.
>>>
>>> Could please someone from APIM team can shed a light on this issue?
>>>
>>> [2015-10-14 23:00:18,924] hars...@wso2.com [1] [MDM] WARN
>>> {org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Could not
>>> create
>>> /home/harshan/development/cdm/wso2mdm-2.0.0-SNAPSHOT/repository/tenants/1/synapse-configs/default/sequences
>>> [2015-10-14 23:00:18,925] hars...@wso2.com [1] [MDM]ERROR
>>> {org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Error
>>> while reading API manager specific synapse
>>> sequencesjava.io.FileNotFoundException: File
>>> '/home/harshan/development/cdm/wso2mdm-2.0.0-SNAPSHOT/repository/resources/apim-synapse-config/_auth_failure_handler_.xml'
>>> does not exist
>>> [2015-10-14 23:00:18,927] hars...@wso2.com [1] [MDM]ERROR
>>> {org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator} -  Couldn't
>>> serialise the initial synapse configuration for the domain : wso2.com
>>> java.lang.NullPointerException
>>> at
>>> org.apache.synapse.config.xml.MultiXMLConfigurationSerializer.serializeSequence(MultiXMLConfigurationSerializer.java:470)
>>> at
>>> org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator.createTenantSynapseConfigHierarchy(TenantServiceCreator.java:234)
>>> at
>>> org.wso2.carbon.apimgt.gateway.internal.TenantServiceCreator.createdConfigurationContext(TenantServiceCreator.java:141)
>>> at
>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:357)
>>> at
>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:148)
>>> at
>>> org.wso2.carbon.core.services.util.CarbonAuthenticationUtil.onSuccessAdminLogin(CarbonAuthenticationUtil.java:134)
>>> at
>>> org.wso2.carbon.core.services.authentication.AuthenticationAdmin.login(AuthenticationAdmin.java:117)
>>> 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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>>> at
>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>> at
>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
>>> at
>>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
>>> at
>>> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>>> at
>>> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>>> at
>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>>> at
>>> 

[Dev] [EMM]Issue in Policy Monitoring Service

2015-10-14 Thread Hasunie Adikari
Hi All,

There is a issue in Policy monitoring task.Service add monitor operation to
the DM_OPERATION Table without considering the status of the MONITOR
operation in the DM_ENROLLMENT_OPERATION_MAPPING.
It should not be a proper behavior.Monitor operation should add new Monitor
operation to the table, If existing MONITOR operation status has changed in
to the COMPLETED status.
Task need to be checked status of the existing one.Before adding to new
MONITOR operation.


​
​


-- 
*Hasunie Adikari*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
blog http://hasuniea.blogspot.com
Mobile:+94715139495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.2 RC2

2015-10-14 Thread Kishanthan Thangarajah
Can we also have test case for this fix please?

On Wed, Oct 14, 2015 at 6:13 PM, Isura Karunaratne  wrote:

> Hi,
>
> This issue is fixed in [1].
>
>
> Thanks
> isura
>
>
> [1] https://wso2.org/jira/browse/CARBON-15517
>
>
> On Wed, Oct 14, 2015 at 11:25 AM, Johann Nallathamby 
> wrote:
>
>> Hi Isura,
>>
>> Can you look into this issue urgently. I remember you fixing an issue
>> related to this.
>>
>> Thanks.
>>
>> On Wed, Oct 14, 2015 at 7:16 AM, Indika Sampath  wrote:
>>
>>> Hi All,
>>>
>>> I debug code of our and found issue. It seems implementation of some API
>>> changed in user-core. Let me explain the flow.
>>>
>>> Our queue/topic creation has two call.
>>>
>>> 1. We create internal role when adding queue and assign
>>> "changePermission", "publish", "consume"  permissions to it. Which means
>>> that, user who created particular queue can update permission, publish or
>>> consume.
>>>
>>> - Below code line used to get internal role name:
>>>
>>> UserCoreUtil.addInternalDomainName(QUEUE_ROLE_PREFIX +
>>> queueName.replace(".","-").replace("/", "-"))
>>>
>>> result = {java.lang.String@10289}"*Internal/Q_userQueue*"
>>> value = {char[21]@10290}
>>> hash = 0
>>> hash32 = 0
>>>
>>> - assign permission as below:
>>>
>>> userStoreManager.addRole(roleName, user, null);
>>> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>>> PERMISSION_CHANGE_PERMISSION);
>>> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>>> TreeNode.Permission.CONSUME.toString().toLowerCase());
>>> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>>> TreeNode.Permission.PUBLISH.toString().toLowerCase());
>>>
>>> 2. User can select some other role listed in in queue add page. He can
>>> select these role when adding queue or later by updating queue. So in
>>> update permission we checked whether any of user's role has above assign
>>> change permission.
>>>
>>> - get role list of user:
>>>
>>> userRealm.getUserStoreManager().getRoleListOfUser(loggedInUser)
>>>
>>> result = {java.lang.String[3]@9689}
>>> [0] = {java.lang.String@9690}"*Internal/Q_userQueue*"
>>> [1] = {java.lang.String@9691}"Internal/everyone"
>>> [2] = {java.lang.String@9692}"role1"
>>>
>>> - check whether any of role has change permission
>>>
>>> for (String userRole : userRoles) {
>>> if
>>> (userRealm.getAuthorizationManager().isRoleAuthorized(userRole, queueID,
>>> PERMISSION_CHANGE_PERMISSION)) {
>>> isUserHasChangePermission = true;
>>> }
>>> }
>>>
>>> Issue is above check false for all roles. But we assigned change
>>> permission to *Internal/Q_userQueue*  role when creating queue.
>>>
>>> 3. Next I evaluate below code line to check whether which role has
>>> change permission to queueID. Result is as below:
>>>
>>> userRealm.getAuthorizationManager().getAllowedRolesForResource(queueID,
>>> PERMISSION_CHANGE_PERMISSION)
>>>
>>> result = {java.lang.String[1]@9694}
>>> [0] = {java.lang.String@9686}"*INTERNAL/Q_userQueue*"
>>>
>>> Result has different role name. We created role name called
>>> *Internal/Q_userQueue* and assign permissions but it has created with
>>> different name *INTERNAL/Q_userQueue* and assign permission.
>>>
>>> Please have look into this because it is blocking issue to our
>>> implementation.
>>>
>>> Cheers!
>>>
>>>
>>> On Tue, Oct 13, 2015 at 5:22 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 Was this issue found in 4.4.2 RC1 too?

 On Tue, Oct 13, 2015 at 4:58 PM, Sasikala Kottegoda 
 wrote:

> Hi Manuri,
>
> We tested MB 3.0.0 with this release and our scenario of queue
> creation fails after giving a permission denied error. The scenario is as
> follows:
>
> 1. Create a user "user1" with a role assigned with permission to
> create queues.
> 2. Login from "user1" and try to create a queue, we get a permission
> denied error.
>
> When creating a queue the following happens from our code.
>
> 1. We create an internal role for the queue and assign it to the
> current user with permissions assigned.
>
> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>   
> PERMISSION_CHANGE_PERMISSION);
>
> 2. Next, we create the queue and update permissions for the queue. In 
> this step, we check if the current user has permissions to change the 
> queue.
>
> String[] userRoles = 
> userRealm.getUserStoreManager().getRoleListOfUser(loggedInUser);
> for (String userRole : userRoles) {
> if (userRealm.getAuthorizationManager().isRoleAuthorized(
> userRole, queueID, PERMISSION_CHANGE_PERMISSION)) {
> isUserHasChangePermission = true;
> }
> }
>
> At 

[Dev] WSO2IS sessionDataKey

2015-10-14 Thread Júnior
Hi,

Is there any way to get the sessionDatakey after a OAuth Login?

I´d Like to use the sessionDataKey generated in a OAuth login to keep the
user logged in a IDp Initiated SSO in a different browser. Is this possible?

Thanks

-- 
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [EMM]Issue in Policy Monitoring Service

2015-10-14 Thread Geeth Munasinghe
Hi all,

This issue has been fixed. Please check now.

Thanks
Geeth


*G. K. S. Munasinghe*
*Senior Software Engineer,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226

On Wed, Oct 14, 2015 at 4:41 PM, Geeth Munasinghe  wrote:

> Hi all,
>
> I am looking in to this,  Will update soon.
>
> Thanks
> Geeth
>
>
> *G. K. S. Munasinghe*
> *Senior Software Engineer,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226
>
> On Wed, Oct 14, 2015 at 4:36 PM, Dilshan Edirisuriya 
> wrote:
>
>> Once we get the monitoring response back we need to update it to
>> completed state. For other operations what we do is to set the status
>> manually. For this I think we can update the status at the policy core
>> level?
>>
>> On Wed, Oct 14, 2015 at 6:20 PM, Hasunie Adikari 
>> wrote:
>>
>>> Hi All,
>>>
>>> There is a issue in Policy monitoring task.Service add monitor operation
>>> to the DM_OPERATION Table without considering the status of the MONITOR
>>> operation in the DM_ENROLLMENT_OPERATION_MAPPING.
>>> It should not be a proper behavior.Monitor operation should add new
>>> Monitor operation to the table, If existing MONITOR operation status has
>>> changed in to the COMPLETED status.
>>> Task need to be checked status of the existing one.Before adding to new
>>> MONITOR operation.
>>>
>>>
>>> ​
>>> ​
>>>
>>>
>>> --
>>> *Hasunie Adikari*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>> blog http://hasuniea.blogspot.com
>>> Mobile:+94715139495
>>>
>>
>>
>>
>> --
>> Dilshan Edirisuriya
>> Senior Software Engineer - WSO2
>> Mob: + 94 777878905
>> http://wso2.com/
>> https://www.linkedin.com/profile/view?id=50486426
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [IS] Using unregistered realm in PassiveSTS request

2015-10-14 Thread Hasanthi Purnima Dissanayake
Hi,

This is regarding the passive sts logout scenario which is mentioned in
[1]. According to the specification [2] in Sign-Out Request Syntax part it
has mentioned to use the 'wsreply' parameter if it is specified and to use
realm-specified if it is not specified. But when considering the security
considerations mentioned in the section 8 of [2] it is  RECOMMENDED that
the Identity Provider should  verify the 'wsreply' url. So we decided to
redirect the logout request to the 'wsreply' url configured in Identity
Provider side in the case if the 'wsreply' url we get from the request and
the url configured in the Identity Provider are different.

Further as Chamara mentioned above, at the moment we don't expect wtreply
must be a sub domain of wtrealm as mentioned in the specification.

[1] https://wso2.org/jira/browse/IDENTITY-2835
[2]http://public.dhe.ibm.com/software/dw/specs/ws-fedpass/ws-fedpass.pdf

Thanks




Hasanthi Dissanayake

Software Engineer | WSO2

E: hasan...@wso2.com 
M :0718407133| http://wso2.com 

On Thu, Oct 8, 2015 at 12:01 PM, Chamara Philips  wrote:

> Hi,
>
> This is regarding [1] .
> Currently when we send an unregistered realm or no realm with the
> parameter 'wtrealm' in the Passive STS request, we receive the same
> response as it is with the correct realm, but without the claim attributes.
> When an unregistered realm is passed a log is printed at back-end
> from RegistryBasedTrustedServiceStore. This is the expected behavior at the
> moment.
> The specification at [2]
> ,
> doesn't specify what to do when a invalid 'wtrealm' is passed. How ever
> according to [2]
>  both
> the 'wtreply' and 'wtrealm' are optional parameters. In section 8 in [2]
> ,
> as security concerns, there is a possibility of man-in-the -middle-attack
> when the Identity Provider doesn't verify whether the 'wtreply' is same or
> is in 'wtrealm'. The following part is quoted from [2]
> .
>
>
> [Man-in-the-Middle attacks: The wtreply must be in wtrealm (i.e., the same
> URL, or, e.g., wtreply is a host within the domain of wtrealm). It is
> strongly RECOMMENDED that the Identity Provider verifies this, and that
> wtreply is an valid HTTP/S address.
>
> • The wtrealm SHOULD be a security realm of the resource in which nobody
> can control URLs.
>
> • For Kerberos tokens the key distribution SHOULD distribute correct
> realms for the keys, so that Identity Providers know what the correct
> realms are for keys that they use.
>
> • For SAML tokens the resource SHOULD verify that exactly this realm is in
> one of the two (fix one!) fields of the ticket.
>
> • For other token types similar considerations SHOULD be made before using
> them.
>
> It is strongly RECOMMENDED that the resourceSTS secure information or use
> HTTP/S or some other transport-level security mechanism for all
> communications. ]
>
> As far as I understand the behavior when an unregistered realm is passed
> in request, is OK according to the spec [2]
> .
> Though we don't support the verification of 'wtreply' and 'wtrealm' as
> described in spec [2]
> 
> at the moment, we can enforce to verify the provided 'wtreply' in the
> request to be similar to the provided 'Passive STS WReply URL' when
> registering the Service Provider in IS. If they are not similar the user
> will be redirected to the given 'Passive STS WReply URL'.
>
> As far as I understand overall realm validation workflow is ok to proceed.
> Any suggestions on any improvement are welcome.
>
> [1] https://wso2.org/jira/browse/IDENTITY-2803
> 
> [2] http://public.dhe.ibm.com/software/dw/specs/ws-fedpass/ws-fedpass.pdf
>
> Thank you.
> --
> Hareendra Chamara Philips
> *Software  Engineer*
> Mobile : +94 (0) 767 184161 <%2B94%20%280%29%20773%20451194>
> chama...@wso2.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] WSO2 MSS JAX-RS Runtime Features

2015-10-14 Thread Samiyuru Senarathne
Hi,

We have been developing our own JAX-RS runtime for WSO2 Micro Services
Server (MSS). The purpose of that runtime is not to support the full JAX-RS
specification but to support a subset of the JAX-RS specification plus a
set of additional features focusing on performance and lightweightness to
run microservices.

With latest development work currently the MSS JAX-RS runtime supports the
following features.

   - The runtime can process annotated POJO JAX-RS resource classes and
   their annotated methods to create REST service endpoints for valid resource
   methods.
   - The runtime supports the following class level annotations.
  - @Path - Root path for resource methods
  - @Consumes - Default consume media type(s) for resource methods
  - @Produces - Default produce media type(s) for resource methods
   - Supports the following method level annotations.
  - @Path - Endpoint of the method relative to @Path of the class
  - @Consumes - Media type(s) that the method can consume
  - @Produces - Media type(s) that is produced by the method
  - @GET - HTTP GET method
  - @PUT - HTTP PUT method
  - @POST - HTTP POST method
  - @DELETE - HTTP DELETE method
   - Supports the following parameter level annotations.
  - @DefaultValue - Specify a default parameter value
  - @Context - Inject additional objects. Currently supports injection
  of io.netty.handler.codec.http.HttpRequest and
  org.wso2.carbon.mss.HttpResponder
  - @PathParam - /StockQuote/{*symbol*} to get value of symbol
  - @QueryParam - /Students?*age=18* to get value of age
  - @HeaderParam - To read HTTP request header values
   - Supports returning POJO from resource methods to response by xml or
   json and getting injected POJO to resource methods for request bodies that
   are json or xml.
   - Supports returning *javax.ws.rs.core.Response* objects from resource
   methods to send HTTP responses in a more customised way.

Product-MSS repository url: https://github.com/wso2/product-mss

Best Regards,
Samiyuru
-- 
Samiyuru Senarathne
*Software Engineer*
Mobile : +94 (0) 71 134 6087
samiy...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Orbit] [BRS] Upgrade jxl, dools, Joda-time and Revamp group IDs of jsr94, janino for BRS

2015-10-14 Thread Nandika Jayawardana
Hi Maheshika,

Can we have these bundles released please. We need them to proceed

Regards
Nandika

On Wed, Oct 14, 2015 at 5:57 PM, Aruna Karunarathna  wrote:

> This is merged.
>
> @Maheshika can you host these bundles please?
>
> Regards,
> Aruna
>
> On Wed, Oct 14, 2015 at 4:56 PM, Milinda Perera  wrote:
>
>> Hi,
>>
>> Updated suggestions, Please review and merge.
>>
>> Thanks,
>> Milinda
>>
>> On Tue, Oct 13, 2015 at 11:48 AM, Milinda Perera 
>> wrote:
>>
>>> Hi Aruna,
>>>
>>> Will update suggestions, test BRS and let you know ASAP.
>>>
>>> Thanks,
>>> Milinda
>>>
>>> On Tue, Oct 13, 2015 at 11:28 AM, Aruna Karunarathna 
>>> wrote:
>>>
 Hi Milinda,

 I have added some comments to your PR. Can you please check them?.

 Regards,
 Aruna

 On Tue, Oct 13, 2015 at 12:31 AM, Milinda Perera 
 wrote:

> Hi,
>
> Please review and merge PR : https://github.com/wso2/orbit/pull/139
>
> Please refer following information about the changes and upgrades:
>
> *jsr94*
> 
> jsr94 used by BRS.
> Currently jsr94 in located in SVN orrbit [1] with groupID "jsr94.wso2"
> which does not match to current WSO2 orbit groupID naming convention. So
> with next release of BRS we decided to move it from SVN to GIT with 
> current
> orbit naming convention
>
> New groupId : org.wso2.orbit.jsr94
> artifactId : jsr94
>
>
> *janino*
> 
> janino used by BRS.
> Same as jsr94 it also located in SVN orrbit [2] with groupID
> "janino.wso2" which also not match with current WSO2 orbit groupID naming
> convention. So with next release of BRS we decided to move it from SVN to
> GIT with current orbit naming convention
>
> New groupId : org.wso2.orbit.org.codehaus.janino
> artifactId : janino
>
> *jxl*
> 
> jxl used by BRS.
> same as above it also located in SVN orbit [3] with groupID "jxl.wso2"
> which also not match with current WSO2 orbit groupID naming convention. So
> with next release of BRS we decided to move it from SVN to GIT with 
> current
> orbit naming convention.
>
> And also with this there is a version upgrade of jxl from 2.6.8 to
> 2.6.12
>
> New groupId : org.wso2.orbit.net.sourceforge.jexcelapi
> artifactId : jxl
>
> *joda-time*
> ===
> This orbit [4] also with groupID "joda-time.wso2" which also not match
> with current WSO2 orbit groupID naming convention. For next release of 
> BRS,
> need version upgrade 1.6.0 to 2.8.2 with proper orbit groupID naming
> convention
>
> New groupId : org.wso2.orbit.joda-time
> artifactId : joda-time
>
> *dools*
> 
> Version upgrade from 6.0.1 to 6.3.0.
> GroupID also revamped to match current convention
>
> New groupId : org.wso2.orbit.org.drools
> artifactId : drools
>
>
>
> [1] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jsr94/
> [2] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/janino
> [3] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jxl/
> [4]
> https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/joda-time
>
> 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
>
>


 --

 *Aruna Sujith Karunarathna *| Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 9040362 | Work: +94 112145345
 Email: ar...@wso2.com | Web: www.wso2.com


>>>
>>>
>>>
>>> --
>>> Milinda Perera
>>> Software Engineer;
>>> WSO2 Inc. http://wso2.com ,
>>> Mobile: (+94) 714 115 032
>>>
>>>
>>
>>
>> --
>> Milinda Perera
>> Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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


Re: [Dev] WSO2 MSS JAX-RS Runtime Features

2015-10-14 Thread Sagara Gunathunga
Shall we also create a doc with all JAX-RS annotations, extensions and
mentioning what MSS supported and what not supported ?

Thanks !

On Thu, Oct 15, 2015 at 10:30 AM, Samiyuru Senarathne 
wrote:

> Hi,
>
> We have been developing our own JAX-RS runtime for WSO2 Micro Services
> Server (MSS). The purpose of that runtime is not to support the full JAX-RS
> specification but to support a subset of the JAX-RS specification plus a
> set of additional features focusing on performance and lightweightness to
> run microservices.
>
> With latest development work currently the MSS JAX-RS runtime supports the
> following features.
>
>- The runtime can process annotated POJO JAX-RS resource classes and
>their annotated methods to create REST service endpoints for valid resource
>methods.
>- The runtime supports the following class level annotations.
>   - @Path - Root path for resource methods
>   - @Consumes - Default consume media type(s) for resource methods
>   - @Produces - Default produce media type(s) for resource methods
>- Supports the following method level annotations.
>   - @Path - Endpoint of the method relative to @Path of the class
>   - @Consumes - Media type(s) that the method can consume
>   - @Produces - Media type(s) that is produced by the method
>   - @GET - HTTP GET method
>   - @PUT - HTTP PUT method
>   - @POST - HTTP POST method
>   - @DELETE - HTTP DELETE method
>- Supports the following parameter level annotations.
>   - @DefaultValue - Specify a default parameter value
>   - @Context - Inject additional objects. Currently supports
>   injection of io.netty.handler.codec.http.HttpRequest and
>   org.wso2.carbon.mss.HttpResponder
>   - @PathParam - /StockQuote/{*symbol*} to get value of symbol
>   - @QueryParam - /Students?*age=18* to get value of age
>   - @HeaderParam - To read HTTP request header values
>- Supports returning POJO from resource methods to response by xml or
>json and getting injected POJO to resource methods for request bodies that
>are json or xml.
>- Supports returning *javax.ws.rs.core.Response* objects from resource
>methods to send HTTP responses in a more customised way.
>
> Product-MSS repository url: https://github.com/wso2/product-mss
>
> Best Regards,
> Samiyuru
> --
> Samiyuru Senarathne
> *Software Engineer*
> Mobile : +94 (0) 71 134 6087
> samiy...@wso2.com
>



-- 
Sagara Gunathunga

Architect; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Orbit] [BRS] Upgrade jxl, dools, Joda-time and Revamp group IDs of jsr94, janino for BRS

2015-10-14 Thread Maheshika Goonetilleke
Hi Milinda

This is completed. The bundle was successfully deployed.

On Thu, Oct 15, 2015 at 10:37 AM, Maheshika Goonetilleke  wrote:

> Hi Nandika
>
> I am in the process of completing them, will update the thread once
> completed.
>
> On Thu, Oct 15, 2015 at 10:30 AM, Nandika Jayawardana 
> wrote:
>
>> Hi Maheshika,
>>
>> Can we have these bundles released please. We need them to proceed
>>
>> Regards
>> Nandika
>>
>> On Wed, Oct 14, 2015 at 5:57 PM, Aruna Karunarathna 
>> wrote:
>>
>>> This is merged.
>>>
>>> @Maheshika can you host these bundles please?
>>>
>>> Regards,
>>> Aruna
>>>
>>> On Wed, Oct 14, 2015 at 4:56 PM, Milinda Perera 
>>> wrote:
>>>
 Hi,

 Updated suggestions, Please review and merge.

 Thanks,
 Milinda

 On Tue, Oct 13, 2015 at 11:48 AM, Milinda Perera 
 wrote:

> Hi Aruna,
>
> Will update suggestions, test BRS and let you know ASAP.
>
> Thanks,
> Milinda
>
> On Tue, Oct 13, 2015 at 11:28 AM, Aruna Karunarathna 
> wrote:
>
>> Hi Milinda,
>>
>> I have added some comments to your PR. Can you please check them?.
>>
>> Regards,
>> Aruna
>>
>> On Tue, Oct 13, 2015 at 12:31 AM, Milinda Perera 
>> wrote:
>>
>>> Hi,
>>>
>>> Please review and merge PR : https://github.com/wso2/orbit/pull/139
>>>
>>> Please refer following information about the changes and upgrades:
>>>
>>> *jsr94*
>>> 
>>> jsr94 used by BRS.
>>> Currently jsr94 in located in SVN orrbit [1] with groupID
>>> "jsr94.wso2" which does not match to current WSO2 orbit groupID naming
>>> convention. So with next release of BRS we decided to move it from SVN 
>>> to
>>> GIT with current orbit naming convention
>>>
>>> New groupId : org.wso2.orbit.jsr94
>>> artifactId : jsr94
>>>
>>>
>>> *janino*
>>> 
>>> janino used by BRS.
>>> Same as jsr94 it also located in SVN orrbit [2] with groupID
>>> "janino.wso2" which also not match with current WSO2 orbit groupID 
>>> naming
>>> convention. So with next release of BRS we decided to move it from SVN 
>>> to
>>> GIT with current orbit naming convention
>>>
>>> New groupId : org.wso2.orbit.org.codehaus.janino
>>> artifactId : janino
>>>
>>> *jxl*
>>> 
>>> jxl used by BRS.
>>> same as above it also located in SVN orbit [3] with groupID
>>> "jxl.wso2" which also not match with current WSO2 orbit groupID naming
>>> convention. So with next release of BRS we decided to move it from SVN 
>>> to
>>> GIT with current orbit naming convention.
>>>
>>> And also with this there is a version upgrade of jxl from 2.6.8 to
>>> 2.6.12
>>>
>>> New groupId : org.wso2.orbit.net.sourceforge.jexcelapi
>>> artifactId : jxl
>>>
>>> *joda-time*
>>> ===
>>> This orbit [4] also with groupID "joda-time.wso2" which also not
>>> match with current WSO2 orbit groupID naming convention. For next 
>>> release
>>> of BRS, need version upgrade 1.6.0 to 2.8.2 with proper orbit groupID
>>> naming convention
>>>
>>> New groupId : org.wso2.orbit.joda-time
>>> artifactId : joda-time
>>>
>>> *dools*
>>> 
>>> Version upgrade from 6.0.1 to 6.3.0.
>>> GroupID also revamped to match current convention
>>>
>>> New groupId : org.wso2.orbit.org.drools
>>> artifactId : drools
>>>
>>>
>>>
>>> [1]
>>> https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jsr94/
>>> [2]
>>> https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/janino
>>> [3] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jxl/
>>> [4]
>>> https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/joda-time
>>>
>>> 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
>>>
>>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *| Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.wso2.com
>>
>>
>
>
>
> --
> Milinda Perera
> Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>


 --
 Milinda Perera
 Software Engineer;
 WSO2 Inc. http://wso2.com ,
 Mobile: (+94) 714 

Re: [Dev] WSO2 MSS JAX-RS Runtime Features

2015-10-14 Thread Samiyuru Senarathne
Sure, we will.

On Thu, Oct 15, 2015 at 10:33 AM, Sagara Gunathunga  wrote:

>
> Shall we also create a doc with all JAX-RS annotations, extensions and
> mentioning what MSS supported and what not supported ?
>
> Thanks !
>
> On Thu, Oct 15, 2015 at 10:30 AM, Samiyuru Senarathne 
> wrote:
>
>> Hi,
>>
>> We have been developing our own JAX-RS runtime for WSO2 Micro Services
>> Server (MSS). The purpose of that runtime is not to support the full JAX-RS
>> specification but to support a subset of the JAX-RS specification plus a
>> set of additional features focusing on performance and lightweightness to
>> run microservices.
>>
>> With latest development work currently the MSS JAX-RS runtime supports
>> the following features.
>>
>>- The runtime can process annotated POJO JAX-RS resource classes and
>>their annotated methods to create REST service endpoints for valid 
>> resource
>>methods.
>>- The runtime supports the following class level annotations.
>>   - @Path - Root path for resource methods
>>   - @Consumes - Default consume media type(s) for resource methods
>>   - @Produces - Default produce media type(s) for resource methods
>>- Supports the following method level annotations.
>>   - @Path - Endpoint of the method relative to @Path of the class
>>   - @Consumes - Media type(s) that the method can consume
>>   - @Produces - Media type(s) that is produced by the method
>>   - @GET - HTTP GET method
>>   - @PUT - HTTP PUT method
>>   - @POST - HTTP POST method
>>   - @DELETE - HTTP DELETE method
>>- Supports the following parameter level annotations.
>>   - @DefaultValue - Specify a default parameter value
>>   - @Context - Inject additional objects. Currently supports
>>   injection of io.netty.handler.codec.http.HttpRequest and
>>   org.wso2.carbon.mss.HttpResponder
>>   - @PathParam - /StockQuote/{*symbol*} to get value of symbol
>>   - @QueryParam - /Students?*age=18* to get value of age
>>   - @HeaderParam - To read HTTP request header values
>>- Supports returning POJO from resource methods to response by xml or
>>json and getting injected POJO to resource methods for request bodies that
>>are json or xml.
>>- Supports returning *javax.ws.rs.core.Response* objects from
>>resource methods to send HTTP responses in a more customised way.
>>
>> Product-MSS repository url: https://github.com/wso2/product-mss
>>
>> Best Regards,
>> Samiyuru
>> --
>> Samiyuru Senarathne
>> *Software Engineer*
>> Mobile : +94 (0) 71 134 6087
>> samiy...@wso2.com
>>
>
>
>
> --
> Sagara Gunathunga
>
> Architect; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 
Samiyuru Senarathne
*Software Engineer*
Mobile : +94 (0) 71 134 6087
samiy...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Orbit] [BRS] Upgrade jxl, dools, Joda-time and Revamp group IDs of jsr94, janino for BRS

2015-10-14 Thread Maheshika Goonetilleke
Hi Nandika

I am in the process of completing them, will update the thread once
completed.

On Thu, Oct 15, 2015 at 10:30 AM, Nandika Jayawardana 
wrote:

> Hi Maheshika,
>
> Can we have these bundles released please. We need them to proceed
>
> Regards
> Nandika
>
> On Wed, Oct 14, 2015 at 5:57 PM, Aruna Karunarathna 
> wrote:
>
>> This is merged.
>>
>> @Maheshika can you host these bundles please?
>>
>> Regards,
>> Aruna
>>
>> On Wed, Oct 14, 2015 at 4:56 PM, Milinda Perera 
>> wrote:
>>
>>> Hi,
>>>
>>> Updated suggestions, Please review and merge.
>>>
>>> Thanks,
>>> Milinda
>>>
>>> On Tue, Oct 13, 2015 at 11:48 AM, Milinda Perera 
>>> wrote:
>>>
 Hi Aruna,

 Will update suggestions, test BRS and let you know ASAP.

 Thanks,
 Milinda

 On Tue, Oct 13, 2015 at 11:28 AM, Aruna Karunarathna 
 wrote:

> Hi Milinda,
>
> I have added some comments to your PR. Can you please check them?.
>
> Regards,
> Aruna
>
> On Tue, Oct 13, 2015 at 12:31 AM, Milinda Perera 
> wrote:
>
>> Hi,
>>
>> Please review and merge PR : https://github.com/wso2/orbit/pull/139
>>
>> Please refer following information about the changes and upgrades:
>>
>> *jsr94*
>> 
>> jsr94 used by BRS.
>> Currently jsr94 in located in SVN orrbit [1] with groupID
>> "jsr94.wso2" which does not match to current WSO2 orbit groupID naming
>> convention. So with next release of BRS we decided to move it from SVN to
>> GIT with current orbit naming convention
>>
>> New groupId : org.wso2.orbit.jsr94
>> artifactId : jsr94
>>
>>
>> *janino*
>> 
>> janino used by BRS.
>> Same as jsr94 it also located in SVN orrbit [2] with groupID
>> "janino.wso2" which also not match with current WSO2 orbit groupID naming
>> convention. So with next release of BRS we decided to move it from SVN to
>> GIT with current orbit naming convention
>>
>> New groupId : org.wso2.orbit.org.codehaus.janino
>> artifactId : janino
>>
>> *jxl*
>> 
>> jxl used by BRS.
>> same as above it also located in SVN orbit [3] with groupID
>> "jxl.wso2" which also not match with current WSO2 orbit groupID naming
>> convention. So with next release of BRS we decided to move it from SVN to
>> GIT with current orbit naming convention.
>>
>> And also with this there is a version upgrade of jxl from 2.6.8 to
>> 2.6.12
>>
>> New groupId : org.wso2.orbit.net.sourceforge.jexcelapi
>> artifactId : jxl
>>
>> *joda-time*
>> ===
>> This orbit [4] also with groupID "joda-time.wso2" which also not
>> match with current WSO2 orbit groupID naming convention. For next release
>> of BRS, need version upgrade 1.6.0 to 2.8.2 with proper orbit groupID
>> naming convention
>>
>> New groupId : org.wso2.orbit.joda-time
>> artifactId : joda-time
>>
>> *dools*
>> 
>> Version upgrade from 6.0.1 to 6.3.0.
>> GroupID also revamped to match current convention
>>
>> New groupId : org.wso2.orbit.org.drools
>> artifactId : drools
>>
>>
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jsr94/
>> [2]
>> https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/janino
>> [3] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jxl/
>> [4]
>> https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/joda-time
>>
>> 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
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>



 --
 Milinda Perera
 Software Engineer;
 WSO2 Inc. http://wso2.com ,
 Mobile: (+94) 714 115 032


>>>
>>>
>>> --
>>> Milinda Perera
>>> Software Engineer;
>>> WSO2 Inc. http://wso2.com ,
>>> Mobile: (+94) 714 115 032
>>>
>>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *| Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.wso2.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> 

Re: [Dev] WSO2 MSS JAX-RS Runtime Features

2015-10-14 Thread Sameera Jayasoma
+1. Since we are providing a subset of JAX-RC specification, we need to be
clear on what we support. Otherwise we will get into trouble later. This
got to be a public doc.

Initially we forked netty-http to process JAX-RC annotations, but later
decided to completely revamp that implementation. Can you give us a summary
of the changes we have introduced.

Thanks,
Sameera.

On Thu, Oct 15, 2015 at 10:39 AM, Samiyuru Senarathne 
wrote:

> Sure, we will.
>
> On Thu, Oct 15, 2015 at 10:33 AM, Sagara Gunathunga 
> wrote:
>
>>
>> Shall we also create a doc with all JAX-RS annotations, extensions and
>> mentioning what MSS supported and what not supported ?
>>
>> Thanks !
>>
>> On Thu, Oct 15, 2015 at 10:30 AM, Samiyuru Senarathne 
>> wrote:
>>
>>> Hi,
>>>
>>> We have been developing our own JAX-RS runtime for WSO2 Micro Services
>>> Server (MSS). The purpose of that runtime is not to support the full JAX-RS
>>> specification but to support a subset of the JAX-RS specification plus a
>>> set of additional features focusing on performance and lightweightness to
>>> run microservices.
>>>
>>> With latest development work currently the MSS JAX-RS runtime supports
>>> the following features.
>>>
>>>- The runtime can process annotated POJO JAX-RS resource classes and
>>>their annotated methods to create REST service endpoints for valid 
>>> resource
>>>methods.
>>>- The runtime supports the following class level annotations.
>>>   - @Path - Root path for resource methods
>>>   - @Consumes - Default consume media type(s) for resource methods
>>>   - @Produces - Default produce media type(s) for resource methods
>>>- Supports the following method level annotations.
>>>   - @Path - Endpoint of the method relative to @Path of the class
>>>   - @Consumes - Media type(s) that the method can consume
>>>   - @Produces - Media type(s) that is produced by the method
>>>   - @GET - HTTP GET method
>>>   - @PUT - HTTP PUT method
>>>   - @POST - HTTP POST method
>>>   - @DELETE - HTTP DELETE method
>>>- Supports the following parameter level annotations.
>>>   - @DefaultValue - Specify a default parameter value
>>>   - @Context - Inject additional objects. Currently supports
>>>   injection of io.netty.handler.codec.http.HttpRequest and
>>>   org.wso2.carbon.mss.HttpResponder
>>>   - @PathParam - /StockQuote/{*symbol*} to get value of symbol
>>>   - @QueryParam - /Students?*age=18* to get value of age
>>>   - @HeaderParam - To read HTTP request header values
>>>- Supports returning POJO from resource methods to response by xml
>>>or json and getting injected POJO to resource methods for request bodies
>>>that are json or xml.
>>>- Supports returning *javax.ws.rs.core.Response* objects from
>>>resource methods to send HTTP responses in a more customised way.
>>>
>>> Product-MSS repository url: https://github.com/wso2/product-mss
>>>
>>> Best Regards,
>>> Samiyuru
>>> --
>>> Samiyuru Senarathne
>>> *Software Engineer*
>>> Mobile : +94 (0) 71 134 6087
>>> samiy...@wso2.com
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Architect; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services;http://ws.apache.org/
>> Linkedin; http://www.linkedin.com/in/ssagara
>> Blog ;  http://ssagara.blogspot.com
>>
>>
>
>
> --
> Samiyuru Senarathne
> *Software Engineer*
> Mobile : +94 (0) 71 134 6087
> samiy...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sameera Jayasoma,
Software Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://blog.sameera.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

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