[Dev] Is there a way to manually expire all active tokens in AM

2013-07-12 Thread Supun Malinga
Hi,

$subject?
Would like to know the possible options/workarounds..

thanks,
-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 
mobile - 071 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] User Core API refactoring

2013-07-12 Thread Prabath Siriwardena
Also.. following method too not needed..

String[] getHybridRoles() throws UserStoreException;

Thanks & regards,
-Prabath

On Sat, Jul 13, 2013 at 12:00 PM, Prabath Siriwardena wrote:

> Why do we need Permission in UsetStoreManager API.Planning to remove this
> out.. If any objections please shout...
>
> void addRole(String roleName, String[] userList, Permission[] permissions)
>  throws UserStoreException;
>
>
> Thanks & Regards,
> Prabath
>
> Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>



-- 
Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

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


[Dev] User Core API refactoring

2013-07-12 Thread Prabath Siriwardena
Why do we need Permission in UsetStoreManager API.Planning to remove this
out.. If any objections please shout...

void addRole(String roleName, String[] userList, Permission[] permissions)
throws UserStoreException;


Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

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


Re: [Dev] Multiple Synapse versions on trunk

2013-07-12 Thread Jeewantha Dharmaparakrama
Already removed synapse v7 in commit r177645


On Fri, Jul 12, 2013 at 10:36 PM, Isuru Udana  wrote:

> Yes we have to remove 2.1.1-wso2v7.
>
> @Jeewantha,
> If you have completed updating synapse version to 2.1.1-wso2v8, please
> remove 2.1.1-wso2v7.
>
> Thanks.
>
>
>
>
> On Fri, Jul 12, 2013 at 10:17 PM, Sagara Gunathunga wrote:
>
>>
>> We have 2.1.1-wso2v7  and 2.1.1-wso2v8 versions on trunk, can we get rid
>> of 2.1.1-wso2v7 ?
>>
>> Thanks !
>>
>> --
>> Sagara Gunathunga
>>
>> Senior Technical Lead; 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
>>
>>
>
>
> --
> *Isuru Udana*
> *
>  *
> Senior *
> Software Engineer
> *
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>



-- 
Jeewantha Dharmaparakrama
Software Engineer; WSO2, Inc.; http://wso2.com/
Phone : (+94) 774726790
Skype : prasad.jeewantha
LinkedIn : http://www.linkedin.com/in/jeewanthad
Twitter: https://twitter.com/jeewamp
Blog: http://jeewanthad.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] SecurityException: Key Store with a name : domain2.jks does not exist

2013-07-12 Thread Dimuthu Leelarathne
On Sat, Jul 13, 2013 at 12:29 AM, Manjula Rathnayake wrote:

> Hi Dimuthu,
>
> Just to understand the scenario,
> 1. Is it the normal AF deployment and you are trying to login to AF appmgt
> app?
>

yes to both. My tenant can successfully login to the carbon console of AF
now. :) But that is not SSO.


> 2. Have we updated Identity features recently?
>

No


> 3. Have we configured other carbon servers as service providers in AF
> setup, currently, only the appmgt, publisher and store are the service
> providers
>

Nothing is changed. Same setup.

thanks,
dimuthu


>
> Regarding the above issue, domain2 is the tenant(or application name)  and
> Identity server looks for default jks of tenant(AFAIR this is created at
> tenant creation time) not the super tenant one. I can not figure out such a
> scenario we use tenancy jks.
>
> thank you.
>
>
> On Fri, Jul 12, 2013 at 7:00 AM, Dimuthu Leelarathne wrote:
>
>> Hi,
>>
>> I am trying to login to appmgt with of AF with SSO, as a tenant and
>> getting the following exception. Any pointers on where I should look at?
>>
>> [2013-07-12 19:27:39,534] ERROR
>> {org.wso2.carbon.identity.sso.saml.processors.AuthnRequestProcessor} -
>> Error processing the authentication request
>> org.wso2.carbon.identity.base.IdentityException: Key Store with a name :
>> domain2.jks does not exist.
>> at
>> org.wso2.carbon.identity.sso.saml.builders.SignKeyDataHolder.(SignKeyDataHolder.java:135)
>> at
>> org.wso2.carbon.identity.sso.saml.builders.ResponseBuilder.buildResponse(ResponseBuilder.java:96)
>> at
>> org.wso2.carbon.identity.sso.saml.processors.AuthnRequestProcessor.process(AuthnRequestProcessor.java:154)
>> at
>> org.wso2.carbon.identity.sso.saml.SAMLSSOService.authenticate(SAMLSSOService.java:113)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> 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:398)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>> at
>> org.wso2.carbon.identity.sso.saml.stub.IdentitySAMLSSOServiceStub.authenticate(IdentitySAMLSSOServiceStub.java:783)
>> at
>> org.wso2.carbon.identity.sso.saml.ui.client.SAMLSSOServiceClient.authenticate(SAMLSSOServiceClient.java:81)
>> at
>> org.wso2.carbon.identity.sso.saml.ui.SAMLSSOProvider.handleRequestFromLoginPage(SAMLSSOProvider.java:323)
>> at
>> org.wso2.carbon.identity.sso.saml.ui.SAMLSSOProvider.doPost(SAMLSSOProvider.java:131)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>> 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:60)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>> at
>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>> at
>> org.apache.catal

Re: [Dev] Several service components in AppServer are in the Unsatisfied state

2013-07-12 Thread Afkham Azeez
Please look into the following Unsatisfied SCs. These will lead to critical
runtime bugs. I will take a look at the caching SC.

41 Unsatisfied wsevent.component.admin org.wso2.carbon.event.admin(bid=222)
42 Unsatisfied eventbrokerbuilder.component
org.wso2.carbon.event.core(bid=226)
43 Unsatisfied wsevent.component org.wso2.carbon.event.ws(bid=229)
63 Unsatisfied org.wso2.carbon.registry.eventing
org.wso2.carbon.registry.eventing(bid=324)
66 Unsatisfied registry.search.dscomponent
org.wso2.carbon.registry.search(bid=331)
85 Unsatisfied task.manager.componenet org.wso2.carbon.task(bid=381)



On Fri, Jul 12, 2013 at 9:53 PM, Sagara Gunathunga  wrote:

>
>
>
> On Fri, Jul 12, 2013 at 8:59 PM, Afkham Azeez  wrote:
>
>> The reason why the WebappMgtServiceComponent is not getting activated is
>> because the org.wso2.carbon.url.mapper bundle is missing in AS. Can
>> somebody look into it?
>>
>
>
> But the problem is why we need url-mapper in AS, there is no UI option, no
> configuration option and I can't recall any usage of url-mapper within AS.
> As I remember during AS 5.0.0 release cycle we tried  to add url-mapper to
> AS but due to number of issues we haven't do that. IMHO let's review this
> and remove this bundle if there is no real usage within AS.
>
> Thanks !
>
>>
>> Azeez
>>
>>
>> On Thu, Jul 11, 2013 at 10:55 PM, Afkham Azeez  wrote:
>>
>>> All Components:
>>> ID State Component Name Located in bundle
>>> 1 Unsatisfied
>>> org.wso2.carbon.caching.impl.internal.CachingServiceComponent
>>> javax.cache.wso2(bid=65)
>>> 2 Registered org.eclipse.equinox.frameworkadmin.equinox
>>> org.eclipse.equinox.frameworkadmin.equinox(bid=115)
>>> 3 Active org.eclipse.equinox.p2.artifact.repository
>>> org.eclipse.equinox.p2.artifact.repository(bid=121)
>>> 4 Active org.eclipse.equinox.p2.core.eventbus
>>> org.eclipse.equinox.p2.core(bid=123)
>>> 5 Active org.eclipse.equinox.p2.di.agentProvider
>>> org.eclipse.equinox.p2.core(bid=123)
>>> 6 Registered org.eclipse.equinox.p2.director
>>> org.eclipse.equinox.p2.director(bid=124)
>>> 7 Active org.eclipse.equinox.p2.planner
>>> org.eclipse.equinox.p2.director(bid=124)
>>> 8 Active org.eclipse.equinox.p2.engine.registry
>>> org.eclipse.equinox.p2.engine(bid=127)
>>> 9 Active org.eclipse.equinox.p2.engine
>>> org.eclipse.equinox.p2.engine(bid=127)
>>> 10 Active org.eclipse.equinox.p2.garbagecollector
>>> org.eclipse.equinox.p2.garbagecollector(bid=129)
>>> 11 Active org.eclipse.equinox.p2.metadata.repository
>>> org.eclipse.equinox.p2.metadata.repository(bid=132)
>>> 12 Registered org.eclipse.equinox.p2.repository
>>> org.eclipse.equinox.p2.repository(bid=135)
>>> 13 Registered org.eclipse.equinox.p2.transport.ecf
>>> org.eclipse.equinox.p2.transport.ecf(bid=139)
>>> 14 Registered org.eclipse.equinox.p2.updatechecker
>>> org.eclipse.equinox.p2.updatechecker(bid=140)
>>> 15 Registered org.eclipse.equinox.simpleconfigurator.manipulator
>>> org.eclipse.equinox.simpleconfigurator.manipulator(bid=145)
>>> 16 Active mashup.javascript.hostobjects.registry.dscomponent
>>> org.jaggeryjs.hostobjects.registry(bid=155)
>>> 17 Active mashup.javascript.hostobjects.wsrequest.dscomponent
>>> org.jaggeryjs.hostobjects.ws(bid=159)
>>> 18 Active
>>> org.jaggeryjs.jaggery.app.mgt.internal.JaggeryappManagementServiceComponent
>>> org.jaggeryjs.jaggery.app.mgt(bid=162)
>>> 19 Active org.jaggeryjs.jaggery.core org.jaggeryjs.jaggery.core(bid=165)
>>> 20 Active org.wso2.carbon.metering org.wso2.carbon.activation(bid=175)
>>> 21 Active application.deployer.dscomponent
>>> org.wso2.carbon.application.deployer(bid=178)
>>> 22 Active application.deployer.mashup
>>> org.wso2.carbon.application.deployer.mashup(bid=179)
>>> 23 Active application.deployer.war
>>> org.wso2.carbon.application.deployer.webapp(bid=180)
>>> 24 Active application.mgt.dscomponent
>>> org.wso2.carbon.application.mgt(bid=181)
>>> 25 Active application.mgt.webapp.dscomponent
>>> org.wso2.carbon.application.mgt.webapp(bid=184)
>>> 26 Active org.wso2.carbon.bam.service.data.publisher
>>> org.wso2.carbon.bam.service.data.publisher(bid=191)
>>> 27 Active
>>> org.wso2.carbon.captcha.mgt.internal.CaptchaMgtServiceComponent
>>> org.wso2.carbon.captcha.mgt(bid=198)
>>> 28 Active coordination.client.component
>>> org.wso2.carbon.coordination.core(bid=201)
>>> 29 Active carbon.core.dscomponent org.wso2.carbon.core(bid=202)
>>> 30 Active
>>> org.wso2.carbon.core.internal.ListenerManagerRetrieverServiceComponent
>>> org.wso2.carbon.core(bid=202)
>>> 31 Active org.wso2.carbon.core.internal.StartupFinalizerServiceComponent
>>> org.wso2.carbon.core(bid=202)
>>> 32 Active
>>> org.wso2.stratos.permission.update.PermissionUpdateServiceComponent
>>> org.wso2.carbon.core(bid=202)
>>> 33 Active MIMEType2FileExtensionMap.component
>>> org.wso2.carbon.core(bid=202)
>>> 34 Active core.services.dscomponent
>>> org.wso2.carbon.core.services(bid=206)
>>> 35 Active agentservice.component
>>> org.wso2.carbon.databridge.agent.thrift(bid=207)
>>> 36 Active data

Re: [Dev] An essential integration test for every product

2013-07-12 Thread Krishantha Samaraweera
Will write a sample test for this

Thanks,
Krishnatha.

On Sat, Jul 13, 2013 at 4:54 AM, Afkham Azeez  wrote:

> One of the problems that you would come across at runtime would be due to
> ServiceComponents being in the "Unsatisfied" state. The server startup
> could be successful but the server is not in a correct running state
> because of these unsatisfied SCs. I came across such a scenario in AS,
> where webapp & tenant lazy loading did not work because of this issue.
>
> If we could startup the server with the OSGi console enabled, do an ls,
> and grep for "Unsatified" during integration testing, we can catch these
> situation easily. Otherwise, critical issues may show up after we release
> or during production.
>
> Azeez
>
> --
> *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 3320919
> blog: **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


[Dev] An essential integration test for every product

2013-07-12 Thread Afkham Azeez
One of the problems that you would come across at runtime would be due to
ServiceComponents being in the "Unsatisfied" state. The server startup
could be successful but the server is not in a correct running state
because of these unsatisfied SCs. I came across such a scenario in AS,
where webapp & tenant lazy loading did not work because of this issue.

If we could startup the server with the OSGi console enabled, do an ls, and
grep for "Unsatified" during integration testing, we can catch these
situation easily. Otherwise, critical issues may show up after we release
or during production.

Azeez

-- 
*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 3320919
blog: **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


[Dev] [Bamboo-Build] Developer Studio > Eclipse-Tools > #1032 was SUCCESSFUL. Change made by Viraj Rajaguru.

2013-07-12 Thread Bamboo

---
Developer Studio > Eclipse-Tools > #1032 was successful.
---
Code has been updated by Viraj Rajaguru.

http://wso2.org/bamboo/browse/DS0001-DSET01-1032/




--
Code Changes
--
Viraj Rajaguru (178154):

>Fixing TOOLS-1715



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [Bamboo-Build] Developer Studio > Eclipse-Tools > #1031 has FAILED. Change made by Viraj Rajaguru.

2013-07-12 Thread Bamboo

---
Developer Studio > Eclipse-Tools > #1031 failed.
---
Code has been updated by Viraj Rajaguru.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/DS0001-DSET01-1031/

-
Currently Responsible
-

Viraj Rajaguru (Automatically assigned)



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
Viraj Rajaguru (178152):

>Fixing TOOLS-1715

Viraj Rajaguru (178153):

>Fixing TOOLS-1715

Viraj Rajaguru (178151):

>Fixing TOOLS-1715



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] SecurityException: Key Store with a name : domain2.jks does not exist

2013-07-12 Thread Manjula Rathnayake
Hi Dimuthu,

Just to understand the scenario,
1. Is it the normal AF deployment and you are trying to login to AF appmgt
app?
2. Have we updated Identity features recently?
3. Have we configured other carbon servers as service providers in AF
setup, currently, only the appmgt, publisher and store are the service
providers.

Regarding the above issue, domain2 is the tenant(or application name)  and
Identity server looks for default jks of tenant(AFAIR this is created at
tenant creation time) not the super tenant one. I can not figure out such a
scenario we use tenancy jks.

thank you.


On Fri, Jul 12, 2013 at 7:00 AM, Dimuthu Leelarathne wrote:

> Hi,
>
> I am trying to login to appmgt with of AF with SSO, as a tenant and
> getting the following exception. Any pointers on where I should look at?
>
> [2013-07-12 19:27:39,534] ERROR
> {org.wso2.carbon.identity.sso.saml.processors.AuthnRequestProcessor} -
> Error processing the authentication request
> org.wso2.carbon.identity.base.IdentityException: Key Store with a name :
> domain2.jks does not exist.
> at
> org.wso2.carbon.identity.sso.saml.builders.SignKeyDataHolder.(SignKeyDataHolder.java:135)
> at
> org.wso2.carbon.identity.sso.saml.builders.ResponseBuilder.buildResponse(ResponseBuilder.java:96)
> at
> org.wso2.carbon.identity.sso.saml.processors.AuthnRequestProcessor.process(AuthnRequestProcessor.java:154)
> at
> org.wso2.carbon.identity.sso.saml.SAMLSSOService.authenticate(SAMLSSOService.java:113)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:398)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.identity.sso.saml.stub.IdentitySAMLSSOServiceStub.authenticate(IdentitySAMLSSOServiceStub.java:783)
> at
> org.wso2.carbon.identity.sso.saml.ui.client.SAMLSSOServiceClient.authenticate(SAMLSSOServiceClient.java:81)
> at
> org.wso2.carbon.identity.sso.saml.ui.SAMLSSOProvider.handleRequestFromLoginPage(SAMLSSOProvider.java:323)
> at
> org.wso2.carbon.identity.sso.saml.ui.SAMLSSOProvider.doPost(SAMLSSOProvider.java:131)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> 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:60)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authent

Re: [Dev] Please refrain from doing changes to user.core and user.api till next Monday...

2013-07-12 Thread Prabath Siriwardena
Gentle Reminder..!!! I've take up just now..

Thanks & regards,
-Prabath

On Thu, Jul 11, 2013 at 12:42 PM, Prabath Siriwardena wrote:

> Hi folks,
>
> I am working on doing some core changes in user.api and user.core.. so
> please refrain from doing any changes in those components..
>
> If you need to do any changes please talk to me...
>
> --
> Thanks & Regards,
> Prabath
>
> Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>



-- 
Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

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


Re: [Dev] Several service components in AppServer are in the Unsatisfied state

2013-07-12 Thread Afkham Azeez
We will have to bring back URL mapped with the aPaaS effort.

Azeez


On Fri, Jul 12, 2013 at 9:53 PM, Sagara Gunathunga  wrote:

>
>
>
> On Fri, Jul 12, 2013 at 8:59 PM, Afkham Azeez  wrote:
>
>> The reason why the WebappMgtServiceComponent is not getting activated is
>> because the org.wso2.carbon.url.mapper bundle is missing in AS. Can
>> somebody look into it?
>>
>
>
> But the problem is why we need url-mapper in AS, there is no UI option, no
> configuration option and I can't recall any usage of url-mapper within AS.
> As I remember during AS 5.0.0 release cycle we tried  to add url-mapper to
> AS but due to number of issues we haven't do that. IMHO let's review this
> and remove this bundle if there is no real usage within AS.
>
> Thanks !
>
>>
>> Azeez
>>
>>
>> On Thu, Jul 11, 2013 at 10:55 PM, Afkham Azeez  wrote:
>>
>>> All Components:
>>> ID State Component Name Located in bundle
>>> 1 Unsatisfied
>>> org.wso2.carbon.caching.impl.internal.CachingServiceComponent
>>> javax.cache.wso2(bid=65)
>>> 2 Registered org.eclipse.equinox.frameworkadmin.equinox
>>> org.eclipse.equinox.frameworkadmin.equinox(bid=115)
>>> 3 Active org.eclipse.equinox.p2.artifact.repository
>>> org.eclipse.equinox.p2.artifact.repository(bid=121)
>>> 4 Active org.eclipse.equinox.p2.core.eventbus
>>> org.eclipse.equinox.p2.core(bid=123)
>>> 5 Active org.eclipse.equinox.p2.di.agentProvider
>>> org.eclipse.equinox.p2.core(bid=123)
>>> 6 Registered org.eclipse.equinox.p2.director
>>> org.eclipse.equinox.p2.director(bid=124)
>>> 7 Active org.eclipse.equinox.p2.planner
>>> org.eclipse.equinox.p2.director(bid=124)
>>> 8 Active org.eclipse.equinox.p2.engine.registry
>>> org.eclipse.equinox.p2.engine(bid=127)
>>> 9 Active org.eclipse.equinox.p2.engine
>>> org.eclipse.equinox.p2.engine(bid=127)
>>> 10 Active org.eclipse.equinox.p2.garbagecollector
>>> org.eclipse.equinox.p2.garbagecollector(bid=129)
>>> 11 Active org.eclipse.equinox.p2.metadata.repository
>>> org.eclipse.equinox.p2.metadata.repository(bid=132)
>>> 12 Registered org.eclipse.equinox.p2.repository
>>> org.eclipse.equinox.p2.repository(bid=135)
>>> 13 Registered org.eclipse.equinox.p2.transport.ecf
>>> org.eclipse.equinox.p2.transport.ecf(bid=139)
>>> 14 Registered org.eclipse.equinox.p2.updatechecker
>>> org.eclipse.equinox.p2.updatechecker(bid=140)
>>> 15 Registered org.eclipse.equinox.simpleconfigurator.manipulator
>>> org.eclipse.equinox.simpleconfigurator.manipulator(bid=145)
>>> 16 Active mashup.javascript.hostobjects.registry.dscomponent
>>> org.jaggeryjs.hostobjects.registry(bid=155)
>>> 17 Active mashup.javascript.hostobjects.wsrequest.dscomponent
>>> org.jaggeryjs.hostobjects.ws(bid=159)
>>> 18 Active
>>> org.jaggeryjs.jaggery.app.mgt.internal.JaggeryappManagementServiceComponent
>>> org.jaggeryjs.jaggery.app.mgt(bid=162)
>>> 19 Active org.jaggeryjs.jaggery.core org.jaggeryjs.jaggery.core(bid=165)
>>> 20 Active org.wso2.carbon.metering org.wso2.carbon.activation(bid=175)
>>> 21 Active application.deployer.dscomponent
>>> org.wso2.carbon.application.deployer(bid=178)
>>> 22 Active application.deployer.mashup
>>> org.wso2.carbon.application.deployer.mashup(bid=179)
>>> 23 Active application.deployer.war
>>> org.wso2.carbon.application.deployer.webapp(bid=180)
>>> 24 Active application.mgt.dscomponent
>>> org.wso2.carbon.application.mgt(bid=181)
>>> 25 Active application.mgt.webapp.dscomponent
>>> org.wso2.carbon.application.mgt.webapp(bid=184)
>>> 26 Active org.wso2.carbon.bam.service.data.publisher
>>> org.wso2.carbon.bam.service.data.publisher(bid=191)
>>> 27 Active
>>> org.wso2.carbon.captcha.mgt.internal.CaptchaMgtServiceComponent
>>> org.wso2.carbon.captcha.mgt(bid=198)
>>> 28 Active coordination.client.component
>>> org.wso2.carbon.coordination.core(bid=201)
>>> 29 Active carbon.core.dscomponent org.wso2.carbon.core(bid=202)
>>> 30 Active
>>> org.wso2.carbon.core.internal.ListenerManagerRetrieverServiceComponent
>>> org.wso2.carbon.core(bid=202)
>>> 31 Active org.wso2.carbon.core.internal.StartupFinalizerServiceComponent
>>> org.wso2.carbon.core(bid=202)
>>> 32 Active
>>> org.wso2.stratos.permission.update.PermissionUpdateServiceComponent
>>> org.wso2.carbon.core(bid=202)
>>> 33 Active MIMEType2FileExtensionMap.component
>>> org.wso2.carbon.core(bid=202)
>>> 34 Active core.services.dscomponent
>>> org.wso2.carbon.core.services(bid=206)
>>> 35 Active agentservice.component
>>> org.wso2.carbon.databridge.agent.thrift(bid=207)
>>> 36 Active dataservices.component
>>> org.wso2.carbon.dataservices.core(bid=211)
>>> 37 Active org.wso2.carbon.deployment.synchronizer.XXX
>>> org.wso2.carbon.deployment.synchronizer(bid=216)
>>> 38 Active org.wso2.carbon.deployment.synchronizer.subversion
>>> org.wso2.carbon.deployment.synchronizer.subversion(bid=217)
>>> 39 Active org.wso2.carbon.discovery
>>> org.wso2.carbon.discovery.core(bid=219)
>>> 40 Active
>>> org.wso2.carbon.email.verification.internal.EmailVerificationServiceComponent
>>> org.wso2.carbon.email.verification(bid=2

Re: [Dev] Multiple Synapse versions on trunk

2013-07-12 Thread Isuru Udana
Yes we have to remove 2.1.1-wso2v7.

@Jeewantha,
If you have completed updating synapse version to 2.1.1-wso2v8, please
remove 2.1.1-wso2v7.

Thanks.




On Fri, Jul 12, 2013 at 10:17 PM, Sagara Gunathunga  wrote:

>
> We have 2.1.1-wso2v7  and 2.1.1-wso2v8 versions on trunk, can we get rid
> of 2.1.1-wso2v7 ?
>
> Thanks !
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; 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
>
>


-- 
*Isuru Udana*
*
 *
Senior *
Software Engineer
*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Multiple Synapse versions on trunk

2013-07-12 Thread Sagara Gunathunga
We have 2.1.1-wso2v7  and 2.1.1-wso2v8 versions on trunk, can we get rid of
2.1.1-wso2v7 ?

Thanks !

-- 
Sagara Gunathunga

Senior Technical Lead; 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] [Architecture] WSO2 CEP 3.0.0 Milestone 2 Released!

2013-07-12 Thread Srinath Perera
Lets add a jira, and fix that.

--Srinath


On Fri, Jul 12, 2013 at 9:55 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> Hi,
>
> Yes that's true, But at the moment we don't have any time associated with
> "not occurrence"... We need to flush the data out from event
> tables separately,
> or we need to find any other approach.. I think Suho can add more on
> this...
>
> Regards,
> Mohan
>
>
> On Fri, Jul 12, 2013 at 1:39 PM, Srinath Perera  wrote:
>
>> Hi Mohan,
>>
>> Is there a time period associated with "not occurrence"? I think we need
>> to have that or we will fill up the disk and slow it down as time passes.
>>
>> --Srinath
>>
>>
>> On Wed, Jul 10, 2013 at 6:31 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> Hi Cyril,
>>>
>>> We are on the way of creating the documentation for CEP 3.0.0...
>>> We'll share the documentation with the CEP 3.0.0 release soon...
>>>
>>> Yes, 'non occurrence' of events is already implemented and can be
>>> achieved using the event tables in CEP 3.0.0..
>>>
>>> We'll update when CEP 3.0.0 released... Thanks for your interest on
>>> CEP...
>>>
>>> Regards,
>>> Mohan
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Jul 10, 2013 at 1:47 PM, Cyril Rognon  wrote:
>>>
 Hello cep team,

 thank you for this new milestone. I am wondering if there is any
 documentation link for  the upcoming 3.0.0 version.

 As far as I know, there is still no logical 'not' operator that we
 could use to filter the 'non occurrence' of events

 in siddhi language there is

 * **::=  *

 it would be nice to be able to say*
 *

 * **::= not  *
 I reckon I have not looked into the code to evaluate the cost of this
 requirement, so feel free to turn it down if it is prohibitive.

 Maybe eventTables will allow one to simulate this ?

 thanks,
 Cyril


 On Fri, Jul 5, 2013 at 10:47 PM, Mohanadarshan Vivekanandalingam <
 mo...@wso2.com> wrote:

> *WSO2 Complex Event Processor 3.0.0 Milestone 2 Released!*
>
> Date :5th July 2013
>
> This milestone is available at :
> https://svn.wso2.org/repos/wso2/people/suho/packs/cep/3.0.0/wso2cep-3.0.0-M2.zip
>
> To run the samples please follow the read-me,
> wso2cep-3.0.0/samples/cep-samples/ReadMe.txt
>
>
> Following are the bug fixes, improvements and the new features
>
> Bug
>
>- [CEP-258 ] - When trying
>to deploy the multiple configuration files, File reference is missing
>- [CEP-261 ] - Table is not
>properly generated when creating WSO2 Event mapping and Map mapping
>
> Improvement
>
>- [CEP-179 ] - It is better
>if the UI supports to check the validity of "Event Sink URL" when
>subscribing to a topic
>- [CEP-243 ] - Separate
>implementation classes & UI for handing in/out sequences of transport
>adapators
>- [CEP-247 ] - Making
>Coalesce as a ExecutorFunction
>- [CEP-248 ] - Removing
>conversion types from output attribute processor
>- [CEP-249 ] - Replacing
>Condition Extentions using bool returning Expression Extentions
>- [CEP-251 ] - White-board
>pattern for Transport Adaptors and Event sources
>- [CEP-257 ] - Event Tracer
>output in UI need to be formatted
>- [CEP-260 ] - UI to
>retrieve the deployed Event Formatter configuration details
>- [CEP-262 ] -
>EventFormatter to receive WSO2Event and format it to other different
>types.. For products like BAM
>- [CEP-267 ] -
>Listing/editing undeployed event builders
>- [CEP-268 ] - Handing
>dependency between the components when removing the configuration files
>
> New Feature
>
>- [CEP-156 ] - Add a default
>timeStamp convertor
>- [CEP-162 ] - Add Attribute
>Type Convetors to Siddhi
>- [CEP-215 ] - Adding
>snapshot output support for Siddhi window
>- [CEP-231 ] - New component
>called "EventFormatter" to handle the events when sending out from the 
> CEP
>- [CEP-250 ] -
>IsMatchExecutorFunction to regex matching
>

Re: [Dev] [Architecture] WSO2 CEP 3.0.0 Milestone 2 Released!

2013-07-12 Thread Mohanadarshan Vivekanandalingam
Hi,

Yes that's true, But at the moment we don't have any time associated with
"not occurrence"... We need to flush the data out from event
tables separately,
or we need to find any other approach.. I think Suho can add more on this...

Regards,
Mohan


On Fri, Jul 12, 2013 at 1:39 PM, Srinath Perera  wrote:

> Hi Mohan,
>
> Is there a time period associated with "not occurrence"? I think we need
> to have that or we will fill up the disk and slow it down as time passes.
>
> --Srinath
>
>
> On Wed, Jul 10, 2013 at 6:31 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> Hi Cyril,
>>
>> We are on the way of creating the documentation for CEP 3.0.0...
>> We'll share the documentation with the CEP 3.0.0 release soon...
>>
>> Yes, 'non occurrence' of events is already implemented and can be
>> achieved using the event tables in CEP 3.0.0..
>>
>> We'll update when CEP 3.0.0 released... Thanks for your interest on CEP...
>>
>> Regards,
>> Mohan
>>
>>
>>
>>
>>
>> On Wed, Jul 10, 2013 at 1:47 PM, Cyril Rognon  wrote:
>>
>>> Hello cep team,
>>>
>>> thank you for this new milestone. I am wondering if there is any
>>> documentation link for  the upcoming 3.0.0 version.
>>>
>>> As far as I know, there is still no logical 'not' operator that we could
>>> use to filter the 'non occurrence' of events
>>>
>>> in siddhi language there is
>>>
>>> * **::=  *
>>>
>>> it would be nice to be able to say*
>>> *
>>>
>>> * **::= not  *
>>> I reckon I have not looked into the code to evaluate the cost of this
>>> requirement, so feel free to turn it down if it is prohibitive.
>>>
>>> Maybe eventTables will allow one to simulate this ?
>>>
>>> thanks,
>>> Cyril
>>>
>>>
>>> On Fri, Jul 5, 2013 at 10:47 PM, Mohanadarshan Vivekanandalingam <
>>> mo...@wso2.com> wrote:
>>>
 *WSO2 Complex Event Processor 3.0.0 Milestone 2 Released!*

 Date :5th July 2013

 This milestone is available at :
 https://svn.wso2.org/repos/wso2/people/suho/packs/cep/3.0.0/wso2cep-3.0.0-M2.zip

 To run the samples please follow the read-me,
 wso2cep-3.0.0/samples/cep-samples/ReadMe.txt


 Following are the bug fixes, improvements and the new features

 Bug

- [CEP-258 ] - When trying to
deploy the multiple configuration files, File reference is missing
- [CEP-261 ] - Table is not
properly generated when creating WSO2 Event mapping and Map mapping

 Improvement

- [CEP-179 ] - It is better
if the UI supports to check the validity of "Event Sink URL" when
subscribing to a topic
- [CEP-243 ] - Separate
implementation classes & UI for handing in/out sequences of transport
adapators
- [CEP-247 ] - Making
Coalesce as a ExecutorFunction
- [CEP-248 ] - Removing
conversion types from output attribute processor
- [CEP-249 ] - Replacing
Condition Extentions using bool returning Expression Extentions
- [CEP-251 ] - White-board
pattern for Transport Adaptors and Event sources
- [CEP-257 ] - Event Tracer
output in UI need to be formatted
- [CEP-260 ] - UI to retrieve
the deployed Event Formatter configuration details
- [CEP-262 ] - EventFormatter
to receive WSO2Event and format it to other different types.. For 
 products
like BAM
- [CEP-267 ] -
Listing/editing undeployed event builders
- [CEP-268 ] - Handing
dependency between the components when removing the configuration files

 New Feature

- [CEP-156 ] - Add a default
timeStamp convertor
- [CEP-162 ] - Add Attribute
Type Convetors to Siddhi
- [CEP-215 ] - Adding
snapshot output support for Siddhi window
- [CEP-231 ] - New component
called "EventFormatter" to handle the events when sending out from the 
 CEP
- [CEP-250 ] -
IsMatchExecutorFunction to regex matching
- [CEP-252 ] - Wiring between
the components when adding the configuration files
- [CEP-253 ] -
ConvertExecutorFunction for type conversion
- [CEP-264 

Re: [Dev] Several service components in AppServer are in the Unsatisfied state

2013-07-12 Thread Sagara Gunathunga
On Fri, Jul 12, 2013 at 8:59 PM, Afkham Azeez  wrote:

> The reason why the WebappMgtServiceComponent is not getting activated is
> because the org.wso2.carbon.url.mapper bundle is missing in AS. Can
> somebody look into it?
>


But the problem is why we need url-mapper in AS, there is no UI option, no
configuration option and I can't recall any usage of url-mapper within AS.
As I remember during AS 5.0.0 release cycle we tried  to add url-mapper to
AS but due to number of issues we haven't do that. IMHO let's review this
and remove this bundle if there is no real usage within AS.

Thanks !

>
> Azeez
>
>
> On Thu, Jul 11, 2013 at 10:55 PM, Afkham Azeez  wrote:
>
>> All Components:
>> ID State Component Name Located in bundle
>> 1 Unsatisfied
>> org.wso2.carbon.caching.impl.internal.CachingServiceComponent
>> javax.cache.wso2(bid=65)
>> 2 Registered org.eclipse.equinox.frameworkadmin.equinox
>> org.eclipse.equinox.frameworkadmin.equinox(bid=115)
>> 3 Active org.eclipse.equinox.p2.artifact.repository
>> org.eclipse.equinox.p2.artifact.repository(bid=121)
>> 4 Active org.eclipse.equinox.p2.core.eventbus
>> org.eclipse.equinox.p2.core(bid=123)
>> 5 Active org.eclipse.equinox.p2.di.agentProvider
>> org.eclipse.equinox.p2.core(bid=123)
>> 6 Registered org.eclipse.equinox.p2.director
>> org.eclipse.equinox.p2.director(bid=124)
>> 7 Active org.eclipse.equinox.p2.planner
>> org.eclipse.equinox.p2.director(bid=124)
>> 8 Active org.eclipse.equinox.p2.engine.registry
>> org.eclipse.equinox.p2.engine(bid=127)
>> 9 Active org.eclipse.equinox.p2.engine
>> org.eclipse.equinox.p2.engine(bid=127)
>> 10 Active org.eclipse.equinox.p2.garbagecollector
>> org.eclipse.equinox.p2.garbagecollector(bid=129)
>> 11 Active org.eclipse.equinox.p2.metadata.repository
>> org.eclipse.equinox.p2.metadata.repository(bid=132)
>> 12 Registered org.eclipse.equinox.p2.repository
>> org.eclipse.equinox.p2.repository(bid=135)
>> 13 Registered org.eclipse.equinox.p2.transport.ecf
>> org.eclipse.equinox.p2.transport.ecf(bid=139)
>> 14 Registered org.eclipse.equinox.p2.updatechecker
>> org.eclipse.equinox.p2.updatechecker(bid=140)
>> 15 Registered org.eclipse.equinox.simpleconfigurator.manipulator
>> org.eclipse.equinox.simpleconfigurator.manipulator(bid=145)
>> 16 Active mashup.javascript.hostobjects.registry.dscomponent
>> org.jaggeryjs.hostobjects.registry(bid=155)
>> 17 Active mashup.javascript.hostobjects.wsrequest.dscomponent
>> org.jaggeryjs.hostobjects.ws(bid=159)
>> 18 Active
>> org.jaggeryjs.jaggery.app.mgt.internal.JaggeryappManagementServiceComponent
>> org.jaggeryjs.jaggery.app.mgt(bid=162)
>> 19 Active org.jaggeryjs.jaggery.core org.jaggeryjs.jaggery.core(bid=165)
>> 20 Active org.wso2.carbon.metering org.wso2.carbon.activation(bid=175)
>> 21 Active application.deployer.dscomponent
>> org.wso2.carbon.application.deployer(bid=178)
>> 22 Active application.deployer.mashup
>> org.wso2.carbon.application.deployer.mashup(bid=179)
>> 23 Active application.deployer.war
>> org.wso2.carbon.application.deployer.webapp(bid=180)
>> 24 Active application.mgt.dscomponent
>> org.wso2.carbon.application.mgt(bid=181)
>> 25 Active application.mgt.webapp.dscomponent
>> org.wso2.carbon.application.mgt.webapp(bid=184)
>> 26 Active org.wso2.carbon.bam.service.data.publisher
>> org.wso2.carbon.bam.service.data.publisher(bid=191)
>> 27 Active org.wso2.carbon.captcha.mgt.internal.CaptchaMgtServiceComponent
>> org.wso2.carbon.captcha.mgt(bid=198)
>> 28 Active coordination.client.component
>> org.wso2.carbon.coordination.core(bid=201)
>> 29 Active carbon.core.dscomponent org.wso2.carbon.core(bid=202)
>> 30 Active
>> org.wso2.carbon.core.internal.ListenerManagerRetrieverServiceComponent
>> org.wso2.carbon.core(bid=202)
>> 31 Active org.wso2.carbon.core.internal.StartupFinalizerServiceComponent
>> org.wso2.carbon.core(bid=202)
>> 32 Active
>> org.wso2.stratos.permission.update.PermissionUpdateServiceComponent
>> org.wso2.carbon.core(bid=202)
>> 33 Active MIMEType2FileExtensionMap.component
>> org.wso2.carbon.core(bid=202)
>> 34 Active core.services.dscomponent
>> org.wso2.carbon.core.services(bid=206)
>> 35 Active agentservice.component
>> org.wso2.carbon.databridge.agent.thrift(bid=207)
>> 36 Active dataservices.component
>> org.wso2.carbon.dataservices.core(bid=211)
>> 37 Active org.wso2.carbon.deployment.synchronizer.XXX
>> org.wso2.carbon.deployment.synchronizer(bid=216)
>> 38 Active org.wso2.carbon.deployment.synchronizer.subversion
>> org.wso2.carbon.deployment.synchronizer.subversion(bid=217)
>> 39 Active org.wso2.carbon.discovery
>> org.wso2.carbon.discovery.core(bid=219)
>> 40 Active
>> org.wso2.carbon.email.verification.internal.EmailVerificationServiceComponent
>> org.wso2.carbon.email.verification(bid=221)
>> 41 Unsatisfied wsevent.component.admin
>> org.wso2.carbon.event.admin(bid=222)
>> 42 Unsatisfied eventbrokerbuilder.component
>> org.wso2.carbon.event.core(bid=226)
>> 43 Unsatisfied wsevent.component org.wso2.carbon.event.ws(bid=229)
>> 44 Activ

Re: [Dev] Several service components in AppServer are in the Unsatisfied state

2013-07-12 Thread Afkham Azeez
The reason why the WebappMgtServiceComponent is not getting activated is
because the org.wso2.carbon.url.mapper bundle is missing in AS. Can
somebody look into it?

Azeez


On Thu, Jul 11, 2013 at 10:55 PM, Afkham Azeez  wrote:

> All Components:
> ID State Component Name Located in bundle
> 1 Unsatisfied
> org.wso2.carbon.caching.impl.internal.CachingServiceComponent
> javax.cache.wso2(bid=65)
> 2 Registered org.eclipse.equinox.frameworkadmin.equinox
> org.eclipse.equinox.frameworkadmin.equinox(bid=115)
> 3 Active org.eclipse.equinox.p2.artifact.repository
> org.eclipse.equinox.p2.artifact.repository(bid=121)
> 4 Active org.eclipse.equinox.p2.core.eventbus
> org.eclipse.equinox.p2.core(bid=123)
> 5 Active org.eclipse.equinox.p2.di.agentProvider
> org.eclipse.equinox.p2.core(bid=123)
> 6 Registered org.eclipse.equinox.p2.director
> org.eclipse.equinox.p2.director(bid=124)
> 7 Active org.eclipse.equinox.p2.planner
> org.eclipse.equinox.p2.director(bid=124)
> 8 Active org.eclipse.equinox.p2.engine.registry
> org.eclipse.equinox.p2.engine(bid=127)
> 9 Active org.eclipse.equinox.p2.engine
> org.eclipse.equinox.p2.engine(bid=127)
> 10 Active org.eclipse.equinox.p2.garbagecollector
> org.eclipse.equinox.p2.garbagecollector(bid=129)
> 11 Active org.eclipse.equinox.p2.metadata.repository
> org.eclipse.equinox.p2.metadata.repository(bid=132)
> 12 Registered org.eclipse.equinox.p2.repository
> org.eclipse.equinox.p2.repository(bid=135)
> 13 Registered org.eclipse.equinox.p2.transport.ecf
> org.eclipse.equinox.p2.transport.ecf(bid=139)
> 14 Registered org.eclipse.equinox.p2.updatechecker
> org.eclipse.equinox.p2.updatechecker(bid=140)
> 15 Registered org.eclipse.equinox.simpleconfigurator.manipulator
> org.eclipse.equinox.simpleconfigurator.manipulator(bid=145)
> 16 Active mashup.javascript.hostobjects.registry.dscomponent
> org.jaggeryjs.hostobjects.registry(bid=155)
> 17 Active mashup.javascript.hostobjects.wsrequest.dscomponent
> org.jaggeryjs.hostobjects.ws(bid=159)
> 18 Active
> org.jaggeryjs.jaggery.app.mgt.internal.JaggeryappManagementServiceComponent
> org.jaggeryjs.jaggery.app.mgt(bid=162)
> 19 Active org.jaggeryjs.jaggery.core org.jaggeryjs.jaggery.core(bid=165)
> 20 Active org.wso2.carbon.metering org.wso2.carbon.activation(bid=175)
> 21 Active application.deployer.dscomponent
> org.wso2.carbon.application.deployer(bid=178)
> 22 Active application.deployer.mashup
> org.wso2.carbon.application.deployer.mashup(bid=179)
> 23 Active application.deployer.war
> org.wso2.carbon.application.deployer.webapp(bid=180)
> 24 Active application.mgt.dscomponent
> org.wso2.carbon.application.mgt(bid=181)
> 25 Active application.mgt.webapp.dscomponent
> org.wso2.carbon.application.mgt.webapp(bid=184)
> 26 Active org.wso2.carbon.bam.service.data.publisher
> org.wso2.carbon.bam.service.data.publisher(bid=191)
> 27 Active org.wso2.carbon.captcha.mgt.internal.CaptchaMgtServiceComponent
> org.wso2.carbon.captcha.mgt(bid=198)
> 28 Active coordination.client.component
> org.wso2.carbon.coordination.core(bid=201)
> 29 Active carbon.core.dscomponent org.wso2.carbon.core(bid=202)
> 30 Active
> org.wso2.carbon.core.internal.ListenerManagerRetrieverServiceComponent
> org.wso2.carbon.core(bid=202)
> 31 Active org.wso2.carbon.core.internal.StartupFinalizerServiceComponent
> org.wso2.carbon.core(bid=202)
> 32 Active
> org.wso2.stratos.permission.update.PermissionUpdateServiceComponent
> org.wso2.carbon.core(bid=202)
> 33 Active MIMEType2FileExtensionMap.component
> org.wso2.carbon.core(bid=202)
> 34 Active core.services.dscomponent org.wso2.carbon.core.services(bid=206)
> 35 Active agentservice.component
> org.wso2.carbon.databridge.agent.thrift(bid=207)
> 36 Active dataservices.component
> org.wso2.carbon.dataservices.core(bid=211)
> 37 Active org.wso2.carbon.deployment.synchronizer.XXX
> org.wso2.carbon.deployment.synchronizer(bid=216)
> 38 Active org.wso2.carbon.deployment.synchronizer.subversion
> org.wso2.carbon.deployment.synchronizer.subversion(bid=217)
> 39 Active org.wso2.carbon.discovery
> org.wso2.carbon.discovery.core(bid=219)
> 40 Active
> org.wso2.carbon.email.verification.internal.EmailVerificationServiceComponent
> org.wso2.carbon.email.verification(bid=221)
> 41 Unsatisfied wsevent.component.admin
> org.wso2.carbon.event.admin(bid=222)
> 42 Unsatisfied eventbrokerbuilder.component
> org.wso2.carbon.event.core(bid=226)
> 43 Unsatisfied wsevent.component org.wso2.carbon.event.ws(bid=229)
> 44 Active component.manager.core.service.comp
> org.wso2.carbon.feature.mgt.core(bid=230)
> 45 Active saml2.sso.authenticator.dscomponent
> org.wso2.carbon.identity.authenticator.saml2.sso(bid=236)
> 46 Active saml2.sso.authenticator.ui.dscomponent
> org.wso2.carbon.identity.authenticator.saml2.sso.ui(bid=239)
> 47 Active org.wso2.carbon.keystore.mgt
> org.wso2.carbon.keystore.mgt(bid=253)
> 48 Active org.wso2.carbon.logging.services
> org.wso2.carbon.logging.service(bid=259)
> 49 Active mashup.javascript.hostobjects.email.dscomponent
> 

Re: [Dev] Updated Invitation: User Store Manager Configuration UI - Code Review @ Fri Jul 12, 2013 2:30pm - 3:30pm (darsh...@wso2.com)

2013-07-12 Thread Darshana Gunawardana
Hi all,

Following is the summary for the code review of UserStore UI,

   - Remove user-store related mappings when deleting user-stores(define an
   extension point).
   - Ignore UserStoreConfigurationDeployer logic for files other than
   userstore configurations.
   - Needed to search and update relevant userstore configuration files
   when updating.

Please add if anything missed.

Thanks


On Fri, Jul 12, 2013 at 11:52 AM, Pushpalanka Jayawardhana
wrote:

> This event has been changed.
> more details 
> »
> User Store Manager Configuration UI - Code Review
> Cruicible Link : 
> http://wso2.org/crucible/cru/WCP050-1
> *When*
> *Changed: *Fri Jul 12, 2013 2:30pm – 3:30pm Colombo
> *Where*
> LK #58 5th Floor - Meeting room 
> (map
> )
> *Calendar*
> darsh...@wso2.com
> *Who*
>  •
> Pushpalanka Jayawardhana - organizer
> •
> Asela Pathberiya
> •
> Darshana Gunawardana
> •
> Prabath Siriwardana
> •
> Suresh Attanayaka
> •
> Venura Kahawala
> •
> Johann Nallathamby
> •
> dev@wso2.org
> •
> Dulanja Liyanage
>
> Going?   
> ***Yes-
> Maybe-
> No
> ***more options 
> »
>
> Invitation from Google Calendar 
>
> You are receiving this email at the account darsh...@wso2.com because you
> are subscribed for updated invitations on calendar darsh...@wso2.com.
>
> To stop receiving these notifications, please log in to
> https://www.google.com/calendar/ and change your notification settings
> for this calendar.
>



-- 
Regards,

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


[Dev] SecurityException: Key Store with a name : domain2.jks does not exist

2013-07-12 Thread Dimuthu Leelarathne
Hi,

I am trying to login to appmgt with of AF with SSO, as a tenant and getting
the following exception. Any pointers on where I should look at?

[2013-07-12 19:27:39,534] ERROR
{org.wso2.carbon.identity.sso.saml.processors.AuthnRequestProcessor} -
Error processing the authentication request
org.wso2.carbon.identity.base.IdentityException: Key Store with a name :
domain2.jks does not exist.
at
org.wso2.carbon.identity.sso.saml.builders.SignKeyDataHolder.(SignKeyDataHolder.java:135)
at
org.wso2.carbon.identity.sso.saml.builders.ResponseBuilder.buildResponse(ResponseBuilder.java:96)
at
org.wso2.carbon.identity.sso.saml.processors.AuthnRequestProcessor.process(AuthnRequestProcessor.java:154)
at
org.wso2.carbon.identity.sso.saml.SAMLSSOService.authenticate(SAMLSSOService.java:113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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:398)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.identity.sso.saml.stub.IdentitySAMLSSOServiceStub.authenticate(IdentitySAMLSSOServiceStub.java:783)
at
org.wso2.carbon.identity.sso.saml.ui.client.SAMLSSOServiceClient.authenticate(SAMLSSOServiceClient.java:81)
at
org.wso2.carbon.identity.sso.saml.ui.SAMLSSOProvider.handleRequestFromLoginPage(SAMLSSOProvider.java:323)
at
org.wso2.carbon.identity.sso.saml.ui.SAMLSSOProvider.doPost(SAMLSSOProvider.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
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:60)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:177)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:161)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.

[Dev] Updated Invitation: Custom Permissions UI and Shared Roles - Code Review @ Mon Jul 15, 2013 2:30pm - 3:30pm (ven...@wso2.com)

2013-07-12 Thread Venura Kahawala
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20130715T09Z
DTEND:20130715T10Z
DTSTAMP:20130712T113616Z
ORGANIZER;CN=ven...@wso2.com:mailto:ven...@wso2.com
UID:ma4onnkoghm73hdpj2avple...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Asela Pathberiya;X-NUM-GUESTS=0:mailto:as...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Prabath Siriwardana;X-NUM-GUESTS=0:mailto:prab...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Suresh Attanayaka;X-NUM-GUESTS=0:mailto:sur...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Johann Nallathamby;X-NUM-GUESTS=0:mailto:joh...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Dulanja Liyanage;X-NUM-GUESTS=0:mailto:dula...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Pushpalanka Jayawardhana;X-NUM-GUESTS=0:mailto:la...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Chamath Gunawardana;X-NUM-GUESTS=0:mailto:chama...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Darshana Gunawardana;X-NUM-GUESTS=0:mailto:darsh...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@wso2.org;X-NUM-GUESTS=0:mailto:dev@wso2.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Venura Kahawala;X-NUM-GUESTS=0:mailto:ven...@wso2.com
CREATED:20130712T052905Z
DESCRIPTION:View your event at http://www.google.com/calendar/event?action=
 VIEW&eid=bWE0b25ua29naG03M2hkcGoyYXZwbGV0djggZGV2QHdzbzIub3Jn&tok=MTUjdmVud
 XJhQHdzbzIuY29tNTgzMzk2ZTVjODJlMDVjMjRmMGU3YTk2Y2JkMDZmNGQzMDdkZDE1Yg&ctz=A
 sia/Colombo&hl=en.
LAST-MODIFIED:20130712T113616Z
LOCATION:LK #58 5th Floor
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:Custom Permissions UI and Shared Roles - Code Review
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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


Re: [Dev] depsync + profile issues in AS worker/manager setup

2013-07-12 Thread Kasun Gajasinghe
Yes. We are working on bug fixes at the moment. Currently we can not build
AS packs since trunk is currently broken.

Thanks,
KasunG


On Fri, Jul 12, 2013 at 4:53 PM, Pradeep Fernando  wrote:

> Hi as team,
>
> You have to carry out tests in depsync enabled worker manager setup with
> depsync enabled..
>
> --Pradeep
> sent from my phone
> On Jul 12, 2013 3:47 PM, "Kasun Gajasinghe"  wrote:
>
>> Committed in r178066.
>>
>> Thanks,
>> KasunG
>>
>>
>> On Fri, Jul 12, 2013 at 12:17 PM, Piyum Fernando  wrote:
>>
>>>
>>>
>>>
>>> On Thu, Jul 11, 2013 at 2:24 PM, Kasun Gajasinghe wrote:
>>>
 Hi Pradeep,

 Carbon UI bundle comes from the kernel. What would be the procedure to
 remove bundles from there during worker profile build?

 DepSync subversion feature comes from
 org.wso2.carbon.deployment.synchronizer.subversion.feature. Piyum, please
 include this in p2-profile-gen  and the above requirement, and provide a
 patch.

>>>
>>> HI KasunG,
>>>
>>> Made the changes. Find the patch here.
>>> https://wso2.org/jira/browse/WSAS-1308
>>>
>>> Thanks.
>>>
>>>
 Thanks,
 KasunG




 On Thu, Jul 11, 2013 at 1:15 PM, Pradeep Fernando wrote:

> Hi Appserver team,
>
> I'm testing AS in a worker/setup with worker profile. getting below
> errors.looks like,
>
>
>
> - Carbon UI bundle is still there in the worker profile.
> - snv depsync bundles are not available in the profile
>
> please have a look asap.
>
> thanks.
>
>
>
> INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt
> Console URL  : https://192.168.131.1:9444/carbon/
> [2013-07-11 13:11:46,878] ERROR
> {org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
> Deployment synchronization update for tenant -1234 failed
> java.lang.RuntimeException:
> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: 
> No
> Repository found for type svn
> at
> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.update(DeploymentSynchronizerServiceImpl.java:89)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.deploymentSyncUpdate(CarbonDeploymentSchedulerTask.java:144)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:109)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>
> --
> *Pradeep Fernando*
> Associate Technical Lead;WSO2 Inc.; http://wso2.com
>
> blog: http://pradeepfernando.blogspot.com
> m: +94776603662
>



 --
 *Kasun Gajasinghe*
 Software Engineer;
 Development Technologies Team, WSO2 Inc.; http://wso2.com


  ,
 *email: **kasung AT spamfree wso2.com


 ** cell: **+94 (77) 678-0813*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe


 *
 *
 *blog: **http://kasunbg.org* 


 *
 twitter: **http://twitter.com/kasunbg* 


 *
 *

>>>
>>>
>>>
>>> --
>>> Piyum Fernando
>>> Software Engineer
>>>
>>> Mobile: +94 77 22 93 880
>>> Home:  +94 31 22 75 715
>>>
>>
>>
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> Development Technologies Team, WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: **kasung AT spamfree wso2.com
>>
>>
>> ** cell: **+94 (77) 678-0813*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>> *
>> *
>> *blog: **http://kasunbg.org* 
>>
>>
>> *
>> twitter: **http://twitter.com/kasunbg* 
>>
>>
>> *
>> *
>>
>


-- 
*Kasun Gajasinghe*
Software Engineer;
Development Technologies Team, WSO2 Inc.; http://wso2.com


 ,
*email: **kasung AT spamfree wso2.com


** cell: **+94 (77) 678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe


*
*
*blog: **http://kasunbg.org* 


*
twitter: **http://twitter.com/kasunbg* 


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


Re: [Dev] depsync + profile issues in AS worker/manager setup

2013-07-12 Thread Pradeep Fernando
Hi as team,

You have to carry out tests in depsync enabled worker manager setup with
depsync enabled..

--Pradeep
sent from my phone
On Jul 12, 2013 3:47 PM, "Kasun Gajasinghe"  wrote:

> Committed in r178066.
>
> Thanks,
> KasunG
>
>
> On Fri, Jul 12, 2013 at 12:17 PM, Piyum Fernando  wrote:
>
>>
>>
>>
>> On Thu, Jul 11, 2013 at 2:24 PM, Kasun Gajasinghe wrote:
>>
>>> Hi Pradeep,
>>>
>>> Carbon UI bundle comes from the kernel. What would be the procedure to
>>> remove bundles from there during worker profile build?
>>>
>>> DepSync subversion feature comes from
>>> org.wso2.carbon.deployment.synchronizer.subversion.feature. Piyum, please
>>> include this in p2-profile-gen  and the above requirement, and provide a
>>> patch.
>>>
>>
>> HI KasunG,
>>
>> Made the changes. Find the patch here.
>> https://wso2.org/jira/browse/WSAS-1308
>>
>> Thanks.
>>
>>
>>> Thanks,
>>> KasunG
>>>
>>>
>>>
>>>
>>> On Thu, Jul 11, 2013 at 1:15 PM, Pradeep Fernando wrote:
>>>
 Hi Appserver team,

 I'm testing AS in a worker/setup with worker profile. getting below
 errors.looks like,



 - Carbon UI bundle is still there in the worker profile.
 - snv depsync bundles are not available in the profile

 please have a look asap.

 thanks.



 INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt
 Console URL  : https://192.168.131.1:9444/carbon/
 [2013-07-11 13:11:46,878] ERROR
 {org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
 Deployment synchronization update for tenant -1234 failed
 java.lang.RuntimeException:
 org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: No
 Repository found for type svn
 at
 org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.update(DeploymentSynchronizerServiceImpl.java:89)
 at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.deploymentSyncUpdate(CarbonDeploymentSchedulerTask.java:144)
 at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:109)
 at
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

 --
 *Pradeep Fernando*
 Associate Technical Lead;WSO2 Inc.; http://wso2.com

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662

>>>
>>>
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> Development Technologies Team, WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: **kasung AT spamfree wso2.com
>>>
>>>
>>> ** cell: **+94 (77) 678-0813*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>> *
>>> *
>>> *blog: **http://kasunbg.org* 
>>>
>>>
>>> *
>>> twitter: **http://twitter.com/kasunbg* 
>>>
>>>
>>> *
>>> *
>>>
>>
>>
>>
>> --
>> Piyum Fernando
>> Software Engineer
>>
>> Mobile: +94 77 22 93 880
>> Home:  +94 31 22 75 715
>>
>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> Development Technologies Team, WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: **kasung AT spamfree wso2.com
>
>
> ** cell: **+94 (77) 678-0813*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
> *
> *
> *blog: **http://kasunbg.org* 
>
>
> *
> twitter: **http://twitter.com/kasunbg* 
>
>
> *
> *
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] depsync + profile issues in AS worker/manager setup

2013-07-12 Thread Kasun Gajasinghe
Committed in r178066.

Thanks,
KasunG


On Fri, Jul 12, 2013 at 12:17 PM, Piyum Fernando  wrote:

>
>
>
> On Thu, Jul 11, 2013 at 2:24 PM, Kasun Gajasinghe  wrote:
>
>> Hi Pradeep,
>>
>> Carbon UI bundle comes from the kernel. What would be the procedure to
>> remove bundles from there during worker profile build?
>>
>> DepSync subversion feature comes from
>> org.wso2.carbon.deployment.synchronizer.subversion.feature. Piyum, please
>> include this in p2-profile-gen  and the above requirement, and provide a
>> patch.
>>
>
> HI KasunG,
>
> Made the changes. Find the patch here.
> https://wso2.org/jira/browse/WSAS-1308
>
> Thanks.
>
>
>> Thanks,
>> KasunG
>>
>>
>>
>>
>> On Thu, Jul 11, 2013 at 1:15 PM, Pradeep Fernando wrote:
>>
>>> Hi Appserver team,
>>>
>>> I'm testing AS in a worker/setup with worker profile. getting below
>>> errors.looks like,
>>>
>>>
>>>
>>> - Carbon UI bundle is still there in the worker profile.
>>> - snv depsync bundles are not available in the profile
>>>
>>> please have a look asap.
>>>
>>> thanks.
>>>
>>>
>>>
>>> INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt
>>> Console URL  : https://192.168.131.1:9444/carbon/
>>> [2013-07-11 13:11:46,878] ERROR
>>> {org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
>>> Deployment synchronization update for tenant -1234 failed
>>> java.lang.RuntimeException:
>>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: No
>>> Repository found for type svn
>>> at
>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.update(DeploymentSynchronizerServiceImpl.java:89)
>>> at
>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.deploymentSyncUpdate(CarbonDeploymentSchedulerTask.java:144)
>>> at
>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:109)
>>> at
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>>>
>>> --
>>> *Pradeep Fernando*
>>> Associate Technical Lead;WSO2 Inc.; http://wso2.com
>>>
>>> blog: http://pradeepfernando.blogspot.com
>>> m: +94776603662
>>>
>>
>>
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> Development Technologies Team, WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: **kasung AT spamfree wso2.com
>>
>>
>> ** cell: **+94 (77) 678-0813*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>> *
>> *
>> *blog: **http://kasunbg.org* 
>>
>>
>> *
>> twitter: **http://twitter.com/kasunbg* 
>>
>>
>> *
>> *
>>
>
>
>
> --
> Piyum Fernando
> Software Engineer
>
> Mobile: +94 77 22 93 880
> Home:  +94 31 22 75 715
>



-- 
*Kasun Gajasinghe*
Software Engineer;
Development Technologies Team, WSO2 Inc.; http://wso2.com


 ,
*email: **kasung AT spamfree wso2.com


** cell: **+94 (77) 678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe


*
*
*blog: **http://kasunbg.org* 


*
twitter: **http://twitter.com/kasunbg* 


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


[Dev] Compilation error.

2013-07-12 Thread Amila Suriarachchi
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.identity.provider.mgt.ui:
Compilation failure
[ERROR]
/home/amila/projects/trunk/platform/components/identity/org.wso2.carbon.identity.provider.mgt.ui/src/main/java/org/wso2/carbon/identity/provider/mgt/ui/client/IdentityProviderMgtServiceClient.java:[62,23]
getTenantIdP(java.lang.String) in
org.wso2.carbon.identity.provider.mgt.stub.IdentityProviderMgtServiceStub
cannot be applied to ()
[ERROR] -> [Help 1]

please fix.

thanks,
Amila.

-- 
*Amila Suriarachchi*

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

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


Re: [Dev] Upgrading Synapse dependencies in Developer Studio

2013-07-12 Thread Susinda Perera
good if we can maintain a doc of upgrading process.

On Fri, Jul 12, 2013 at 2:34 PM, Melan Nimesh  wrote:

>
>
> On Fri, Jul 12, 2013 at 2:30 PM, Melan Nimesh  wrote:
>
>>
>>
>> On Fri, Jul 12, 2013 at 1:33 PM, Viraj Rajaguru  wrote:
>>
>>> Hi,
>>>
>>>
>>> On Fri, Jul 12, 2013 at 12:30 PM, Harshana Martin wrote:
>>>
 Hi Viraj,

 Upgrading Synapse dependencies alone will not work since they might
 have dependencies to other core dependencies such as Axiom, Axis2, etc.

 So if you are upgrading the versions, you need to check their
 dependencies which are used in our codebase and upgrade them as well.

 Yes. We are upgrading those dependencies as well.
>>>
>>
>> Please refactor
>> "org.wso2.developerstudio.libraries.libraryprovider" extension-point and
>> use that extension-point to include dependencies to other projects
>> with hard-coding there jar file names
>>
>
> Sorry about the typos, I meant to say * without hard-coding their jar
> file names
>
>
>
>>
>> e.g. we can define following configuration
>>
>>   > identifier="synapse-core"
>> categoryId="org.wso2.developerstudio.eclipse.libraries.category.esb"
>>   />
>>
>>  and introduce a method to add particular jar using it's identifier as
>> a parameter
>>
>> Thanks,
>> Melan
>>
>>
>>>
>>>
 Please have a look how we did the 4.0.5 upgrade as well.

>>>
>>> Thanks for pointing this. Will refer that.
>>>

 Hope this helps!

 Thanks and Regards,
 Harshana


 On Thu, Jul 11, 2013 at 11:06 PM, Viraj Rajaguru wrote:

> Hi,
>
> We are upgrading the Synapse jars in Developer Studio to implement new
> features related to ESB 4.7.0 within Developer Studio.
>
>
>
> Thanks,
> Viraj.
>
> --
> Viraj Rajaguru
> Software Engineer
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>


 --

 Harshana Martin
 Associate Technical Lead
 WSO2 Inc. : http://wso2.com

 Mobile: +94 775 998 115
 Profile: https://www.google.com/profiles/harshana05
 Blog: http://harshana05.blogspot.com
 Twitter: http://twitter.com/harshana05


>>> Thanks,,
>>> Viraj.
>>>
>>> --
>>> Viraj Rajaguru
>>> Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile: +94 77 3683068
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Melan Nimesh Jayasingha
>> Software Engineer;
>> WSO2 Inc.
>> m:  77 631 6759
>> PGP: 0x7B42450A
>>
>>
>
>
> --
> Melan Nimesh Jayasingha
> Software Engineer;
> WSO2 Inc.
> m:  77 631 6759
> PGP: 0x7B42450A
>
>


-- 
*Susinda Perera*
Software Engineer
Mobile:(+94)716049075

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


Re: [Dev] Upgrading Synapse dependencies in Developer Studio

2013-07-12 Thread Melan Nimesh
On Fri, Jul 12, 2013 at 2:30 PM, Melan Nimesh  wrote:

>
>
> On Fri, Jul 12, 2013 at 1:33 PM, Viraj Rajaguru  wrote:
>
>> Hi,
>>
>>
>> On Fri, Jul 12, 2013 at 12:30 PM, Harshana Martin wrote:
>>
>>> Hi Viraj,
>>>
>>> Upgrading Synapse dependencies alone will not work since they might have
>>> dependencies to other core dependencies such as Axiom, Axis2, etc.
>>>
>>> So if you are upgrading the versions, you need to check their
>>> dependencies which are used in our codebase and upgrade them as well.
>>>
>>> Yes. We are upgrading those dependencies as well.
>>
>
> Please refactor
> "org.wso2.developerstudio.libraries.libraryprovider" extension-point and
> use that extension-point to include dependencies to other projects
> with hard-coding there jar file names
>

Sorry about the typos, I meant to say * without hard-coding their jar file
names



>
> e.g. we can define following configuration
>
>identifier="synapse-core"
> categoryId="org.wso2.developerstudio.eclipse.libraries.category.esb"
>   />
>
>  and introduce a method to add particular jar using it's identifier as
> a parameter
>
> Thanks,
> Melan
>
>
>>
>>
>>> Please have a look how we did the 4.0.5 upgrade as well.
>>>
>>
>> Thanks for pointing this. Will refer that.
>>
>>>
>>> Hope this helps!
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>>
>>> On Thu, Jul 11, 2013 at 11:06 PM, Viraj Rajaguru  wrote:
>>>
 Hi,

 We are upgrading the Synapse jars in Developer Studio to implement new
 features related to ESB 4.7.0 within Developer Studio.



 Thanks,
 Viraj.

 --
 Viraj Rajaguru
 Software Engineer
 WSO2 Inc. : http://wso2.com

 Mobile: +94 77 3683068




>>>
>>>
>>> --
>>>
>>> Harshana Martin
>>> Associate Technical Lead
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile: +94 775 998 115
>>> Profile: https://www.google.com/profiles/harshana05
>>> Blog: http://harshana05.blogspot.com
>>> Twitter: http://twitter.com/harshana05
>>>
>>>
>> Thanks,,
>> Viraj.
>>
>> --
>> Viraj Rajaguru
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>
>
> --
> Melan Nimesh Jayasingha
> Software Engineer;
> WSO2 Inc.
> m:  77 631 6759
> PGP: 0x7B42450A
>
>


-- 
Melan Nimesh Jayasingha
Software Engineer;
WSO2 Inc.
m:  77 631 6759
PGP: 0x7B42450A
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Upgrading Synapse dependencies in Developer Studio

2013-07-12 Thread Melan Nimesh
On Fri, Jul 12, 2013 at 1:33 PM, Viraj Rajaguru  wrote:

> Hi,
>
>
> On Fri, Jul 12, 2013 at 12:30 PM, Harshana Martin wrote:
>
>> Hi Viraj,
>>
>> Upgrading Synapse dependencies alone will not work since they might have
>> dependencies to other core dependencies such as Axiom, Axis2, etc.
>>
>> So if you are upgrading the versions, you need to check their
>> dependencies which are used in our codebase and upgrade them as well.
>>
>> Yes. We are upgrading those dependencies as well.
>

Please refactor
"org.wso2.developerstudio.libraries.libraryprovider" extension-point and
use that extension-point to include dependencies to other projects
with hard-coding there jar file names

e.g. we can define following configuration

  

 and introduce a method to add particular jar using it's identifier as
a parameter

Thanks,
Melan


>
>
>> Please have a look how we did the 4.0.5 upgrade as well.
>>
>
> Thanks for pointing this. Will refer that.
>
>>
>> Hope this helps!
>>
>> Thanks and Regards,
>> Harshana
>>
>>
>> On Thu, Jul 11, 2013 at 11:06 PM, Viraj Rajaguru  wrote:
>>
>>> Hi,
>>>
>>> We are upgrading the Synapse jars in Developer Studio to implement new
>>> features related to ESB 4.7.0 within Developer Studio.
>>>
>>>
>>>
>>> Thanks,
>>> Viraj.
>>>
>>> --
>>> Viraj Rajaguru
>>> Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile: +94 77 3683068
>>>
>>>
>>>
>>>
>>
>>
>> --
>>
>> Harshana Martin
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 775 998 115
>> Profile: https://www.google.com/profiles/harshana05
>> Blog: http://harshana05.blogspot.com
>> Twitter: http://twitter.com/harshana05
>>
>>
> Thanks,,
> Viraj.
>
> --
> Viraj Rajaguru
> Software Engineer
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>


-- 
Melan Nimesh Jayasingha
Software Engineer;
WSO2 Inc.
m:  77 631 6759
PGP: 0x7B42450A
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Has caching & throttling been tested with multi-tenancy?

2013-07-12 Thread Amila Suriarachchi
On Fri, Jul 12, 2013 at 12:27 PM, Supun Malinga  wrote:

> Hi,
>
> AFAIR, caching/throttling worked.
> One issue we have is that where there are several nodes in the cluster,
> throttling request count is not shared between the nodes..
>

you need to switch on the state replication for this. I am not sure whether
this has set in stratos live.

thanks,
Amila.

>
> thanks,
>
>
> On Fri, Jul 12, 2013 at 11:27 AM, Charitha Kankanamge 
> wrote:
>
>> Works in SLive. You can try with
>> http://appserver.stratoslive.wso2.com/services/t/superqa.com/Axis2Service?wsdl
>> Currently throttling is not distributed in cluster and it applies per
>> node. Hence, your quota will be exceeded once you send 10 requests to the
>> service.
>>
>>
>> On Fri, Jul 12, 2013 at 11:16 AM, Charitha Kankanamge 
>> wrote:
>>
>>> This cannot be true. Isuru S has closed
>>> https://wso2.org/jira/browse/STRATOS-686 saying that he cannot
>>> reproduce and mentioned that access throttling worked in AS MT mode. So, it
>>> may have been broken in later release. Let me check in SLive now.
>>>
>>> /Charitha
>>>
>>>
>>> On Fri, Jul 12, 2013 at 11:09 AM, Afkham Azeez  wrote:
>>>
 But the throttling & caching code doesn't look like it supports MT


 On Fri, Jul 12, 2013 at 11:00 AM, Charitha Kankanamge <
 chari...@wso2.com> wrote:

> IIRC, the happy paths of throttling have been tested in C4 release
> (August 2012). However, a complete functional test has not been done.
>
>
> On Thu, Jul 11, 2013 at 12:56 PM, Afkham Azeez  wrote:
>
>> $subject
>>
>> --
>> *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 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: 
>> **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>
>


 --
 *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 3320919
 blog: **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
>>
>>
>
>
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
> email - sup...@wso2.com 
> mobile - 071 56 91 321
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Amila Suriarachchi*

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

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


Re: [Dev] Has caching & throttling been tested with multi-tenancy?

2013-07-12 Thread Amila Suriarachchi
Lets say you have two tenants. and your maximum count is 10. Now if you
send 5 to one tenant can you send 10 to the second tenant?

thanks,
Amila.


On Fri, Jul 12, 2013 at 11:27 AM, Charitha Kankanamge wrote:

> Works in SLive. You can try with
> http://appserver.stratoslive.wso2.com/services/t/superqa.com/Axis2Service?wsdl
> Currently throttling is not distributed in cluster and it applies per
> node. Hence, your quota will be exceeded once you send 10 requests to the
> service.
>
>
> On Fri, Jul 12, 2013 at 11:16 AM, Charitha Kankanamge 
> wrote:
>
>> This cannot be true. Isuru S has closed
>> https://wso2.org/jira/browse/STRATOS-686 saying that he cannot reproduce
>> and mentioned that access throttling worked in AS MT mode. So, it may have
>> been broken in later release. Let me check in SLive now.
>>
>> /Charitha
>>
>>
>> On Fri, Jul 12, 2013 at 11:09 AM, Afkham Azeez  wrote:
>>
>>> But the throttling & caching code doesn't look like it supports MT
>>>
>>>
>>> On Fri, Jul 12, 2013 at 11:00 AM, Charitha Kankanamge >> > wrote:
>>>
 IIRC, the happy paths of throttling have been tested in C4 release
 (August 2012). However, a complete functional test has not been done.


 On Thu, Jul 11, 2013 at 12:56 PM, Afkham Azeez  wrote:

> $subject
>
> --
> *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 3320919
> blog: **http://blog.afkham.org* *
> twitter: 
> **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>


>>>
>>>
>>> --
>>> *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 3320919
>>> blog: **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
>
>


-- 
*Amila Suriarachchi*

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

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


[Dev] Inconsistent tenant domain information in session object when logging in as tenant

2013-07-12 Thread Pulasthi Supun
Hi All

I encountered this error when logging in as a tenant. The tenant Domain
value that is added to the session object is "carbon.super" while the
Carbon Context holds the correct value this seems to happen in
the AbstractCarbonUIAuthenticator.onSuccessAdminLogin().

>From debugging what i understood is that this happens
because MultitenantUtils.getTenantDomain(String username) returns the super
tenant domain if the username is not sent in the format of "t...@test.com".
Has the IS team encountered this issue ?

This inconsistency can also be seen from the console logs when logging into
IS as tenant and logging out

[2013-07-12 14:08:41,396]  INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  'PRIMARY/
q...@qwe.com [1]' logged in at [2013-07-12 14:08:41,396+0530]
[2013-07-12 14:08:46,616]  INFO
{org.wso2.carbon.core.services.authentication.AuthenticationAdmin} -
 'PRIMARY/qwe@carbon.super [-1234]' logged out at [2013-07-12 14:08:46,0616]




Regards,
Pulasthi
-- 
--
Pulasthi Supun
Software Engineer; WSO2 Inc.; http://wso2.com,
Email: pulas...@wso2.com
Mobile: +94 (71) 9258281
Blog : http://pulasthisupun.blogspot.com/
Git hub profile: https://github.com/pulasthi
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] WSO2 CEP 3.0.0 Milestone 2 Released!

2013-07-12 Thread Srinath Perera
Hi Mohan,

Is there a time period associated with "not occurrence"? I think we need to
have that or we will fill up the disk and slow it down as time passes.

--Srinath


On Wed, Jul 10, 2013 at 6:31 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> Hi Cyril,
>
> We are on the way of creating the documentation for CEP 3.0.0...
> We'll share the documentation with the CEP 3.0.0 release soon...
>
> Yes, 'non occurrence' of events is already implemented and can be
> achieved using the event tables in CEP 3.0.0..
>
> We'll update when CEP 3.0.0 released... Thanks for your interest on CEP...
>
> Regards,
> Mohan
>
>
>
>
>
> On Wed, Jul 10, 2013 at 1:47 PM, Cyril Rognon  wrote:
>
>> Hello cep team,
>>
>> thank you for this new milestone. I am wondering if there is any
>> documentation link for  the upcoming 3.0.0 version.
>>
>> As far as I know, there is still no logical 'not' operator that we could
>> use to filter the 'non occurrence' of events
>>
>> in siddhi language there is
>>
>> * **::=  *
>>
>> it would be nice to be able to say*
>> *
>>
>> * **::= not  *
>> I reckon I have not looked into the code to evaluate the cost of this
>> requirement, so feel free to turn it down if it is prohibitive.
>>
>> Maybe eventTables will allow one to simulate this ?
>>
>> thanks,
>> Cyril
>>
>>
>> On Fri, Jul 5, 2013 at 10:47 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> *WSO2 Complex Event Processor 3.0.0 Milestone 2 Released!*
>>>
>>> Date :5th July 2013
>>>
>>> This milestone is available at :
>>> https://svn.wso2.org/repos/wso2/people/suho/packs/cep/3.0.0/wso2cep-3.0.0-M2.zip
>>>
>>> To run the samples please follow the read-me,
>>> wso2cep-3.0.0/samples/cep-samples/ReadMe.txt
>>>
>>>
>>> Following are the bug fixes, improvements and the new features
>>>
>>> Bug
>>>
>>>- [CEP-258 ] - When trying to
>>>deploy the multiple configuration files, File reference is missing
>>>- [CEP-261 ] - Table is not
>>>properly generated when creating WSO2 Event mapping and Map mapping
>>>
>>> Improvement
>>>
>>>- [CEP-179 ] - It is better if
>>>the UI supports to check the validity of "Event Sink URL" when 
>>> subscribing
>>>to a topic
>>>- [CEP-243 ] - Separate
>>>implementation classes & UI for handing in/out sequences of transport
>>>adapators
>>>- [CEP-247 ] - Making Coalesce
>>>as a ExecutorFunction
>>>- [CEP-248 ] - Removing
>>>conversion types from output attribute processor
>>>- [CEP-249 ] - Replacing
>>>Condition Extentions using bool returning Expression Extentions
>>>- [CEP-251 ] - White-board
>>>pattern for Transport Adaptors and Event sources
>>>- [CEP-257 ] - Event Tracer
>>>output in UI need to be formatted
>>>- [CEP-260 ] - UI to retrieve
>>>the deployed Event Formatter configuration details
>>>- [CEP-262 ] - EventFormatter
>>>to receive WSO2Event and format it to other different types.. For 
>>> products
>>>like BAM
>>>- [CEP-267 ] - Listing/editing
>>>undeployed event builders
>>>- [CEP-268 ] - Handing
>>>dependency between the components when removing the configuration files
>>>
>>> New Feature
>>>
>>>- [CEP-156 ] - Add a default
>>>timeStamp convertor
>>>- [CEP-162 ] - Add Attribute
>>>Type Convetors to Siddhi
>>>- [CEP-215 ] - Adding snapshot
>>>output support for Siddhi window
>>>- [CEP-231 ] - New component
>>>called "EventFormatter" to handle the events when sending out from the 
>>> CEP
>>>- [CEP-250 ] -
>>>IsMatchExecutorFunction to regex matching
>>>- [CEP-252 ] - Wiring between
>>>the components when adding the configuration files
>>>- [CEP-253 ] -
>>>ConvertExecutorFunction for type conversion
>>>- [CEP-264 ] - Added the
>>>ability for Siddhi to retrieve properties from registry
>>>- [CEP-265 ] - Added the
>>>ability for Siddhi to retrieve resources from registry
>>>- [CEP-266 ] - Adding/editing
>>>event builders through UI
>>>
>>> Task
>>>
>>>- [CEP-246 ] - Merging
>>>Tra

Re: [Dev] Upgrading Synapse dependencies in Developer Studio

2013-07-12 Thread Viraj Rajaguru
Hi,


On Fri, Jul 12, 2013 at 12:30 PM, Harshana Martin  wrote:

> Hi Viraj,
>
> Upgrading Synapse dependencies alone will not work since they might have
> dependencies to other core dependencies such as Axiom, Axis2, etc.
>
> So if you are upgrading the versions, you need to check their dependencies
> which are used in our codebase and upgrade them as well.
>
> Yes. We are upgrading those dependencies as well.


> Please have a look how we did the 4.0.5 upgrade as well.
>

Thanks for pointing this. Will refer that.

>
> Hope this helps!
>
> Thanks and Regards,
> Harshana
>
>
> On Thu, Jul 11, 2013 at 11:06 PM, Viraj Rajaguru  wrote:
>
>> Hi,
>>
>> We are upgrading the Synapse jars in Developer Studio to implement new
>> features related to ESB 4.7.0 within Developer Studio.
>>
>>
>>
>> Thanks,
>> Viraj.
>>
>> --
>> Viraj Rajaguru
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>
>
> --
>
> Harshana Martin
> Associate Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 775 998 115
> Profile: https://www.google.com/profiles/harshana05
> Blog: http://harshana05.blogspot.com
> Twitter: http://twitter.com/harshana05
>
>
Thanks,,
Viraj.

-- 
Viraj Rajaguru
Software Engineer
WSO2 Inc. : http://wso2.com

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


Re: [Dev] Upgrading Synapse dependencies in Developer Studio

2013-07-12 Thread Harshana Martin
Hi Viraj,

Upgrading Synapse dependencies alone will not work since they might have
dependencies to other core dependencies such as Axiom, Axis2, etc.

So if you are upgrading the versions, you need to check their dependencies
which are used in our codebase and upgrade them as well.

Please have a look how we did the 4.0.5 upgrade as well.

Hope this helps!

Thanks and Regards,
Harshana


On Thu, Jul 11, 2013 at 11:06 PM, Viraj Rajaguru  wrote:

> Hi,
>
> We are upgrading the Synapse jars in Developer Studio to implement new
> features related to ESB 4.7.0 within Developer Studio.
>
>
>
> Thanks,
> Viraj.
>
> --
> Viraj Rajaguru
> Software Engineer
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>


-- 

Harshana Martin
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 775 998 115
Profile: https://www.google.com/profiles/harshana05
Blog: http://harshana05.blogspot.com
Twitter: http://twitter.com/harshana05
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Has caching & throttling been tested with multi-tenancy?

2013-07-12 Thread Supun Malinga
Hi,

AFAIR, caching/throttling worked.
One issue we have is that where there are several nodes in the cluster,
throttling request count is not shared between the nodes..

thanks,


On Fri, Jul 12, 2013 at 11:27 AM, Charitha Kankanamge wrote:

> Works in SLive. You can try with
> http://appserver.stratoslive.wso2.com/services/t/superqa.com/Axis2Service?wsdl
> Currently throttling is not distributed in cluster and it applies per
> node. Hence, your quota will be exceeded once you send 10 requests to the
> service.
>
>
> On Fri, Jul 12, 2013 at 11:16 AM, Charitha Kankanamge 
> wrote:
>
>> This cannot be true. Isuru S has closed
>> https://wso2.org/jira/browse/STRATOS-686 saying that he cannot reproduce
>> and mentioned that access throttling worked in AS MT mode. So, it may have
>> been broken in later release. Let me check in SLive now.
>>
>> /Charitha
>>
>>
>> On Fri, Jul 12, 2013 at 11:09 AM, Afkham Azeez  wrote:
>>
>>> But the throttling & caching code doesn't look like it supports MT
>>>
>>>
>>> On Fri, Jul 12, 2013 at 11:00 AM, Charitha Kankanamge >> > wrote:
>>>
 IIRC, the happy paths of throttling have been tested in C4 release
 (August 2012). However, a complete functional test has not been done.


 On Thu, Jul 11, 2013 at 12:56 PM, Afkham Azeez  wrote:

> $subject
>
> --
> *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 3320919
> blog: **http://blog.afkham.org* *
> twitter: 
> **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>


>>>
>>>
>>> --
>>> *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 3320919
>>> blog: **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
>
>


-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 
mobile - 071 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev