Re: [Dev] [DEV] IllegalStateException while running a load with multiple tenants

[Malaka Silva]

Adding following seems to fix the issue for the tests I have done with 3
domains.

PrivilegedCarbonContext.destroyCurrentContext();

Do we need to write the following(two lines) inside a Synchronous block?

PrivilegedCarbonContext.destroyCurrentContext();
PrivilegedCarbonContext cc = PrivilegedCarbonContext.
getThreadLocalCarbonContext();



Jira - https://wso2.org/jira/browse/ESBJAVA-2849


On Tue, Jan 21, 2014 at 12:22 PM, Nuwan Silva nuw...@wso2.com wrote:

 Same issue is still observable in 20thJan packs. This was easily
 reproducible.

 TID: [0] [ESB] [2014-01-21 12:06:54,003]  INFO
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
 -  Received ClusteringMessage: SynchronizeRepositoryRequest{tenantId=6,
 tenantDomain='evan.com', messageId=32240355-9e6f-4b81-849e-b1336317560a}
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
 TID: [0] [ESB] [2014-01-21 12:06:54,005]  INFO
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} -  Received
 [SynchronizeRepositoryRequest{tenantId=6, tenantDomain='evan.com',
 messageId=32240355-9e6f-4b81-849e-b1336317560a}]
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest}
 TID: [0] [ESB] [2014-01-21 12:06:54,005]  INFO
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} -  Updating
 repo update required parameter
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest}
 TID: [0] [ESB] [2014-01-21 12:07:11,420] ERROR
 {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
 the domain from 3 to 6
 {org.wso2.carbon.context.internal.CarbonContextDataHolder}

 java.lang.IllegalStateException: Trying to set the domain from 3 to 6
 at
 org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantId(CarbonContextDataHolder.java:1587)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:208)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:197)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:284)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:104)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getAxisService(TenantAxisUtils.java:195)
 at
 org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:300)
 at
 org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:155)

 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 TID: [0] [ESB] [2014-01-21 12:07:11,423] ERROR
 {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
 the domain from nuwan.com to 
 evan.com{org.wso2.carbon.context.internal.CarbonContextDataHolder}
 java.lang.IllegalStateException: Trying to set the domain from nuwan.comto
 evan.com

 at
 org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantDomain(CarbonContextDataHolder.java:1636)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:245)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:234)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:285)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:104)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getAxisService(TenantAxisUtils.java:195)
 at
 org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:300)
 at
 org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:155)

 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)

 same issue is reopened.

 Thanks  Regards,
 NuwanS.



 On Sun, Jan 12, 2014 at 2:22 PM, Afkham Azeez az...@wso2.com wrote:

 The fix has to go into the handler


 On Sun, Jan 12, 2014 at 1:36 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Azeez,

 The fix mentioned already there with kernel patch0004.

 

Re: [Dev] [DEV] IllegalStateException while running a load with multiple tenants

[Afkham Azeez]

In which class did you add this code?


On Tue, Jan 21, 2014 at 1:43 PM, Malaka Silva mal...@wso2.com wrote:

 Adding following seems to fix the issue for the tests I have done with 3
 domains.

 PrivilegedCarbonContext.destroyCurrentContext();

 Do we need to write the following(two lines) inside a Synchronous block?

 PrivilegedCarbonContext.destroyCurrentContext();
 PrivilegedCarbonContext cc = PrivilegedCarbonContext.
 getThreadLocalCarbonContext();



 Jira - https://wso2.org/jira/browse/ESBJAVA-2849


 On Tue, Jan 21, 2014 at 12:22 PM, Nuwan Silva nuw...@wso2.com wrote:

 Same issue is still observable in 20thJan packs. This was easily
 reproducible.

 TID: [0] [ESB] [2014-01-21 12:06:54,003]  INFO
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
 -  Received ClusteringMessage: SynchronizeRepositoryRequest{tenantId=6,
 tenantDomain='evan.com', messageId=32240355-9e6f-4b81-849e-b1336317560a}
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
 TID: [0] [ESB] [2014-01-21 12:06:54,005]  INFO
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} -  Received
 [SynchronizeRepositoryRequest{tenantId=6, tenantDomain='evan.com',
 messageId=32240355-9e6f-4b81-849e-b1336317560a}]
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest}
 TID: [0] [ESB] [2014-01-21 12:06:54,005]  INFO
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} -  Updating
 repo update required parameter
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest}
 TID: [0] [ESB] [2014-01-21 12:07:11,420] ERROR
 {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
 the domain from 3 to 6
 {org.wso2.carbon.context.internal.CarbonContextDataHolder}

 java.lang.IllegalStateException: Trying to set the domain from 3 to 6
 at
 org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantId(CarbonContextDataHolder.java:1587)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:208)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:197)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:284)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:104)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getAxisService(TenantAxisUtils.java:195)
 at
 org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:300)
 at
 org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:155)

 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 TID: [0] [ESB] [2014-01-21 12:07:11,423] ERROR
 {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
 the domain from nuwan.com to 
 evan.com{org.wso2.carbon.context.internal.CarbonContextDataHolder}
 java.lang.IllegalStateException: Trying to set the domain from nuwan.comto
 evan.com

 at
 org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantDomain(CarbonContextDataHolder.java:1636)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:245)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:234)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:285)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:104)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getAxisService(TenantAxisUtils.java:195)
 at
 org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:300)
 at
 org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:155)

 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)

 same issue is reopened.

 Thanks  Regards,
 NuwanS.



 On Sun, Jan 12, 2014 at 2:22 PM, Afkham Azeez az...@wso2.com wrote:

 The fix has to go into the handler


 On Sun, Jan 12, 2014 at 

Re: [Dev] [DEV] IllegalStateException while running a load with multiple tenants

[Malaka Silva]

https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/mediation-initializer/org.wso2.carbon.mediation.initializer/4.2.2/src/main/java/org/wso2/carbon/mediation/initializer/handler/CarbonTenantInfoConfigurator.java


On Tue, Jan 21, 2014 at 1:46 PM, Afkham Azeez az...@wso2.com wrote:

 In which class did you add this code?


 On Tue, Jan 21, 2014 at 1:43 PM, Malaka Silva mal...@wso2.com wrote:

 Adding following seems to fix the issue for the tests I have done with 3
 domains.

 PrivilegedCarbonContext.destroyCurrentContext();

 Do we need to write the following(two lines) inside a Synchronous block?

 PrivilegedCarbonContext.destroyCurrentContext();
 PrivilegedCarbonContext cc = PrivilegedCarbonContext.
 getThreadLocalCarbonContext();



 Jira - https://wso2.org/jira/browse/ESBJAVA-2849


 On Tue, Jan 21, 2014 at 12:22 PM, Nuwan Silva nuw...@wso2.com wrote:

 Same issue is still observable in 20thJan packs. This was easily
 reproducible.

 TID: [0] [ESB] [2014-01-21 12:06:54,003]  INFO
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
 -  Received ClusteringMessage: SynchronizeRepositoryRequest{tenantId=6,
 tenantDomain='evan.com',
 messageId=32240355-9e6f-4b81-849e-b1336317560a}
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
 TID: [0] [ESB] [2014-01-21 12:06:54,005]  INFO
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} -  Received
 [SynchronizeRepositoryRequest{tenantId=6, tenantDomain='evan.com',
 messageId=32240355-9e6f-4b81-849e-b1336317560a}]
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest}
 TID: [0] [ESB] [2014-01-21 12:06:54,005]  INFO
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} -  Updating
 repo update required parameter
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest}
 TID: [0] [ESB] [2014-01-21 12:07:11,420] ERROR
 {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
 the domain from 3 to 6
 {org.wso2.carbon.context.internal.CarbonContextDataHolder}

 java.lang.IllegalStateException: Trying to set the domain from 3 to 6
 at
 org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantId(CarbonContextDataHolder.java:1587)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:208)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:197)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:284)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:104)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getAxisService(TenantAxisUtils.java:195)
 at
 org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:300)
 at
 org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:155)

 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 TID: [0] [ESB] [2014-01-21 12:07:11,423] ERROR
 {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
 the domain from nuwan.com to 
 evan.com{org.wso2.carbon.context.internal.CarbonContextDataHolder}
 java.lang.IllegalStateException: Trying to set the domain from nuwan.comto
 evan.com

 at
 org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantDomain(CarbonContextDataHolder.java:1636)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:245)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:234)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:285)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:104)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getAxisService(TenantAxisUtils.java:195)
 at
 org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:300)
 at
 org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:155)

 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
 

Re: [Dev] [DEV] IllegalStateException while running a load with multiple tenants

[Afkham Azeez]

Is this a handler? Is it engaged in the global in flow? If so, you don't
need to synchronize that block. If you do it, it will be a performance
killer.


On Tue, Jan 21, 2014 at 1:49 PM, Malaka Silva mal...@wso2.com wrote:


 https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/mediation-initializer/org.wso2.carbon.mediation.initializer/4.2.2/src/main/java/org/wso2/carbon/mediation/initializer/handler/CarbonTenantInfoConfigurator.java


 On Tue, Jan 21, 2014 at 1:46 PM, Afkham Azeez az...@wso2.com wrote:

 In which class did you add this code?


 On Tue, Jan 21, 2014 at 1:43 PM, Malaka Silva mal...@wso2.com wrote:

 Adding following seems to fix the issue for the tests I have done with 3
 domains.

 PrivilegedCarbonContext.destroyCurrentContext();

 Do we need to write the following(two lines) inside a Synchronous block?

 PrivilegedCarbonContext.destroyCurrentContext();
 PrivilegedCarbonContext cc = PrivilegedCarbonContext.
 getThreadLocalCarbonContext();



 Jira - https://wso2.org/jira/browse/ESBJAVA-2849


 On Tue, Jan 21, 2014 at 12:22 PM, Nuwan Silva nuw...@wso2.com wrote:

 Same issue is still observable in 20thJan packs. This was easily
 reproducible.

 TID: [0] [ESB] [2014-01-21 12:06:54,003]  INFO
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
 -  Received ClusteringMessage: SynchronizeRepositoryRequest{tenantId=6,
 tenantDomain='evan.com',
 messageId=32240355-9e6f-4b81-849e-b1336317560a}
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
 TID: [0] [ESB] [2014-01-21 12:06:54,005]  INFO
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} -  Received
 [SynchronizeRepositoryRequest{tenantId=6, tenantDomain='evan.com',
 messageId=32240355-9e6f-4b81-849e-b1336317560a}]
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest}
 TID: [0] [ESB] [2014-01-21 12:06:54,005]  INFO
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} -  Updating
 repo update required parameter
 {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest}
 TID: [0] [ESB] [2014-01-21 12:07:11,420] ERROR
 {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
 the domain from 3 to 6
 {org.wso2.carbon.context.internal.CarbonContextDataHolder}

 java.lang.IllegalStateException: Trying to set the domain from 3 to 6
 at
 org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantId(CarbonContextDataHolder.java:1587)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:208)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:197)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:284)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:104)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getAxisService(TenantAxisUtils.java:195)
 at
 org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:300)
 at
 org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:155)

 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 TID: [0] [ESB] [2014-01-21 12:07:11,423] ERROR
 {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
 the domain from nuwan.com to 
 evan.com{org.wso2.carbon.context.internal.CarbonContextDataHolder}
 java.lang.IllegalStateException: Trying to set the domain from
 nuwan.com to evan.com

 at
 org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantDomain(CarbonContextDataHolder.java:1636)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:245)
 at
 org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:234)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:285)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:104)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getAxisService(TenantAxisUtils.java:195)
 at
 org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:300)
 at
 

Re: [Dev] Invoke Proxy Services RESTfully via MultiTenant broken [https://wso2.org/jira/browse/ESBJAVA-2906]

[Dushan Abeyruwan]

Hi Manoj,
  Modified patched attached
https://wso2.org/jira/secure/attachment/30083/FixRESTfulInvokeMultitenant.txt

Cheers
Dushan


On Tue, Jan 21, 2014 at 12:10 PM, Manoj Kumara ma...@wso2.com wrote:

 Hi Dushan,

 Provided patch is not complete according to [1], Please update the patch.
 You may need to update update README.txt file and bin.xml file as well.

 [1] http://docs.wso2.org/display/Carbon420/Creating+a+Carbon+Kernel+Patch


 Thanks,
 Manoj

 Best Regards..


 Manoj Kumara
 Software Engineer
 WSO2, Inc.; http://wso2.com

 Twitter:  http://twitter.com/ManKuma
 Mobile: +94713448188


 On Tue, Jan 21, 2014 at 11:57 AM, Dushan Abeyruwan dus...@wso2.comwrote:

 Hi Manoj,
   $subject, the patch is attached in [1] please do apply this ASAP to
 carbon core MultitenantMessageReceiver


 [1] https://wso2.org/jira/browse/ESBJAVA-2906

 cheers,
 Dushan Abeyruwan | Associate Tech Lead
 Integration Technologies Team
 PMC Member Apache Synpase
 WSO2 Inc. http://wso2.com/
 Blog:http://dushansview.blogspot.com/
 Mobile:(0094)713942042





-- 
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Proposed code repository restructuring move to GitHub

[Kishanthan Thangarajah]

On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed sha...@wso2.com wrote:

 On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Yes, we don't need to separately say service-stubs, it should be under
 the components level as just another component.


 Initially we extracted out the service stubs because it doesn't change
 frequently. So we can reduce the build time because we don't need to do
 wsdl2java in each build cycle. Looks like we are going to add it back?


The situation is different than earlier. If we look at the current proposed
approach, we will not be building the components, which, in most case, are
not directly related to what we work on. They will get built separately and
deployed to the maven repo and the other components which are depending on
will be using them. This way the build time will be greatly reduced.






 On Tue, Jan 21, 2014 at 12:30 PM, Eranda Sooriyabandara 
 era...@wso2.comwrote:

 Hi Kicha,
 There will be no service stubs directory it will be a additional
 component in the same level as BE + FE components.

 thanks
 Eranda


 On Tue, Jan 21, 2014 at 11:41 AM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi Eranda,

 Where have you put the service-stubs related to governance component?
 It should come under the same repo as carbon-component-governance.


 On Tue, Jan 21, 2014 at 12:29 AM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi All,
 As a PoC I just completed the carbon-component-governance. Please
 find it in [1] and let me know your comments and suggestions. Please keep
 in mind that this is not in a buildable state since other components
 need to build before this.

 thanks
 Eranda

 [1] https://github.com/wso2/carbon-component-governance


 On Fri, Jan 17, 2014 at 9:26 PM, Afkham Azeez az...@wso2.com wrote:

  [Sorry for the very long mail. I want to document all that I had in
 mind  the stuff we discussed. I would recommend all devs to take
 some time to read this]


 I would like to summarize he discussion we had a couple of days back.

 *The Problems*
 The problems we are trying to solve are as follows:

 1. Trunk  branches structures being completely different
 2. Branches containing directories with version numbers
 3. It is impossible to move to GitHub with the current structure
 because of #2
 4. It is very easy to break the build by changing already released
 code. The room for human error is high.
 5. Bamboo builds are eternally broken because the build fails at some
 point  Bamboo cannot continue any further
 6. When we branch, the trunk quickly becomes obsolete, and remains
 in that broken state until the next major platform release.
 7. Everybody has to build all components/features, even if those are
 not related to their products
 8. Fixed versions in branches instead of using SNAPSHOT versions.
 This makes it impossible to upload build artifacts to Maven/Nexus
 repos. This leads to #7.
 9. Impossible to integrate code quality tools such as EraInsight
 because of #5

 *Proposed solution*
 We have come up with the following solution after much deliberation 
 thought.

 Rationale:
 We started looking at other open source projects out there. We took
 Axis2 as an example. Axis2 had many dependencies including Axiom,
 XmlSchema, Woden, WSS4J etc. Those 3rd party dependencies were also
 developed by some Axis2 contributors, but we never branched all of those
 together and brought them into the same code branch. We used to start 
 what
 we used to call a release train, where the upstream code would have to be
 released first before the downstream code such as Axis2  Synapse could 
 be
 released. This way, we never had any of the problems outlined above.

 If you look at the WSO2 product releases, again, the scenario is not
 that much different from the Axis2/Synapse releases. Components  
 features
 are simply dependencies of the products. In order to get product releases
 out, we first need releases of those dependencies (components/features). 
 So
 the proposal is to identify the top level components/features, and first
 release that code before doing product releases. Each of those components
 will have a GitHub repo. All active development will be done on the
 main branch of those components, and will be branched when they are close
 to the release. Instead of granting commit rights to all, we could only
 allow the primary developers of those components to commit, and
 others can send pull requests, which will be merged in by the primary
 owners after reviewing. These component teams could even have an internal
 Git repo or clone, and commit to that, run all tests, and when they
 are satisfied that the code is in a good state to be merged into the main
 branch, they can send a pull request  merge the changes. We would run
 Bamboo which would build the components several times a day  deploy them
 to the Nexus repo. That way, you would not have to build code that
 is not directly related to what you are 

[Dev] [ESB] Sending POST requests with x-www-form-urlencoded content type

[Ramindu Deshapriya]

Hi,

I am trying to send a POST request with a set of paramters in the form of
x-www-form-urlencoded to a backend API.

I need to send a set of key value pairs but am having trouble setting these
key value pairs using a synapse template. 



Would appreciate guidance on how to accomplish this. 

Thanks. 

P.S. I noticed that a default message builder and formatter exist for this
content type in the default ESB configuration. Would these be able to carry
out the task or would I need to enable any other configuration values?






--
View this message in context: 
http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-Sending-POST-requests-with-x-www-form-urlencoded-content-type-tp90956.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invoke Proxy Services RESTfully via MultiTenant broken [https://wso2.org/jira/browse/ESBJAVA-2906]

[Manoj Kumara]

Hi,

Committed to patch0005 with 194815.

Thanks,
Manoj

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Tue, Jan 21, 2014 at 2:03 PM, Dushan Abeyruwan dus...@wso2.com wrote:

 Hi Manoj,
   Modified patched attached
 https://wso2.org/jira/secure/attachment/30083/FixRESTfulInvokeMultitenant.txt

 Cheers
 Dushan


 On Tue, Jan 21, 2014 at 12:10 PM, Manoj Kumara ma...@wso2.com wrote:

 Hi Dushan,

 Provided patch is not complete according to [1], Please update the patch.
 You may need to update update README.txt file and bin.xml file as well.

 [1] http://docs.wso2.org/display/Carbon420/Creating+a+Carbon+Kernel+Patch


 Thanks,
 Manoj

 Best Regards..


 Manoj Kumara
 Software Engineer
 WSO2, Inc.; http://wso2.com

 Twitter:  http://twitter.com/ManKuma
 Mobile: +94713448188


 On Tue, Jan 21, 2014 at 11:57 AM, Dushan Abeyruwan dus...@wso2.comwrote:

 Hi Manoj,
   $subject, the patch is attached in [1] please do apply this ASAP to
 carbon core MultitenantMessageReceiver


 [1] https://wso2.org/jira/browse/ESBJAVA-2906

 cheers,
 Dushan Abeyruwan | Associate Tech Lead
 Integration Technologies Team
 PMC Member Apache Synpase
 WSO2 Inc. http://wso2.com/
 Blog:http://dushansview.blogspot.com/
 Mobile:(0094)713942042





 --
 Dushan Abeyruwan | Associate Tech Lead
  Integration Technologies Team
 PMC Member Apache Synpase
 WSO2 Inc. http://wso2.com/
 Blog:http://dushansview.blogspot.com/
 Mobile:(0094)713942042


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

[Dev] Invitation: [Code Review] - Balana @ Fri Jan 24, 2014 11am - 12pm (chama...@wso2.com)

[Chamath Gunawardana]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20140124T053000Z
DTEND:20140124T063000Z
DTSTAMP:20140121T085720Z
ORGANIZER;CN=Chamath Gunawardana:mailto:chama...@wso2.com
UID:s8gkp5tfli25ic1mpqi4oqh...@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=Darshana Gunawardana;X-NUM-GUESTS=0:mailto:darsh...@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=Venura Kahawala;X-NUM-GUESTS=0:mailto:ven...@wso2.com
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR
 UE;CN=LK 5th Floor Meeting Room - Garage;X-NUM-GUESTS=0:mailto:wso2.com_2d3
 431383635313232393...@resource.calendar.google.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=OPT-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=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=Ishara Karunarathna;X-NUM-GUESTS=0:mailto:isha...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Chamath Gunawardana;X-NUM-GUESTS=0:mailto:chama...@wso2.com
CREATED:20140121T085720Z
DESCRIPTION:View your event at http://www.google.com/calendar/event?action=
 VIEWeid=czhna3A1dGZsaTI1aWMxbXBxaTRvcWhxbjggZGV2QHdzbzIub3Jntok=MTcjY2hhb
 WF0aGdAd3NvMi5jb21hZjIxZjdkZWIzNTljOTA5YTc4OGY1ZDU1NDlkNjVjN2I5OTdmMzkwctz
 =Asia/Colombohl=en.
LAST-MODIFIED:20140121T085720Z
LOCATION:LK 5th Floor Meeting Room - Garage
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:[Code Review] - Balana
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] We will also need to move Carbon 4.x kernel to GitHub

[Kishanthan Thangarajah]

We already have a repo with the name carbon-kernel, where the C5 work is
being carried. So this 4.x kernel repo should be of a different name. Lets
name it as carbon4-kernel

After that, we can move the components found under core to the
components category. And all the features to features category in git.
We will NOT need a separate product repo for carbon.


On Mon, Jan 20, 2014 at 8:38 PM, Kishanthan Thangarajah kishant...@wso2.com
 wrote:

 We will have to move the current kernel branch (4.2.0) with components
 updated with latest kernel patches.


 On Mon, Jan 20, 2014 at 8:26 PM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 So this will be starting from kernel 4.2.0 or we have to wait till kernel
 trunk is ready?.

 thanks,


 On Mon, Jan 20, 2014 at 7:47 PM, Afkham Azeez az...@wso2.com wrote:

  I think the AppServer team needs to do a kernel 4.3.0 release because
 they need to upgrade Tomcat for WebSockets support. One option is to move
 the kernel to GitHub and do the release from there.


 On Mon, Jan 20, 2014 at 7:46 PM, Eranda Sooriyabandara 
 era...@wso2.comwrote:

 Hi Azeez,
 +1. We will add it to our porting plan.

 thanks
 Eranda


 On Mon, Jan 20, 2014 at 7:30 PM, Afkham Azeez az...@wso2.com wrote:

 $subject

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




 --

 *Eranda Sooriyabandara*Senior Software Engineer;
 Integration Technologies Team;
 WSO2 Inc.; http://wso2.com
  Lean . Enterprise . Middleware

 E-mail: eranda AT wso2.com
 Mobile: +94 716 472 816
 Linked-In: http://www.linkedin.com/in/erandasooriyabandara
 Blog: http://emsooriyabandara.blogspot.com/







 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 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
 email: sup...@wso2.com sup...@wso2.com
 mobile: +94 (0)71 56 91 321

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




 --
 *Kishanthan Thangarajah*
 Senior Software Engineer,
 Platform Technologies Team,
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com*
 Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan*




-- 
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Behavior of SimpleRealmConfigBuilder and CommonLDAPRealmConfigBuilder in Authorizing Admin Role for /permission

[Ajanthan Balachandran]

Hi All,
When i connected to JDBCUserstore with  SimpleRealmConfigBuilder after
creating tenant i can observer that /permission is given to admin role
of the tenant.
but when i connected to LDAP user store with
CommonLDAPRealmConfigBuilder i can see /permission/admin is given to
admin role.

If you look at the CommonLDAPRealmConfigBuilder there you can see that
the AdminRoleManagementPermissions property is overwritten by
/permission/admin but in
SimpleRealmConfigBuilder it is cloned from bootstrap config.

Shall we fix this ? Due to this problem we are not able to call
Stratos admin APIs after connecting to LDAP.

Thanks.

-- 
ajanthan
-- 
Ajanthan Balachandiran
Senior Software Engineer;
Solutions Technologies Team ;WSO2, Inc.;  http://wso2.com/

email: ajant...@wso2.com; cell: +94775581497
blog: http://bkayts.blogspot.com/

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

Re: [Dev] [Architecture] Proposed code repository restructuring move to GitHub

[Eranda Sooriyabandara]

Hi Shariq,
Yeah, we may not needed those to be build again and again. So let's add
related stubs to service-stubs directory in each repo.

thanks
Eranda


On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed sha...@wso2.com wrote:

 On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Yes, we don't need to separately say service-stubs, it should be under
 the components level as just another component.


 Initially we extracted out the service stubs because it doesn't change
 frequently. So we can reduce the build time because we don't need to do
 wsdl2java in each build cycle. Looks like we are going to add it back?





 On Tue, Jan 21, 2014 at 12:30 PM, Eranda Sooriyabandara 
 era...@wso2.comwrote:

 Hi Kicha,
 There will be no service stubs directory it will be a additional
 component in the same level as BE + FE components.

 thanks
 Eranda


 On Tue, Jan 21, 2014 at 11:41 AM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi Eranda,

 Where have you put the service-stubs related to governance component?
 It should come under the same repo as carbon-component-governance.


 On Tue, Jan 21, 2014 at 12:29 AM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi All,
 As a PoC I just completed the carbon-component-governance. Please
 find it in [1] and let me know your comments and suggestions. Please keep
 in mind that this is not in a buildable state since other components
 need to build before this.

 thanks
 Eranda

 [1] https://github.com/wso2/carbon-component-governance


 On Fri, Jan 17, 2014 at 9:26 PM, Afkham Azeez az...@wso2.com wrote:

  [Sorry for the very long mail. I want to document all that I had in
 mind  the stuff we discussed. I would recommend all devs to take
 some time to read this]


 I would like to summarize he discussion we had a couple of days back.

 *The Problems*
 The problems we are trying to solve are as follows:

 1. Trunk  branches structures being completely different
 2. Branches containing directories with version numbers
 3. It is impossible to move to GitHub with the current structure
 because of #2
 4. It is very easy to break the build by changing already released
 code. The room for human error is high.
 5. Bamboo builds are eternally broken because the build fails at some
 point  Bamboo cannot continue any further
 6. When we branch, the trunk quickly becomes obsolete, and remains
 in that broken state until the next major platform release.
 7. Everybody has to build all components/features, even if those are
 not related to their products
 8. Fixed versions in branches instead of using SNAPSHOT versions.
 This makes it impossible to upload build artifacts to Maven/Nexus
 repos. This leads to #7.
 9. Impossible to integrate code quality tools such as EraInsight
 because of #5

 *Proposed solution*
 We have come up with the following solution after much deliberation 
 thought.

 Rationale:
 We started looking at other open source projects out there. We took
 Axis2 as an example. Axis2 had many dependencies including Axiom,
 XmlSchema, Woden, WSS4J etc. Those 3rd party dependencies were also
 developed by some Axis2 contributors, but we never branched all of those
 together and brought them into the same code branch. We used to start 
 what
 we used to call a release train, where the upstream code would have to be
 released first before the downstream code such as Axis2  Synapse could 
 be
 released. This way, we never had any of the problems outlined above.

 If you look at the WSO2 product releases, again, the scenario is not
 that much different from the Axis2/Synapse releases. Components  
 features
 are simply dependencies of the products. In order to get product releases
 out, we first need releases of those dependencies (components/features). 
 So
 the proposal is to identify the top level components/features, and first
 release that code before doing product releases. Each of those components
 will have a GitHub repo. All active development will be done on the
 main branch of those components, and will be branched when they are close
 to the release. Instead of granting commit rights to all, we could only
 allow the primary developers of those components to commit, and
 others can send pull requests, which will be merged in by the primary
 owners after reviewing. These component teams could even have an internal
 Git repo or clone, and commit to that, run all tests, and when they
 are satisfied that the code is in a good state to be merged into the main
 branch, they can send a pull request  merge the changes. We would run
 Bamboo which would build the components several times a day  deploy them
 to the Nexus repo. That way, you would not have to build code that
 is not directly related to what you are working on, which would save 100s
 of valuable dev hours.

 In the majority of the cases, the P2 features correspond to one or
 more related components. So we would keep the feature close to the
 component. There are 

Re: [Dev] [Architecture] Proposed code repository restructuring move to GitHub

[Shariq Muhammed]

On Tue, Jan 21, 2014 at 2:42 PM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi Shariq,
 Yeah, we may not needed those to be build again and again. So let's add
 related stubs to service-stubs directory in each repo.


Yea lets structure it that way.



 thanks
 Eranda


 On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed sha...@wso2.com wrote:

 On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Yes, we don't need to separately say service-stubs, it should be under
 the components level as just another component.


 Initially we extracted out the service stubs because it doesn't change
 frequently. So we can reduce the build time because we don't need to do
 wsdl2java in each build cycle. Looks like we are going to add it back?





 On Tue, Jan 21, 2014 at 12:30 PM, Eranda Sooriyabandara era...@wso2.com
  wrote:

 Hi Kicha,
 There will be no service stubs directory it will be a additional
 component in the same level as BE + FE components.

 thanks
 Eranda


 On Tue, Jan 21, 2014 at 11:41 AM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi Eranda,

 Where have you put the service-stubs related to governance component?
 It should come under the same repo as carbon-component-governance.


 On Tue, Jan 21, 2014 at 12:29 AM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi All,
 As a PoC I just completed the carbon-component-governance. Please
 find it in [1] and let me know your comments and suggestions. Please keep
 in mind that this is not in a buildable state since other components
 need to build before this.

 thanks
 Eranda

 [1] https://github.com/wso2/carbon-component-governance


 On Fri, Jan 17, 2014 at 9:26 PM, Afkham Azeez az...@wso2.com wrote:

  [Sorry for the very long mail. I want to document all that I had
 in mind  the stuff we discussed. I would recommend all devs to
 take some time to read this]


 I would like to summarize he discussion we had a couple of days
 back.

 *The Problems*
 The problems we are trying to solve are as follows:

 1. Trunk  branches structures being completely different
 2. Branches containing directories with version numbers
 3. It is impossible to move to GitHub with the current structure
 because of #2
 4. It is very easy to break the build by changing already released
 code. The room for human error is high.
 5. Bamboo builds are eternally broken because the build fails at
 some point  Bamboo cannot continue any further
 6. When we branch, the trunk quickly becomes obsolete, and remains
 in that broken state until the next major platform release.
 7. Everybody has to build all components/features, even if those are
 not related to their products
 8. Fixed versions in branches instead of using SNAPSHOT versions.
 This makes it impossible to upload build artifacts to Maven/Nexus
 repos. This leads to #7.
 9. Impossible to integrate code quality tools such as EraInsight
 because of #5

 *Proposed solution*
 We have come up with the following solution after much deliberation
  thought.

 Rationale:
 We started looking at other open source projects out there. We took
 Axis2 as an example. Axis2 had many dependencies including Axiom,
 XmlSchema, Woden, WSS4J etc. Those 3rd party dependencies were also
 developed by some Axis2 contributors, but we never branched all of those
 together and brought them into the same code branch. We used to start 
 what
 we used to call a release train, where the upstream code would have to 
 be
 released first before the downstream code such as Axis2  Synapse could 
 be
 released. This way, we never had any of the problems outlined above.

 If you look at the WSO2 product releases, again, the scenario is not
 that much different from the Axis2/Synapse releases. Components  
 features
 are simply dependencies of the products. In order to get product 
 releases
 out, we first need releases of those dependencies 
 (components/features). So
 the proposal is to identify the top level components/features, and first
 release that code before doing product releases. Each of those 
 components
 will have a GitHub repo. All active development will be done on the
 main branch of those components, and will be branched when they are 
 close
 to the release. Instead of granting commit rights to all, we could only
 allow the primary developers of those components to commit, and
 others can send pull requests, which will be merged in by the primary
 owners after reviewing. These component teams could even have an 
 internal
 Git repo or clone, and commit to that, run all tests, and when they
 are satisfied that the code is in a good state to be merged into the 
 main
 branch, they can send a pull request  merge the changes. We would run
 Bamboo which would build the components several times a day  deploy 
 them
 to the Nexus repo. That way, you would not have to build code that
 is not directly related to what you are working on, which would save 
 100s
 of valuable dev hours.

 In the majority of 

Re: [Dev] [Architecture] Proposed code repository restructuring move to GitHub

[Eranda Sooriyabandara]

Hi All
Please find the updated governance component in [1].

thanks
Eranda

[1]. https://github.com/wso2/carbon-governance


On Tue, Jan 21, 2014 at 2:56 PM, Shariq Muhammed sha...@wso2.com wrote:

 On Tue, Jan 21, 2014 at 2:42 PM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi Shariq,
 Yeah, we may not needed those to be build again and again. So let's add
 related stubs to service-stubs directory in each repo.


 Yea lets structure it that way.



 thanks
 Eranda


 On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed sha...@wso2.comwrote:

 On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Yes, we don't need to separately say service-stubs, it should be
 under the components level as just another component.


 Initially we extracted out the service stubs because it doesn't change
 frequently. So we can reduce the build time because we don't need to do
 wsdl2java in each build cycle. Looks like we are going to add it back?





 On Tue, Jan 21, 2014 at 12:30 PM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi Kicha,
 There will be no service stubs directory it will be a additional
 component in the same level as BE + FE components.

 thanks
 Eranda


 On Tue, Jan 21, 2014 at 11:41 AM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi Eranda,

 Where have you put the service-stubs related to governance component?
 It should come under the same repo as carbon-component-governance.


 On Tue, Jan 21, 2014 at 12:29 AM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi All,
 As a PoC I just completed the carbon-component-governance. Please
 find it in [1] and let me know your comments and suggestions. Please 
 keep
 in mind that this is not in a buildable state since other
 components need to build before this.

 thanks
 Eranda

 [1] https://github.com/wso2/carbon-component-governance


 On Fri, Jan 17, 2014 at 9:26 PM, Afkham Azeez az...@wso2.comwrote:

  [Sorry for the very long mail. I want to document all that I had
 in mind  the stuff we discussed. I would recommend all devs to
 take some time to read this]


 I would like to summarize he discussion we had a couple of days
 back.

 *The Problems*
 The problems we are trying to solve are as follows:

 1. Trunk  branches structures being completely different
 2. Branches containing directories with version numbers
 3. It is impossible to move to GitHub with the current structure
 because of #2
 4. It is very easy to break the build by changing already released
 code. The room for human error is high.
 5. Bamboo builds are eternally broken because the build fails at
 some point  Bamboo cannot continue any further
 6. When we branch, the trunk quickly becomes obsolete, and remains
 in that broken state until the next major platform release.
 7. Everybody has to build all components/features, even if those
 are not related to their products
 8. Fixed versions in branches instead of using SNAPSHOT versions.
 This makes it impossible to upload build artifacts to Maven/Nexus
 repos. This leads to #7.
 9. Impossible to integrate code quality tools such as EraInsight
 because of #5

 *Proposed solution*
 We have come up with the following solution after much deliberation
  thought.

 Rationale:
 We started looking at other open source projects out there. We took
 Axis2 as an example. Axis2 had many dependencies including Axiom,
 XmlSchema, Woden, WSS4J etc. Those 3rd party dependencies were
 also developed by some Axis2 contributors, but we never branched all of
 those together and brought them into the same code branch. We used to 
 start
 what we used to call a release train, where the upstream code would 
 have to
 be released first before the downstream code such as Axis2  Synapse 
 could
 be released. This way, we never had any of the problems outlined above.

 If you look at the WSO2 product releases, again, the scenario is
 not that much different from the Axis2/Synapse releases. Components 
 features are simply dependencies of the products. In order to get 
 product
 releases out, we first need releases of those
 dependencies (components/features). So the proposal is to identify the 
 top
 level components/features, and first release that code before doing 
 product
 releases. Each of those components will have a GitHub repo. All
 active development will be done on the main branch of those 
 components, and
 will be branched when they are close to the release. Instead of 
 granting
 commit rights to all, we could only allow the primary developersof 
 those components to commit, and others can send pull requests, which
 will be merged in by the primary owners after reviewing. These 
 component
 teams could even have an internal Git repo or clone, and commit to
 that, run all tests, and when they are satisfied that the code is in a 
 good
 state to be merged into the main branch, they can send a pull request 
 merge the changes. We would run Bamboo which would build the components
 several times a day  

Re: [Dev] [Architecture] Proposed code repository restructuring move to GitHub

[Sriskandarajah Suhothayan]

How about WSO2 Commons projects, E.g Siddhi ?

Currently its in commons and under dependencies/commons

Where should we have this?

I believe projects like Siddhi also need to be top level repos may be
commons-siddhi and it don't need be in dependencies/commons anymore.

WDYT?

Suho


On Tue, Jan 21, 2014 at 3:13 PM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi All
 Please find the updated governance component in [1].

 thanks
 Eranda

 [1]. https://github.com/wso2/carbon-governance


 On Tue, Jan 21, 2014 at 2:56 PM, Shariq Muhammed sha...@wso2.com wrote:

 On Tue, Jan 21, 2014 at 2:42 PM, Eranda Sooriyabandara 
 era...@wso2.comwrote:

 Hi Shariq,
 Yeah, we may not needed those to be build again and again. So let's add
 related stubs to service-stubs directory in each repo.


 Yea lets structure it that way.



 thanks
 Eranda


 On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed sha...@wso2.comwrote:

 On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Yes, we don't need to separately say service-stubs, it should be
 under the components level as just another component.


 Initially we extracted out the service stubs because it doesn't change
 frequently. So we can reduce the build time because we don't need to do
 wsdl2java in each build cycle. Looks like we are going to add it back?





 On Tue, Jan 21, 2014 at 12:30 PM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi Kicha,
 There will be no service stubs directory it will be a additional
 component in the same level as BE + FE components.

 thanks
 Eranda


 On Tue, Jan 21, 2014 at 11:41 AM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi Eranda,

 Where have you put the service-stubs related to governance
 component? It should come under the same repo as carbon-component-
 governance.


 On Tue, Jan 21, 2014 at 12:29 AM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi All,
 As a PoC I just completed the carbon-component-governance. Please
 find it in [1] and let me know your comments and suggestions. Please 
 keep
 in mind that this is not in a buildable state since other
 components need to build before this.

 thanks
 Eranda

 [1] https://github.com/wso2/carbon-component-governance


 On Fri, Jan 17, 2014 at 9:26 PM, Afkham Azeez az...@wso2.comwrote:

  [Sorry for the very long mail. I want to document all that I had
 in mind  the stuff we discussed. I would recommend all devs to
 take some time to read this]


 I would like to summarize he discussion we had a couple of days
 back.

 *The Problems*
 The problems we are trying to solve are as follows:

 1. Trunk  branches structures being completely different
 2. Branches containing directories with version numbers
 3. It is impossible to move to GitHub with the current structure
 because of #2
 4. It is very easy to break the build by changing already released
 code. The room for human error is high.
 5. Bamboo builds are eternally broken because the build fails at
 some point  Bamboo cannot continue any further
 6. When we branch, the trunk quickly becomes obsolete, and
 remains in that broken state until the next major platform release.
 7. Everybody has to build all components/features, even if those
 are not related to their products
 8. Fixed versions in branches instead of using SNAPSHOT versions.
 This makes it impossible to upload build artifacts to Maven/Nexus
 repos. This leads to #7.
 9. Impossible to integrate code quality tools such as EraInsight
 because of #5

 *Proposed solution*
 We have come up with the following solution after much
 deliberation  thought.

 Rationale:
 We started looking at other open source projects out there. We
 took Axis2 as an example. Axis2 had many dependencies includingAxiom,
 XmlSchema, Woden, WSS4J etc. Those 3rd party dependencies were
 also developed by some Axis2 contributors, but we never branched all 
 of
 those together and brought them into the same code branch. We used to 
 start
 what we used to call a release train, where the upstream code would 
 have to
 be released first before the downstream code such as Axis2  Synapse 
 could
 be released. This way, we never had any of the problems outlined 
 above.

 If you look at the WSO2 product releases, again, the scenario is
 not that much different from the Axis2/Synapse releases. Components 
 features are simply dependencies of the products. In order to get 
 product
 releases out, we first need releases of those
 dependencies (components/features). So the proposal is to identify 
 the top
 level components/features, and first release that code before doing 
 product
 releases. Each of those components will have a GitHub repo. All
 active development will be done on the main branch of those 
 components, and
 will be branched when they are close to the release. Instead of 
 granting
 commit rights to all, we could only allow the primary developersof 
 those components to commit, and others can send pull requests, which
 will be merged in 

Re: [Dev] Please provide an update on stabilizing the current branches chunks?

[Krishantha Samaraweera]

I was able to get though the basic POC to run UI integration tests on sauce
labs environment.

Need to apply all configurations to chunk build plans and see how it is
going. Will update this thread once it is done.

Sample screencast of running tests can be found here -
https://saucelabs.com/tests/92052de7f2304f6f8d589402d57732e0 :)

Thanks,
Krishantha.



On Tue, Jan 21, 2014 at 10:28 AM, Isuruwan Herath isuru...@wso2.com wrote:

 Hi Azeez,
 I created plans and executed all released chunks under Bamboo plan TEST
 4.2.0. Apart from the failure in 'WSO2 API Manager - P2 Profile
 Generation' (noted yesterday) in chunk06 other failures are related to UI
 integration tests (in chunk02, chunk05, chunk06). Krishantha is working on
 the failures in UI tests to run them remotely (I see chunk02 is being built
 at the moment). If we get that through we can run all plans once more and
 confirm all released chunks are clean.

 Regards!
 Isuruwan


 On Tue, Jan 21, 2014 at 8:53 AM, Afkham Azeez az...@wso2.com wrote:

 Isuruwan,
 $subject please.

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




 --
 Isuruwan Herath
 Technical Lead

 Contact: +94 776 273 296




-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Developer Studio 3.5.0 RC 1 Released!

[Asanka Sanjeewa]

Hi All,

We have WSO2 Developer Studio 3.5.0 RC 1 ready to be downloaded at [1].
Installed eclipse distributions available at [2].

This release includes following bug fixes.

Bug Fixes

   - [TOOLS-2312 https://wso2.org/jira/browse/TOOLS-2312] - Complex
   Endpoint editor does not open when double click on created Load Balance,
   Fail Over or Recipient List Endpoint
   - [TOOLS-2315 https://wso2.org/jira/browse/TOOLS-2315] - Default, wsdl
   , http EP templates open in xml editor
   - [TOOLS-2316 https://wso2.org/jira/browse/TOOLS-2316] - When
   importing a synapse config with large number of files its not deserialize
   properly
   - [TOOLS-2317 https://wso2.org/jira/browse/TOOLS-2317] - Default Value
   is wrong in Message processor creation
   - [TOOLS-2322 https://wso2.org/jira/browse/TOOLS-2322] - Message Store
   property value missing in Message Processor configuration
   - [TOOLS-2327 https://wso2.org/jira/browse/TOOLS-2327] - Cannot deploy
   BPEL artifact created from Developer Studio in Business Process Server

Your feedback is most welcome. Please report issues at [3] and specify the
affect version as 3.5.0 RC1.

[1]
http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.5.0/RC1/wso2-developer-studio_3.5.0.zip
[2]
http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.5.0/RC1/
[3] https://wso2.org/jira/browse/TOOLS


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

Thanks and Regards,
WSO2 Developer Studio Team.

-- 
*Asanka Sanjeewa*
Senior Software Engineer
Mobile: +94772532924
WSO2 Inc. http://wso2.com/
Blog: http://asanka-tech-blog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DevS] Version of the source tree (branch) differs from the real version

[Viraj Rajaguru]

Hi,

Created 3.5.0 branch [1].

Thanks,
Viraj.

[1] -
https://svn.wso2.org/repos/wso2/branches/tools/eclipse/developer-studio/3.5.0/


On Thu, Jan 16, 2014 at 9:14 AM, Asanka Sanjeewa asan...@wso2.com wrote:

 Hi Prabath,

 Initially we named the next version of developer studio as 3.3.0 (since
 the last released version was 3.2.0). Therefore the 3.3.0 svn branch was
 created. But while we were working with 3.3.0 version number was changed
 since there are considerable number of new features and improvements
 includes in this release. So the finalized release version number is 3.5.0.
 But still we couldn't rename the svn branch. We'll rename svn branch as
 3.5.0 as it sink with release version number.

 Thanks and Regards,
 AsankaS.


 On Thu, Jan 16, 2014 at 3:40 AM, Prabath Abeysekera praba...@wso2.comwrote:

 Hi DevS team,

 Noticed the $subject. Eventhough the source tree of the branch [1]
 carries the version v3.3.0, the contents seem to refer to v3.5.0. Am I
 missing something?

 [1]
 https://svn.wso2.org/repos/wso2/branches/tools/eclipse/developer-studio/3.3.0/


 Cheers,
 Prabath
 --
 Prabath Abeysekara
 Associate Technical Lead, Data TG.
 WSO2 Inc.
 Email: praba...@wso2.com
 Mobile: +94774171471

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




 --
 *Asanka Sanjeewa*
 Senior Software Engineer
 Mobile: +94772532924
 WSO2 Inc. http://wso2.com/
 Blog: http://asanka-tech-blog.blogspot.com/


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




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

[Dev] Get rid of XKMS, XFer Mex components?

[Afkham Azeez]

Is anybody using this? Using as in, users. Looks like these standards
weren't used much  are now obsolete. Shall we get rid of these?

-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/*
*email: **az...@wso2.com* az...@wso2.com
* cell: +94 77 3320919 blog: **http://blog.afkham.org*http://blog.afkham.org
*twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
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] Get rid of XKMS, XFer Mex components?

[Prabath Siriwardena]

+1 for XKMS

Thanks  regards,
-Prabath


On Tue, Jan 21, 2014 at 5:06 PM, Afkham Azeez az...@wso2.com wrote:

 Is anybody using this? Using as in, users. Looks like these standards
 weren't used much  are now obsolete. Shall we get rid of these?

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




-- 
Thanks  Regards,
Prabath

Twitter : @prabath
LinkedIn : http://www.linkedin.com/in/prabathsiriwardena

Mobile : +94 71 809 6732

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

[Dev] ESB 4.8.1 pack and p2-repo - 21 Jan

[Malaka Silva]

https://svn.wso2.org/repos/wso2/people/malaka/ESB/ESB4.8.1/21-01/

-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/

Save a tree -Conserve nature  Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Jaggery] Writing a Jaggery Client for secured REST Resource

[Kambiz Darabi]

Hi Samisa,

I hope I understand your use case.

I have successfully called Basic Auth secured REST services by creating an
Authorization header in the jaggery code and sending the GET request
with that header.

Quoting from

http://en.wikipedia.org/wiki/Basic_access_authentication#Client_side

you can see that you just have to create a string username:password
(separated by a colon) and encode it in base64, then you add an HTTP
'Authorization' header to the request which contains

Basic + base64_encode( username + : + password);

Here is an example of a js implementation of base64 encoding (I don't
know what the licence is):

http://phpjs.org/functions/base64_encode/


Is this what you are looking for?

I could also dig out some code, when I get back to the office, if that
is necessary.

HTH



Kambiz Darabi
-- 
m-creations gmbh
Acker 2
55116 Mainz
Germany

W: http://www.m-creations.com
E: dar...@m-creations.com
T: +49 6131 6224417
F: +49 6131 6224418
--
Registered Office: Mainz, HRB Mainz 7382
Managing Directors: Frank Pacholak, Kambiz Darabi


Samisa Abeysinghe sam...@wso2.com wrote:
 
 Do we have a sample around this? We need one!

 Thanks,
 Samisa...

 Samisa Abeysinghe

 Vice President Developer Evangelism

 WSO2 Inc. 
 http://wso2.com

 On Tue, Jan 21, 2014 at 10:43 AM, Madhuka Udantha madh...@wso2.com
 wrote:

 Hi Sudheera.
 
 
 you can pass token as header or data[1] depending on your BE
 service is expect. 
 
 
 get(url[, data][, headers][, type][, success(data, xhr)])
 
 
 [1] http://jaggeryjs.org/apidocs/get.jag
 
 
 
 
 
 On Tue, Jan 21, 2014 at 10:22 AM, Sudheera Palihakkara
 sudhe...@wso2.com wrote:
 
 
 
 
 Hi madhuka,
 
 
 Yeah I'm referring to those, But I couldn't find any
 documentation about how to send the security parameters with
 the request. For example I have secured my data service with
 UsernameToken method[1], so in oder to invoke the service I
 have to send the username and the password with the request.
 How to send those parameters with jaggery GET or POST methods?
 
 [1]
 
 http://docs.wso2.org/display/DSS311/Security+Implementation#SecurityImplementation-
 1UsernameToken
 
 
 thank you all. :)
 
 
 
 
 
 
 On Tue, Jan 21, 2014 at 10:13 AM, Madhuka Udantha
 madh...@wso2.com wrote:
 
 
 Hi Sudheera,
 
 
 To call REST service you can try Http Client define in
 jaggery, You can fine sample codes in jaggery
 documentation as well. 
 
 
 * get()[1]
   
 * post() [2]
   
 * put() [3]
   
 * del() [4]
   

 Thanks
 
 
 [1] http://jaggeryjs.org/apidocs/get.jag
 
 [2] http://jaggeryjs.org/apidocs/post.jag
 [3] http://jaggeryjs.org/apidocs/put.jag
 [4] http://jaggeryjs.org/apidocs/del.jag
 
 
 
 
 
 On Tue, Jan 21, 2014 at 9:47 AM, Sudheera Palihakkara
 sudhe...@wso2.com wrote:
 
 
 
 
 Hi,
 
 Thank you for the reply. Can we use the WSRequest
 object to invoke a REST resource defined in DSS? I
 have followed this blog post so far[1], and using http
 GET, POST, DELETE etc methods to invoke the REST
 resources. 
 
 [1]
 http://blog.samisa.org/2014/01/rest-in-json-with-wso2-data-
 services.html
 
 
 thanks.
 
 
 
 
 
 
 On Mon, Jan 20, 2014 at 6:33 PM, Ruchira Wageesha
 ruch...@wso2.com wrote:
 
 
 You can invoke the secured service using WSRequest
 object of Jaggery. Please refer the doc at [1].
 Several sections of the article [2](written for
 mashup server), would also be helpful.
 
 
 /Ruchira
 
 
 
 [1] http://jaggeryjs.org/apidocs/ws.jag
 [2]
 http://ruchirawageesha.blogspot.com/2011/12/blog-post.
 html
 
 
 
 
 
 

[Dev] Fwd: [Commits] [Carbon-platform] svn commit r194818 - carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resou

[Lasantha Fernando]

Hi Malaka,

AFAIK version 1.3.0 of the platform-automated-test-suite is already
released and cannot be committed to. Can you revert this commit and create
a new version and add your commits?

Thanks,
Lasantha

-- Forwarded message --
From: mal...@wso2.com
Date: 21 January 2014 15:20
Subject: [Commits] [Carbon-platform] svn commit r194818 -
carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport
To: comm...@wso2.org


Author: mal...@wso2.com
Date: Tue Jan 21 15:20:48 2014
New Revision: 194818
URL: http://wso2.org/svn/browse/wso2?view=revrevision=194818

Log:
Fix for ESBJAVA-2762

Added:

 
carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml

Added:
carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml?pathrev=194818
==
--- (empty file)
+++
carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml
 Tue Jan 21 15:20:48 2014
@@ -0,0 +1,48 @@
+?xml version=1.0 encoding=UTF-8?
+definitions xmlns=http://ws.apache.org/ns/synapse;
+   registry provider=org.wso2.carbon.mediation.registry.WSO2Registry
+  parameter name=cachableDuration15000/parameter
+   /registry
+   proxy name=JmsToRestProxy
+  transports=jms
+  startOnLoad=true
+  trace=disable
+  description/
+  target
+ inSequence
+property name=OUT_ONLY value=true/
+send
+   endpoint
+  address uri=
http://localhost:8080/rest/api/customerservice/customers/
+   /endpoint
+/send
+ /inSequence
+  /target
+  parameter name=transport.jms.ContentType
+ rules
+jmsPropertycontentType/jmsProperty
+defaultapplication/xml/default
+ /rules
+  /parameter
+   /proxy
+   sequence name=fault
+  log level=full
+ property name=MESSAGE value=Executing default 'fault'
sequence/
+ property name=ERROR_CODE
expression=get-property('ERROR_CODE')/
+ property name=ERROR_MESSAGE
expression=get-property('ERROR_MESSAGE')/
+  /log
+  drop/
+   /sequence
+   sequence name=main
+  in
+ log level=full/
+ filter source=get-property('To') regex=http://localhost:9000.
*
+send/
+ /filter
+  /in
+  out
+ send/
+  /out
+  descriptionThe main sequence for the message
mediation/description
+   /sequence
+/definitions
\ No newline at end of file
___
Commits mailing list
comm...@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/commits



-- 
*Lasantha Fernando*
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] BPS 3.2.0 [Ch-7] Testing

[Amal Gunatilake]

Jan 21st pack -
https://svn.wso2.org/repos/wso2/scratch/amalg/pre-release/bps-3.2.0/2014-01-21/wso2bps-3.2.0.zip

Thank you   Best regards,

*Amal Gunatilake*
 Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware


On Mon, Jan 20, 2014 at 2:47 PM, Thilini Ishaka thil...@wso2.com wrote:

 Jan 20th pack -
 https://svn.wso2.org/repos/wso2/people/thilini/pre-release/bps-3.2.0/2014-01-20/wso2bps-3.2.0.zip

 Thanks
 Thilini


 On Thu, Jan 16, 2014 at 2:28 PM, Thilini Ishaka thil...@wso2.com wrote:

 Jan 16th pack  -
 https://svn.wso2.org/repos/wso2/people/thilini/pre-release/bps-3.2.0/2014-01-16/wso2bps-3.2.0.zip

 This includes humantask versioning implementation.

 Thanks
 Thilini



 On Thu, Jan 9, 2014 at 8:00 PM, Thilini Ishaka thil...@wso2.com wrote:

 Jan-09th pack. This pack contains some important fixes.

 https://svn.wso2.org/repos/wso2/people/thilini/pre-release/bps-3.2.0/2014-01-09/


 Thanks
 Thilini


 On Thu, Jan 9, 2014 at 4:20 PM, Thilini Ishaka thil...@wso2.com wrote:




 On Thu, Jan 9, 2014 at 3:52 PM, Nandika Jayawardana 
 nand...@wso2.comwrote:

 Great. Lets get this tested for Remote oracle, mysql and mssql server.
 Also the process we are testing has to be against a real complex process .
 Otherwise there would not be enough process events written to the db to
 identify the real production scenario impact.


 +1


 Regards
 Nandika


 On Thu, Jan 9, 2014 at 3:44 PM, Thilini Ishaka thil...@wso2.comwrote:

 Hi Nandika,

 Yes, this has been tested for 1 million process instances. You can
 use the attached sample code in 
 BPS-297https://wso2.org/jira/browse/BPS-297[ProcessCleanupToolTest] 
 for load testing this tool.

 Thanks
 Thilini



 On Thu, Jan 9, 2014 at 3:30 PM, Nandika Jayawardana nand...@wso2.com
  wrote:

 Hi Thilini,

 Have we verified the tool with at least a  million process instances
 from different versions of the same process.

 Regards
 Nandika


 On Thu, Jan 9, 2014 at 1:25 PM, Thilini Ishaka thil...@wso2.comwrote:

 We need help for testing the process cleanup tool 
 BPS-297https://wso2.org/jira/browse/BPS-297
 [1]

 Tool is self explanatory, config guide is given with the readme.

 Please note, we have developer tested this only on linux platform.
 Can we pls test this on windows as well?

 [1]
 https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/bps/3.2.0/modules/samples/product/process-cleanup-tool

 Thanks
 Thilini


 On Wed, Jan 8, 2014 at 6:57 PM, Thilini Ishaka thil...@wso2.comwrote:

 BPS 3.2.0 - 08/01/2014 pack is at
 https://svn.wso2.org/repos/wso2/people/thilini/pre-release/bps-3.2.0/2014-01-08

 Thanks
 Thilini


 On Tue, Jan 7, 2014 at 6:29 PM, Thilini Ishaka 
 thil...@wso2.comwrote:

 Please find BPS 3.2.0 - 07/01/2014 build pack at [1].

 [1]
 https://svn.wso2.org/repos/wso2/people/thilini/pre-release/bps-3.2.0/2014-01-07/


 Thanks
 Thilini

 On Mon, Jan 6, 2014 at 4:33 PM, Thilini Ishaka 
 thil...@wso2.comwrote:

 Hi Aparna, Pavithra,

 Latest pack is available to QA.

 [1]
 https://svn.wso2.org/repos/wso2/people/thilini/pre-release/bps-3.2.0/2014-01-06/wso2bps-3.2.0.zip

 Thanks
 Thilini

 --
 Thilini Ishaka
 Senior Software Engineer
  Phone: +94 11 214 5345
 WSO2 Inc. http://wso2.com

 blog: thiliniishaka.blogspot.com
 linkedin: http://lk.linkedin.com/in/thiliniishaka
 twitter: https://twitter.com/#!/ThiliniIsh




 --
 Thilini Ishaka
 Senior Software Engineer
 Phone: +94 11 214 5345
 WSO2 Inc. http://wso2.com

 blog: thiliniishaka.blogspot.com
 linkedin: http://lk.linkedin.com/in/thiliniishaka
 twitter: https://twitter.com/#!/ThiliniIsh




 --
 Thilini Ishaka
 Senior Software Engineer
 Phone: +94 11 214 5345
 WSO2 Inc. http://wso2.com

 blog: thiliniishaka.blogspot.com
 linkedin: http://lk.linkedin.com/in/thiliniishaka
 twitter: https://twitter.com/#!/ThiliniIsh




 --
 Thilini Ishaka
 Senior Software Engineer
 Phone: +94 11 214 5345
 WSO2 Inc. http://wso2.com

 blog: thiliniishaka.blogspot.com
 linkedin: http://lk.linkedin.com/in/thiliniishaka
 twitter: https://twitter.com/#!/ThiliniIsh




 --
 Nandika Jayawardana
 Senior Technical Lead
 WSO2 Inc ; http://wso2.com
 lean.enterprise.middleware




 --
 Thilini Ishaka
 Senior Software Engineer
 Phone: +94 11 214 5345
 WSO2 Inc. http://wso2.com

 blog: thiliniishaka.blogspot.com
 linkedin: http://lk.linkedin.com/in/thiliniishaka
 twitter: https://twitter.com/#!/ThiliniIsh




 --
 Nandika Jayawardana
 Senior Technical Lead
 WSO2 Inc ; http://wso2.com
 lean.enterprise.middleware




 --
 Thilini Ishaka
 Senior Software Engineer
 Phone: +94 11 214 5345
 WSO2 Inc. http://wso2.com

 blog: thiliniishaka.blogspot.com
 linkedin: http://lk.linkedin.com/in/thiliniishaka
 twitter: https://twitter.com/#!/ThiliniIsh




 --
 Thilini Ishaka
 Senior Software Engineer
 Phone: +94 11 214 5345
 WSO2 Inc. http://wso2.com

 blog: thiliniishaka.blogspot.com
 linkedin: http://lk.linkedin.com/in/thiliniishaka
 twitter: https://twitter.com/#!/ThiliniIsh




 --
 Thilini Ishaka
 

Re: [Dev] [Jaggery] Writing a Jaggery Client for secured REST Resource

[Samisa Abeysinghe]

Yes this is what I was looking for. Thanks for the information. And we
should document this

Thanks,
Samisa...


Samisa Abeysinghe

Vice President Developer Evangelism

WSO2 Inc.
http://wso2.com



On Tue, Jan 21, 2014 at 6:29 PM, Kambiz Darabi dar...@m-creations.comwrote:

 Hi Samisa,

 I hope I understand your use case.

 I have successfully called Basic Auth secured REST services by creating an
 Authorization header in the jaggery code and sending the GET request
 with that header.

 Quoting from

 http://en.wikipedia.org/wiki/Basic_access_authentication#Client_side

 you can see that you just have to create a string username:password
 (separated by a colon) and encode it in base64, then you add an HTTP
 'Authorization' header to the request which contains

 Basic + base64_encode( username + : + password);

 Here is an example of a js implementation of base64 encoding (I don't
 know what the licence is):

 http://phpjs.org/functions/base64_encode/


 Is this what you are looking for?

 I could also dig out some code, when I get back to the office, if that
 is necessary.

 HTH



 Kambiz Darabi
 --
 m-creations gmbh
 Acker 2
 55116 Mainz
 Germany

 W: http://www.m-creations.com
 E: dar...@m-creations.com
 T: +49 6131 6224417
 F: +49 6131 6224418
 --
 Registered Office: Mainz, HRB Mainz 7382
 Managing Directors: Frank Pacholak, Kambiz Darabi


 Samisa Abeysinghe sam...@wso2.com wrote:
 
  Do we have a sample around this? We need one!
 
  Thanks,
  Samisa...
 
  Samisa Abeysinghe
 
  Vice President Developer Evangelism
 
  WSO2 Inc.
  http://wso2.com
 
  On Tue, Jan 21, 2014 at 10:43 AM, Madhuka Udantha madh...@wso2.com
  wrote:
 
  Hi Sudheera.
 
 
  you can pass token as header or data[1] depending on your BE
  service is expect.
 
 
  get(url[, data][, headers][, type][, success(data, xhr)])
 
 
  [1] http://jaggeryjs.org/apidocs/get.jag
 
 
 
 
 
  On Tue, Jan 21, 2014 at 10:22 AM, Sudheera Palihakkara
  sudhe...@wso2.com wrote:
 
 
 
 
  Hi madhuka,
 
 
  Yeah I'm referring to those, But I couldn't find any
  documentation about how to send the security parameters with
  the request. For example I have secured my data service with
  UsernameToken method[1], so in oder to invoke the service I
  have to send the username and the password with the request.
  How to send those parameters with jaggery GET or POST methods?
 
  [1]
 
 http://docs.wso2.org/display/DSS311/Security+Implementation#SecurityImplementation-
  1UsernameToken
 
 
  thank you all. :)
 
 
 
 
 
 
  On Tue, Jan 21, 2014 at 10:13 AM, Madhuka Udantha
  madh...@wso2.com wrote:
 
 
  Hi Sudheera,
 
 
  To call REST service you can try Http Client define in
  jaggery, You can fine sample codes in jaggery
  documentation as well.
 
 
  * get()[1]
 
  * post() [2]
 
  * put() [3]
 
  * del() [4]
 
 
  Thanks
 
 
  [1] http://jaggeryjs.org/apidocs/get.jag
 
  [2] http://jaggeryjs.org/apidocs/post.jag
  [3] http://jaggeryjs.org/apidocs/put.jag
  [4] http://jaggeryjs.org/apidocs/del.jag
 
 
 
 
 
  On Tue, Jan 21, 2014 at 9:47 AM, Sudheera Palihakkara
  sudhe...@wso2.com wrote:
 
 
 
 
  Hi,
 
  Thank you for the reply. Can we use the WSRequest
  object to invoke a REST resource defined in DSS? I
  have followed this blog post so far[1], and using http
  GET, POST, DELETE etc methods to invoke the REST
  resources.
 
  [1]
 
 http://blog.samisa.org/2014/01/rest-in-json-with-wso2-data-
  services.html
 
 
  thanks.
 
 
 
 
 
 
  On Mon, Jan 20, 2014 at 6:33 PM, Ruchira Wageesha
  ruch...@wso2.com wrote:
 
 
  You can invoke the secured service using WSRequest
  object of Jaggery. Please refer the doc at [1].
  Several sections of the article [2](written for
  mashup server), would also be helpful.
 
 
  /Ruchira
 
 
 
  [1] http://jaggeryjs.org/apidocs/ws.jag
  [2]
 
 http://ruchirawageesha.blogspot.com/2011/12/blog-post.
  html
 
 
 
 
 
  On Mon, Jan 20, 2014 at 4:06 PM, Sudheera
  Palihakkara sudhe...@wso2.com wrote:
 
 
 
 
 
 
  Hi,
 
 
  I have exposed a data service as a REST
  resource and coded a Jaggery client for the
  service. Now I want to secure this service,
  using DSS I have already secured the service
  with Username 

Re: [Dev] Please provide an update on stabilizing the current branches chunks?

[Krishantha Samaraweera]

Hi Isuruwan,

Following build plans were updated to run UI integration tests on remote
machine. Please rerun the builds and check again.

Chunk 02 - APIM 1.5.0 - Done
Chunk 03 - NONE
Chunk 04 - ESB - 4.8.0 - Done
Chunk 05 - AS - 5.2.1 - Done
Chunk 06 - APIM 1.6.0 - Done

Thanks,
Krishantha.




On Tue, Jan 21, 2014 at 3:49 PM, Krishantha Samaraweera krishan...@wso2.com
 wrote:

 I was able to get though the basic POC to run UI integration tests on
 sauce labs environment.

 Need to apply all configurations to chunk build plans and see how it is
 going. Will update this thread once it is done.

 Sample screencast of running tests can be found here -
 https://saucelabs.com/tests/92052de7f2304f6f8d589402d57732e0 :)

 Thanks,
 Krishantha.



 On Tue, Jan 21, 2014 at 10:28 AM, Isuruwan Herath isuru...@wso2.comwrote:

 Hi Azeez,
 I created plans and executed all released chunks under Bamboo plan TEST
 4.2.0. Apart from the failure in 'WSO2 API Manager - P2 Profile
 Generation' (noted yesterday) in chunk06 other failures are related to UI
 integration tests (in chunk02, chunk05, chunk06). Krishantha is working on
 the failures in UI tests to run them remotely (I see chunk02 is being built
 at the moment). If we get that through we can run all plans once more and
 confirm all released chunks are clean.

 Regards!
 Isuruwan


 On Tue, Jan 21, 2014 at 8:53 AM, Afkham Azeez az...@wso2.com wrote:

 Isuruwan,
 $subject please.

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




 --
 Isuruwan Herath
 Technical Lead

 Contact: +94 776 273 296




 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.




-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Jaggery] Writing a Jaggery Client for secured REST Resource

[Sudheera Palihakkara]

Hi Kambiz,

Thank you very much. :)


On Tue, Jan 21, 2014 at 6:29 PM, Kambiz Darabi dar...@m-creations.comwrote:

 Hi Samisa,

 I hope I understand your use case.

 I have successfully called Basic Auth secured REST services by creating an
 Authorization header in the jaggery code and sending the GET request
 with that header.

 Quoting from

 http://en.wikipedia.org/wiki/Basic_access_authentication#Client_side

 you can see that you just have to create a string username:password
 (separated by a colon) and encode it in base64, then you add an HTTP
 'Authorization' header to the request which contains

 Basic + base64_encode( username + : + password);

 Here is an example of a js implementation of base64 encoding (I don't
 know what the licence is):

 http://phpjs.org/functions/base64_encode/


 Is this what you are looking for?

 I could also dig out some code, when I get back to the office, if that
 is necessary.

 HTH



 Kambiz Darabi
 --
 m-creations gmbh
 Acker 2
 55116 Mainz
 Germany

 W: http://www.m-creations.com
 E: dar...@m-creations.com
 T: +49 6131 6224417
 F: +49 6131 6224418
 --
 Registered Office: Mainz, HRB Mainz 7382
 Managing Directors: Frank Pacholak, Kambiz Darabi


 Samisa Abeysinghe sam...@wso2.com wrote:
 
  Do we have a sample around this? We need one!
 
  Thanks,
  Samisa...
 
  Samisa Abeysinghe
 
  Vice President Developer Evangelism
 
  WSO2 Inc.
  http://wso2.com
 
  On Tue, Jan 21, 2014 at 10:43 AM, Madhuka Udantha madh...@wso2.com
  wrote:
 
  Hi Sudheera.
 
 
  you can pass token as header or data[1] depending on your BE
  service is expect.
 
 
  get(url[, data][, headers][, type][, success(data, xhr)])
 
 
  [1] http://jaggeryjs.org/apidocs/get.jag
 
 
 
 
 
  On Tue, Jan 21, 2014 at 10:22 AM, Sudheera Palihakkara
  sudhe...@wso2.com wrote:
 
 
 
 
  Hi madhuka,
 
 
  Yeah I'm referring to those, But I couldn't find any
  documentation about how to send the security parameters with
  the request. For example I have secured my data service with
  UsernameToken method[1], so in oder to invoke the service I
  have to send the username and the password with the request.
  How to send those parameters with jaggery GET or POST methods?
 
  [1]
 
 http://docs.wso2.org/display/DSS311/Security+Implementation#SecurityImplementation-
  1UsernameToken
 
 
  thank you all. :)
 
 
 
 
 
 
  On Tue, Jan 21, 2014 at 10:13 AM, Madhuka Udantha
  madh...@wso2.com wrote:
 
 
  Hi Sudheera,
 
 
  To call REST service you can try Http Client define in
  jaggery, You can fine sample codes in jaggery
  documentation as well.
 
 
  * get()[1]
 
  * post() [2]
 
  * put() [3]
 
  * del() [4]
 
 
  Thanks
 
 
  [1] http://jaggeryjs.org/apidocs/get.jag
 
  [2] http://jaggeryjs.org/apidocs/post.jag
  [3] http://jaggeryjs.org/apidocs/put.jag
  [4] http://jaggeryjs.org/apidocs/del.jag
 
 
 
 
 
  On Tue, Jan 21, 2014 at 9:47 AM, Sudheera Palihakkara
  sudhe...@wso2.com wrote:
 
 
 
 
  Hi,
 
  Thank you for the reply. Can we use the WSRequest
  object to invoke a REST resource defined in DSS? I
  have followed this blog post so far[1], and using http
  GET, POST, DELETE etc methods to invoke the REST
  resources.
 
  [1]
 
 http://blog.samisa.org/2014/01/rest-in-json-with-wso2-data-
  services.html
 
 
  thanks.
 
 
 
 
 
 
  On Mon, Jan 20, 2014 at 6:33 PM, Ruchira Wageesha
  ruch...@wso2.com wrote:
 
 
  You can invoke the secured service using WSRequest
  object of Jaggery. Please refer the doc at [1].
  Several sections of the article [2](written for
  mashup server), would also be helpful.
 
 
  /Ruchira
 
 
 
  [1] http://jaggeryjs.org/apidocs/ws.jag
  [2]
 
 http://ruchirawageesha.blogspot.com/2011/12/blog-post.
  html
 
 
 
 
 
  On Mon, Jan 20, 2014 at 4:06 PM, Sudheera
  Palihakkara sudhe...@wso2.com wrote:
 
 
 
 
 
 
  Hi,
 
 
  I have exposed a data service as a REST
  resource and coded a Jaggery client for the
  service. Now I want to secure this service,
  using DSS I have already secured the service
  with Username Token implementation, but I have
  no idea how to write a Jaggery client to go
  along with it. Is there are any 

Re: [Dev] ESB 4.8.1 pack and p2-repo - 21 Jan

[Shavantha Weerasinghe]

Hi Malaka

Are their new hl7 features that can be tested with this release

Upto now we are able to test
Reading from hl7
Reading from FTP
Use threadpool for sender/receiver
Pass through invalid mesages

Regards,shavantha
On 21 Jan 2014 18:07, Malaka Silva mal...@wso2.com wrote:

 https://svn.wso2.org/repos/wso2/people/malaka/ESB/ESB4.8.1/21-01/

 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.

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

Re: [Dev] Get rid of XKMS, XFer Mex components?

[Sagara Gunathunga]

+1 per AS perspective no one use these stuff.

Thanks !


On Tue, Jan 21, 2014 at 5:07 PM, Prabath Siriwardena prab...@wso2.comwrote:

 +1 for XKMS

 Thanks  regards,
 -Prabath


 On Tue, Jan 21, 2014 at 5:06 PM, Afkham Azeez az...@wso2.com wrote:

 Is anybody using this? Using as in, users. Looks like these standards
 weren't used much  are now obsolete. Shall we get rid of these?

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




 --
 Thanks  Regards,
 Prabath

 Twitter : @prabath
 LinkedIn : http://www.linkedin.com/in/prabathsiriwardena

 Mobile : +94 71 809 6732

 http://blog.facilelogin.com
 http://blog.api-security.org




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

[Dev] Why BAM 2.4.0 zip file does not contain the ciphertool.sh file?

[Chanaka Fernando]

Hi,

Is there any specific reason to omit ciphertool.sh file from from the BAM
2.4.0 ZIP file?


Thanks,
Chanaka

-- 
--
Chanaka Fernando
Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
Wordpress:http://chanakaudaya.wordpress.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Proposed code repository restructuring move to GitHub

[Sagara Gunathunga]

On Tue, Jan 21, 2014 at 3:34 PM, Sriskandarajah Suhothayan s...@wso2.comwrote:

 How about WSO2 Commons projects, E.g Siddhi ?

 Currently its in commons and under dependencies/commons

 Where should we have this?

 I believe projects like Siddhi also need to be top level repos may be
 commons-siddhi and it don't need be in dependencies/commons anymore.

 WDYT?


Ideally these projects should be treated as external dependencies to Carbon
code base just like Apache XMLSchema or Axiom only difference here is those
project are managed by WSO2. We should create separate repos for each of
them and Carbon should only take them as Maven dependencies only. For
naming I guess Siddhi is a good name because commons part does not make
any meaning here.

in my POV these should be the project we need to move out of Carbon code
base.


Jaggery ( we just need to get rid of SVN externals as code base it already
on GitHub)
Caramel
Charon
Balana
Siddhi

Thanks !





 Suho


 On Tue, Jan 21, 2014 at 3:13 PM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi All
 Please find the updated governance component in [1].

 thanks
 Eranda

 [1]. https://github.com/wso2/carbon-governance


 On Tue, Jan 21, 2014 at 2:56 PM, Shariq Muhammed sha...@wso2.com wrote:

 On Tue, Jan 21, 2014 at 2:42 PM, Eranda Sooriyabandara 
 era...@wso2.comwrote:

 Hi Shariq,
 Yeah, we may not needed those to be build again and again. So let's
 add related stubs to service-stubs directory in each repo.


 Yea lets structure it that way.



 thanks
 Eranda


 On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed sha...@wso2.comwrote:

 On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Yes, we don't need to separately say service-stubs, it should be
 under the components level as just another component.


 Initially we extracted out the service stubs because it doesn't change
 frequently. So we can reduce the build time because we don't need to do
 wsdl2java in each build cycle. Looks like we are going to add it back?





 On Tue, Jan 21, 2014 at 12:30 PM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi Kicha,
 There will be no service stubs directory it will be a additional
 component in the same level as BE + FE components.

 thanks
 Eranda


 On Tue, Jan 21, 2014 at 11:41 AM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi Eranda,

 Where have you put the service-stubs related to governance
 component? It should come under the same repo as carbon-component-
 governance.


 On Tue, Jan 21, 2014 at 12:29 AM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi All,
 As a PoC I just completed the carbon-component-governance. Please
 find it in [1] and let me know your comments and suggestions. Please 
 keep
 in mind that this is not in a buildable state since other
 components need to build before this.

 thanks
 Eranda

 [1] https://github.com/wso2/carbon-component-governance


 On Fri, Jan 17, 2014 at 9:26 PM, Afkham Azeez az...@wso2.comwrote:

  [Sorry for the very long mail. I want to document all that I
 had in mind  the stuff we discussed. I would recommend all devsto 
 take some time to read this]


 I would like to summarize he discussion we had a couple of days
 back.

 *The Problems*
 The problems we are trying to solve are as follows:

 1. Trunk  branches structures being completely different
 2. Branches containing directories with version numbers
 3. It is impossible to move to GitHub with the current structure
 because of #2
 4. It is very easy to break the build by changing already
 released code. The room for human error is high.
 5. Bamboo builds are eternally broken because the build fails at
 some point  Bamboo cannot continue any further
 6. When we branch, the trunk quickly becomes obsolete, and
 remains in that broken state until the next major platform release.
 7. Everybody has to build all components/features, even if those
 are not related to their products
 8. Fixed versions in branches instead of using SNAPSHOT versions.
 This makes it impossible to upload build artifacts to Maven/Nexus
 repos. This leads to #7.
 9. Impossible to integrate code quality tools such as EraInsight
 because of #5

 *Proposed solution*
 We have come up with the following solution after much
 deliberation  thought.

 Rationale:
 We started looking at other open source projects out there. We
 took Axis2 as an example. Axis2 had many dependencies includingAxiom,
 XmlSchema, Woden, WSS4J etc. Those 3rd party dependencies were
 also developed by some Axis2 contributors, but we never branched all 
 of
 those together and brought them into the same code branch. We used 
 to start
 what we used to call a release train, where the upstream code would 
 have to
 be released first before the downstream code such as Axis2  Synapse 
 could
 be released. This way, we never had any of the problems outlined 
 above.

 If you look at the WSO2 product releases, again, the scenario is
 not that much different from the 

Re: [Dev] Why BAM 2.4.0 zip file does not contain the ciphertool.sh file?

[Ajith Vitharana]

On Tue, Jan 21, 2014 at 9:09 PM, Chanaka Fernando chana...@wso2.com wrote:

 Hi,

 Is there any specific reason to omit ciphertool.sh file from from the BAM
 2.4.0 ZIP file? .


I don't think so, Every product should have. This should be a mistake at
the release time.
Anyway you can see the following description top of the file which is
available in other products :)

*ciphertool script for generating stub, skeleton and other required
classes *

Thanks
Ajith.



 Thanks,
 Chanaka

 --
 --
 Chanaka Fernando
 Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com




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




-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why BAM 2.4.0 zip file does not contain the ciphertool.sh file?

[Isuru Perera]

Hi,

I don't know about the reason for excluding, but BAM must have the
ciphertool.sh and ciphertool.bat files. Could you please create a JIRA [1],
so that the BAM team can include it in next release?

Thanks!

[1] https://wso2.org/jira/browse/BAM


On Tue, Jan 21, 2014 at 9:09 PM, Chanaka Fernando chana...@wso2.com wrote:

 Hi,

 Is there any specific reason to omit ciphertool.sh file from from the BAM
 2.4.0 ZIP file?


 Thanks,
 Chanaka

 --
 --
 Chanaka Fernando
 Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com




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




-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

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

Re: [Dev] Why BAM 2.4.0 zip file does not contain the ciphertool.sh file?

[Chanaka Fernando]

Jira created.

https://wso2.org/jira/browse/BAM-1423




On Tue, Jan 21, 2014 at 11:00 AM, Isuru Perera isu...@wso2.com wrote:

 Hi,

 I don't know about the reason for excluding, but BAM must have the
 ciphertool.sh and ciphertool.bat files. Could you please create a JIRA [1],
 so that the BAM team can include it in next release?

 Thanks!

 [1] https://wso2.org/jira/browse/BAM


 On Tue, Jan 21, 2014 at 9:09 PM, Chanaka Fernando chana...@wso2.comwrote:

 Hi,

 Is there any specific reason to omit ciphertool.sh file from from the BAM
 2.4.0 ZIP file?


 Thanks,
 Chanaka

 --
 --
 Chanaka Fernando
 Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com




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




 --
 Isuru Perera
 Senior Software Engineer | WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 about.me/chrishantha




-- 
--
Chanaka Fernando
Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
Wordpress:http://chanakaudaya.wordpress.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] How to add internally used roles at the product startup

[Venura Kahawala]

Hi,

I have seen at some places, roles which are used internally are added to
the user store without having the 'internal' domain. One such case is
org.wso2.carbon.cloud.gateway.agent.internal.CGAgentServiceComponent.activate
method. AFAIK if the user store is configured as a read only one, then an
exception will be thrown.

Aren't we suppose to add internally used roles with 'internal' domain? If
we do so, even though the actual user store is configured as a read only
user store, role will be added to the user management database.

Regards,
Venura

-- 
Senior Software Engineer

Mobile: +94 71 82 300 20
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Proposed code repository restructuring move to GitHub

[Senaka Fernando]

Hi all,

+1 for Sagara's proposal. These projects have a life outside the Carbon
Platform. But, we need to find a place to host them. If everything ends up
on GitHub should these be in their too? If so, are they a WSO2 repository?
Or is it a separate TLP?

Thanks,
Senaka.


On Tue, Jan 21, 2014 at 9:11 PM, Sagara Gunathunga sag...@wso2.com wrote:




 On Tue, Jan 21, 2014 at 3:34 PM, Sriskandarajah Suhothayan 
 s...@wso2.comwrote:

 How about WSO2 Commons projects, E.g Siddhi ?

 Currently its in commons and under dependencies/commons

 Where should we have this?

 I believe projects like Siddhi also need to be top level repos may be
 commons-siddhi and it don't need be in dependencies/commons anymore.

 WDYT?


 Ideally these projects should be treated as external dependencies to
 Carbon code base just like Apache XMLSchema or Axiom only difference here
 is those project are managed by WSO2. We should create separate repos for
 each of them and Carbon should only take them as Maven dependencies only.
 For naming I guess Siddhi is a good name because commons part does not
 make any meaning here.

 in my POV these should be the project we need to move out of Carbon code
 base.


 Jaggery ( we just need to get rid of SVN externals as code base it already
 on GitHub)
 Caramel
 Charon
 Balana
 Siddhi

 Thanks !





 Suho


 On Tue, Jan 21, 2014 at 3:13 PM, Eranda Sooriyabandara 
 era...@wso2.comwrote:

 Hi All
 Please find the updated governance component in [1].

 thanks
 Eranda

 [1]. https://github.com/wso2/carbon-governance


 On Tue, Jan 21, 2014 at 2:56 PM, Shariq Muhammed sha...@wso2.comwrote:

 On Tue, Jan 21, 2014 at 2:42 PM, Eranda Sooriyabandara era...@wso2.com
  wrote:

 Hi Shariq,
 Yeah, we may not needed those to be build again and again. So let's
 add related stubs to service-stubs directory in each repo.


 Yea lets structure it that way.



 thanks
 Eranda


 On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed sha...@wso2.comwrote:

 On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Yes, we don't need to separately say service-stubs, it should be
 under the components level as just another component.


 Initially we extracted out the service stubs because it doesn't
 change frequently. So we can reduce the build time because we don't need 
 to
 do wsdl2java in each build cycle. Looks like we are going to add it back?





 On Tue, Jan 21, 2014 at 12:30 PM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi Kicha,
 There will be no service stubs directory it will be a additional
 component in the same level as BE + FE components.

 thanks
 Eranda


 On Tue, Jan 21, 2014 at 11:41 AM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi Eranda,

 Where have you put the service-stubs related to governance
 component? It should come under the same repo as carbon-component-
 governance.


 On Tue, Jan 21, 2014 at 12:29 AM, Eranda Sooriyabandara 
 era...@wso2.com wrote:

 Hi All,
 As a PoC I just completed the carbon-component-governance.
 Please find it in [1] and let me know your comments and suggestions. 
 Please
 keep in mind that this is not in a buildable state since other
 components need to build before this.

 thanks
 Eranda

 [1] https://github.com/wso2/carbon-component-governance


 On Fri, Jan 17, 2014 at 9:26 PM, Afkham Azeez az...@wso2.comwrote:

  [Sorry for the very long mail. I want to document all that I
 had in mind  the stuff we discussed. I would recommend all devsto 
 take some time to read this]


 I would like to summarize he discussion we had a couple of days
 back.

 *The Problems*
 The problems we are trying to solve are as follows:

 1. Trunk  branches structures being completely different
 2. Branches containing directories with version numbers
 3. It is impossible to move to GitHub with the current structure
 because of #2
 4. It is very easy to break the build by changing already
 released code. The room for human error is high.
 5. Bamboo builds are eternally broken because the build fails at
 some point  Bamboo cannot continue any further
 6. When we branch, the trunk quickly becomes obsolete, and
 remains in that broken state until the next major platform release.
 7. Everybody has to build all components/features, even if those
 are not related to their products
 8. Fixed versions in branches instead of using SNAPSHOT
 versions. This makes it impossible to upload build artifacts to 
 Maven/Nexus
 repos. This leads to #7.
 9. Impossible to integrate code quality tools such as EraInsight
 because of #5

 *Proposed solution*
 We have come up with the following solution after much
 deliberation  thought.

 Rationale:
 We started looking at other open source projects out there. We
 took Axis2 as an example. Axis2 had many dependencies 
 includingAxiom,
 XmlSchema, Woden, WSS4J etc. Those 3rd party dependencies were
 also developed by some Axis2 contributors, but we never branched 
 all of
 those together and brought them into 

Re: [Dev] [Architecture] Proposed code repository restructuring move to GitHub

[Eranda Sooriyabandara]

Hi all,

On Tuesday, January 21, 2014, Senaka Fernando sen...@wso2.com wrote:

 Hi all,

 +1 for Sagara's proposal. These projects have a life outside the Carbon
 Platform. But, we need to find a place to host them. If everything ends up
 on GitHub should these be in their too? If so, are they a WSO2 repository?
 Or is it a separate TLP?


Here Sagara, Senaka came up with a good point. We don't need each and every
one to have a git repo in wso2 space but we can still use svn for managing
these codes where not much of the developers of carbon worry about. WDYT?

Thanks
Eranda


 Thanks,
 Senaka.


 On Tue, Jan 21, 2014 at 9:11 PM, Sagara Gunathunga sag...@wso2.comwrote:




 On Tue, Jan 21, 2014 at 3:34 PM, Sriskandarajah Suhothayan 
 s...@wso2.comwrote:

 How about WSO2 Commons projects, E.g Siddhi ?

 Currently its in commons and under dependencies/commons

 Where should we have this?

 I believe projects like Siddhi also need to be top level repos may be
 commons-siddhi and it don't need be in dependencies/commons anymore.

 WDYT?


 Ideally these projects should be treated as external dependencies to
 Carbon code base just like Apache XMLSchema or Axiom only difference here
 is those project are managed by WSO2. We should create separate repos for
 each of them and Carbon should only take them as Maven dependencies only.
 For naming I guess Siddhi is a good name because commons part does not
 make any meaning here.

 in my POV these should be the project we need to move out of Carbon code
 base.


 Jaggery ( we just need to get rid of SVN externals as code base it already
 on GitHub)
 Caramel
 Charon
 Balana
 Siddhi

 Thanks !





 Suho


 On Tue, Jan 21, 2014 at 3:13 PM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi All
 Please find the updated governance component in [1].

 thanks
 Eranda

 [1]. https://github.com/wso2/carbon-governance


 On Tue, Jan 21, 2014 at 2:56 PM, Shariq Muhammed sha...@wso2.com wrote:

 On Tue, Jan 21, 2014 at 2:42 PM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi Shariq,
 Yeah, we may not needed those to be build again and again. So let's add
 related stubs to service-stubs directory in each repo.


 Yea lets structure it that way.



 thanks
 Eranda


 On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed sha...@wso2.com wrote:

 On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah



 *[image: http://wso2.com] http://wso2.com Senaka Fernando*
 Senior Technical Lead; WSO2 Inc.; http://wso2.com



 * Member; Apache Software Foundation; http://apache.org
 http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1
 408 754 7388; ext: 51736*;


 *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando
 http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware



-- 

*Eranda Sooriyabandara*Senior Software Engineer;
Integration Technologies Team;
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Proposed code repository restructuring move to GitHub

[Afkham Azeez]

On Wed, Jan 22, 2014 at 7:28 AM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi all,


 On Tuesday, January 21, 2014, Senaka Fernando sen...@wso2.com wrote:

 Hi all,

 +1 for Sagara's proposal. These projects have a life outside the Carbon
 Platform. But, we need to find a place to host them. If everything ends up
 on GitHub should these be in their too? If so, are they a WSO2 repository?
 Or is it a separate TLP?


 Here Sagara, Senaka came up with a good point. We don't need each and
 every one to have a git repo in wso2 space but we can still use svn for
 managing these codes where not much of the developers of carbon worry
 about. WDYT?


Let's bring these dependencies into GitHub or any other repo as  when
needed. The changes we make to such dependencies need to be minimized.



 Thanks
 Eranda


 Thanks,
 Senaka.


 On Tue, Jan 21, 2014 at 9:11 PM, Sagara Gunathunga sag...@wso2.comwrote:




 On Tue, Jan 21, 2014 at 3:34 PM, Sriskandarajah Suhothayan s...@wso2.com
  wrote:

 How about WSO2 Commons projects, E.g Siddhi ?

 Currently its in commons and under dependencies/commons

 Where should we have this?

 I believe projects like Siddhi also need to be top level repos may be
 commons-siddhi and it don't need be in dependencies/commons anymore.

 WDYT?


 Ideally these projects should be treated as external dependencies to
 Carbon code base just like Apache XMLSchema or Axiom only difference here
 is those project are managed by WSO2. We should create separate repos for
 each of them and Carbon should only take them as Maven dependencies only.
 For naming I guess Siddhi is a good name because commons part does not
 make any meaning here.

 in my POV these should be the project we need to move out of Carbon code
 base.


 Jaggery ( we just need to get rid of SVN externals as code base it
 already on GitHub)
 Caramel
 Charon
 Balana
 Siddhi

 Thanks !





 Suho


 On Tue, Jan 21, 2014 at 3:13 PM, Eranda Sooriyabandara 
 era...@wso2.comwrote:

 Hi All
 Please find the updated governance component in [1].

 thanks
 Eranda

 [1]. https://github.com/wso2/carbon-governance


 On Tue, Jan 21, 2014 at 2:56 PM, Shariq Muhammed sha...@wso2.com wrote:

 On Tue, Jan 21, 2014 at 2:42 PM, Eranda Sooriyabandara 
 era...@wso2.comwrote:

 Hi Shariq,
 Yeah, we may not needed those to be build again and again. So let's add
 related stubs to service-stubs directory in each repo.


 Yea lets structure it that way.



 thanks
 Eranda


 On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed sha...@wso2.comwrote:

 On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah



 *[image: http://wso2.com] http://wso2.com Senaka Fernando*
 Senior Technical Lead; WSO2 Inc.; http://wso2.com



 * Member; Apache Software Foundation; http://apache.org
 http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1
 408 754 7388 %2B1%20408%20754%207388; ext: 51736*;


 *M: +94 77 322 1818 %2B94%2077%20322%201818 Linked-In:
 http://linkedin.com/in/senakafernando
 http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware



 --

 *Eranda Sooriyabandara*Senior Software Engineer;
 Integration Technologies Team;
 WSO2 Inc.; http://wso2.com
 Lean . Enterprise . Middleware

 E-mail: eranda AT wso2.com
 Mobile: +94 716 472 816
 Linked-In: http://www.linkedin.com/in/erandasooriyabandara
 Blog: http://emsooriyabandara.blogspot.com/






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




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/*
*email: **az...@wso2.com* az...@wso2.com
* cell: +94 77 3320919 blog: **http://blog.afkham.org*http://blog.afkham.org
*twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
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] Why BAM 2.4.0 zip file does not contain the ciphertool.sh file?

[Anjana Fernando]

Hi,

Yeah, it should be included in the product, thanks for reporting it, we
will fix it for the next release.

Cheers,
Anjana.


On Tue, Jan 21, 2014 at 9:39 PM, Chanaka Fernando chana...@wso2.com wrote:

 Jira created.

 https://wso2.org/jira/browse/BAM-1423




 On Tue, Jan 21, 2014 at 11:00 AM, Isuru Perera isu...@wso2.com wrote:

 Hi,

 I don't know about the reason for excluding, but BAM must have the
 ciphertool.sh and ciphertool.bat files. Could you please create a JIRA [1],
 so that the BAM team can include it in next release?

 Thanks!

 [1] https://wso2.org/jira/browse/BAM


 On Tue, Jan 21, 2014 at 9:09 PM, Chanaka Fernando chana...@wso2.comwrote:

 Hi,

 Is there any specific reason to omit ciphertool.sh file from from the
 BAM 2.4.0 ZIP file?


 Thanks,
 Chanaka

 --
 --
 Chanaka Fernando
 Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com




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




 --
 Isuru Perera
 Senior Software Engineer | WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 about.me/chrishantha




 --
 --
 Chanaka Fernando
 Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com






-- 
*Anjana Fernando*
Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Why do we have wso2-carbon-5.0 carbon-kernel both in GitHub?

[Afkham Azeez]

$subject

-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/*
*email: **az...@wso2.com* az...@wso2.com
* cell: +94 77 3320919 blog: **http://blog.afkham.org*http://blog.afkham.org
*twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
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] Why BAM 2.4.0 zip file does not contain the ciphertool.sh file?

[Gokul Balakrishnan]

AFAIK the ciphertool.sh and ciphertool.bat files have so far never been
included in BAM packs. I've fixed this so they will be available in the
subsequent releases.




On 22 January 2014 09:24, Anjana Fernando anj...@wso2.com wrote:

 Hi,

 Yeah, it should be included in the product, thanks for reporting it, we
 will fix it for the next release.

 Cheers,
 Anjana.


 On Tue, Jan 21, 2014 at 9:39 PM, Chanaka Fernando chana...@wso2.comwrote:

 Jira created.

 https://wso2.org/jira/browse/BAM-1423




 On Tue, Jan 21, 2014 at 11:00 AM, Isuru Perera isu...@wso2.com wrote:

 Hi,

 I don't know about the reason for excluding, but BAM must have the
 ciphertool.sh and ciphertool.bat files. Could you please create a JIRA [1],
 so that the BAM team can include it in next release?

 Thanks!

 [1] https://wso2.org/jira/browse/BAM


 On Tue, Jan 21, 2014 at 9:09 PM, Chanaka Fernando chana...@wso2.comwrote:

 Hi,

 Is there any specific reason to omit ciphertool.sh file from from the
 BAM 2.4.0 ZIP file?


 Thanks,
 Chanaka

 --
 --
 Chanaka Fernando
 Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com




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




 --
 Isuru Perera
 Senior Software Engineer | WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 about.me/chrishantha




 --
 --
 Chanaka Fernando
 Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com






 --
 *Anjana Fernando*
 Technical Lead
 WSO2 Inc. | http://wso2.com
 lean . enterprise . middleware

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




-- 
*Balakrishnan Gokulakrishnan*
Software Engineer,
WSO2, Inc.; http://wso2.com
Tel: 0094 11 214 5345  |  Fax: 0094 11 214 5300

Twitter:  http://twitter.com/gokulbs
Mobile: 0094 77 593 5789
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Commits] [Carbon-platform] svn commit r194818 - carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resour

[Malaka Silva]

Yes this was done by mistake. thank you for pointing this out.


On Tue, Jan 21, 2014 at 7:20 PM, Lasantha Fernando lasan...@wso2.comwrote:

 Hi Malaka,

 AFAIK version 1.3.0 of the platform-automated-test-suite is already
 released and cannot be committed to. Can you revert this commit and create
 a new version and add your commits?

 Thanks,
 Lasantha


 -- Forwarded message --
 From: mal...@wso2.com
 Date: 21 January 2014 15:20
 Subject: [Commits] [Carbon-platform] svn commit r194818 -
 carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport
 To: comm...@wso2.org


 Author: mal...@wso2.com
 Date: Tue Jan 21 15:20:48 2014
 New Revision: 194818
 URL: http://wso2.org/svn/browse/wso2?view=revrevision=194818

 Log:
 Fix for ESBJAVA-2762

 Added:

  
 carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml

 Added:
 carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml
 URL:
 http://wso2.org/svn/browse/wso2/carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml?pathrev=194818

 ==
 --- (empty file)
 +++
 carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml
  Tue Jan 21 15:20:48 2014
 @@ -0,0 +1,48 @@
 +?xml version=1.0 encoding=UTF-8?
 +definitions xmlns=http://ws.apache.org/ns/synapse;
 +   registry provider=org.wso2.carbon.mediation.registry.WSO2Registry
 +  parameter name=cachableDuration15000/parameter
 +   /registry
 +   proxy name=JmsToRestProxy
 +  transports=jms
 +  startOnLoad=true
 +  trace=disable
 +  description/
 +  target
 + inSequence
 +property name=OUT_ONLY value=true/
 +send
 +   endpoint
 +  address uri=
 http://localhost:8080/rest/api/customerservice/customers/
 +   /endpoint
 +/send
 + /inSequence
 +  /target
 +  parameter name=transport.jms.ContentType
 + rules
 +jmsPropertycontentType/jmsProperty
 +defaultapplication/xml/default
 + /rules
 +  /parameter
 +   /proxy
 +   sequence name=fault
 +  log level=full
 + property name=MESSAGE value=Executing default 'fault'
 sequence/
 + property name=ERROR_CODE
 expression=get-property('ERROR_CODE')/
 + property name=ERROR_MESSAGE
 expression=get-property('ERROR_MESSAGE')/
 +  /log
 +  drop/
 +   /sequence
 +   sequence name=main
 +  in
 + log level=full/
 + filter source=get-property('To') regex=http://localhost:9000.
 *
 +send/
 + /filter
 +  /in
 +  out
 + send/
 +  /out
 +  descriptionThe main sequence for the message
 mediation/description
 +   /sequence
 +/definitions
 \ No newline at end of file
 ___
 Commits mailing list
 comm...@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/commits



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

 email: lasan...@wso2.com
 mobile: (+94) 71 5247551




-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/

Save a tree -Conserve nature  Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why do we have wso2-carbon-5.0 carbon-kernel both in GitHub?

[Manoj Kumara]

Hi,

The *carbon-kernel* project is the one used currently on active
development. AFAIK  *wso2-carbon-5.0* project has the efforts done during
the time prior to 4.2.0 release targeting C5. I think this is not used
anymore.

@Kishanthan,
Can you confirm.

Thanks,
Manoj

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Wed, Jan 22, 2014 at 9:38 AM, Afkham Azeez az...@wso2.com wrote:

 $subject

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*

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


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

Re: [Dev] Why do we have wso2-carbon-5.0 carbon-kernel both in GitHub?

[Sameera Jayasoma]

Yeah. We no longer need the wso2-carbon-5. 0 repo. It has been created
sometime ago. We should not include the version name in the repo nane.

Active C5 development happens on the other repo.



On Tuesday, January 21, 2014, Manoj Kumara ma...@wso2.com wrote:

 Hi,

 The *carbon-kernel* project is the one used currently on active
 development. AFAIK  *wso2-carbon-5.0* project has the efforts done during
 the time prior to 4.2.0 release targeting C5. I think this is not used
 anymore.

 @Kishanthan,
 Can you confirm.

 Thanks,
 Manoj

 Best Regards..


 Manoj Kumara
 Software Engineer
 WSO2, Inc.; http://wso2.com

 Twitter:  http://twitter.com/ManKuma
 Mobile: +94713448188


 On Wed, Jan 22, 2014 at 9:38 AM, Afkham Azeez 
 az...@wso2.comjavascript:_e({}, 'cvml', 'az...@wso2.com');
  wrote:

 $subject

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* javascript:_e({}, 'cvml', 'az...@wso2.com');
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*

 ___
 Dev mailing list
 Dev@wso2.org javascript:_e({}, 'cvml', 'Dev@wso2.org');
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Sameera Jayasoma,
Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://sameera.adahas.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

Re: [Dev] [ESB] Is there a way other than xslt mediator to alter xml attributes in a payload/header element

[Malaka Silva]

Hi Subash,

You can use Enrich Mediator.

Best Regards,
Malaka


On Fri, Jan 17, 2014 at 9:26 PM, Subash Chaturanga sub...@wso2.com wrote:

 Hi all,
 $subject?

 --
 Thanks
 /subash

 *Subash Chaturanga*
 Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com

 email: sub...@wso2.com
 blog:  http://subashsdm.blogspot.com/
 twitter: @subash89
 phone: +9477 2225922
 Lean . Enterprise . Middleware

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




-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/

Save a tree -Conserve nature  Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Jaggery] Writing a Jaggery Client for secured REST Resource

[Kambiz Darabi]

Hi Samisa,

this thread rang a bell with me and I found something in my personal
notes.

The XMLHttpRequest spec's definition of xhr.open already contains a
username/password argument for basic auth [1].

And according to Mozilla's XHR browser compatibility chart [2], all
desktop browsers are compatible.

It would be simple to add support for it to jaggery.

I have created a DRAFT and COMPLETELY UNTESTED pull request [3] which
sketches the idea, but unfortunately, I don't have the time to implement
that feature myself.

Cheers


Kambiz

[1] http://www.w3.org/TR/XMLHttpRequest/#the-open%28%29-method

[2] 
https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest#Browser_Compatibility

[3] https://github.com/wso2/jaggery/pull/72

Samisa Abeysinghe sam...@wso2.com wrote:
 
 Yes this is what I was looking for. Thanks for the information. And we
 should document this 

 Thanks,
 Samisa...

 Samisa Abeysinghe

 Vice President Developer Evangelism

 WSO2 Inc. 
 http://wso2.com

 On Tue, Jan 21, 2014 at 6:29 PM, Kambiz Darabi
 dar...@m-creations.com wrote:

 Hi Samisa,
 
 I hope I understand your use case.
 
 I have successfully called Basic Auth secured REST services by
 creating an
 Authorization header in the jaggery code and sending the GET
 request
 with that header.
 
 Quoting from
 
 http://en.wikipedia.org/wiki/Basic_access_authentication#Client_side
 
 you can see that you just have to create a string
 username:password
 (separated by a colon) and encode it in base64, then you add an
 HTTP
 'Authorization' header to the request which contains
 
 Basic + base64_encode( username + : + password);
 
 Here is an example of a js implementation of base64 encoding (I
 don't
 know what the licence is):
 
 http://phpjs.org/functions/base64_encode/
 
 
 Is this what you are looking for?
 
 I could also dig out some code, when I get back to the office, if
 that
 is necessary.
 
 HTH
 
 
 
 Kambiz Darabi
 --
 m-creations gmbh
 Acker 2
 55116 Mainz
 Germany
 
 W: http://www.m-creations.com
 E: dar...@m-creations.com
 T: +49 6131 6224417
 F: +49 6131 6224418
 --
 Registered Office: Mainz, HRB Mainz 7382
 Managing Directors: Frank Pacholak, Kambiz Darabi
 
 
 
 
 Samisa Abeysinghe sam...@wso2.com wrote:
 
  Do we have a sample around this? We need one!
 
  Thanks,
  Samisa...
 
  Samisa Abeysinghe
 
  Vice President Developer Evangelism
 
  WSO2 Inc.
  http://wso2.com
 
  On Tue, Jan 21, 2014 at 10:43 AM, Madhuka Udantha
 madh...@wso2.com
  wrote:
 
  Hi Sudheera.
 
 
  you can pass token as header or data[1] depending on your BE
  service is expect.
 
 
  get(url[, data][, headers][, type][, success(data, xhr)])
 
 
  [1] http://jaggeryjs.org/apidocs/get.jag
 
 
 
 
 
  On Tue, Jan 21, 2014 at 10:22 AM, Sudheera Palihakkara
  sudhe...@wso2.com wrote:
 
 
 
 
  Hi madhuka,
 
 
  Yeah I'm referring to those, But I couldn't find any
  documentation about how to send the security parameters with
  the request. For example I have secured my data service with
  UsernameToken method[1], so in oder to invoke the service I
  have to send the username and the password with the request.
  How to send those parameters with jaggery GET or POST methods?
 
  [1]
 
 
 http://docs.wso2.org/display/DSS311/Security+Implementation#SecurityImplementation-
  1UsernameToken
 
 
  thank you all. :)
 
 
 
 
 
 
  On Tue, Jan 21, 2014 at 10:13 AM, Madhuka Udantha
  madh...@wso2.com wrote:
 
 
  Hi Sudheera,
 
 
  To call REST service you can try Http Client define in
  jaggery, You can fine sample codes in jaggery
  documentation as well.
 
 
 
  * get()[1]
 
  * post() [2]
 
  * put() [3]
 
  * del() [4]
 
 
 
 
  Thanks
 
 
  [1] http://jaggeryjs.org/apidocs/get.jag
 
  [2] http://jaggeryjs.org/apidocs/post.jag
  [3] http://jaggeryjs.org/apidocs/put.jag
  [4] http://jaggeryjs.org/apidocs/del.jag
 
 
 
 
 
  On Tue, Jan 21, 2014 at 9:47 AM, Sudheera Palihakkara
  sudhe...@wso2.com wrote:
 
 
 
 
  Hi,
 
  Thank you for the reply. Can we use the WSRequest
  object to invoke a REST resource defined in DSS? I
  have followed this blog post so far[1], and using http
  GET, POST, DELETE etc methods to invoke the REST
  resources.
 
  [1]
  http://blog.samisa.org/2014/01/rest-in-json-with-wso2-data-
  services.html
 
 
  thanks.
 
 
 
   

Re: [Dev] Are we allow users to update artifacts deployed through a CApp using Admin console UI

[Manoj Kumara]

Hi,

AFAIK we agreed not to allow users to modify deployed CApps or its
artifacts through management console.

We consider CApp as an atomic unit and we only support creating or
modifying CApp artifacts through Developer Studio and we may need to
encourage users to use the Dev tool if they need to modify the CApp or its
artifacts.

Once CApp is deployed users cannot modify it. If he need to modify the CApp
or its artifacts he may need to use DevStudio for that and redeploy the
CApp.

Thanks,
Manoj

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Wed, Jan 22, 2014 at 11:10 AM, Asanka Vithanage asan...@wso2.com wrote:

 Hi All,

 If some user try to update a artifact deployed through an CApp as
 described in below scenario, What should be the our answer to an user?

 *Scenario:*
 1. User have created a CApp which include all the artifacts need to try
 out MS and MP on ESB [Attached a such artifact].
 2. Start the ESB server and Deploys the created CApp on ESB server
 3. Due to some reason user wants to just change an one Message Processor
 parameter like Maximum delivery attempts, So using admin console UI he
 changes the parameter value {[UI is the easiest way to do such a small
 change]
 4. Once user restart the server, he will experience the below listed
 exception on stack-trace due to artifact duplication.

 *Note*:
 With current CApp deploy architecture all artifacts deployed through a
 CApp keep on a temporarily location
 [wso2esb-4.8.1/repository/carbonapps/work/] and At every restart CApp will
 redeploy again.
 But if user edits one of capp deployed artifacts It will duplicate same
 artifact inside wso2esb-4.8.1/repository/deployment/server folder hierarchy
 as well.So artifact duplication happen at server restart time.


 So whats our stand on this kind of situation?
 May be we can say we are not allow to update CApp deployed artifacts
 through Admin console UI.
 But we do have real usability issue here, since users tend to use admin
 console UI to make a small changes on an artifact.
 Further our docs [1] does not say anything about this as well.

 [This concern is valid for all the wso2 products which supports CApp
 deployment]


 *Observed following Error:*

 [2014-01-21 18:17:55,517] ERROR - MessageProcessorDeployer Message
 Processor Deployment from the file :
 /home/asankav/servers/releasetest/ESB481/wso2esb-4.8.1/repository/carbonapps/work/1390308470104ESB_MSandMP_WSO2MB_Schenario_TestPack_O_CApp_1.0.0.car/MessageProcessorO1_1.0.0/MessageProcessorO1-1.0.0.xml
 : Failed.
 org.apache.synapse.SynapseException: Error scheduling job : JobDetail
 'synapse.message.processor.quartz.MessageProcessorO1-job':  jobClass:
 'org.apache.synapse.message.processor.impl.forwarder.ForwardingService
 concurrentExectionDisallowed: false persistJobDataAfterExecution: false
 isDurable: false requestsRecovers: false with trigger Trigger
 'DEFAULT.MessageProcessorO1-trigger':  triggerClass:
 'org.quartz.impl.triggers.SimpleTriggerImpl calendar: 'null'
 misfireInstruction: 4 nextFireTime: Tue Jan 21 18:17:55 IST 2014
 at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.start(ScheduledMessageProcessor.java:153)
 at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.init(ScheduledMessageProcessor.java:108)
 at
 org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor.init(ScheduledMessageForwardingProcessor.java:43)
 at
 org.apache.synapse.deployers.MessageProcessorDeployer.deploySynapseArtifact(MessageProcessorDeployer.java:52)
 at
 org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:190)
 at
 org.wso2.carbon.application.deployer.synapse.SynapseAppDeployer.deployArtifacts(SynapseAppDeployer.java:140)
 at
 org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:251)
 at
 org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:114)
 at
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
 at
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
 at
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
 at
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
 at
 org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
 at
 org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
 at
 

Re: [Dev] Are we allow users to update artifacts deployed through a CApp using Admin console UI

[Iranga Muthuthanthri]

This impacts the testing on a cluster setup as well. Please refer
https://wso2.org/jira/browse/ESBJAVA-2912

Regards,
Iranga


On Wed, Jan 22, 2014 at 11:10 AM, Asanka Vithanage asan...@wso2.com wrote:

 Hi All,

 If some user try to update a artifact deployed through an CApp as
 described in below scenario, What should be the our answer to an user?

 *Scenario:*
 1. User have created a CApp which include all the artifacts need to try
 out MS and MP on ESB [Attached a such artifact].
 2. Start the ESB server and Deploys the created CApp on ESB server
 3. Due to some reason user wants to just change an one Message Processor
 parameter like Maximum delivery attempts, So using admin console UI he
 changes the parameter value {[UI is the easiest way to do such a small
 change]
 4. Once user restart the server, he will experience the below listed
 exception on stack-trace due to artifact duplication.

 *Note*:
 With current CApp deploy architecture all artifacts deployed through a
 CApp keep on a temporarily location
 [wso2esb-4.8.1/repository/carbonapps/work/] and At every restart CApp will
 redeploy again.
 But if user edits one of capp deployed artifacts It will duplicate same
 artifact inside wso2esb-4.8.1/repository/deployment/server folder hierarchy
 as well.So artifact duplication happen at server restart time.


 So whats our stand on this kind of situation?
 May be we can say we are not allow to update CApp deployed artifacts
 through Admin console UI.
 But we do have real usability issue here, since users tend to use admin
 console UI to make a small changes on an artifact.
 Further our docs [1] does not say anything about this as well.

 [This concern is valid for all the wso2 products which supports CApp
 deployment]


 *Observed following Error:*

 [2014-01-21 18:17:55,517] ERROR - MessageProcessorDeployer Message
 Processor Deployment from the file :
 /home/asankav/servers/releasetest/ESB481/wso2esb-4.8.1/repository/carbonapps/work/1390308470104ESB_MSandMP_WSO2MB_Schenario_TestPack_O_CApp_1.0.0.car/MessageProcessorO1_1.0.0/MessageProcessorO1-1.0.0.xml
 : Failed.
 org.apache.synapse.SynapseException: Error scheduling job : JobDetail
 'synapse.message.processor.quartz.MessageProcessorO1-job':  jobClass:
 'org.apache.synapse.message.processor.impl.forwarder.ForwardingService
 concurrentExectionDisallowed: false persistJobDataAfterExecution: false
 isDurable: false requestsRecovers: false with trigger Trigger
 'DEFAULT.MessageProcessorO1-trigger':  triggerClass:
 'org.quartz.impl.triggers.SimpleTriggerImpl calendar: 'null'
 misfireInstruction: 4 nextFireTime: Tue Jan 21 18:17:55 IST 2014
 at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.start(ScheduledMessageProcessor.java:153)
 at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.init(ScheduledMessageProcessor.java:108)
 at
 org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor.init(ScheduledMessageForwardingProcessor.java:43)
 at
 org.apache.synapse.deployers.MessageProcessorDeployer.deploySynapseArtifact(MessageProcessorDeployer.java:52)
 at
 org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:190)
 at
 org.wso2.carbon.application.deployer.synapse.SynapseAppDeployer.deployArtifacts(SynapseAppDeployer.java:140)
 at
 org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:251)
 at
 org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:114)
 at
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
 at
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
 at
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
 at
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
 at
 org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
 at
 org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
 at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
 at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
 at
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
 at
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
 at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
 at
 

Re: [Dev] Are we allow users to update artifacts deployed through a CApp using Admin console UI

[Afkham Azeez]

On Wed, Jan 22, 2014 at 11:22 AM, Manoj Kumara ma...@wso2.com wrote:

 Hi,

 AFAIK we agreed not to allow users to modify deployed CApps or its
 artifacts through management console.

 We consider CApp as an atomic unit and we only support creating or
 modifying CApp artifacts through Developer Studio and we may need to
 encourage users to use the Dev tool if they need to modify the CApp or its
 artifacts.


Yes, we cannot allow modifications to parts of deployed artifacts through
the console. We tried to support this, and it was a slippery slope.
Besides, nobody would do this in production.


 Once CApp is deployed users cannot modify it. If he need to modify the
 CApp or its artifacts he may need to use DevStudio for that and redeploy
 the CApp.

 Thanks,
 Manoj

 Best Regards..


 Manoj Kumara
 Software Engineer
 WSO2, Inc.; http://wso2.com

 Twitter:  http://twitter.com/ManKuma
 Mobile: +94713448188


 On Wed, Jan 22, 2014 at 11:10 AM, Asanka Vithanage asan...@wso2.comwrote:

 Hi All,

 If some user try to update a artifact deployed through an CApp as
 described in below scenario, What should be the our answer to an user?

 *Scenario:*
 1. User have created a CApp which include all the artifacts need to try
 out MS and MP on ESB [Attached a such artifact].
 2. Start the ESB server and Deploys the created CApp on ESB server
 3. Due to some reason user wants to just change an one Message Processor
 parameter like Maximum delivery attempts, So using admin console UI he
 changes the parameter value {[UI is the easiest way to do such a small
 change]
 4. Once user restart the server, he will experience the below listed
 exception on stack-trace due to artifact duplication.

 *Note*:
 With current CApp deploy architecture all artifacts deployed through a
 CApp keep on a temporarily location
 [wso2esb-4.8.1/repository/carbonapps/work/] and At every restart CApp will
 redeploy again.
 But if user edits one of capp deployed artifacts It will duplicate same
 artifact inside wso2esb-4.8.1/repository/deployment/server folder hierarchy
 as well.So artifact duplication happen at server restart time.


 So whats our stand on this kind of situation?
 May be we can say we are not allow to update CApp deployed artifacts
 through Admin console UI.
 But we do have real usability issue here, since users tend to use admin
 console UI to make a small changes on an artifact.
 Further our docs [1] does not say anything about this as well.

 [This concern is valid for all the wso2 products which supports CApp
 deployment]


 *Observed following Error:*

 [2014-01-21 18:17:55,517] ERROR - MessageProcessorDeployer Message
 Processor Deployment from the file :
 /home/asankav/servers/releasetest/ESB481/wso2esb-4.8.1/repository/carbonapps/work/1390308470104ESB_MSandMP_WSO2MB_Schenario_TestPack_O_CApp_1.0.0.car/MessageProcessorO1_1.0.0/MessageProcessorO1-1.0.0.xml
 : Failed.
 org.apache.synapse.SynapseException: Error scheduling job : JobDetail
 'synapse.message.processor.quartz.MessageProcessorO1-job':  jobClass:
 'org.apache.synapse.message.processor.impl.forwarder.ForwardingService
 concurrentExectionDisallowed: false persistJobDataAfterExecution: false
 isDurable: false requestsRecovers: false with trigger Trigger
 'DEFAULT.MessageProcessorO1-trigger':  triggerClass:
 'org.quartz.impl.triggers.SimpleTriggerImpl calendar: 'null'
 misfireInstruction: 4 nextFireTime: Tue Jan 21 18:17:55 IST 2014
 at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.start(ScheduledMessageProcessor.java:153)
 at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.init(ScheduledMessageProcessor.java:108)
 at
 org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor.init(ScheduledMessageForwardingProcessor.java:43)
 at
 org.apache.synapse.deployers.MessageProcessorDeployer.deploySynapseArtifact(MessageProcessorDeployer.java:52)
 at
 org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:190)
 at
 org.wso2.carbon.application.deployer.synapse.SynapseAppDeployer.deployArtifacts(SynapseAppDeployer.java:140)
 at
 org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:251)
 at
 org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:114)
 at
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
 at
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
 at
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
 at
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
 at
 org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
 at
 org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
 at
 

Re: [Dev] Are we allow users to update artifacts deployed through a CApp using Admin console UI

[Kishanthan Thangarajah]

CApp is a self contained project. So you cant update part of the project as
every artifact in the CApp is part of it. If any update needed, it should
be to whole CApp project and it should come through the process starting
from DevStudio - Update Artifact - Repack CApp - Update CApp in Server.
This is our recommendation.

Other ways to update an artifact in CApp is not recommended. We need to
update the docs.


On Wed, Jan 22, 2014 at 11:10 AM, Asanka Vithanage asan...@wso2.com wrote:

 Hi All,

 If some user try to update a artifact deployed through an CApp as
 described in below scenario, What should be the our answer to an user?

 *Scenario:*
 1. User have created a CApp which include all the artifacts need to try
 out MS and MP on ESB [Attached a such artifact].
 2. Start the ESB server and Deploys the created CApp on ESB server
 3. Due to some reason user wants to just change an one Message Processor
 parameter like Maximum delivery attempts, So using admin console UI he
 changes the parameter value {[UI is the easiest way to do such a small
 change]
 4. Once user restart the server, he will experience the below listed
 exception on stack-trace due to artifact duplication.

 *Note*:
 With current CApp deploy architecture all artifacts deployed through a
 CApp keep on a temporarily location
 [wso2esb-4.8.1/repository/carbonapps/work/] and At every restart CApp will
 redeploy again.
 But if user edits one of capp deployed artifacts It will duplicate same
 artifact inside wso2esb-4.8.1/repository/deployment/server folder hierarchy
 as well.So artifact duplication happen at server restart time.


 So whats our stand on this kind of situation?
 May be we can say we are not allow to update CApp deployed artifacts
 through Admin console UI.
 But we do have real usability issue here, since users tend to use admin
 console UI to make a small changes on an artifact.
 Further our docs [1] does not say anything about this as well.

 [This concern is valid for all the wso2 products which supports CApp
 deployment]


 *Observed following Error:*

 [2014-01-21 18:17:55,517] ERROR - MessageProcessorDeployer Message
 Processor Deployment from the file :
 /home/asankav/servers/releasetest/ESB481/wso2esb-4.8.1/repository/carbonapps/work/1390308470104ESB_MSandMP_WSO2MB_Schenario_TestPack_O_CApp_1.0.0.car/MessageProcessorO1_1.0.0/MessageProcessorO1-1.0.0.xml
 : Failed.
 org.apache.synapse.SynapseException: Error scheduling job : JobDetail
 'synapse.message.processor.quartz.MessageProcessorO1-job':  jobClass:
 'org.apache.synapse.message.processor.impl.forwarder.ForwardingService
 concurrentExectionDisallowed: false persistJobDataAfterExecution: false
 isDurable: false requestsRecovers: false with trigger Trigger
 'DEFAULT.MessageProcessorO1-trigger':  triggerClass:
 'org.quartz.impl.triggers.SimpleTriggerImpl calendar: 'null'
 misfireInstruction: 4 nextFireTime: Tue Jan 21 18:17:55 IST 2014
 at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.start(ScheduledMessageProcessor.java:153)
 at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.init(ScheduledMessageProcessor.java:108)
 at
 org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor.init(ScheduledMessageForwardingProcessor.java:43)
 at
 org.apache.synapse.deployers.MessageProcessorDeployer.deploySynapseArtifact(MessageProcessorDeployer.java:52)
 at
 org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:190)
 at
 org.wso2.carbon.application.deployer.synapse.SynapseAppDeployer.deployArtifacts(SynapseAppDeployer.java:140)
 at
 org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:251)
 at
 org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:114)
 at
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
 at
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
 at
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
 at
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
 at
 org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
 at
 org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
 at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
 at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
 at
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
 at
 

Re: [Dev] Are we allow users to update artifacts deployed through a CApp using Admin console UI

[Asanka Vithanage]

Hi Doc team,
Shall we update the carbon documentation appropriately then?


On Wed, Jan 22, 2014 at 11:25 AM, Kishanthan Thangarajah 
kishant...@wso2.com wrote:

 CApp is a self contained project. So you cant update part of the project
 as every artifact in the CApp is part of it. If any update needed, it
 should be to whole CApp project and it should come through the process
 starting from DevStudio - Update Artifact - Repack CApp - Update CApp in
 Server. This is our recommendation.

 Other ways to update an artifact in CApp is not recommended. We need to
 update the docs.


 On Wed, Jan 22, 2014 at 11:10 AM, Asanka Vithanage asan...@wso2.comwrote:

 Hi All,

 If some user try to update a artifact deployed through an CApp as
 described in below scenario, What should be the our answer to an user?

 *Scenario:*
 1. User have created a CApp which include all the artifacts need to try
 out MS and MP on ESB [Attached a such artifact].
 2. Start the ESB server and Deploys the created CApp on ESB server
 3. Due to some reason user wants to just change an one Message Processor
 parameter like Maximum delivery attempts, So using admin console UI he
 changes the parameter value {[UI is the easiest way to do such a small
 change]
 4. Once user restart the server, he will experience the below listed
 exception on stack-trace due to artifact duplication.

 *Note*:
 With current CApp deploy architecture all artifacts deployed through a
 CApp keep on a temporarily location
 [wso2esb-4.8.1/repository/carbonapps/work/] and At every restart CApp will
 redeploy again.
 But if user edits one of capp deployed artifacts It will duplicate same
 artifact inside wso2esb-4.8.1/repository/deployment/server folder hierarchy
 as well.So artifact duplication happen at server restart time.


 So whats our stand on this kind of situation?
 May be we can say we are not allow to update CApp deployed artifacts
 through Admin console UI.
 But we do have real usability issue here, since users tend to use admin
 console UI to make a small changes on an artifact.
 Further our docs [1] does not say anything about this as well.

 [This concern is valid for all the wso2 products which supports CApp
 deployment]


 *Observed following Error:*

 [2014-01-21 18:17:55,517] ERROR - MessageProcessorDeployer Message
 Processor Deployment from the file :
 /home/asankav/servers/releasetest/ESB481/wso2esb-4.8.1/repository/carbonapps/work/1390308470104ESB_MSandMP_WSO2MB_Schenario_TestPack_O_CApp_1.0.0.car/MessageProcessorO1_1.0.0/MessageProcessorO1-1.0.0.xml
 : Failed.
 org.apache.synapse.SynapseException: Error scheduling job : JobDetail
 'synapse.message.processor.quartz.MessageProcessorO1-job':  jobClass:
 'org.apache.synapse.message.processor.impl.forwarder.ForwardingService
 concurrentExectionDisallowed: false persistJobDataAfterExecution: false
 isDurable: false requestsRecovers: false with trigger Trigger
 'DEFAULT.MessageProcessorO1-trigger':  triggerClass:
 'org.quartz.impl.triggers.SimpleTriggerImpl calendar: 'null'
 misfireInstruction: 4 nextFireTime: Tue Jan 21 18:17:55 IST 2014
 at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.start(ScheduledMessageProcessor.java:153)
 at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.init(ScheduledMessageProcessor.java:108)
 at
 org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor.init(ScheduledMessageForwardingProcessor.java:43)
 at
 org.apache.synapse.deployers.MessageProcessorDeployer.deploySynapseArtifact(MessageProcessorDeployer.java:52)
 at
 org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:190)
 at
 org.wso2.carbon.application.deployer.synapse.SynapseAppDeployer.deployArtifacts(SynapseAppDeployer.java:140)
 at
 org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:251)
 at
 org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:114)
 at
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
 at
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
 at
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
 at
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
 at
 org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
 at
 org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
 at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
 at
 

[Dev] [DEV][ESB] Message Processor change state after throwing exception

[Rajith Vitharana]

Hi,

I was doing some tests about EIP with ESB. There I created a
ScheduledMessageForwardingProcessor to retry the messages when ever the
service is unavailable. It works fine, it retries and send the message when
the service is available,but in the process it throws
java.lang.InterruptedException and message processor goes back to
Inactive state. Please find the full stack trace below. Am I missing
something? I have followed this[1] tutorial about Dead Letter Channel EIP

stack trace -

java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:552)


[1] http://docs.wso2.org/display/IntegrationPatterns/Dead+Letter+Channel

-- 
Rajith Vitharana

Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94715883223
Blog : http://lankavitharana.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please provide an update on stabilizing the current branches chunks?

[Lasantha Fernando]

On 21 January 2014 12:55, Isuruwan Herath isuru...@wso2.com wrote:

 Hi Lasantha,

 Following is the error occurred in Bamboo log [1] :

 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5.3:p2-profile-gen
 (p2-profile-generation-for-gateway-manager-profile) on project
 am-p2-profile: P2 publisher return code was 137 - [Help 1]

 Bamboo plan is configured to build from chunk06 folder in branch.

 [1] http://wso2.org/bamboo/browse/TEST001-EPC6-1/log


Hi Isuruwan,

Asked for the logs since thought I might have made a mistake in creating
the tag for chunk-06. I did verify it in a clean repo build. AFAIK, there
were some changes done to the p2-repo after the tag was created. But no
changes were done to the product builds. Guess those commits also need to
go into the tag.

Anyway, looks like the current build failure in chunk-06 is due to UI
integration tests.

Thanks,
Lasantha




 Regards!



 On Tue, Jan 21, 2014 at 11:28 AM, Lasantha Fernando lasan...@wso2.comwrote:

 Hi Isuruwan,

 Can you post the error you encountered in building chunk-06? Are you
 building from the chunk-06 tag?

 Thanks,
 Lasantha


 On 21 January 2014 10:45, Afkham Azeez az...@wso2.com wrote:

  Krishantha,
 If the UI tests cannot be fixed by EOD today, let's disable them until
 we find a proper solution.


 On Tue, Jan 21, 2014 at 10:28 AM, Isuruwan Herath isuru...@wso2.comwrote:

 Hi Azeez,
 I created plans and executed all released chunks under Bamboo plan TEST
 4.2.0. Apart from the failure in 'WSO2 API Manager - P2 Profile
 Generation' (noted yesterday) in chunk06 other failures are related to UI
 integration tests (in chunk02, chunk05, chunk06). Krishantha is working on
 the failures in UI tests to run them remotely (I see chunk02 is being built
 at the moment). If we get that through we can run all plans once more and
 confirm all released chunks are clean.

 Regards!
 Isuruwan


 On Tue, Jan 21, 2014 at 8:53 AM, Afkham Azeez az...@wso2.com wrote:

 Isuruwan,
 $subject please.

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




 --
 Isuruwan Herath
 Technical Lead

 Contact: +94 776 273 296




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*

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




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

 email: lasan...@wso2.com
 mobile: (+94) 71 5247551




 --
 Isuruwan Herath
 Technical Lead

 Contact: +94 776 273 296




-- 
*Lasantha Fernando*
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] Please provide an update on stabilizing the current branches chunks?

[Isuruwan Herath]

Yes, rebuilding the failures did not give the mentioned error again. As the
UI tests have been worked around I'm running bamboo plans again from
chunk02 and let's see if the p2-profile-gen fails again. Thanks for looking
into this.

Cheers!
Isuruwan


On Wed, Jan 22, 2014 at 11:51 AM, Lasantha Fernando lasan...@wso2.comwrote:




 On 21 January 2014 12:55, Isuruwan Herath isuru...@wso2.com wrote:

 Hi Lasantha,

 Following is the error occurred in Bamboo log [1] :

 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5.3:p2-profile-gen
 (p2-profile-generation-for-gateway-manager-profile) on project
 am-p2-profile: P2 publisher return code was 137 - [Help 1]

 Bamboo plan is configured to build from chunk06 folder in branch.

 [1] http://wso2.org/bamboo/browse/TEST001-EPC6-1/log


 Hi Isuruwan,

 Asked for the logs since thought I might have made a mistake in creating
 the tag for chunk-06. I did verify it in a clean repo build. AFAIK, there
 were some changes done to the p2-repo after the tag was created. But no
 changes were done to the product builds. Guess those commits also need to
 go into the tag.

 Anyway, looks like the current build failure in chunk-06 is due to UI
 integration tests.

 Thanks,
 Lasantha




 Regards!



 On Tue, Jan 21, 2014 at 11:28 AM, Lasantha Fernando lasan...@wso2.comwrote:

 Hi Isuruwan,

 Can you post the error you encountered in building chunk-06? Are you
 building from the chunk-06 tag?

 Thanks,
 Lasantha


 On 21 January 2014 10:45, Afkham Azeez az...@wso2.com wrote:

  Krishantha,
 If the UI tests cannot be fixed by EOD today, let's disable them until
 we find a proper solution.


 On Tue, Jan 21, 2014 at 10:28 AM, Isuruwan Herath isuru...@wso2.comwrote:

 Hi Azeez,
 I created plans and executed all released chunks under Bamboo plan
 TEST 4.2.0. Apart from the failure in 'WSO2 API Manager - P2 Profile
 Generation' (noted yesterday) in chunk06 other failures are related to UI
 integration tests (in chunk02, chunk05, chunk06). Krishantha is working on
 the failures in UI tests to run them remotely (I see chunk02 is being 
 built
 at the moment). If we get that through we can run all plans once more and
 confirm all released chunks are clean.

 Regards!
 Isuruwan


 On Tue, Jan 21, 2014 at 8:53 AM, Afkham Azeez az...@wso2.com wrote:

 Isuruwan,
 $subject please.

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




 --
 Isuruwan Herath
 Technical Lead

 Contact: +94 776 273 296




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*

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




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

 email: lasan...@wso2.com
 mobile: (+94) 71 5247551




 --
 Isuruwan Herath
 Technical Lead

 Contact: +94 776 273 296




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

 email: lasan...@wso2.com
 mobile: (+94) 71 5247551




-- 
Isuruwan Herath
Technical Lead

Contact: +94 776 273 296
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] r194908 - carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport

[Malaka Silva]

I commit ed to
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/esb/4.8.1/modules/integration/tests-transport/

But commit has gone to some other location?

carbon/platform/branches/turing/platform-integration/
platform-automated-test-suite/1.3.0/org.wso2.carbon.
automation.test.repo/src/main/resources/artifacts/ESB/jms/
transport/jmsclient-and-restService.xml


On Wed, Jan 22, 2014 at 1:27 PM, mal...@wso2.com wrote:

 Author: mal...@wso2.com
 Date: 2014-01-22 13:27:25 +0530 (Wed, 22 Jan 2014)
 New Revision: 194908

 Added:

  
 carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml
 Log:
 test case resource added

 Added:
 carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml
 ===
 ---
 carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml
  (rev 0)
 +++
 carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/1.3.0/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB/jms/transport/jmsclient-and-restService.xml
  2014-01-22 07:57:25 UTC (rev 194908)
 @@ -0,0 +1,48 @@
 +?xml version=1.0 encoding=UTF-8?
 +definitions xmlns=http://ws.apache.org/ns/synapse;
 +   registry provider=org.wso2.carbon.mediation.registry.WSO2Registry
 +  parameter name=cachableDuration15000/parameter
 +   /registry
 +   proxy name=JmsToRestProxy
 +  transports=jms
 +  startOnLoad=true
 +  trace=disable
 +  description/
 +  target
 + inSequence
 +property name=OUT_ONLY value=true/
 +send
 +   endpoint
 +  address uri=
 http://localhost:8080/rest/api/customerservice/customers/
 +   /endpoint
 +/send
 + /inSequence
 +  /target
 +  parameter name=transport.jms.ContentType
 + rules
 +jmsPropertycontentType/jmsProperty
 +defaultapplication/xml/default
 + /rules
 +  /parameter
 +   /proxy
 +   sequence name=fault
 +  log level=full
 + property name=MESSAGE value=Executing default 'fault'
 sequence/
 + property name=ERROR_CODE
 expression=get-property('ERROR_CODE')/
 + property name=ERROR_MESSAGE
 expression=get-property('ERROR_MESSAGE')/
 +  /log
 +  drop/
 +   /sequence
 +   sequence name=main
 +  in
 + log level=full/
 + filter source=get-property('To') regex=http://localhost:9000.
 *
 +send/
 + /filter
 +  /in
 +  out
 + send/
 +  /out
 +  descriptionThe main sequence for the message
 mediation/description
 +   /sequence
 +/definitions




-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/

Save a tree -Conserve nature  Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev