Re: [Dev] Please merge pull request #83
Hi Pulasthi, We will review and merge the pull request. On Fri, Aug 22, 2014 at 5:36 PM, Pulasthi Mahawithana wrote: > Hi, > > Please merge pull request #83 [1] which is a fix to the issue discussed in > thread [2] > > [1] https://github.com/wso2-dev/carbon4-kernel/pull/83 > [2] [DEV] JAX-RS servlet instantiation fails due to NoClassDefFoundError > > -- > *Pulasthi Mahawithana* > Software Engineer > WSO2 Inc., http://wso2.com/ > Mobile: +94-71-5179022 > Blog: http://blog.pulasthi.org > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please merge performance improvemts for caching pull request
Hi Thanuja, Could you please update the relevant Jira ticket, that way we can keep track everything in one place. Thanks, Shameera. On Thu, Aug 21, 2014 at 11:07 PM, Thanuja Jayasinghe wrote: > Hi Carbon Team, > > Please merge the pull request - > https://github.com/wso2-dev/carbon4-kernel/pull/82 > > Thanks, > Thanuja. > -- > *Thanuja Lakmal* > Software Engineer > WSO2 Inc. http://wso2.com/ > *lean.enterprise.middleware* > Mobile: +94715979891 > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failure in chunk-13 ntask component
Hi Gokul, Merged the Hazelcast upgrade request to the kernel git repo, please re apply ntask. It isn't that easy to merge a fix like this as we need to think about all the downstream builds. However sorry for the delay and inconvenience this made. Thanks, Shameera. On Fri, Aug 15, 2014 at 4:43 PM, Gokul Balakrishnan wrote: > The Hz pull request was 6 days old and should by rights have been merged, > unless there was some compelling reason stopping it (if there was, it was > never communicated). Since the change was already propagated to SVN (and > was causing a build failure) I made the fix and sent the corresponding pull > request to the carbon-utils. IMO the discrepancy between SVN and Git is > what causes situations like this. > > @Kernel team please let us know once the pull request has been merged so > that we can re-apply the fix for ntask. > > > On 15 August 2014 16:27, Gayashan Amarasinghe wrote: > >> Hi Gokul, >> >> >> On Fri, Aug 15, 2014 at 3:39 PM, Gokul Balakrishnan >> wrote: >> >>> I've reverted the change to ntask in Git so that the build will pass for >>> the time being, but it will have to be made again once the version upgrade >>> is merged; so IMO this is not the correct way to deal this situation, as we >>> should have merged the Hz version upgrade pull request instead. >>> >> >> +1, Agree with you on this. We need to find a better process to handle >> scenarios like this. (I have came across the same scenario when fixing >> [1].) Anyway it shouldn't have been merged to utils since the HZ upgrade >> was not there in the first place. As KasunG has mentioned it might take >> some time to get this merged to kernel. >> >> [1] https://wso2.org/jira/browse/CARBON-14867 >> >> >> >>> Any reason why we haven't done so? >>> >>> >>> On 15 August 2014 15:30, Gayashan Amarasinghe wrote: >>> >>>> Hi Gokul, >>>> >>>> Hazelcast upgrade [1] has not been merged to the >>>> wso2-dev/carbon4-kernel yet. I did check with the hazelcast upgrade on a >>>> local merge and carbon-utils (with your changes on ntask) get built without >>>> an issue. So might need to revert the changes done to carbon-utils until >>>> the relevant hz changes are merged to kernel. >>>> >>>> [1] https://github.com/wso2-dev/carbon4-kernel/pull/62 >>>> >>>> Thanks. >>>> >>>> /Gayashan >>>> >>>> >>>> On Fri, Aug 15, 2014 at 2:58 PM, Gokul Balakrishnan >>>> wrote: >>>> >>>>> Hi Kasun, >>>>> >>>>> Has the Hazelcast upgrade in question not been done in the git repo, >>>>> because the fix causes build failures in the ntask component under >>>>> wso2-dev >>>>> (as per mail "Build Failure in Carbon-utils")? Can you please clarify? >>>>> >>>>> Thanks, >>>>> >>>>> >>>>> On 14 August 2014 11:40, Gokul Balakrishnan wrote: >>>>> >>>>>> Fixed in r206532. >>>>>> >>>>>> >>>>>> On 14 August 2014 09:36, Sinthuja Ragendran >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Still the issue exists. Please fix it ASAP, since we need to get the >>>>>>> pack out for testing. >>>>>>> >>>>>>> Thanks, >>>>>>> Sinthuja >>>>>>> >>>>>>> >>>>>>> On Wed, Aug 13, 2014 at 10:48 AM, Shameera Rathnayaka < >>>>>>> shame...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi Kasun, >>>>>>>> >>>>>>>> Please fix this, This is downstream build error with hazelcast >>>>>>>> upgrade. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Shameera. >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Aug 13, 2014 at 9:53 AM, Dinusha Senanayaka < >>>>>>>> dinu...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> Getting following build failure. Should be relate with patch0009 >>>>>>>>> updates ? >>
Re: [Dev] Patch for kernel 4.2.0
Hi Ajith, Merged the pull reqeuest , https://github.com/wso2-dev/carbon4-kernel/pull/74 Thanks, Shameera. On Fri, Aug 15, 2014 at 11:53 AM, Ajith Vitharana wrote: > > > > On Wed, Aug 13, 2014 at 7:44 AM, Shameera Rathnayaka > wrote: > >> Hi Ajith, >> >> Applied patch to kernel patch0009 , BTW i moved above JIRA to WSO2 >> CARBON[1] as it solve carbon kernel component. Please send a pull request >> to carbon kernel 4.3.0 git repo. >> > > Please merge [1]. > > [1]https://github.com/wso2-dev/carbon4-kernel/pull/66 > > Thanks > Ajith > >> >> [1] https://wso2.org/jira/browse/CARBON-14912 >> >> Thanks, >> Shameera. >> >> >> On Tue, Aug 12, 2014 at 9:35 PM, Ajith Vitharana wrote: >> >>> [Adding dev group.] >>> >>> >>> On Tue, Aug 12, 2014 at 9:32 PM, Ajith Vitharana >>> wrote: >>> >>>> Hi Shameera, >>>> >>>> Please commit the patch [1] to registry.core. >>>> >>>> [1]https://wso2.org/jira/browse/REGISTRY-2262 >>>> >>>> Thanks >>>> Ajith. >>>> >>>> -- >>>> Ajith Vitharana. >>>> WSO2 Inc. - http://wso2.org >>>> Email : aji...@wso2.com >>>> Mobile : +94772217350 >>>> >>>> >>> >>> >>> -- >>> Ajith Vitharana. >>> WSO2 Inc. - http://wso2.org >>> Email : aji...@wso2.com >>> Mobile : +94772217350 >>> >>> >> >> >> -- >> *Software Engineer - WSO2 Inc.* >> *email: shameera AT wso2.com , shameera AT apache.org >> * >> *phone: +9471 922 1454 <%2B9471%20922%201454>* >> >> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >> *Twitter : *https://twitter.com/Shameera_R >> > > > > -- > Ajith Vitharana. > WSO2 Inc. - http://wso2.org > Email : aji...@wso2.com > Mobile : +94772217350 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Commit to kernal patch0009
Done , Committed revision 206555. ~Shameera. On Fri, Aug 15, 2014 at 11:24 AM, Isura Karunaratne wrote: > Hi All, > > Please commit following > > https://wso2.org/jira/browse/CARBON-14916 > > Thanks > Isura > -- > Isura Dilhara Karunaratne > Software Engineer > > Mob +94 772 254 810 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Request to commit the patch CARBON-14911
Hi Azeez, Done, Committed revision 206550. @Thanuja, you need to send a pull request to the carbon kernel 4.3.0 git repo in order to resolve this ticker please do the needful. Thanks, Shameera. On Thu, Aug 14, 2014 at 7:44 PM, Afkham Azeez wrote: > This patch contains the changes from the previous caching patch too. Hence > it needs to be applied to the previous revision. > > > On Thu, Aug 14, 2014 at 7:15 PM, Aruna Karunarathna > wrote: > >> Hi all, >> >> >> https://wso2.org/jira/secure/attachment/33260/caching-perf-optimizations.patch >> >> file cannot commit. There are some conflicts. Please check. >> >> Regards, >> Aruna >> >> >> On Thu, Aug 14, 2014 at 3:15 PM, Thanuja Jayasinghe >> wrote: >> >>> Hi Carbon Team, >>> >>> Please commit the diffs attached with [1]. >>> >>> [1] - https://wso2.org/jira/browse/CARBON-14911 >>> >>> Thanks, >>> Thanuja. >>> -- >>> *Thanuja Lakmal* >>> Software Engineer >>> WSO2 Inc. http://wso2.com/ >>> *lean.enterprise.middleware* >>> Mobile: +94715979891 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> * Aruna Sujith Karunarathna* | Software Engineer >> WSO2, Inc | lean. enterprise. middleware. >> #20, Palm Grove, Colombo 03, Sri Lanka >> Mobile: +94 71 9040362 | Work: +94 112145345 >> Email: ar...@wso2.com | Web: www.wso2.com >> >> > > > > -- > *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* > * 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* > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Deploying dataservice configuration with services.xml using Capp.
Hi Chanika,
In Axis2 .aar file we use META-INF directory to keep the services.xml file
and in tomcat .war file there is WEB-INF to keep web.xml file, By looking
at the consistency it is better to keep services.xml file in a separate
directory . And make sure to use proper name for the above subdirectory.
Thanks,
Shameera.
On Wed, Aug 13, 2014 at 4:45 PM, Chanika Geeganage wrote:
> Hi,
>
> There is a requirement to deploy dataservice configuration (.dbs) file
> with its corresponding services.xml using Capp. According to the current
> implementation, DefaultAppDeployer[1] calls .dsb files deployer. As the
> artifacts in the Capp are extracted and copied to a temporary location
> before deploying the services, we thought of changing the dataservice
> deployer code to pick the services.xml as well. So I tried to add the
> services.xml file as below to the car file.
>
> SampleCar-1.0.0
> |-- artifacts.xml
> |-- SampleDataService_1.0.0
> |-- artifacts.xml
> |-- SampleDataService-1.0.0.dbs
> |-- SampleDataService_service.xml
>
>
> But it seems only one file is allowed to have per a dependency.
> (SampleDataService is a dependency for the root artifact). It gives the
> following error.
>
> ERROR {org.wso2.carbon.application.deployer.handler.DefaultAppDeployer} -
> service/dataservice type must have a single file. But 2 files found.
>
> Then the idea is to use the following dependency tree.
> testCar-1.0.0
> |-- artifacts.xml
> |-- SampleDataService_1.0.0
> |-- artifacts.xml
> |-- SampleDataService-1.0.0.dbs
> |-- servicesMetaFiles
> |-- SampleDataService_service.xml
> |-- artifacts.xml
>
> We may need to change the dataservice code to lookup for servicesMetaFiles
> folder for services.xml file.
>
> Will this be a correct way to fulfill the requirement?
>
> Anyway in the future we will move to a single archive format to archive
> both dataservice config and the services.xml file.
>
> [1]
> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/handler/DefaultAppDeployer.java
>
> --
> Best Regards..
>
> Chanika Geeganage
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
>
--
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com , shameera AT apache.org
*
*phone: +9471 922 1454*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] SystemFilter not filtering __MultitenantDispatcherService
Hi Gokul, Carbon kernel doesn't has a service call "MultitenantDispatcherService". I did a grep and found out that this is coming from data-agent which is bam component :). Thanks, Shameera. On Thu, Aug 14, 2014 at 1:55 PM, Gokul Balakrishnan wrote: > Hi Shameera, > > Since AFAIK it is the kernel team who's managing the core multitenancy > components, can you make this service a filteredOutService? > > Thanks, > > > On 13 August 2014 12:47, Shameera Rathnayaka wrote: > >> Hi Gokul, >> >> Basically above util method filltered out all adminservices , >> hiddenServices and dynamicServices. If you define any of these parameters >> to true using services.xml then that services is become filteredOutService. >> >> Thanks, >> Shameera. >> >> >> >> >> On Mon, Aug 11, 2014 at 3:32 PM, Gokul Balakrishnan >> wrote: >> >>> Hi Kernel team, >>> >>> In BAM Message Tracer, our requirement is to log calls to all hosted >>> services while filtering out any admin service calls. We >>> use SystemFilter.isFilteredOutService() from Carbon core for this purpose. >>> >>> However, it appears that __MultitenantDispatcherService is not being >>> filtered out as expected and ends up getting logged and sent to Cassandra >>> when publishing as tenant [1]. Can you please shed some light as to the >>> cause and any possible fixes for this? >>> >>> [1] https://wso2.org/jira/browse/BAM-1730 >>> >>> Thanks, >>> >>> -- >>> *Balakrishnan Gokulakrishnan* >>> Software Engineer, >>> WSO2, Inc. http://wso2.com >>> Mob: +94 77 593 5789 | +1 650 272 9927 >>> >> >> >> >> -- >> *Software Engineer - WSO2 Inc.* >> *email: shameera AT wso2.com , shameera AT apache.org >> * >> *phone: +9471 922 1454 <%2B9471%20922%201454>* >> >> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >> *Twitter : *https://twitter.com/Shameera_R >> > > > > -- > *Balakrishnan Gokulakrishnan* > Software Engineer, > WSO2, Inc. http://wso2.com > Mob: +94 77 593 5789 | +1 650 272 9927 > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] SystemFilter not filtering __MultitenantDispatcherService
Hi Gokul, Basically above util method filltered out all adminservices , hiddenServices and dynamicServices. If you define any of these parameters to true using services.xml then that services is become filteredOutService. Thanks, Shameera. On Mon, Aug 11, 2014 at 3:32 PM, Gokul Balakrishnan wrote: > Hi Kernel team, > > In BAM Message Tracer, our requirement is to log calls to all hosted > services while filtering out any admin service calls. We > use SystemFilter.isFilteredOutService() from Carbon core for this purpose. > > However, it appears that __MultitenantDispatcherService is not being > filtered out as expected and ends up getting logged and sent to Cassandra > when publishing as tenant [1]. Can you please shed some light as to the > cause and any possible fixes for this? > > [1] https://wso2.org/jira/browse/BAM-1730 > > Thanks, > > -- > *Balakrishnan Gokulakrishnan* > Software Engineer, > WSO2, Inc. http://wso2.com > Mob: +94 77 593 5789 | +1 650 272 9927 > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failure in chunk-13 ntask component
Hi Kasun, Please fix this, This is downstream build error with hazelcast upgrade. Cheers, Shameera. On Wed, Aug 13, 2014 at 9:53 AM, Dinusha Senanayaka wrote: > Hi, > > Getting following build failure. Should be relate with patch0009 updates ? > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile > (default-compile) on project org.wso2.carbon.ntask.core: Compilation failure > [ERROR] > /opt/checkout_chunk13/platform/branches/turing/components/ntask/org.wso2.carbon.ntask.core/4.2.4/src/main/java/org/wso2/carbon/ntask/core/impl/clustered/ClusterGroupCommunicator.java:[45,7] > org.wso2.carbon.ntask.core.impl.clustered.ClusterGroupCommunicator is not > abstract and does not override abstract method > memberAttributeChanged(com.hazelcast.core.MemberAttributeEvent) in > com.hazelcast.core.MembershipListener > > Regards, > Dinusha. > > -- > Dinusha Dilrukshi > Senior Software Engineer > WSO2 Inc.: http://wso2.com/ > Mobile: +94725255071 > Blog: http://dinushasblog.blogspot.com/ > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Patch for kernel 4.2.0
Hi Ajith, Applied patch to kernel patch0009 , BTW i moved above JIRA to WSO2 CARBON[1] as it solve carbon kernel component. Please send a pull request to carbon kernel 4.3.0 git repo. [1] https://wso2.org/jira/browse/CARBON-14912 Thanks, Shameera. On Tue, Aug 12, 2014 at 9:35 PM, Ajith Vitharana wrote: > [Adding dev group.] > > > On Tue, Aug 12, 2014 at 9:32 PM, Ajith Vitharana wrote: > >> Hi Shameera, >> >> Please commit the patch [1] to registry.core. >> >> [1]https://wso2.org/jira/browse/REGISTRY-2262 >> >> Thanks >> Ajith. >> >> -- >> Ajith Vitharana. >> WSO2 Inc. - http://wso2.org >> Email : aji...@wso2.com >> Mobile : +94772217350 >> >> > > > -- > Ajith Vitharana. > WSO2 Inc. - http://wso2.org > Email : aji...@wso2.com > Mobile : +94772217350 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Shall we remove unused modules from Carbon kernel code base?
org.wso2.carbon.caching.core is there in nexus. On Tue, Aug 12, 2014 at 12:47 AM, Shameera Rathnayaka wrote: > Hi all, > > There are two moduldes( org.wso2.carbon.caching.core and > org.wso2.carbon.context ) that we have commented out in our root pom.xml > and we haven't released those artifacts with 4.2.0. either. Shall we > remove those two components from carbon kernel 4.3.0 code base? > > Thanks, > Shameera. > > -- > *Software Engineer - WSO2 Inc.* > *email: shameera AT wso2.com , shameera AT apache.org > * > *phone: +9471 922 1454 <%2B9471%20922%201454>* > > *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 > *Twitter : *https://twitter.com/Shameera_R > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Shall we remove unused modules from Carbon kernel code base?
Hi all, There are two moduldes( org.wso2.carbon.caching.core and org.wso2.carbon.context ) that we have commented out in our root pom.xml and we haven't released those artifacts with 4.2.0. either. Shall we remove those two components from carbon kernel 4.3.0 code base? Thanks, Shameera. -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failure in kernel patch0009
Fixed , please take an svn up and try . On Tue, Aug 12, 2014 at 12:21 AM, Dinusha Senanayaka wrote: > Hi, > > Getting following compilation failures while building patch0009. > > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/HazelcastGroupManagementAgent.java:[33,25] > cannot find symbol > symbol : class MemberAttributeEvent > location: package com.hazelcast.core > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/HazelcastGroupManagementAgent.java:[204,43] > cannot find symbol > symbol : class MemberAttributeEvent > location: class > org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent.GroupMembershipListener > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/multicast/MulticastBasedMembershipScheme.java:[24,25] > cannot find symbol > symbol : class MemberAttributeEvent > location: package com.hazelcast.core > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/multicast/MulticastBasedMembershipScheme.java:[144,43] > cannot find symbol > symbol : class MemberAttributeEvent > location: class > org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme.MulticastMembershipListener > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/aws/AWSBasedMembershipScheme.java:[26,25] > cannot find symbol > symbol : class MemberAttributeEvent > location: package com.hazelcast.core > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/aws/AWSBasedMembershipScheme.java:[155,43] > cannot find symbol > symbol : class MemberAttributeEvent > location: class > org.wso2.carbon.core.clustering.hazelcast.aws.AWSBasedMembershipScheme.AWSMembershipListener > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/HazelcastClusteringAgent.java:[24,27] > cannot find symbol > symbol : class InMemoryFormat > location: package com.hazelcast.config > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/wka/WKABasedMembershipScheme.java:[28,25] > cannot find symbol > symbol : class MemberAttributeEvent > location: package com.hazelcast.core > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/wka/WKABasedMembershipScheme.java:[177,43] > cannot find symbol > symbol : class MemberAttributeEvent > location: class > org.wso2.carbon.core.clustering.hazelcast.wka.WKABasedMembershipScheme.WKAMembershipListener > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/multicast/MulticastBasedMembershipScheme.java:[143,8] > method does not override or implement a method from a supertype > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/HazelcastClusteringAgent.java:[148,40] > cannot find symbol > symbol : variable InMemoryFormat > location: class > org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent > [ERROR] > /opt/checkout_chunk13/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/wka/WKABasedMembershipScheme.java:[176,8] > method does not override or implement a method from a supertype > [INFO] 12 errors > [INFO] - > > > Regards, > Dinusha. > > -- > Dinusha Dilrukshi > Senior Software Engineer > WSO2 Inc.: http://wso2.com/ > Mobile: +94725255071 > Blog: http://dinushasblog.blogspot.com/ > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Carbon Commit Required.
Hi Malaka, Done , Committed revision 206456. In order to resolve this issue you need to send a pull request to relevant git repo. ~Shameera. On Mon, Aug 11, 2014 at 3:29 PM, Malaka Silva wrote: > Hi Carbon Team, > > Please commit the diff attached with [1] > > [1] https://wso2.org/jira/browse/CARBON-14910 > > Thank you. > > Best Regards, > > Malaka Silva > Senior Tech Lead > M: +94 777 219 791 > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > 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. > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Disable reloading super tenant themes to the registry in each server start
Hi All, With the provided patch, there is a side effect when someone accidentally delete one file(lets say *.gif image) in the theme location, that file not get replace with server restart. However we can resolve this by a workaround which is ask user to restart by setting "true" to ReloadThemeOnServerRestart and then again change it to "false" and restart. I have attached preQA patch to the support ticket and move to WOC, will release Official patch as soon as all QA works complete. Thanks, Shameera. On Fri, Aug 8, 2014 at 12:33 PM, Shameera Rathnayaka wrote: > Hi Eranda et al, > > Little bit concern regarding the 4th configuration value decision, Please > see my comment inline. > > On Sat, Apr 19, 2014 at 5:03 AM, Eranda Sooriyabandara > wrote: > >> >> Here is the configuration which we will be adding to the carbon.xml >> >> true >> >> There can be several cases, >> >>1. Configuration is not in carbon.xml - This will consider this >>configuration value as true and will reload the themes every time start >> the >>server >>2. Configuration value true - This will reload the themes every time >>start the server >>3. Configuration value false - This will stop updating the themes in >>registry every time start the server >>4. Configuration value other than true/false - This will consider >>this configuration value as false and won't reload the themes. >> >> Shouldn't we go with default value which is true, when the configuration > is missing or wrong ? Above rule seems bit inconsistence in that case. > > Thanks, > Shameera. > >> >>1. Theme not in the registry - If the theme which is in the file >>system is not there in the registry, it will ignore the ReloadThemes >>configuration value and add that theme to registry. >> >> Thoughts? >> Patch attached. >> >> thanks >> Eranda >> >> -- >> >> *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 >> >> > > > -- > *Software Engineer - WSO2 Inc.* > *email: shameera AT wso2.com , shameera AT apache.org > * > *phone: +9471 922 1454 <%2B9471%20922%201454>* > > *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 > *Twitter : *https://twitter.com/Shameera_R > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Disable reloading super tenant themes to the registry in each server start
Hi Eranda et al, Little bit concern regarding the 4th configuration value decision, Please see my comment inline. On Sat, Apr 19, 2014 at 5:03 AM, Eranda Sooriyabandara wrote: > > Here is the configuration which we will be adding to the carbon.xml > > true > > There can be several cases, > >1. Configuration is not in carbon.xml - This will consider this >configuration value as true and will reload the themes every time start the >server >2. Configuration value true - This will reload the themes every time >start the server >3. Configuration value false - This will stop updating the themes in >registry every time start the server >4. Configuration value other than true/false - This will consider this >configuration value as false and won't reload the themes. > > Shouldn't we go with default value which is true, when the configuration is missing or wrong ? Above rule seems bit inconsistence in that case. Thanks, Shameera. > >1. Theme not in the registry - If the theme which is in the file >system is not there in the registry, it will ignore the ReloadThemes >configuration value and add that theme to registry. > > Thoughts? > Patch attached. > > thanks > Eranda > > -- > > *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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454 <%2B9471%20922%201454>* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?
Even though jar name is synapse-core-test its artifactId is synapse-core , try with org.apache.synapse synapse-core 2.1.2-wso2v4 ~Shameera. On Thu, Aug 7, 2014 at 9:58 PM, Ishara Premadasa wrote: > Hi all, > > I get the following build error when trying to check out remote ESB > mediator project and trying to build it online. Since there are test cases > created for the class mediators, it is required to add synapse-core-tests > dependency into the pom.xml and use that in the test cases. Below is the > dependency and my maven repository entry. > > > org.apache.synapse > synapse-core-tests > 2.1.2-wso2v4 > > > > true > daily > ignore > > wso2-nexus > http://maven.wso2.org/nexus/content/groups/wso2-public/ > > > > Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure > to find org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 in > http://maven.wso2.org/nexus/content/groups/ws > o2-public/ was cached in the local repository, resolution will not be > reattempted until the update interval of wso2-nexus has elapsed or updates > are forced > at > org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:232) > at > org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206) > at > org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:599) > at > org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:518) > at > org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:436) > ... 26 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > > This says unable to find > org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 jar but if you > traverse this can be located in neus-repo [1]. > Any help is appreciated. > > [1] > http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/synapse/synapse-core/2.1.2-wso2v4/ > > Thanks! > Ishara > -- > Ishara Premasada > Software Engineer, > WSO2 Inc. http://wso2.com/ > > > *Blog : http://isharapremadasa.blogspot.com/ > <http://isharapremadasa.blogspot.com/>Twitter : > https://twitter.com/ishadil <https://twitter.com/ishadil> Mobile : > +94 714445832 <%2B94%20714445832>* > > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Commits to kernel patch0009
Hi Asela, Applied patches , Committed revision 206380, please send pull request to 4.3.0 git repo too. Thanks, Shameera. On Wed, Aug 6, 2014 at 7:45 PM, Afkham Azeez wrote: > Here is the new patch with eviction made a private package, and also > removing API additions in CacheImpl. Asela, we need to test with the new > caching jar. > > > On Wed, Aug 6, 2014 at 5:52 PM, Afkham Azeez wrote: > >> >> >> >> On Wed, Aug 6, 2014 at 5:35 PM, Shameera Rathnayaka >> wrote: >> >>> Hi Azeez, >>> >>> On Wed, Aug 6, 2014 at 5:11 PM, Afkham Azeez wrote: >>> >>>> Yes, ideally we should have exported only javax.cache.*. However, I >>>> think one of Asela's patch has a coupling to CacheImpl since caching API >>>> does not provide a way to set the cache capacity. However, there are no API >>>> changes in CacheImpl. >>>> >>> >>> There are API changes in CacheImpl class ( it has two public method to >>> get size and cache capacity). and both are used in classes in eviction >>> package. In that case what should we do? >>> >>> >>> >> >> I can remove those methods. Let me do that & resend the patch. >> >> >>> Thanks, >>> Shameera. >>> >>> >>> The only API changes are in the org.wso2.carbon.caching.impl.eviction >>>> package. That package is totally internal to the caching impl. We can make >>>> that private. >>>> >>>> >>>> On Wed, Aug 6, 2014 at 4:50 PM, Shameera Rathnayaka >>>> wrote: >>>> >>>>> Hi Azeez, >>>>> >>>>> Saw that "org.wso2.carbon.caching.impl.*, " is there under export >>>>> packages, should this expose the latest API addition to the outside at >>>>> runtime?. My understand is this can be an issue in future. WDYT? if this >>>>> is the only way to patch this, isn't it better we make all new API private >>>>> to this bundle, i mean configure it as private package? >>>>> >>>>> Thanks, >>>>> Shameera. >>>>> >>>>> >>>>> >>>>> >>>>> On Wed, Aug 6, 2014 at 2:32 PM, Afkham Azeez wrote: >>>>> >>>>>> There are API changes within java.cache, but all of those changes >>>>>> affect only that bundle, and are internal to that bundle, and don't >>>>>> affect >>>>>> the bundles outside it. Hence, there is no issue in committing the >>>>>> caching >>>>>> fix. >>>>>> >>>>>> >>>>>> On Wed, Aug 6, 2014 at 2:28 PM, Asela Pathberiya >>>>>> wrote: >>>>>> >>>>>>> Hi Shameera, >>>>>>> >>>>>>> There is no any API in user core patch... We have only added a >>>>>>> private method. As i got to know, It is not allowed to add even >>>>>>> private method. Therefore i modified the code and attached the patch >>>>>>> in to the jira. >>>>>>> >>>>>>> AFAIK, there is no any caching API changes in caching.core as well... >>>>>>> >>>>>>> Therefore i hope it is fine to apply the patches... >>>>>>> >>>>>>> Adding Azeez... >>>>>>> >>>>>>> Thanks, >>>>>>> Asela. >>>>>>> >>>>>>> On Wed, Aug 6, 2014 at 2:13 PM, Shameera Rathnayaka < >>>>>>> shame...@wso2.com> wrote: >>>>>>> > Hi Asela, >>>>>>> > >>>>>>> > As we discussed, it is not allowed to do any API changes to 4.2.0 >>>>>>> patches. >>>>>>> > So please reattached the patch removing all API changes. And the >>>>>>> already >>>>>>> > attached patch can be applied to 4.3.0 git repo. So please send >>>>>>> those as >>>>>>> > pull request. >>>>>>> > >>>>>>> > Thanks, >>>>>>> > Shameera. >>>>>>> > >>>>>>> > >>>>>>> > On Wed, Aug 6, 2014 at 1:02 PM, Asela Pathberiya >>>>>>> wrote: >>>>>>> >>
Re: [Dev] [GReg] Build failure on carbon-governance wso2-dev git repo
Hi Subash, Thanks for the quick reply, If this is because of latest change then you can simply revert it back to previous stable state. Later you can merge the changes once you confirm it will not cause to any build issue. This is one of major feature we get with git. Thanks, Shameera. On Wed, Aug 6, 2014 at 11:39 PM, Subash Chaturanga wrote: > Hi Shameera, > Currently entire team on support/patches. Will followup once those are > sorted out. > > > On Wed, Aug 6, 2014 at 10:57 PM, Shameera Rathnayaka > wrote: > >> Hi Greg team, >> >> This issue is still there, please fix this. Jenkins build will not work >> because of this. find the error log below. >> >> T E S T S >> --- >> Running org.wso2.carbon.governance.api.test.WSDLTest >> log4j:WARN No appenders could be found for logger >> (org.wso2.carbon.context.internal.CarbonContextDataHolder). >> log4j:WARN Please initialize the log4j system properly. >> Retrieving document at ' >> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl >> '. >> Retrieving schema at '../xsd/purchasing.xsd', relative to ' >> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl >> '. >> Retrieving document at ' >> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl >> '. >> Retrieving schema at '../xsd/purchasing.xsd', relative to ' >> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl >> '. >> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.203 sec >> <<< FAILURE! >> Running org.wso2.carbon.governance.api.test.SchemaTest >> log4j:WARN No appenders could be found for logger >> (org.wso2.carbon.context.internal.CarbonContextDataHolder). >> log4j:WARN Please initialize the log4j system properly. >> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.762 sec >> Running org.wso2.carbon.governance.api.test.PolicyTest >> log4j:WARN No appenders could be found for logger >> (org.wso2.carbon.context.internal.CarbonContextDataHolder). >> log4j:WARN Please initialize the log4j system properly. >> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.196 sec >> >> Results : >> >> Tests in error: >> testAddWSDL(org.wso2.carbon.governance.api.test.WSDLTest): Error in >> adding the wsdl. wsdl id: bcb699c4-3134-4442-92f3-e28900805942. >> >> >> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0 >> >> >> >> >> >> >> >> >> On Tue, Aug 5, 2014 at 3:24 PM, Gayashan Amarasinghe >> wrote: >> >>> Hi GReg team, >>> >>> I am getting the following test failures when building carbon-governance >>> git repo. (mvn 3.0.5, java 1.6) Can we get this fixed? >>> >>> Results : >>> >>> Tests in error: >>> testAddWSDL(org.wso2.carbon.governance.api.test.WSDLTest): Error in >>> adding the wsdl. wsdl id: 758ae3e7-7c2e-4dab-8f55-70406525e207. >>> >>> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0 >>> >>> [INFO] >>> >>> [INFO] Reactor Summary: >>> [INFO] >>> [INFO] WSO2 Carbon - Platform Aggregator Pom . SUCCESS >>> [0.103s] >>> [INFO] WSO2 Carbon - Service Stubs - Aggregator Module ... SUCCESS >>> [0.008s] >>> [INFO] WSO2 Carbon - Governance - Notifications Work list Human Task >>> Stub SUCCESS [3.893s] >>> [INFO] WSO2 Carbon - Governance - Gadgets User Interface Stub SUCCESS >>> [4.622s] >>> [INFO] WSO2 Carbon - Governance - Generic Artifact User Interface Stub >>> SUCCESS [2.137s] >>> [INFO] WSO2 Carbon - Governance - Custom Lifecycle Checklist Stub >>> SUCCESS [1.474s] >>> [INFO] WSO2 Carbon - Governance - Life Cycles User Interface Stub >>> SUCCESS [1.720s] >>> [INFO] WSO2 Carbon - Governance - List Metadata User Interface Stub >>> SUCCESS [1.973s] >>> [INFO] WSO2 Carbon - Governance - Notifications User Interface Stub >>> SUCCESS [2.365s] >>> [INFO] WS
Re: [Dev] [GReg] Build failure on carbon-governance wso2-dev git repo
Hi Greg team, This issue is still there, please fix this. Jenkins build will not work because of this. find the error log below. T E S T S --- Running org.wso2.carbon.governance.api.test.WSDLTest log4j:WARN No appenders could be found for logger (org.wso2.carbon.context.internal.CarbonContextDataHolder). log4j:WARN Please initialize the log4j system properly. Retrieving document at ' http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl '. Retrieving schema at '../xsd/purchasing.xsd', relative to ' http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl '. Retrieving document at ' http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl '. Retrieving schema at '../xsd/purchasing.xsd', relative to ' http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl '. Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.203 sec <<< FAILURE! Running org.wso2.carbon.governance.api.test.SchemaTest log4j:WARN No appenders could be found for logger (org.wso2.carbon.context.internal.CarbonContextDataHolder). log4j:WARN Please initialize the log4j system properly. Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.762 sec Running org.wso2.carbon.governance.api.test.PolicyTest log4j:WARN No appenders could be found for logger (org.wso2.carbon.context.internal.CarbonContextDataHolder). log4j:WARN Please initialize the log4j system properly. Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.196 sec Results : Tests in error: testAddWSDL(org.wso2.carbon.governance.api.test.WSDLTest): Error in adding the wsdl. wsdl id: bcb699c4-3134-4442-92f3-e28900805942. Tests run: 7, Failures: 0, Errors: 1, Skipped: 0 On Tue, Aug 5, 2014 at 3:24 PM, Gayashan Amarasinghe wrote: > Hi GReg team, > > I am getting the following test failures when building carbon-governance > git repo. (mvn 3.0.5, java 1.6) Can we get this fixed? > > Results : > > Tests in error: > testAddWSDL(org.wso2.carbon.governance.api.test.WSDLTest): Error in > adding the wsdl. wsdl id: 758ae3e7-7c2e-4dab-8f55-70406525e207. > > Tests run: 7, Failures: 0, Errors: 1, Skipped: 0 > > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] WSO2 Carbon - Platform Aggregator Pom . SUCCESS [0.103s] > [INFO] WSO2 Carbon - Service Stubs - Aggregator Module ... SUCCESS [0.008s] > [INFO] WSO2 Carbon - Governance - Notifications Work list Human Task Stub > SUCCESS [3.893s] > [INFO] WSO2 Carbon - Governance - Gadgets User Interface Stub SUCCESS > [4.622s] > [INFO] WSO2 Carbon - Governance - Generic Artifact User Interface Stub > SUCCESS [2.137s] > [INFO] WSO2 Carbon - Governance - Custom Lifecycle Checklist Stub SUCCESS > [1.474s] > [INFO] WSO2 Carbon - Governance - Life Cycles User Interface Stub SUCCESS > [1.720s] > [INFO] WSO2 Carbon - Governance - List Metadata User Interface Stub > SUCCESS [1.973s] > [INFO] WSO2 Carbon - Governance - Notifications User Interface Stub > SUCCESS [2.365s] > [INFO] WSO2 Carbon - Governance - People User Interface Stub SUCCESS > [1.664s] > [INFO] WSO2 Carbon - Governance - Processes User Interface Stub SUCCESS > [1.649s] > [INFO] WSO2 Carbon - Governance - Services User Interface Stub SUCCESS > [1.499s] > [INFO] WSO2 Carbon - Governance - SLA User Interface Stub SUCCESS [1.542s] > [INFO] WSO2 Carbon - Governance - WSDL Tool Stub . SUCCESS [1.176s] > [INFO] WSO2 Carbon - Governance Aggregator Module SUCCESS [0.012s] > [INFO] WSO2 Carbon - Governance .. FAILURE [9.120s] > [INFO] WSO2 Carbon - Governance - S-Ramp Implementation .. SKIPPED > > > Any help is much appreciated. > > Thanks. > > -- > *Gayashan Amarasinghe* > Software Engineer | Platform TG > WSO2, Inc. | http://wso2.com > lean. enterprise. middleware > > Mobile : +94718314517 > Blog : gayashan-a.blogspot.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Commits to kernel patch0009
Hi Azeez, On Wed, Aug 6, 2014 at 5:11 PM, Afkham Azeez wrote: > Yes, ideally we should have exported only javax.cache.*. However, I think > one of Asela's patch has a coupling to CacheImpl since caching API does not > provide a way to set the cache capacity. However, there are no API changes > in CacheImpl. > There are API changes in CacheImpl class ( it has two public method to get size and cache capacity). and both are used in classes in eviction package. In that case what should we do? Thanks, Shameera. The only API changes are in the org.wso2.carbon.caching.impl.eviction > package. That package is totally internal to the caching impl. We can make > that private. > > > On Wed, Aug 6, 2014 at 4:50 PM, Shameera Rathnayaka > wrote: > >> Hi Azeez, >> >> Saw that "org.wso2.carbon.caching.impl.*, " is there under export >> packages, should this expose the latest API addition to the outside at >> runtime?. My understand is this can be an issue in future. WDYT? if this >> is the only way to patch this, isn't it better we make all new API private >> to this bundle, i mean configure it as private package? >> >> Thanks, >> Shameera. >> >> >> >> >> On Wed, Aug 6, 2014 at 2:32 PM, Afkham Azeez wrote: >> >>> There are API changes within java.cache, but all of those changes affect >>> only that bundle, and are internal to that bundle, and don't affect the >>> bundles outside it. Hence, there is no issue in committing the caching fix. >>> >>> >>> On Wed, Aug 6, 2014 at 2:28 PM, Asela Pathberiya wrote: >>> >>>> Hi Shameera, >>>> >>>> There is no any API in user core patch... We have only added a >>>> private method. As i got to know, It is not allowed to add even >>>> private method. Therefore i modified the code and attached the patch >>>> in to the jira. >>>> >>>> AFAIK, there is no any caching API changes in caching.core as well... >>>> >>>> Therefore i hope it is fine to apply the patches... >>>> >>>> Adding Azeez... >>>> >>>> Thanks, >>>> Asela. >>>> >>>> On Wed, Aug 6, 2014 at 2:13 PM, Shameera Rathnayaka >>>> wrote: >>>> > Hi Asela, >>>> > >>>> > As we discussed, it is not allowed to do any API changes to 4.2.0 >>>> patches. >>>> > So please reattached the patch removing all API changes. And the >>>> already >>>> > attached patch can be applied to 4.3.0 git repo. So please send those >>>> as >>>> > pull request. >>>> > >>>> > Thanks, >>>> > Shameera. >>>> > >>>> > >>>> > On Wed, Aug 6, 2014 at 1:02 PM, Asela Pathberiya >>>> wrote: >>>> >> >>>> >> Hi All, >>>> >> >>>> >> Please commit following >>>> >> >>>> >> https://wso2.org/jira/browse/CARBON-14891 >>>> >> https://wso2.org/jira/browse/CARBON-14905 >>>> >> >>>> >> Thanks, >>>> >> Asela. >>>> >> >>>> >> -- >>>> >> Thanks & Regards, >>>> >> Asela >>>> >> >>>> >> ATL >>>> >> Mobile : +94 777 625 933 >>>> > >>>> > >>>> > >>>> > >>>> > -- >>>> > Software Engineer - WSO2 Inc. >>>> > email: shameera AT wso2.com , shameera AT apache.org >>>> > phone: +9471 922 1454 >>>> > >>>> > Linked in : http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>>> > Twitter : https://twitter.com/Shameera_R >>>> >>>> >>>> >>>> -- >>>> Thanks & Regards, >>>> Asela >>>> >>>> ATL >>>> Mobile : +94 777 625 933 >>>> >>> >>> >>> >>> -- >>> *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* >>> * 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* >>> >> >> >> >> -- >> *Software Engineer - WSO2 Inc.* >> *email: shameera AT wso2.com , shameera AT apache.org >> * >> *phone: +9471 922 1454 <%2B9471%20922%201454>* >> >> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >> *Twitter : *https://twitter.com/Shameera_R >> > > > > -- > *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* > * 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* > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Carbon Kernel 4.3.0 - M1 Release
Hi All, Due to other urgent priorities, we are delaying 4.3.0 M1 release. Will update the release date. Thanks, Shameera. On Fri, Aug 1, 2014 at 6:54 PM, Shameera Rathnayaka wrote: > Hi All, > > Among the above 4 features , both Pluggable log provider for log viewer > and SVN 1.7/1.8 support are platform level changes. We don't have any code > changes in Carbon kernel level. All changes go to platform logging > component ( Carbon-utils) and Deployment Sychronizer component( > Carbon-commons). > > We are trying to resolve all JIRAs which have fixes for kernel > 4.2.0-patch0009, in 4.3.0-M1 release. Please send the pull request to the > 4.3.0 repo if you haven't done it yet. > > Thanks, > Shameera. > > > > > > On Wed, Jul 30, 2014 at 9:11 AM, Sameera Jayasoma > wrote: > >> Hi Folks, >> >> We are planning to release Carbon Kernel 4.3.0 M1 in the first week of >> August (7th). This will include following features as well as many bug >> fixes. >> >>- Improved Carbon QOS functionality >>- Pluggable log providers for log viewer >>- Support SVN 1.7 and 1.8 for Deployment Synchronization module. >>- Cross-cluster cache invalidation mechanism. >> >> >> Shameera will be the release manager for Carbon 4.3.0. >> >> >> -- >> Sameera Jayasoma, >> Software 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 >> >> > > > -- > *Software Engineer - WSO2 Inc.* > *email: shameera AT wso2.com , shameera AT apache.org > * > *phone: +9471 922 1454 <%2B9471%20922%201454>* > > *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 > *Twitter : *https://twitter.com/Shameera_R > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Commits to kernel patch0009
Hi Azeez, Saw that "org.wso2.carbon.caching.impl.*, " is there under export packages, should this expose the latest API addition to the outside at runtime?. My understand is this can be an issue in future. WDYT? if this is the only way to patch this, isn't it better we make all new API private to this bundle, i mean configure it as private package? Thanks, Shameera. On Wed, Aug 6, 2014 at 2:32 PM, Afkham Azeez wrote: > There are API changes within java.cache, but all of those changes affect > only that bundle, and are internal to that bundle, and don't affect the > bundles outside it. Hence, there is no issue in committing the caching fix. > > > On Wed, Aug 6, 2014 at 2:28 PM, Asela Pathberiya wrote: > >> Hi Shameera, >> >> There is no any API in user core patch... We have only added a >> private method. As i got to know, It is not allowed to add even >> private method. Therefore i modified the code and attached the patch >> in to the jira. >> >> AFAIK, there is no any caching API changes in caching.core as well... >> >> Therefore i hope it is fine to apply the patches... >> >> Adding Azeez... >> >> Thanks, >> Asela. >> >> On Wed, Aug 6, 2014 at 2:13 PM, Shameera Rathnayaka >> wrote: >> > Hi Asela, >> > >> > As we discussed, it is not allowed to do any API changes to 4.2.0 >> patches. >> > So please reattached the patch removing all API changes. And the already >> > attached patch can be applied to 4.3.0 git repo. So please send those as >> > pull request. >> > >> > Thanks, >> > Shameera. >> > >> > >> > On Wed, Aug 6, 2014 at 1:02 PM, Asela Pathberiya >> wrote: >> >> >> >> Hi All, >> >> >> >> Please commit following >> >> >> >> https://wso2.org/jira/browse/CARBON-14891 >> >> https://wso2.org/jira/browse/CARBON-14905 >> >> >> >> Thanks, >> >> Asela. >> >> >> >> -- >> >> Thanks & Regards, >> >> Asela >> >> >> >> ATL >> >> Mobile : +94 777 625 933 >> > >> > >> > >> > >> > -- >> > Software Engineer - WSO2 Inc. >> > email: shameera AT wso2.com , shameera AT apache.org >> > phone: +9471 922 1454 >> > >> > Linked in : http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >> > Twitter : https://twitter.com/Shameera_R >> >> >> >> -- >> Thanks & Regards, >> Asela >> >> ATL >> Mobile : +94 777 625 933 >> > > > > -- > *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* > * 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* > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Commits to kernel patch0009
Hi Asela, As we discussed, it is not allowed to do any API changes to 4.2.0 patches. So please reattached the patch removing all API changes. And the already attached patch can be applied to 4.3.0 git repo. So please send those as pull request. Thanks, Shameera. On Wed, Aug 6, 2014 at 1:02 PM, Asela Pathberiya wrote: > Hi All, > > Please commit following > > https://wso2.org/jira/browse/CARBON-14891 > https://wso2.org/jira/browse/CARBON-14905 > > Thanks, > Asela. > > -- > Thanks & Regards, > Asela > > ATL > Mobile : +94 777 625 933 > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Kavith Lokuhewage
Congratulation !!! ~Shameera On Mon, Aug 4, 2014 at 1:20 PM, Anuruddha Premalal wrote: > Congratulations !! > > > On Mon, Aug 4, 2014 at 12:07 PM, Asanka Dissanayake > wrote: > >> Congratzz Kavith!! >> >> >> On Mon, Aug 4, 2014 at 11:53 AM, Harsha Kumara wrote: >> >>> Congratulations Kavith! >>> >>> >>> On Mon, Aug 4, 2014 at 11:50 AM, Jayanga Dissanayake >>> wrote: >>> >>>> Congratulations Kavith >>>> >>>> *Jayanga Dissanayake* >>>> Senior Software Engineer >>>> WSO2 Inc. - http://wso2.com/ >>>> >>>> lean . enterprise . middleware >>>> email: jaya...@wso2.com >>>> mobile: +94772207259 >>>> >>>> >>>> On Mon, Aug 4, 2014 at 11:49 AM, Dakshika Jayathilaka < >>>> daksh...@wso2.com> wrote: >>>> >>>>> Congratulations..! >>>>> >>>>> *Dakshika Jayathilaka* >>>>> Software Engineer >>>>> WSO2, Inc. >>>>> lean.enterprise.middleware >>>>> 0771100911 >>>>> >>>>> >>>>> On Mon, Aug 4, 2014 at 6:18 AM, Waruna Jayaweera >>>>> wrote: >>>>> >>>>>> Congratulations..! >>>>>> >>>>>> >>>>>> On Mon, Aug 4, 2014 at 11:43 AM, Shani Ranasinghe >>>>>> wrote: >>>>>> >>>>>>> Congratulations Kavith. >>>>>>> >>>>>>> >>>>>>> On Mon, Aug 4, 2014 at 11:41 AM, Jasintha Dasanayake < >>>>>>> jasin...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> It's my distinct pleasure to welcome kavith Lokuhewage as a WSO2 >>>>>>>> Committer. >>>>>>>> >>>>>>>> Kavith has been a valuable contributor for WSO2 Developer Studio >>>>>>>> since he joined WSO2. In recognition of his contributions to WSO2, he >>>>>>>> has >>>>>>>> been voted as a WSO2 Committer. >>>>>>>> >>>>>>>> Kavith, Congratulations and Keep up the good work! >>>>>>>> >>>>>>>> Thanks and Regards, >>>>>>>> /Jasintha >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *Jasintha Dasanayake * >>>>>>>> >>>>>>>> *Senior Software EngineerWSO2 Inc. | http://wso2.com >>>>>>>> <http://wso2.com/> lean . enterprise . middleware* >>>>>>>> >>>>>>>> >>>>>>>> *mobile :- 0711368118 <0711368118> * >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks and Regards >>>>>>> *,Shani Ranasinghe* >>>>>>> >>>>>>> Software Engineer >>>>>>> WSO2 Inc.; http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> mobile: +94 77 2273555 >>>>>>> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> >>>>>> Waruna Lakshitha Jayaweera >>>>>> Software Engineer >>>>>> WSO2 Inc; http://wso2.com >>>>>> phone: +94713255198 >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Harsha Kumara >>> Software Engineer, WSO2 Inc. >>> Mobile: +94775505618 >>> Blog:harshcreationz.blogspot.com >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> >> *Asanka DissanayakeSoftware Engineer* >> *WSO2 Inc. - lean . enterprise . middleware | wso2.com >> <http://wso2.com/>* >> >> *email: asan...@wso2.com , blog: >> cyberwaadiya.blogspot.com >> <http://cyberwaadiya.blogspot.com>, asankastechtalks.wordpress.com >> <http://asankastechtalks.wordpress.com> mobile: +94 71 8373821* >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Anuruddha Premalal* > Software Eng. | WSO2 Inc. > Mobile : +94710461070 > Web site : www.regilandvalley.com > > "Advances of technology should not leave behind the developing world" > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Carbon Kernel 4.3.0 - M1 Release
Hi All, Among the above 4 features , both Pluggable log provider for log viewer and SVN 1.7/1.8 support are platform level changes. We don't have any code changes in Carbon kernel level. All changes go to platform logging component ( Carbon-utils) and Deployment Sychronizer component( Carbon-commons). We are trying to resolve all JIRAs which have fixes for kernel 4.2.0-patch0009, in 4.3.0-M1 release. Please send the pull request to the 4.3.0 repo if you haven't done it yet. Thanks, Shameera. On Wed, Jul 30, 2014 at 9:11 AM, Sameera Jayasoma wrote: > Hi Folks, > > We are planning to release Carbon Kernel 4.3.0 M1 in the first week of > August (7th). This will include following features as well as many bug > fixes. > >- Improved Carbon QOS functionality >- Pluggable log providers for log viewer >- Support SVN 1.7 and 1.8 for Deployment Synchronization module. >- Cross-cluster cache invalidation mechanism. > > > Shameera will be the release manager for Carbon 4.3.0. > > > -- > Sameera Jayasoma, > Software 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Thanuja Jayasinghe
Congratzz Thanuja. ~Shameera On Wed, Jul 23, 2014 at 4:40 PM, Pulasthi Supun wrote: > Congrats Thanuja !! > > > On Wed, Jul 23, 2014 at 4:38 PM, Bhathiya Jayasekara > wrote: > >> Congratulations >> >> >> On Wed, Jul 23, 2014 at 4:34 PM, Pulasthi Mahawithana > > wrote: >> >>> Congrats Thanuja.. >>> >>> >>> On Wed, Jul 23, 2014 at 4:27 PM, Johann Nallathamby >>> wrote: >>> >>>> Hi All, >>>> >>>> It's my pleasure to announce Thanuja Jayasinghe as a WSO2 Committer. >>>> Thanuja has been a valuable contributor for WSO2 Identity Server >>>> product, and in recognition of his contributions to WSO2, he has been voted >>>> as a WSO2 Committer. >>>> >>>> Thanuja, Congratulations and Keep up the good work! >>>> >>>> Thanks & Regards, >>>> Johann. >>>> >>>> -- >>>> Thanks & Regards, >>>> >>>> *Johann Dilantha Nallathamby* >>>> Associate Technical Lead & Product Lead of WSO2 Identity Server >>>> Integration Technologies Team >>>> WSO2, Inc. >>>> lean.enterprise.middleware >>>> >>>> Mobile - *+9476950* >>>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>* >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Pulasthi Mahawithana* >>> Software Engineer >>> WSO2 Inc., http://wso2.com/ >>> Mobile: +94-71-5179022 >>> Blog: http://blog.pulasthi.org >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Bhathiya Jayasekara* >> *Software Engineer,* >> *WSO2 inc., http://wso2.com <http://wso2.com>* >> >> *Phone: +94715478185 <%2B94715478185>* >> *LinkedIn: http://www.linkedin.com/in/bhathiyaj >> <http://www.linkedin.com/in/bhathiyaj>* >> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>* >> *Blog: http://movingaheadblog.blogspot.com >> <http://movingaheadblog.blogspot.com/>* >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > -- > Pulasthi Supun > Software Engineer; WSO2 Inc.; http://wso2.com, > Email: pulas...@wso2.com > Mobile: +94 (71) 9258281 > Blog : http://pulasthisupun.blogspot.com/ > Git hub profile: https://github.com/pulasthi > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Isura Karunaratne
Congratzz Isura. ~Shameera. On Wed, Jul 23, 2014 at 4:39 PM, Hasintha Indrajee wrote: > Congrats Isura. > > > On Wed, Jul 23, 2014 at 4:37 PM, Pulasthi Mahawithana > wrote: > >> Congrats Isura ... >> >> >> On Wed, Jul 23, 2014 at 4:35 PM, Suresh Attanayaka >> wrote: >> >>> Congrats Isura. >>> >>> >>> On Wed, Jul 23, 2014 at 4:30 PM, Johann Nallathamby >>> wrote: >>> >>>> Hi All, >>>> >>>> It's my pleasure to announce Isura Karunaratne as a WSO2 Committer. >>>> Isura has been a valuable contributor for WSO2 Identity Server >>>> product, and in recognition of his contributions to WSO2, he has been voted >>>> as a WSO2 Committer. >>>> >>>> Isura, Congratulations and Keep up the good work! >>>> >>>> Thanks & Regards, >>>> Johann. >>>> >>>> -- >>>> Thanks & Regards, >>>> >>>> *Johann Dilantha Nallathamby* >>>> Associate Technical Lead & Product Lead of WSO2 Identity Server >>>> Integration Technologies Team >>>> WSO2, Inc. >>>> lean.enterprise.middleware >>>> >>>> Mobile - *+9476950* >>>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>* >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Suresh Attanayake >>> Senior Software Engineer; WSO2 Inc. http://wso2.com/ >>> Blog : http://sureshatt.blogspot.com/ >>> Twitter : https://twitter.com/sureshatt >>> LinkedIn : http://lk.linkedin.com/in/sureshatt >>> Mobile : +94755012060 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Pulasthi Mahawithana* >> Software Engineer >> WSO2 Inc., http://wso2.com/ >> Mobile: +94-71-5179022 >> Blog: http://blog.pulasthi.org >> >> ___ >> 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Prasad Tissera
Congratzz Prasad, ~Shameera. On Wed, Jul 23, 2014 at 4:39 PM, Bhathiya Jayasekara wrote: > Congratulations > > > On Wed, Jul 23, 2014 at 4:28 PM, Johann Nallathamby > wrote: > >> Hi All, >> >> It's my pleasure to announce Prasad Tissera as a WSO2 Committer. Prasad has >> been a valuable contributor for WSO2 Identity Server product, and in >> recognition of his contributions to WSO2, he has been voted as a WSO2 >> Committer. >> >> Prasad, Congratulations and Keep up the good work! >> >> Thanks & Regards, >> Johann. >> >> -- >> Thanks & Regards, >> >> *Johann Dilantha Nallathamby* >> Associate Technical Lead & Product Lead of WSO2 Identity Server >> Integration Technologies Team >> WSO2, Inc. >> lean.enterprise.middleware >> >> Mobile - *+9476950* >> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>* >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Bhathiya Jayasekara* > *Software Engineer,* > *WSO2 inc., http://wso2.com <http://wso2.com>* > > *Phone: +94715478185 <%2B94715478185>* > *LinkedIn: http://www.linkedin.com/in/bhathiyaj > <http://www.linkedin.com/in/bhathiyaj>* > *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>* > *Blog: http://movingaheadblog.blogspot.com > <http://movingaheadblog.blogspot.com/>* > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] MediationTracerService is tightly coupled with MemoryAppender
We should not use appenders to read the logs back, there are set of log providers/readers available in platform for a eg : TenantAwareLogProvider/TenantAwareLogReader can be used to get logs from MemoryAppender. This log provider mechanism has been improved in 4.3.0 trunk to support pluggable log providers. Another thing is , if we disable MemoryAppender in production systems( due to memory issues) then the above components will not function. Relevant product teams, please change this and use Log providers to read logs which is the most clean way to get logs. Thanks, Shameera. On Tue, Jul 22, 2014 at 7:11 PM, Gayashan Amarasinghe wrote: > Hi, > > I observed that the same implementation is followed in > EventTracerAdminService [1] and JiraAppender [2] as well. > > [1] > https://github.com/wso2-dev/carbon-event-processing/blob/master/components/event-monitor/event-tracer/org.wso2.carbon.event.tracer/src/main/java/org/wso2/carbon/event/tracer/EventTracerAdminService.java > > [2] > https://github.com/wso2-dev/platform/blob/master/components/health-monitor/org.wso2.carbon.health/src/main/java/org/wso2/carbon/health/service/JiraAppender.java > > /Gayashan > > > On Thu, Jul 17, 2014 at 4:20 PM, Gayashan Amarasinghe > wrote: > >> Hi all, >> >> MediationTracerService [1] within the carbon-mediation repo is tightly >> coupled with the MemoryAppender which is available in the carbon-kernel. >> MediationTracerService is only reading the log. We believe this is not the >> best way to achieve this. We can use a Logging Provider [2] available >> within the carbon-utils to achieve this task. >> >> WDYT? >> >> >> [1] >> https://github.com/wso2-dev/carbon-mediation/blob/master/components/mediation-monitor/mediation-tracer/org.wso2.carbon.mediation.tracer/src/main/java/org/wso2/carbon/mediation/tracer/MediationTracerService.java >> >> >> [2] >> https://github.com/wso2-dev/carbon-utils/tree/master/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/util >> >> Thanks. >> >> /Gayashan >> >> -- >> *Gayashan Amarasinghe* >> Software Engineer | Platform TG >> WSO2, Inc. | http://wso2.com >> lean. enterprise. middleware >> >> Mobile : +94718314517 >> Blog : gayashan-a.blogspot.com >> > > > > -- > *Gayashan Amarasinghe* > Software Engineer | Platform TG > WSO2, Inc. | http://wso2.com > lean. enterprise. middleware > > Mobile : +94718314517 > Blog : gayashan-a.blogspot.com > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Application deployer gives issue in chunk13
e.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620) >> >> at >> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197) >> >> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343) >> >> at >> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222) >> >> at >> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107) >> >> at >> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861) >> >> at >> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) >> >> at >> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) >> >> at >> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819) >> >> at >> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771) >> >> at >> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130) >> >> at >> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214) >> >> at >> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433) >> >> at >> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81) >> >> at >> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60) >> >> at >> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40) >> >> at >> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38) >> >> at >> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267) >> >> at >> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186) >> >> at >> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081) >> >> at >> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027) >> >> at org.apache.catal >> >> -- >> -Ratha >> mobile: (+94)755906608 >> > > > > -- > -Ratha > mobile: (+94)755906608 > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] wso2server.sh script does not stop the server when ssh terminates
According to the JIRA, you should use -c not -E , did you test with that option as well? , BTW wso2servers.sh is working fine with nohup not sure about stratos.sh . you can update JIRA with your finding. @Isura , For that you need to start the server as background process , if not server process terminate with user logging out. Thanks, Shameera. On Sat, Jul 19, 2014 at 11:33 AM, Isura Karunaratne wrote: > Hi Nipuni, > > AFAIK sever process will not terminate once you terminate the ssh > process . You have to kill the server process manually. User "ps -ef|grep > carbon" to identity the process id and kill it using "kill -9 id" command. > > Thanks > Isura > > > On Sat, Jul 19, 2014 at 10:10 AM, Nipuni Perera wrote: > >> Hi, >> >> I am working on jira issue[1]. I have tested this with a remote BAM >> server and couldn't reproduce the issue. If wso2server.sh has been executed >> over ssh as a nohup process, server does not stop after ssh process >> terminates. >> >> I have followed the steps below: >> >>1. start ssh and connect to remote serrver : ssh -i >> -p >>2. start wso2server as a background process : sudo -E >>./wso2server.sh start (this gives an error "ps: write error: Bad file >>descriptor" but server starts successfully >>3. exit from the remote server and stop ssh >>4. I can access server after ssh is stopped. >> >> I have tested it starting wso2server as a nohup process : nohup sudo -E >> ./wso2server.sh (This also works after ssh terminates) >> >> [1] https://wso2.org/jira/browse/CARBON-14813 >> Thanks, >> Nipuni >> -- >> Nipuni Perera >> Software Engineer; WSO2 Inc.; http://wso2.com >> Email: nip...@wso2.com >> Git hub profile: https://github.com/nipuni >> Mobile: +94 (71) 5626680 >> <http://wso2.com> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Isura Dilhara Karunaratne > Software Engineer > > Mob +94 772 254 810 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DSS][AXIS2][AXIS2-JSON] Writing a new XML to JSON conversion
Hi Rajith, Why are you asking him to build the patches , can't he work on already released DSs pack, Here i am trying to understand which issue Yasas trying to address by implementing a new JSON builder and formatter, we have plenty of Builders and formatters for JSON :) . May i know the real use case and requirement ? Thanks, Shameera On Mon, Jul 14, 2014 at 2:51 PM, Rajith Vitharana wrote: > Hi Yasas, > > Try out creating a simple jar and put it in lib folder as shameera > mentioned in above reply. I have tried out the scenario I have explained to > you, and it worked fine for me > As I mentioned, have you build the whole patch from the pom.xml inside > patch0007 folder? > and have you created "patch0008" folder and copied the > jar(axis2-json-1.6.1-wso2v10.jar) inside > "patch0007/dependencies/orbit/axis2-json/target" > folder to the "patch0008" folder? > > Thanks, > > > > On Mon, Jul 14, 2014 at 1:50 PM, Shameera Rathnayaka > wrote: > >> Hi Yasas, >> >> For you ClassNotFoundException, check do your axis2-json jar has required >> classes, BTW as i mentioned in previous reply you don't need to do any code >> changes to axis2 jars in order to plug your custom builders. >> >> Thanks, >> Shameera. >> >> >> On Mon, Jul 14, 2014 at 1:36 PM, Yasas Karunarathna >> wrote: >> >>> Thank you for the quick responses. I checked in sources from both the >>> locations >>> >>> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0007/dependencies/axis2/modules/json/ >>> >>> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/json >>> >>> Separately build without any modifications, and put generated jar to >>> patch8 folder. Once I restart the server following message shows in the >>> console. >>> >>> "Could not start: >>> null(reference:file:../plugins/axis2-json_1.6.1.wso2v10.jar:15). It's state >>> is uninstalled." >>> >>> After that logs the following error. >>> >>> "Caused by: java.lang.ClassNotFoundException: >>> org.apache.axis2.json.gson.JSONMessageHandler" >>> >>> Any work around? >>> >>> >>> >>> On Sun, Jul 13, 2014 at 11:30 PM, Shameera Rathnayaka >> > wrote: >>> >>>> Hi Yasas, >>>> >>>> Assuming you are going to customize the JSON mapped convention >>>> (Standard Mapped Json support is their with Axis2),You don't need to do >>>> anything to axis2 jar. Implement your new JSON builder and formatter, then >>>> create a new jar(or osgi bundle) using those new classes >>>> and copy that jar ( or osgi bundle) to >>>> /repository/components/lib ( or >>>> /repository/components/dropings) directory. Finally, you need to >>>> configure your builder and formatter in axis2.xm configuration file (like >>>> your 3rd step). >>>> >>>> Thanks, >>>> Shameera. >>>> >>>> >>>> >>>> >>>> On Sun, Jul 13, 2014 at 10:35 PM, Rajith Vitharana >>>> wrote: >>>> >>>>> Hi Yasas, >>>>> >>>>> The points you have mentioned are correct, but there are small changes >>>>> I would like to point out. Below are the steps you'll need to follow to >>>>> achieve your goal. >>>>> >>>>> 1 - There is a patch release for the "axis2-json" so you'll need to >>>>> check out the source from [1] instead of the svn location you have >>>>> mentioned. (checkout the whole "patch0007" instead of json module, so that >>>>> it'll be easy for you to build the source.) >>>>> 2 - Add the classes you need to the source. >>>>> You'll need to extend AbstractJSONMessageFormatter in your >>>>> custom formatter class >>>>> You'll need to extend AbstractJSONOMBuilder in you custom >>>>> builder class >>>>> 3 - Build the whole patch0007. Then go to >>>>> "patch0007/dependencies/orbit/axis2-json/target" folder where you can find >>>>> the osgi bundle created from "axis2-json" module. >>>>> 4 - Create "patch0008" folder inside >>>>> "DSS_HOME/repository/components/patches" folder and copy the osgi bundle >&g
Re: [Dev] [DSS][AXIS2][AXIS2-JSON] Writing a new XML to JSON conversion
Hi Yasas, For you ClassNotFoundException, check do your axis2-json jar has required classes, BTW as i mentioned in previous reply you don't need to do any code changes to axis2 jars in order to plug your custom builders. Thanks, Shameera. On Mon, Jul 14, 2014 at 1:36 PM, Yasas Karunarathna wrote: > Thank you for the quick responses. I checked in sources from both the > locations > > https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0007/dependencies/axis2/modules/json/ > > https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/json > > Separately build without any modifications, and put generated jar to > patch8 folder. Once I restart the server following message shows in the > console. > > "Could not start: > null(reference:file:../plugins/axis2-json_1.6.1.wso2v10.jar:15). It's state > is uninstalled." > > After that logs the following error. > > "Caused by: java.lang.ClassNotFoundException: > org.apache.axis2.json.gson.JSONMessageHandler" > > Any work around? > > > > On Sun, Jul 13, 2014 at 11:30 PM, Shameera Rathnayaka > wrote: > >> Hi Yasas, >> >> Assuming you are going to customize the JSON mapped convention (Standard >> Mapped Json support is their with Axis2),You don't need to do anything to >> axis2 jar. Implement your new JSON builder and formatter, then create a >> new jar(or osgi bundle) using those new classes >> and copy that jar ( or osgi bundle) to >> /repository/components/lib ( or >> /repository/components/dropings) directory. Finally, you need to >> configure your builder and formatter in axis2.xm configuration file (like >> your 3rd step). >> >> Thanks, >> Shameera. >> >> >> >> >> On Sun, Jul 13, 2014 at 10:35 PM, Rajith Vitharana >> wrote: >> >>> Hi Yasas, >>> >>> The points you have mentioned are correct, but there are small changes I >>> would like to point out. Below are the steps you'll need to follow to >>> achieve your goal. >>> >>> 1 - There is a patch release for the "axis2-json" so you'll need to >>> check out the source from [1] instead of the svn location you have >>> mentioned. (checkout the whole "patch0007" instead of json module, so that >>> it'll be easy for you to build the source.) >>> 2 - Add the classes you need to the source. >>> You'll need to extend AbstractJSONMessageFormatter in your >>> custom formatter class >>> You'll need to extend AbstractJSONOMBuilder in you custom >>> builder class >>> 3 - Build the whole patch0007. Then go to >>> "patch0007/dependencies/orbit/axis2-json/target" folder where you can find >>> the osgi bundle created from "axis2-json" module. >>> 4 - Create "patch0008" folder inside >>> "DSS_HOME/repository/components/patches" folder and copy the osgi bundle >>> you found in step 3 to that folder. >>> 5 - Add "messageFormatter" and "messageBuilder" elements to the >>> "DSS_HOME/repository/conf/axis2/axis2.xml" as you have pointed out in your >>> step 3. >>> 6 - Restart the server and invoke your service adding "Accept" request >>> header to the request with new content type you mentioned in "axis2.xml", >>> example would be "Accept:application/json/newformat".(You can find >>> sample of how to do it in [2]) >>> >>> [1] - >>> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0007/dependencies/axis2/modules/json/ >>> [2] - >>> http://janakaranabahu.blogspot.com/2013/06/return-json-response-from-wso2-dss.html >>> >>> Thanks, >>> >>> >>> On Sun, Jul 13, 2014 at 1:45 PM, Yasas Karunarathna >> > wrote: >>> >>>> Hi there, >>>> >>>> I want to do a small change to the json response returned from DSS >>>> 3.2.1. I'm using JSONMessageFormatter & JSONOMBuilder in >>>> org.apache.axis2.json package.(not gson implementations) >>>> My requirements are as follows >>>> >>>> 1) Implement new JSONMessageFormatter, JSONOMBuilder etc. >>>> And additional method accepting the Mapped json response and format >>>> it accordingly, call it at the end of mapped json conversion. >>>> 2) Build axis2-json-1.6.1-wso2v10.jar adding new classes. >&g
Re: [Dev] [DSS][AXIS2][AXIS2-JSON] Writing a new XML to JSON conversion
Hi Yasas, Assuming you are going to customize the JSON mapped convention (Standard Mapped Json support is their with Axis2),You don't need to do anything to axis2 jar. Implement your new JSON builder and formatter, then create a new jar(or osgi bundle) using those new classes and copy that jar ( or osgi bundle) to /repository/components/lib ( or /repository/components/dropings) directory. Finally, you need to configure your builder and formatter in axis2.xm configuration file (like your 3rd step). Thanks, Shameera. On Sun, Jul 13, 2014 at 10:35 PM, Rajith Vitharana wrote: > Hi Yasas, > > The points you have mentioned are correct, but there are small changes I > would like to point out. Below are the steps you'll need to follow to > achieve your goal. > > 1 - There is a patch release for the "axis2-json" so you'll need to check > out the source from [1] instead of the svn location you have mentioned. > (checkout the whole "patch0007" instead of json module, so that it'll be > easy for you to build the source.) > 2 - Add the classes you need to the source. > You'll need to extend AbstractJSONMessageFormatter in your > custom formatter class > You'll need to extend AbstractJSONOMBuilder in you custom > builder class > 3 - Build the whole patch0007. Then go to > "patch0007/dependencies/orbit/axis2-json/target" folder where you can find > the osgi bundle created from "axis2-json" module. > 4 - Create "patch0008" folder inside > "DSS_HOME/repository/components/patches" folder and copy the osgi bundle > you found in step 3 to that folder. > 5 - Add "messageFormatter" and "messageBuilder" elements to the > "DSS_HOME/repository/conf/axis2/axis2.xml" as you have pointed out in your > step 3. > 6 - Restart the server and invoke your service adding "Accept" request > header to the request with new content type you mentioned in "axis2.xml", > example would be "Accept:application/json/newformat".(You can find sample > of how to do it in [2]) > > [1] - > https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0007/dependencies/axis2/modules/json/ > [2] - > http://janakaranabahu.blogspot.com/2013/06/return-json-response-from-wso2-dss.html > > Thanks, > > > On Sun, Jul 13, 2014 at 1:45 PM, Yasas Karunarathna > wrote: > >> Hi there, >> >> I want to do a small change to the json response returned from DSS 3.2.1. >> I'm using JSONMessageFormatter & JSONOMBuilder in org.apache.axis2.json >> package.(not gson implementations) >> My requirements are as follows >> >> 1) Implement new JSONMessageFormatter, JSONOMBuilder etc. >> And additional method accepting the Mapped json response and format it >> accordingly, call it at the end of mapped json conversion. >> 2) Build axis2-json-1.6.1-wso2v10.jar adding new classes. >> I think this is the source used in DSS 3.2.1 : >> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/json >> >> 3) State new Formatter and Builder in axis2.xml & call it with new header >> > >> class="org.apache.axis2.json.newJSONMessageFormatter"/> >> >> > class="org.apache.axis2.json.newJSONOMBuilder"/> >> Can anybody advice me on achieving the above requirements? >> >> -- >> >> Thanks >> >> >> >> *Yasas Karunarathna* >> yasasblog.wordpress.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454 <%2B9471%20922%201454>* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Commit the patch to kernel patch0009 | CARBON-14862 fix
Done, Committed revision 205558. Yes please send the pull request to 4.3.0 dev git repo. Thanks, Shameera. On Thu, Jul 10, 2014 at 8:00 PM, Supun Malinga wrote: > I will send the pull request to 4.3.0 git as well. > > thanks, > > > On Thu, Jul 10, 2014 at 7:59 PM, Supun Malinga wrote: > >> Hi Shameera, >> >> As discussed offline, please do the $subject and let me know.. >> https://wso2.org/jira/browse/CARBON-14862 >> >> thanks, >> -- >> Supun Malinga, >> >> Senior Software Engineer, >> WSO2 Inc. >> http://wso2.com >> email: sup...@wso2.com >> mobile: +94 (0)71 56 91 321 >> > > > > -- > Supun Malinga, > > Senior Software Engineer, > WSO2 Inc. > http://wso2.com > email: sup...@wso2.com > mobile: +94 (0)71 56 91 321 > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please merge the changes to patch0009 of 4.2.0 kernel
yes you have, but for master repository[1] which we don't apply patches. We will merge dev repo[2] to master once dev branch come to a stable state. Therefore you need to provide pull request to wso2-dev repo :) [1] https://github.com/wso2/carbon4-kernel [2] https://github.com/wso2-dev/carbon4-kernel On Thu, Jul 10, 2014 at 7:33 PM, Pradeep Fernando wrote: > I did sent a pull request. What is the commit version of the patch > > > On Thu, Jul 10, 2014 at 7:17 PM, Shameera Rathnayaka > wrote: > >> Hi Pradeep, >> >> Please send the pull request to >> https://github.com/wso2-dev/carbon4-kernel , this is the carbon 4 kernel >> development branch. >> >> Regards, >> Shameera. >> >> >> On Thu, Jul 10, 2014 at 5:24 PM, Shameera Rathnayaka >> wrote: >> >>> Hi Pradeep, >>> >>> Which jdk version you are using to buile the kernel? if it is 1.7 then >>> you probably hit with registry test failures. >>> >>> I will apply the new patch. >>> >>> Thanks, >>> Shameera >>> >>> >>> On Thu, Jul 10, 2014 at 5:22 PM, Pradeep Fernando >>> wrote: >>> >>>> Hi Shameera, >>>> >>>> Attached the new patch with modifications. Ran tests. No new test >>>> failures, AFAIU. >>>> >>>> thanks,. >>>> >>>> >>>> On Thu, Jul 10, 2014 at 5:12 PM, Pradeep Fernando >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> will attach the patch again. However, encountered some registry test >>>>> failures in patch0009/registry.core without my patch. >>>>> >>>>> thanks >>>>> >>>>> >>>>> On Thu, Jul 10, 2014 at 4:46 PM, Shameera Rathnayaka < >>>>> shame...@wso2.com> wrote: >>>>> >>>>>> Hi Pradeep, >>>>>> >>>>>> you have introduced a new API in your patch , please remove that as >>>>>> it is incorrect to do API changes with a patch. But when you provide a >>>>>> pull >>>>>> request to 4.3.0 you can do any API changes. >>>>>> >>>>>> Thanks, >>>>>> Shameera. >>>>>> >>>>>> >>>>>> On Thu, Jul 10, 2014 at 3:47 PM, Pradeep Fernando >>>>>> wrote: >>>>>> >>>>>>> Hi Kernel team, >>>>>>> >>>>>>> Please review and merge the changes please. >>>>>>> >>>>>>> https://wso2.org/jira/browse/CARBON-14861 >>>>>>> >>>>>>> thanks >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Software Engineer - WSO2 Inc.* >>>>>> *email: shameera AT wso2.com , shameera AT >>>>>> apache.org * >>>>>> *phone: +9471 922 1454 <%2B9471%20922%201454>* >>>>>> >>>>>> *Linked in : * >>>>>> http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>>>>> *Twitter : *https://twitter.com/Shameera_R >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Pradeep Fernando* >>>>> Associate Technical Lead;WSO2 Inc.; http://wso2.com >>>>> >>>>> blog: http://pradeepfernando.blogspot.com >>>>> m: +94776603662 >>>>> >>>> >>>> >>>> >>>> -- >>>> *Pradeep Fernando* >>>> Associate Technical Lead;WSO2 Inc.; http://wso2.com >>>> >>>> blog: http://pradeepfernando.blogspot.com >>>> m: +94776603662 >>>> >>> >>> >>> >>> -- >>> *Software Engineer - WSO2 Inc.* >>> *email: shameera AT wso2.com , shameera AT >>> apache.org * >>> *phone: +9471 922 1454 <%2B9471%20922%201454>* >>> >>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>> *Twitter : *https://twitter.com/Shameera_R >>> >> >> >> >> -- >> *Software Engineer - WSO2 Inc.* >> *email: shameera AT wso2.com , shameera AT apache.org >> * >> *phone: +9471 922 1454 <%2B9471%20922%201454>* >> >> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >> *Twitter : *https://twitter.com/Shameera_R >> > > > > -- > *Pradeep Fernando* > Associate Technical Lead;WSO2 Inc.; http://wso2.com > > blog: http://pradeepfernando.blogspot.com > m: +94776603662 > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454 <%2B9471%20922%201454>* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please merge the changes to patch0009 of 4.2.0 kernel
Hi Pradeep, Please send the pull request to https://github.com/wso2-dev/carbon4-kernel , this is the carbon 4 kernel development branch. Regards, Shameera. On Thu, Jul 10, 2014 at 5:24 PM, Shameera Rathnayaka wrote: > Hi Pradeep, > > Which jdk version you are using to buile the kernel? if it is 1.7 then you > probably hit with registry test failures. > > I will apply the new patch. > > Thanks, > Shameera > > > On Thu, Jul 10, 2014 at 5:22 PM, Pradeep Fernando > wrote: > >> Hi Shameera, >> >> Attached the new patch with modifications. Ran tests. No new test >> failures, AFAIU. >> >> thanks,. >> >> >> On Thu, Jul 10, 2014 at 5:12 PM, Pradeep Fernando >> wrote: >> >>> Hi, >>> >>> will attach the patch again. However, encountered some registry test >>> failures in patch0009/registry.core without my patch. >>> >>> thanks >>> >>> >>> On Thu, Jul 10, 2014 at 4:46 PM, Shameera Rathnayaka >>> wrote: >>> >>>> Hi Pradeep, >>>> >>>> you have introduced a new API in your patch , please remove that as it >>>> is incorrect to do API changes with a patch. But when you provide a pull >>>> request to 4.3.0 you can do any API changes. >>>> >>>> Thanks, >>>> Shameera. >>>> >>>> >>>> On Thu, Jul 10, 2014 at 3:47 PM, Pradeep Fernando >>>> wrote: >>>> >>>>> Hi Kernel team, >>>>> >>>>> Please review and merge the changes please. >>>>> >>>>> https://wso2.org/jira/browse/CARBON-14861 >>>>> >>>>> thanks >>>>> >>>> >>>> >>>> >>>> -- >>>> *Software Engineer - WSO2 Inc.* >>>> *email: shameera AT wso2.com , shameera AT >>>> apache.org * >>>> *phone: +9471 922 1454 <%2B9471%20922%201454>* >>>> >>>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>>> *Twitter : *https://twitter.com/Shameera_R >>>> >>> >>> >>> >>> -- >>> *Pradeep Fernando* >>> Associate Technical Lead;WSO2 Inc.; http://wso2.com >>> >>> blog: http://pradeepfernando.blogspot.com >>> m: +94776603662 >>> >> >> >> >> -- >> *Pradeep Fernando* >> Associate Technical Lead;WSO2 Inc.; http://wso2.com >> >> blog: http://pradeepfernando.blogspot.com >> m: +94776603662 >> > > > > -- > *Software Engineer - WSO2 Inc.* > *email: shameera AT wso2.com , shameera AT apache.org > * > *phone: +9471 922 1454 <%2B9471%20922%201454>* > > *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 > *Twitter : *https://twitter.com/Shameera_R > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please merge the changes to patch0009 of 4.2.0 kernel
Hi Pradeep, Which jdk version you are using to buile the kernel? if it is 1.7 then you probably hit with registry test failures. I will apply the new patch. Thanks, Shameera On Thu, Jul 10, 2014 at 5:22 PM, Pradeep Fernando wrote: > Hi Shameera, > > Attached the new patch with modifications. Ran tests. No new test > failures, AFAIU. > > thanks,. > > > On Thu, Jul 10, 2014 at 5:12 PM, Pradeep Fernando > wrote: > >> Hi, >> >> will attach the patch again. However, encountered some registry test >> failures in patch0009/registry.core without my patch. >> >> thanks >> >> >> On Thu, Jul 10, 2014 at 4:46 PM, Shameera Rathnayaka >> wrote: >> >>> Hi Pradeep, >>> >>> you have introduced a new API in your patch , please remove that as it >>> is incorrect to do API changes with a patch. But when you provide a pull >>> request to 4.3.0 you can do any API changes. >>> >>> Thanks, >>> Shameera. >>> >>> >>> On Thu, Jul 10, 2014 at 3:47 PM, Pradeep Fernando >>> wrote: >>> >>>> Hi Kernel team, >>>> >>>> Please review and merge the changes please. >>>> >>>> https://wso2.org/jira/browse/CARBON-14861 >>>> >>>> thanks >>>> >>> >>> >>> >>> -- >>> *Software Engineer - WSO2 Inc.* >>> *email: shameera AT wso2.com , shameera AT >>> apache.org * >>> *phone: +9471 922 1454 <%2B9471%20922%201454>* >>> >>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>> *Twitter : *https://twitter.com/Shameera_R >>> >> >> >> >> -- >> *Pradeep Fernando* >> Associate Technical Lead;WSO2 Inc.; http://wso2.com >> >> blog: http://pradeepfernando.blogspot.com >> m: +94776603662 >> > > > > -- > *Pradeep Fernando* > Associate Technical Lead;WSO2 Inc.; http://wso2.com > > blog: http://pradeepfernando.blogspot.com > m: +94776603662 > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please merge the changes to patch0009 of 4.2.0 kernel
Hi Pradeep, you have introduced a new API in your patch , please remove that as it is incorrect to do API changes with a patch. But when you provide a pull request to 4.3.0 you can do any API changes. Thanks, Shameera. On Thu, Jul 10, 2014 at 3:47 PM, Pradeep Fernando wrote: > Hi Kernel team, > > Please review and merge the changes please. > > https://wso2.org/jira/browse/CARBON-14861 > > thanks > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please Apply the CARBON-14841 changes to kernel patch0009
Done On Thu, Jul 3, 2014 at 9:25 PM, Waruna Jayaweera wrote: > Hi, > Please merge the pull request to carbon4-kernel > https://github.com/wso2-dev/carbon4-kernel/pull/33 > > Thanks, > Waruna > > > On Thu, Jul 3, 2014 at 2:23 PM, Kishanthan Thangarajah < > kishant...@wso2.com> wrote: > >> Waruna, did you send the pull request to the carbon4-kernel repo : >> https://github.com/wso2-dev/carbon4-kernel/ also? >> >> >> On Tue, Jul 1, 2014 at 6:17 PM, Shameera Rathnayaka >> wrote: >> >>> Committed revision 205239 , >>> >>> please provide pull request to carbon 4.3.0 branch too. >>> >>> Thanks, >>> Shameera. >>> >>> >>> On Tue, Jul 1, 2014 at 12:11 PM, Waruna Jayaweera >>> wrote: >>> >>>> Hi , >>>> Please Add this fix for Carbon kernel patch0009. >>>> >>>> Related Jira >>>> >>>> https://wso2.org/jira/browse/CARBON-14841 >>>> >>>> -- >>>> Regards, >>>> >>>> Waruna Lakshitha Jayaweera >>>> Software Engineer >>>> WSO2 Inc; http://wso2.com >>>> phone: +94713255198 >>>> >>>> _______ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Software Engineer - WSO2 Inc.* >>> *email: shameera AT wso2.com , shameera AT >>> apache.org * >>> *phone: +9471 922 1454 <%2B9471%20922%201454>* >>> >>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>> *Twitter : *https://twitter.com/Shameera_R >>> >> >> >> >> -- >> *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>* >> > > > > -- > Regards, > > Waruna Lakshitha Jayaweera > Software Engineer > WSO2 Inc; http://wso2.com > phone: +94713255198 > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please Apply the CARBON-14841 changes to kernel patch0009
Committed revision 205239 , please provide pull request to carbon 4.3.0 branch too. Thanks, Shameera. On Tue, Jul 1, 2014 at 12:11 PM, Waruna Jayaweera wrote: > Hi , > Please Add this fix for Carbon kernel patch0009. > > Related Jira > > https://wso2.org/jira/browse/CARBON-14841 > > -- > Regards, > > Waruna Lakshitha Jayaweera > Software Engineer > WSO2 Inc; http://wso2.com > phone: +94713255198 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] ESB Worker profile contain UI buildes
Hi ESB team, This is regarding ESB 4.8.1. There is no difference between Worker profile and Default profile configurations. both has the same bundle.info file which has both server and UI bundles. As I can see, ESB p2 profile gen is not configured to use only server features when it generate worker profile, it uses common features which has both server and ui features. But correct way is, use common features with Default profile generations and Server features with Worker profile generations. As a result, even i start ESB server as worker i can see the management UI. but when i try to login it says logging failed. Better we fix this for next releases. Thanks, Shameera. -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Shazni Nazir
Congratulation !!! On Tue, Jun 3, 2014 at 8:08 PM, Firzhan Naqash wrote: > Congratulations Shazni... > > Regards, > Firzhan > > > On Tue, Jun 3, 2014 at 7:58 PM, Waruna Jayaweera wrote: > >> Congratzz Shazni... >> >> >> On Tue, Jun 3, 2014 at 7:51 PM, Pulasthi Supun wrote: >> >>> Congrats Shazni!! >>> >>> >>> >>> >>> On Tue, Jun 3, 2014 at 7:49 PM, Subash Chaturanga >>> wrote: >>> >>>> Hi all, >>>> It's my pleasure to announce Shazni as a WSO2 Committer. Shazni has >>>> done great contributions to G-Reg product and showed very good enthusiasm >>>> in his work. And in recognition of his contribution he has been voted as a >>>> wso2 commiter. >>>> >>>> Shazni, welcome aboard and keep up the good work!. >>>> >>>> -- >>>> Thanks >>>> /subash >>>> >>>> *Subash Chaturanga* >>>> Senior Software Engineer :Platform 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 >>>> >>>> >>> >>> >>> -- >>> -- >>> Pulasthi Supun >>> Software Engineer; WSO2 Inc.; http://wso2.com, >>> Email: pulas...@wso2.com >>> Mobile: +94 (71) 9258281 >>> Blog : http://pulasthisupun.blogspot.com/ >>> Git hub profile: https://github.com/pulasthi >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Regards, >> >> Waruna Lakshitha Jayaweera >> Software Engineer >> WSO2 Inc; http://wso2.com >> phone: +94713255198 >> >> ___ >> 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Sohani Weerasinghe
On Mon, Jun 2, 2014 at 4:43 PM, Shameera Rathnayaka wrote: > Congratulation Shani !!! > > It should be Sohani, sorry for mistype :) > > On Mon, Jun 2, 2014 at 3:57 PM, Sohani Weerasinghe > wrote: > >> Thank you everyone >> >> Thanks, >> Sohani >> >> Sohani Weerasinghe >> Software Engineer >> WSO2, Inc: http://wso2.com >> >> Mobile : +94 716439774 >> Blog :http://christinetechtips.blogspot.com/ >> Twitter : https://twitter.com/sohanichristine >> >> >> On Sun, Jun 1, 2014 at 3:10 PM, Dilini Muthumala wrote: >> >>> Congrats, Sohani! >>> >>> >>> On Sun, Jun 1, 2014 at 9:31 AM, Rajith Vitharana >>> wrote: >>> >>>> congrats!!! >>>> >>>> >>>> On Sat, May 31, 2014 at 8:58 AM, Tania Mahanama wrote: >>>> >>>>> Congrats!! >>>>> >>>>> >>>>> On Sat, May 31, 2014 at 7:58 AM, Thanuja Jayasinghe >>>>> wrote: >>>>> >>>>>> Congratz!!! >>>>>> On 30 May 2014 17:00, "Lali Devamanthri" wrote: >>>>>> >>>>>>> Congratulations >>>>>>> >>>>>>> >>>>>>> On Fri, May 30, 2014 at 11:06 AM, Jasintha Dasanayake < >>>>>>> jasin...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> It's my distinct pleasure to welcome Sohani as a WSO2 Committer. >>>>>>>> >>>>>>>> Sohani has been a valuable contributor for WSO2 Developer Studio >>>>>>>> since she joined WSO2. In recognition of her contributions to WSO2, >>>>>>>> she has >>>>>>>> been voted as a WSO2 Committer. >>>>>>>> >>>>>>>> Sohani, Congratulations and Keep up the good work! >>>>>>>> >>>>>>>> Thanks and Regards, >>>>>>>> /Jasintha >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *Jasintha Dasanayake * >>>>>>>> >>>>>>>> *Senior Software EngineerWSO2 Inc. | http://wso2.com >>>>>>>> <http://wso2.com/> lean . enterprise . middleware* >>>>>>>> >>>>>>>> >>>>>>>> *mobile :- 0711368118 <0711368118> * >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Lali Sudaththa Devamanthri* >>>>>>> Software Engineer >>>>>>> WSO2 Inc.; http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> mobile: +94 71 895 4922 >>>>>>> <http://www.wso2.com> >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Tania Mahanama >>>>> Senior Technical Writer >>>>> >>>>> Contact: >>>>> Mob: +94 077 5129270 >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> 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 >>>> >>>> >>> >>> >>> -- >>> *Dilini Muthumala* >>> Software Engineer, >>> WSO2 Inc. >>> >>> *E-mail :* dil...@wso2.com >>> *Mobile: *+94713 400 029 >>> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Software Engineer - WSO2 Inc.* > *email: shameera AT wso2.com , shameera AT apache.org > * > *phone: +9471 922 1454 <%2B9471%20922%201454>* > > *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 > *Twitter : *https://twitter.com/Shameera_R > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Sohani Weerasinghe
Congratulation Shani !!! On Mon, Jun 2, 2014 at 3:57 PM, Sohani Weerasinghe wrote: > Thank you everyone > > Thanks, > Sohani > > Sohani Weerasinghe > Software Engineer > WSO2, Inc: http://wso2.com > > Mobile : +94 716439774 > Blog :http://christinetechtips.blogspot.com/ > Twitter : https://twitter.com/sohanichristine > > > On Sun, Jun 1, 2014 at 3:10 PM, Dilini Muthumala wrote: > >> Congrats, Sohani! >> >> >> On Sun, Jun 1, 2014 at 9:31 AM, Rajith Vitharana >> wrote: >> >>> congrats!!! >>> >>> >>> On Sat, May 31, 2014 at 8:58 AM, Tania Mahanama wrote: >>> >>>> Congrats!! >>>> >>>> >>>> On Sat, May 31, 2014 at 7:58 AM, Thanuja Jayasinghe >>>> wrote: >>>> >>>>> Congratz!!! >>>>> On 30 May 2014 17:00, "Lali Devamanthri" wrote: >>>>> >>>>>> Congratulations >>>>>> >>>>>> >>>>>> On Fri, May 30, 2014 at 11:06 AM, Jasintha Dasanayake < >>>>>> jasin...@wso2.com> wrote: >>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> It's my distinct pleasure to welcome Sohani as a WSO2 Committer. >>>>>>> >>>>>>> Sohani has been a valuable contributor for WSO2 Developer Studio >>>>>>> since she joined WSO2. In recognition of her contributions to WSO2, she >>>>>>> has >>>>>>> been voted as a WSO2 Committer. >>>>>>> >>>>>>> Sohani, Congratulations and Keep up the good work! >>>>>>> >>>>>>> Thanks and Regards, >>>>>>> /Jasintha >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Jasintha Dasanayake * >>>>>>> >>>>>>> *Senior Software EngineerWSO2 Inc. | http://wso2.com >>>>>>> <http://wso2.com/> lean . enterprise . middleware* >>>>>>> >>>>>>> >>>>>>> *mobile :- 0711368118 <0711368118> * >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Lali Sudaththa Devamanthri* >>>>>> Software Engineer >>>>>> WSO2 Inc.; http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> >>>>>> mobile: +94 71 895 4922 >>>>>> <http://www.wso2.com> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Tania Mahanama >>>> Senior Technical Writer >>>> >>>> Contact: >>>> Mob: +94 077 5129270 >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> 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 >>> >>> >> >> >> -- >> *Dilini Muthumala* >> Software Engineer, >> WSO2 Inc. >> >> *E-mail :* dil...@wso2.com >> *Mobile: *+94713 400 029 >> > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] org.apache.axis2.json.gson.JsonFormatter formats the response as JSON without HTTP Content-Type header
Hi Charitha/Anjana,
Shameera any idea on why this would be happening? .. is it something that
> should be done explicitly in the message formatter which we are not doing?
> ..
>
No, Formatter is not responsible for setting content type of message it
only serialize message body to outputStream. Anjana could you please check,
what is different of using above two Formatters, I doubt that we
explicitly handle this content type for old json formatter.
FYI: I am on Study leave.
Thanks,
Shameera.
> @Charitha, we cannot simply tell users to just switch to the other JSON
> formatter because, we lose some features with the old JSON formatter, so
> even without the content type returned, some users may not have an issue
> with it, so I don't think we don't have to put an entry to the docs
> explaining the issue, rather, can you please create an JIRA issue for this
> to track it, so we can fix it in the next release.
>
> Cheers,
> Anjana.
>
>
> On Wed, May 28, 2014 at 11:01 PM, Charitha Kankanamge
> wrote:
>
>> Any update on this? Looks like the latest
>> org.apache.axis2.json.gson.JsonFormatter
>> is broken since the application/json content-type header is not added to
>> the response.
>>
>> Charitha Kankanamge
>> cell: +1 812-391-7730
>> http://charithaka.blogspot.com
>> *SOA and Testing without nonsense*
>>
>>
>> On Wed, May 28, 2014 at 12:51 AM, Charitha Kankanamge
>> wrote:
>>
>>> Hi Anjana et all,
>>> DSS uses org.apache.axis2.json.gson.JsonFormatter by default. However,
>>> when calling a service which responds JSON, the message looks similar to
>>> the following.
>>>
>>> *HTTP/1.1 200 OK*
>>> *Transfer-Encoding: chunked*
>>> *Date: Tue, 27 May 2014 19:14:45 GMT*
>>> *Connection: close*
>>> *Server: WSO2 Carbon Server*
>>>
>>> {"customers":{"customer":[{"phone":"6175559555
>>> ","contact":{"contact-last-name":"Yoshido","customer-name":"Gifts4AllAges.com","contact-first-name":"Juri"},"city":"Boston"},{"phone":"
>>> 6175552555","contact":{"contact-last-name":"Franco","customer-name":"Diecast
>>> Collectables","contact-first-name":"Valarie"},"city":"Boston"}]}}
>>>
>>> I had to comment out this default formatter and use the
>>> org.apache.axis2.json.JSONMessageFormatter.
>>> Then I got the correct response.
>>>
>>> HTTP/1.1 200 OK
>>> *Content-Type: application/json;charset=UTF-8*
>>> Transfer-Encoding: chunked
>>> Date: Tue, 27 May 2014 19:17:02 GMT
>>> Connection: close
>>> Server: WSO2 Carbon Server
>>>
>>> {"customers":{"customer":[{"phone":"6175559555
>>> ","contact":{"contact-last-name":"Yoshido","customer-name":"Gifts4AllAges.com","contact-first-name":"Juri"},"city":"Boston"},{"phone":"
>>> 6175552555","contact":{"contact-last-name":"Franco","customer-name":"Diecast
>>> Collectables","contact-first-name":"Valarie"},"city":"Boston"}]}}
>>>
>>> This can simply be observed by running JSON sample included in a fresh
>>> pack (DSS-3.2.1). Is this a bug in new formatter? If so, it is better to
>>> document this and ask to use org.apache.axis2.json.JSONMessageFormatter
>>> instead.
>>>
>>> Thanks!
>>> Charitha
>>>
>>>
>>> Charitha Kankanamge
>>> cell: +1 812-391-7730
>>> http://charithaka.blogspot.com
>>> *SOA and Testing without nonsense*
>>>
>>
>>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
--
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com , shameera AT apache.org
*
*phone: +9471 922 1454*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ClassNotFoundException in CacheCleanupTask
Hi Prabath, This can be a version issue, give it a try after set the version of exported package. and change the hezalcast osgi bundle too such that it import correct version. Thanks, Shameera. On Mon, May 19, 2014 at 1:09 AM, Afkham Azeez wrote: > > > > On Mon, May 19, 2014 at 1:05 AM, Prabath Siriwardena wrote: > >> >> >> >> On Mon, May 19, 2014 at 12:59 AM, Afkham Azeez wrote: >> >>> That could be one reason, and another way this can happen is this cache >>> entry getting replicated on to another node that cannot see this class, and >>> the first time it tries to access the entry is when it tries to do a >>> cleanup, and at that point, tries to load the class, and then this failure >>> happens. >>> >> >> If this is the case.. do we have a solution for it..? >> > > All nodes in a single cluster should be homogenous; which means, all nodes > should see the same bundles/classes. Then this error will never happen. > > >> >> >>> >>> >>> On Mon, May 19, 2014 at 12:55 AM, Pradeep Fernando wrote: >>> >>>> The class, >>>> >>>> org.wso2.carbon.identity.provisioning.cache.ProvisioningEntityCacheKey >>>> >>>> properly exported ? i know its a dumb question. just checking... :) >>>> >>>> >>>> >>>> >>>> On Mon, May 19, 2014 at 12:43 AM, Prabath Siriwardena >>> > wrote: >>>> >>>>> Appreciate a lot any clue on this...? >>>>> >>>>> https://wso2.org/jira/browse/IDENTITY-2454 >>>>> >>>>> - Error occurred while running CacheCleanupTask >>>>> com.hazelcast.nio.serialization.HazelcastSerializationException: >>>>> java.lang.ClassNotFoundException: >>>>> org.wso2.carbon.identity.provisioning.cache.ProvisioningEntityCacheKey >>>>> at >>>>> com.hazelcast.nio.serialization.DefaultSerializers$ObjectSerializer.read(DefaultSerializers.java:190) >>>>> at >>>>> com.hazelcast.nio.serialization.StreamSerializerAdapter.read(StreamSerializerAdapter.java:59) >>>>> >>>>> -- >>>>> Thanks & Regards, >>>>> Prabath >>>>> >>>>> -- >>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> *Pradeep Fernando* >>>> Associate Technical Lead;WSO2 Inc.; http://wso2.com >>>> >>>> blog: http://pradeepfernando.blogspot.com >>>> m: +94776603662 >>>> >>> >>> >>> >>> -- >>> *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* >>> * 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 >> > > > > -- > *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* > * 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please Commit to Kernel User Core
Hi Pushpalanka/Prabath committed patch to kernel patch0008 with revision 203085. @Pushpalanka please provide a pull request for 4.3.0 git repo too. Thanks, Shameera. On Sun, May 18, 2014 at 5:34 AM, Prabath Siriwardena wrote: > > On Sat, May 17, 2014 at 10:51 PM, Pushpalanka Jayawardhana > wrote: > >> Hi, >> >> The patch attached at the issue [1]. >> >> [1] - https://wso2.org/jira/browse/IDENTITY-2016 >> >> Thanks, >> Pushpalanka. >> -- >> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >> Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >> Mobile: +94779716248 >> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [C5] Refresh OSGi bundles in Hot Patch Deployment
Had an offline chat with Aruna, Regarding refresh all nested level bundles, If we assume developer will follow all osgi best practices( yes, they should be enforced) like not keep object references of classes in imported packages, then we can simply continue with one level dependency closer refreshing process. Thanks Shameera. On Fri, May 16, 2014 at 11:57 AM, Shameera Rathnayaka wrote: > Hi Aruna, > > If you rewire the first level of bundles in dependency closure IMO of > course you need to do it for all next level bundles too. > > I think we came to a conclusion where we doesn't support hot update(with > patch) for top level bundle in bundle hierarchy as it may cause to refresh > almost all the bundle in runtime. which is same as restart. > > List of top level bundles is yet to be decided. You can maintain a > property with you patch meta file to provide this information, where hot > patch deployer print a WARN to restart the server if there is a such top > level bundle comes with patches or deployer will ask a permission to > restart the system after applying all the patches if require. > > thanks, > Shameera. > > > On Fri, May 16, 2014 at 11:43 AM, Aruna Karunarathna wrote: > >> Hi all, >> >> Currently I am involved in the R & D of the Hot patch deployment of OSGi >> Bundles. As per now I have implemented the hot deployment as follows. >> >> >>- Update the bundle using an InputStream >>- Get the FrameworkWiring using the SystemBundle >>- Get the bundle's dependency closure using the FrameworkWiring >>- Then finally refresh the the bundles within the dependency closure >> >> >> My problem is that, is it enough to refresh the first level dependencies >> only to the hot deployment to be successful; or do I have to refresh the >> next level bundles also. >> >> I am not clear enough according to the documentation in [1]. >> >> [1]. >> http://www.osgi.org/javadoc/r4v43/core/org/osgi/framework/wiring/FrameworkWiring.html#refreshBundles(java.util.Collection, >> org.osgi.framework.FrameworkListener...) >> >> >> >> Regards, >> -- >> >> * Aruna Sujith Karunarathna* | Software Engineer >> WSO2, Inc | lean. enterprise. middleware. >> #20, Palm Grove, Colombo 03, Sri Lanka >> Mobile: +94 71 9040362 | Work: +94 112145345 >> Email: ar...@wso2.com | Web: www.wso2.com >> >> > > > > -- > *Software Engineer - WSO2 Inc.* > *email: shameera AT wso2.com , shameera AT apache.org > * > *phone: +9471 922 1454 <%2B9471%20922%201454>* > > *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 > *Twitter : *https://twitter.com/Shameera_R > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [C5] Refresh OSGi bundles in Hot Patch Deployment
Hi Aruna, If you rewire the first level of bundles in dependency closure IMO of course you need to do it for all next level bundles too. I think we came to a conclusion where we doesn't support hot update(with patch) for top level bundle in bundle hierarchy as it may cause to refresh almost all the bundle in runtime. which is same as restart. List of top level bundles is yet to be decided. You can maintain a property with you patch meta file to provide this information, where hot patch deployer print a WARN to restart the server if there is a such top level bundle comes with patches or deployer will ask a permission to restart the system after applying all the patches if require. thanks, Shameera. On Fri, May 16, 2014 at 11:43 AM, Aruna Karunarathna wrote: > Hi all, > > Currently I am involved in the R & D of the Hot patch deployment of OSGi > Bundles. As per now I have implemented the hot deployment as follows. > > >- Update the bundle using an InputStream >- Get the FrameworkWiring using the SystemBundle >- Get the bundle's dependency closure using the FrameworkWiring >- Then finally refresh the the bundles within the dependency closure > > > My problem is that, is it enough to refresh the first level dependencies > only to the hot deployment to be successful; or do I have to refresh the > next level bundles also. > > I am not clear enough according to the documentation in [1]. > > [1]. > http://www.osgi.org/javadoc/r4v43/core/org/osgi/framework/wiring/FrameworkWiring.html#refreshBundles(java.util.Collection, > org.osgi.framework.FrameworkListener...) > > > > Regards, > -- > > * Aruna Sujith Karunarathna* | Software Engineer > WSO2, Inc | lean. enterprise. middleware. > #20, Palm Grove, Colombo 03, Sri Lanka > Mobile: +94 71 9040362 | Work: +94 112145345 > Email: ar...@wso2.com | Web: www.wso2.com > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Streaming JSON Fix
Hi Anjana, I will have a look and apply the patch. Thanks, Shameera. On Sat, May 3, 2014 at 4:11 PM, Anjana Fernando wrote: > Hi Shameera, > > I've fixed a bug in the streaming JSON implementation, related to the > issue [1]. I've given the explanation to the fix there in a comment, please > review it, and commit it to the necessary places, i.e. kernel patch07, > GitHub, Axis2 etc.. We need this for the Monday DSS 3.2.1 release. Chanika > please follow up. > > [1] https://wso2.org/jira/browse/DS-891 > > Cheers, > Anjana. > -- > *Anjana Fernando* > Senior Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [C5] Expose a RESTful service in Carbon Kernel 5
Hi Pradeep, We have a poc level working implementation with Java reflections. But our idea is to write a ultra fast data binding frame work which generate java byte code at deployment time and use that to invoke JAXRS resource, not java reflection which is obviously slow. Feature wise we will follow the JAXRS specs and implement only the basic features that require to expose a JAXRS service and request/response handling. JSON will be our standard data format for request and response. It would be great if you can points out the requirements that you think we should support in our light weight implementation. Thanks, Shameera. On Fri, May 2, 2014 at 11:26 AM, Pradeep Fernando wrote: > Hi kishanthan/devs, > > I believe we already have the first cut implementation of that. If so > shall we do a quick review. I want to see the capabilities it has right now > vs things what we need... > > thanks > > > On Wed, Apr 30, 2014 at 9:02 PM, Aruna Karunarathna wrote: > >> Thanks Kishanthan. >> >> >> On Wed, Apr 30, 2014 at 5:40 PM, Kishanthan Thangarajah < >> kishant...@wso2.com> wrote: >> >>> Not with the latest milestone. The plan is to include this for the next >>> milestone (a light weight RESTful admin services framework). >>> >>> >>> On Wed, Apr 30, 2014 at 12:46 PM, Aruna Karunarathna wrote: >>> >>>> Hi all, >>>> >>>> Can we do the $subject with the current latest milestone release? >>>> >>>> Regards, >>>> -- >>>> >>>> * Aruna Sujith Karunarathna* | Software Engineer >>>> WSO2, Inc | lean. enterprise. middleware. >>>> #20, Palm Grove, Colombo 03, Sri Lanka >>>> Mobile: +94 71 9040362 | Work: +94 112145345 >>>> Email: ar...@wso2.com | Web: www.wso2.com >>>> >>>> >>> >>> >>> >>> -- >>> *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>* >>> >> >> >> >> -- >> >> * Aruna Sujith Karunarathna* | Software Engineer >> WSO2, Inc | lean. enterprise. middleware. >> #20, Palm Grove, Colombo 03, Sri Lanka >> Mobile: +94 71 9040362 | Work: +94 112145345 >> Email: ar...@wso2.com | Web: www.wso2.com >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Pradeep Fernando* > Associate Technical Lead;WSO2 Inc.; http://wso2.com > > blog: http://pradeepfernando.blogspot.com > m: +94776603662 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fixing Shutdown Errors WSO2 MB.
Hi HasithaH,
In the shutdown logs i could see following line, before start andes
deactivation, what does actually mean? does it stop cassandra transport
listener?
[2014-05-02 10:12:19,021] INFO {org.apache.cassandra.transport.Server} -
Stop listening for CQL clients
On Fri, May 2, 2014 at 10:26 AM, Hasitha Hiranya wrote:
> Hi Shameera,
>
> I have added logs and tested. Full Log is attached at (
> https://drive.google.com/a/wso2.com/file/d/0B57HoxWKqqNnN2FPRE9FeC0yYXM/edit?usp=sharing).
> Deactivate of andes service is like follows.
>
> protected void deactivate(ComponentContext ctx) {
> // Unregister QpidService
> System.out.println("+++Started deactivating
> andes");
> System.out.println("Unregistering qpid service");
> try {
> if (null != qpidService) {
> qpidService.unregister();
> }
> } catch (Exception e) {}
> System.out.println("+Unregistered qpidService");
> // Shutdown the Qpid broker
> System.out.println("+Shutting down andes");
> ApplicationRegistry.remove();
> System.out.println("+++done shutting down andes");
> System.out.println("+++done deactivating of andes
> component");
> }
>
> +++Started deactivating andes
> Unregistering qpid service
> +Unregistered qpidService
> +Shutting down andes
> +++done shutting down andes
> +++done deactivating of andes component
> started deactivating cassandra
> ++done deactivating cassandra
>
> I have a doubt like is it correct to unregister qpidService before
> actually shutting down the broker?
> Then I changed the code swapping the order.
>
> protected void deactivate(ComponentContext ctx) {
> // Unregister QpidService
> // Shutdown the Qpid broker
> ApplicationRegistry.remove();
> try {
> if (null != qpidService) {
> qpidService.unregister();
> }
> } catch (Exception e) {}
> }
>
>
> Still errors happened. Order was as follows.
>
> +++Started deactivating andes
> +shutting down andes
> +++done shutting down andes
> unregistering qpidservice
> +Unregistered qpidService
> +++done deactivating of andes component
> started deactivating cassandra
> ++done deactivating cassandra
>
> Pom file has cassandra as a dependency.
>
>
> org.apache.axis2.*;
> version="${axis2.osgi.version.range.qpid}",
> org.apache.axiom.*;
> version="${axiom.osgi.version.range.qpid}",
> org.wso2.carbon.andes.authentication.service,
> org.wso2.carbon.andes.commons,
> org.wso2.carbon.andes.commons.registry,
> * org.wso2.carbon.cassandra.server;
> version="4.2.2",*
> *;resolution:=optional
>
>
> What is going wrong?
>
> Thanks
>
>
> On Fri, May 2, 2014 at 9:33 AM, Shameera Rathnayaka wrote:
>
>> Hi HasithaH,
>>
>> Shall we try with log messages to identify service deactivation and
>> bundle undeployment order of andes and cassandra ?
>>
>> Thanks,
>> Shameera.
>>
>>
>> On Fri, May 2, 2014 at 9:18 AM, Hasitha Hiranya wrote:
>>
>>> During testing I followed following steps.
>>>
>>> 1. create a topic subscriber
>>> 2. publish 1000 msgs
>>> 3. wait until the subscriber get 1000 messages and close
>>> 4. now underneath MB will still be leisurely deleting the content of
>>> removed messages (with timeouts etc)
>>> 5. I shutdown the broker by Ctrl+c
>>> 6. Now with my above fixes it will delete all records that needs to be
>>> deleted before shutting down.
>>>
>>> I can see when the code is at step 6 MB is saying cassandra is down.
>>> Thus before returning from the Close() of message store (hence before
>>> returning from deactivte of andes service), cassandra service get
>>> disappeared. It boils down to an OSGI problem.
>>>
>>> @Shameera,
>>>
>>> I have the dependency to the cassandra bundle as you have suggested in
>>> the andes bundle. But seems there is a p
Re: [Dev] Fixing Shutdown Errors WSO2 MB.
Hi HasithaH, Shall we try with log messages to identify service deactivation and bundle undeployment order of andes and cassandra ? Thanks, Shameera. On Fri, May 2, 2014 at 9:18 AM, Hasitha Hiranya wrote: > During testing I followed following steps. > > 1. create a topic subscriber > 2. publish 1000 msgs > 3. wait until the subscriber get 1000 messages and close > 4. now underneath MB will still be leisurely deleting the content of > removed messages (with timeouts etc) > 5. I shutdown the broker by Ctrl+c > 6. Now with my above fixes it will delete all records that needs to be > deleted before shutting down. > > I can see when the code is at step 6 MB is saying cassandra is down. > Thus before returning from the Close() of message store (hence before > returning from deactivte of andes service), cassandra service get > disappeared. It boils down to an OSGI problem. > > @Shameera, > > I have the dependency to the cassandra bundle as you have suggested in the > andes bundle. But seems there is a problem still. Any idea why that > happens? > > > On Thu, May 1, 2014 at 10:56 AM, Hasitha Hiranya wrote: > >> Hi, >> >> Also in order to stop connection to Cassandra gracefully, we need to do >> following. >> >> cluster.getConnectionManager().shutdown(); >> >> Thanks >> >> >> On Thu, May 1, 2014 at 10:52 AM, Hasitha Hiranya wrote: >> >>> Hi, >>> >>> I intend to cleanup graceful shutdown code of WSO2 Message Broker in >>> following way. We have to do them as a part of fixing shutdown errors. We >>> have managed to keep Cassandra until broker service shutdown properly in >>> OSGI env, but we see problems due to lack of these. >>> >>> 1. When shutting down we have to flush >>> all pubSubMessageContentRemoverTasks, meaning we have to delete all acked >>> messages for topics, otherwise they will never be removed again (After >>> shutting down memory is gone). Concern is we have to wait for timeout for >>> those messages to happen, which will cause shutting down of MB on hold >>> untill all messages are timed out. For now MB will shut down hoping some >>> other node will clear them up. >>> >>> 2. Above argument goes with content removal tasks as well. Merely >>> stopping deletion thread will not help. >>> >>> 3. above two tasks should be done AFTER stopping queue/topic flusher >>> threads. >>> >>> 4. When shutting down we have to clear in-memory message status (for >>> message count to be correct). >>> >>> 5. We have to copy back NQ messages back to GQ. >>> >>> 6. Flush message counts. >>> >>> @pamod, >>> >>> You have a fix to flush the message count before shutdown (As we update >>> it per message chunks). Is it committed? If so, where is the code? It >>> should come as point 6. >>> >>> Apart from point 6 have have done other. Testing now. >>> >>> Thanks >>> >>> -- >>> *Hasitha Abeykoon* >>> Software Engineer; WSO2, Inc.; http://wso2.com >>> *cell:* *+94 719363063* >>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >>> >>> >> >> >> -- >> *Hasitha Abeykoon* >> Software Engineer; WSO2, Inc.; http://wso2.com >> *cell:* *+94 719363063* >> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >> >> > > > -- > *Hasitha Abeykoon* > Senior Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454 <%2B9471%20922%201454>* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Waruna Jayaweera
Congratzz !!! Cheers, Shameera. On Mon, Apr 21, 2014 at 5:40 PM, Isura Karunaratne wrote: > Congrats, Amal..!! > > > On Mon, Apr 21, 2014 at 2:10 PM, Dilini Muthumala wrote: > >> Congrats, Waruna! >> >> >> On Mon, Apr 21, 2014 at 2:05 PM, Amal Gunatilake wrote: >> >>> Congratz Waruna !! >>> >>> Thank you & Best regards, >>> >>> *Amal Gunatilake* >>> Software Engineer >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> >>> On Mon, Apr 21, 2014 at 11:40 AM, Rajith Vitharana wrote: >>> >>>> Congrats Waruna :) >>>> >>>> >>>> On Mon, Apr 21, 2014 at 11:26 AM, Isuruwan Herath wrote: >>>> >>>>> Congrats Waruna...!!! >>>>> >>>>> >>>>> On Mon, Apr 21, 2014 at 10:57 AM, Lasantha Fernando >>>> > wrote: >>>>> >>>>>> Congratulations Waruna...!! >>>>>> >>>>>> >>>>>> On 21 April 2014 10:29, Chathurika Mahaarachchi >>>>>> wrote: >>>>>> >>>>>>> Congratulations Waruna...!!! >>>>>>> >>>>>>> >>>>>>> On Mon, Apr 21, 2014 at 10:27 AM, Aruna Karunarathna >>>>>> > wrote: >>>>>>> >>>>>>>> Congratulations Waruna...!!! >>>>>>>> >>>>>>>> >>>>>>>> On Sat, Apr 19, 2014 at 8:23 AM, Nandika Jayawardana < >>>>>>>> nand...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi All, >>>>>>>>> >>>>>>>>> It's my pleasure to announce Waruna Jayaweera as a WSO2 >>>>>>>>> Committer. Waruna has been a valuable contributor for WSO2 BPS / BRS >>>>>>>>> products and in recognition of his contributions to WSO2, he has been >>>>>>>>> voted >>>>>>>>> as a WSO2 Committer. >>>>>>>>> >>>>>>>>> Waruna, Congratulations and Keep up the good work! >>>>>>>>> >>>>>>>>> Thanks and Regards, >>>>>>>>> Nandika >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Nandika Jayawardana >>>>>>>>> Senior Technical Lead >>>>>>>>> WSO2 Inc ; http://wso2.com >>>>>>>>> lean.enterprise.middleware >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> * Aruna Sujith Karunarathna* | Software Engineer >>>>>>>> WSO2, Inc | lean. enterprise. middleware. >>>>>>>> #20, Palm Grove, Colombo 03, Sri Lanka >>>>>>>> Mobile: +94 71 9040362 | Work: +94 112145345 >>>>>>>> Email: ar...@wso2.com | Web: www.wso2.com >>>>>>>> >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Chathurika Mahaarachchi* >>>>>>> Software Engineer, QA. >>>>>>> WSO2 Inc.: http://wso2.com/ >>>>>>> lean.enterprise.middleware >>>>>>> Mobile: +94718223950 >>>>>>> >>>>>>> ___ >>>>>>> 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 >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Isuruwan Herath >>>>> Technical Lead >>>>> >>>>> Contact: +94 776 273 296 >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> 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 >>>> >>>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Dilini Muthumala* >> Software Engineer, >> WSO2 Inc. >> >> *E-mail :* dil...@wso2.com >> *Mobile: *+94713 400 029 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Isura Dilhara Karunaratne > Software Engineer > > Mob +94 772 254 810 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Remove entries from default carbon.xml file in products
Hi Manoj et al, AFAIK only MB is using that entries(As Ishara has mentioned above) so I think it is safe to remove that element from Carbon.xml file. Thanks, Shameera. On Tue, Apr 1, 2014 at 11:31 AM, Manoj Kumara wrote: > Hi, > > Since currently no other product ships this we can proceed with this. > Please let me know if any concerns with other products. > Once confirmed I'll commit the change. > > Thanks, > Manoj > > > *Manoj Kumara* > Software Engineer > WSO2 Inc. http://wso2.com/ > *lean.enterprise.middleware* > Mobile: +94713448188 > > > On Thu, Mar 27, 2014 at 2:16 PM, Ishara Premadasa wrote: > >> Hi Carbon team, >> >> We no longer ships an embedded qpid broker with any product where this is >> replaced by WSO2 MB. Therefore currently it is not supported to use these >> entries to change Message Broker's ports and hence keeping these might >> mislead the users. >> >> Therefore can we please get the following entries under the >> elelment, removed from carbon.xml file file. Created [1] for this. >> >> >> >> >> 5672 >> >> 8672 >> >> >> Thanks! >> Ishara >> >> [1] https://wso2.org/jira/browse/CARBON-14745 >> >> -- >> Ishara Premasada >> Software Engineer, >> WSO2 Inc. http://wso2.com/ >> >> >> *Blog : http://isharapremadasa.blogspot.com/ >> <http://isharapremadasa.blogspot.com/> Twitter : >> https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile : +94 >> 714445832 <%2B94%20714445832>* >> >> >> >> ___ >> 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Committing 4.2.0 kernel patches to 4.3.0 in Git repo
Hi Geeth, This is required to merge all the modifications in development branch to master branch. Will try our best to review and do the merge today itself. Thanks, Shameera. On Mon, Mar 17, 2014 at 2:39 PM, Geeth Munasinghe wrote: > Hi > > Any update on this ? > > Thanks > Geeth > > > *G. K. S. Munasinghe * > *Software Engineer,* > *WSO2, Inc. http://wso2.com <http://wso2.com/> * > *lean.enterprise.middleware.* > > email: ge...@wso2.com > phone:(+94) 777911226 > > > On Fri, Mar 14, 2014 at 11:31 PM, Geeth Munasinghe wrote: > >> Hi Shameera >> >> Have you committed them to main repo in git hub ? >> If not please commit them soon, because we are depend on them to >> stabilize the product builds. >> >> Thanks >> Geeth >> >> >> *G. K. S. Munasinghe* >> *Software Engineer,* >> *WSO2, Inc. http://wso2.com <http://wso2.com/> * >> *lean.enterprise.middleware.* >> >> email: ge...@wso2.com >> phone:(+94) 777911226 >> >> >> On Thu, Mar 13, 2014 at 7:23 PM, Shameera Rathnayaka >> wrote: >> >>> Hi, >>> >>> I have merged the pull request sent by Geeth to wso2-dev/master. >>> >>> Thanks >>> Shameera. >>> >>> >>> On Thu, Mar 13, 2014 at 6:21 PM, Manoj Kumara wrote: >>> >>>> Thanks IsuruH, Shazni. Will merge them. >>>> >>>> >>>> *Manoj Kumara* >>>> Software Engineer >>>> WSO2 Inc. http://wso2.com/ >>>> *lean.enterprise.middleware* >>>> Mobile: +94713448188 >>>> >>>> >>>> On Thu, Mar 13, 2014 at 6:04 PM, Isuru Haththotuwa wrote: >>>> >>>>> Hi Manoj, >>>>> >>>>> Pull request sent [1] to dev repository. >>>>> >>>>> [1]. https://github.com/wso2-dev/carbon4-kernel/pull/6 >>>>> >>>>> >>>>> On Wed, Mar 12, 2014 at 1:34 PM, Shazni Nazeer wrote: >>>>> >>>>>> Hi Manoj, >>>>>> >>>>>> Pull request for the change is sent to wso2-dev/carbon4-kernel repo. >>>>>> Please review and commit. >>>>>> >>>>>> regards, >>>>>> >>>>>> Shazni Nazeer >>>>>> >>>>>> Senior Software Engineer >>>>>> >>>>>> Mob : +94 715 440 607 >>>>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>>>>> Blog : http://shazninazeer.blogspot.com >>>>>> >>>>>> >>>>>> On Wed, Mar 12, 2014 at 11:40 AM, Manoj Kumara wrote: >>>>>> >>>>>>> Hi Geeth, >>>>>>> >>>>>>> Along with committing the code changes on the kernel patches we may >>>>>>> need to consider the changes on configuration files, dbscripts etc. >>>>>>> Please >>>>>>> consider them during your process. >>>>>>> >>>>>>> Thanks, >>>>>>> Manoj >>>>>>> >>>>>>> >>>>>>> *Manoj Kumara* >>>>>>> Software Engineer >>>>>>> WSO2 Inc. http://wso2.com/ >>>>>>> *lean.enterprise.middleware* >>>>>>> Mobile: +94713448188 >>>>>>> >>>>>>> >>>>>>> On Tue, Mar 11, 2014 at 11:46 PM, Geeth Munasinghe >>>>>>> wrote: >>>>>>> >>>>>>>> Hi >>>>>>>> >>>>>>>> I have compared kernel 4.3.0 git repo with kernel 4.2.0 branch in >>>>>>>> svn and merged the changes to of patches to git repo kernel. I have >>>>>>>> made >>>>>>>> pull request to kernel 4.3.0 and axis2 1.6.1-wso2v11-SNAPSHOT in git >>>>>>>> repo. >>>>>>>> >>>>>>>> Please review and commit to kernel and axis2 repos in git hub. >>>>>>>> >>>>>>>> Svn revision used to compare repos is 197947. Any thing committed >>>>>>>> after this commit does not include in this patches. >>>>>>>> >>>>>>>> When committing new patches, Please make sure to commit them to >>>>>>>> both svn and git repo. >>>>>>>&
Re: [Dev] Committing 4.2.0 kernel patches to 4.3.0 in Git repo
Hi, I have merged the pull request sent by Geeth to wso2-dev/master. Thanks Shameera. On Thu, Mar 13, 2014 at 6:21 PM, Manoj Kumara wrote: > Thanks IsuruH, Shazni. Will merge them. > > > *Manoj Kumara* > Software Engineer > WSO2 Inc. http://wso2.com/ > *lean.enterprise.middleware* > Mobile: +94713448188 > > > On Thu, Mar 13, 2014 at 6:04 PM, Isuru Haththotuwa wrote: > >> Hi Manoj, >> >> Pull request sent [1] to dev repository. >> >> [1]. https://github.com/wso2-dev/carbon4-kernel/pull/6 >> >> >> On Wed, Mar 12, 2014 at 1:34 PM, Shazni Nazeer wrote: >> >>> Hi Manoj, >>> >>> Pull request for the change is sent to wso2-dev/carbon4-kernel repo. >>> Please review and commit. >>> >>> regards, >>> >>> Shazni Nazeer >>> >>> Senior Software Engineer >>> >>> Mob : +94 715 440 607 >>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>> Blog : http://shazninazeer.blogspot.com >>> >>> >>> On Wed, Mar 12, 2014 at 11:40 AM, Manoj Kumara wrote: >>> >>>> Hi Geeth, >>>> >>>> Along with committing the code changes on the kernel patches we may >>>> need to consider the changes on configuration files, dbscripts etc. Please >>>> consider them during your process. >>>> >>>> Thanks, >>>> Manoj >>>> >>>> >>>> *Manoj Kumara* >>>> Software Engineer >>>> WSO2 Inc. http://wso2.com/ >>>> *lean.enterprise.middleware* >>>> Mobile: +94713448188 >>>> >>>> >>>> On Tue, Mar 11, 2014 at 11:46 PM, Geeth Munasinghe wrote: >>>> >>>>> Hi >>>>> >>>>> I have compared kernel 4.3.0 git repo with kernel 4.2.0 branch in svn >>>>> and merged the changes to of patches to git repo kernel. I have made pull >>>>> request to kernel 4.3.0 and axis2 1.6.1-wso2v11-SNAPSHOT in git repo. >>>>> >>>>> Please review and commit to kernel and axis2 repos in git hub. >>>>> >>>>> Svn revision used to compare repos is 197947. Any thing committed >>>>> after this commit does not include in this patches. >>>>> >>>>> When committing new patches, Please make sure to commit them to both >>>>> svn and git repo. >>>>> >>>>> Thanks >>>>> Geeth >>>>> >>>>> >>>>> >>>>> *G. K. S. Munasinghe * >>>>> *Software Engineer,* >>>>> *WSO2, Inc. http://wso2.com <http://wso2.com/> * >>>>> *lean.enterprise.middleware.* >>>>> >>>>> email: ge...@wso2.com >>>>> phone:(+94) 777911226 >>>>> >>>> >>>> >>>> ___ >>>> 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 >>> >>> >> >> >> -- >> Thanks and Regards, >> >> Isuru H. >> +94 716 358 048* <http://wso2.com/>* >> >> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?
Hi Azeez/Sameera, It is bit confuse as we have workerNode property and profile property,AFAIK Manger node means carbon runtime with default profile and worker node mean carbon runtime with worker profile. So what if we remove this workerNode property and use -Dprofile=worker instead ( or add this to carbon.xml for the sake of clearness)? . please correct me if i am wrong here. Thanks, Shameera. On Sat, Mar 8, 2014 at 11:01 PM, Afkham Azeez wrote: > > > > On Sat, Mar 8, 2014 at 8:58 AM, Kasun Gajasinghe wrote: > >> >> >> On Friday, March 7, 2014, Afkham Azeez wrote: >> >>> Worker manager separation is not applicable to all products in the >>> platform. Hence, it is wrong to have an irrelevant parameter in products >>> where this concept does not apply. >>> >>> >> Yes, that's fine Azeez. But if we go with this argument, it's wrong to >> have the GhostDeployment tag in carbon.xml which is only applicable to AS. >> And, whole clustering section in axis2.xml doesn't make sense in products >> like mb, bam etc. isn't it? There are lot of cases like this. >> > > Clustering makes sense. If you need to use distributed caching for > example, you need to enable clustering. > > >> >> I guess this is a trade-off that we have to live with with the wide-range >> of products we have!! It's at least better than the alternative we have >> right now where the user has to be mindful about the use of workerNode >> property. Adding this shows the importance of the property. Wdyt? >> > > Just because we may have done certain things in an not so proper way, it > does not give you an excuse to continue to add to that. > > >> >> Thanks, >> KasunG >> >> >>> >>> Azeez >>> >> >>> >>> On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe wrote: >>> >>>> Hi, >>>> >>>> Shall we $subject from Carbon 4.3.0? And then, force the users to >>>> enable workerNode mode by modifying the startup script itself, instead of >>>> passing -DworkerNode=true property via command-line? >>>> >>>> We have noticed that lot of users are passing the said property via the >>>> command-line, but they sometimes miss to set that. That might lead to lot >>>> of issues especially in DepSync. If we set as above, we can lower the human >>>> errors. WDYT? >>>> >>>> Thanks, >>>> KasunG >>>> >>>> -- >>>> *Kasun Gajasinghe* >>>> Software Engineer; >>>> WSO2 Inc.; http://wso2.com >>>> >>>> >>>> , >>>> *email: * >>>> *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) >>>> 678-0813 <%2B94%20%2877%29%20678-0813>* >>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe >>>> >>>> >>>> >>>> *blog: **http://kasunbg.org* <http://kasunbg.org> >>>> >>>> >>>> >>>> *twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> >>>> >>>> >>>> >>>> >>>> ___ >>>> 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* >>> * 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* >>> >> >> >> -- >> *Kasun Gajasinghe* >> Software Engineer; >> WSO2 Inc.; http://wso2.com >> >> >> , >> *email: * >> *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) >> 678-0813 <%2B94%20%2877%29%20678-0813>* >> *linked-in: *http://lk.linkedin.com/in/gajasinghe >> >> >> >> *blog: **http://kasunbg.org* <http://kasunbg.org> >> >> >> >> *twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> >> >> >> >> >> > > > -- > *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* > * 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?
Hi All, If we didn't start the server as worker, "default" is the profile name which will load, if we start as worker then there should be a profile name "woker" directory in the repository/components. Thanks, Shameera. On Mon, Mar 3, 2014 at 11:26 PM, Shameera Rathnayaka wrote: > Hi Miyuru/Kasun, > > > On Mon, Mar 3, 2014 at 10:54 PM, Kasun Gajasinghe wrote: > >> >> On Mon, Mar 3, 2014 at 10:50 PM, Miyuru Wanninayaka wrote: >> >>> How about during startup, log a message telling that >>> Starting as a manager|worker node. >>> >>> So less chance of missing proper configuration and also by just looking >>> at logs anyone can say that log in from worker/manager node. >>> >> > +1 for logging the type, but not the worker or manager, as now we are > supporting multiple profile with carbon kernel , best way is log the > profile name. WDYS? > > @Kasun, > Can you explain how you gonna add this to carbon.xml ? what is the element > name? > > Thanks, > Shameera. > > > >> >>> >> +1. I will do that as well. >> >> >>> >>> On Monday, March 3, 2014, Kasun Gajasinghe wrote: >>> >>>> Hi, >>>> >>>> Shall we $subject from Carbon 4.3.0? And then, force the users to >>>> enable workerNode mode by modifying the startup script itself, instead of >>>> passing -DworkerNode=true property via command-line? >>>> >>>> We have noticed that lot of users are passing the said property via the >>>> command-line, but they sometimes miss to set that. That might lead to lot >>>> of issues especially in DepSync. If we set as above, we can lower the human >>>> errors. WDYT? >>>> >>>> Thanks, >>>> KasunG >>>> >>>> -- >>>> *Kasun Gajasinghe* >>>> Software Engineer; >>>> WSO2 Inc.; http://wso2.com >>>> >>>> >>>> , >>>> *email: * >>>> *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) >>>> 678-0813 <%2B94%20%2877%29%20678-0813>* >>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe >>>> >>>> >>>> >>>> *blog: **http://kasunbg.org* <http://kasunbg.org> >>>> >>>> >>>> >>>> *twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> >>>> >>>> >>>> >>>> >>> >>> -- >>> Sent from my iPad >>> >> >> >> >> -- >> *Kasun Gajasinghe* >> Software Engineer; >> WSO2 Inc.; http://wso2.com >> >> >> , >> *email: * >> *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) >> 678-0813 <%2B94%20%2877%29%20678-0813>* >> *linked-in: *http://lk.linkedin.com/in/gajasinghe >> >> >> >> *blog: **http://kasunbg.org* <http://kasunbg.org> >> >> >> >> *twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> >> >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Software Engineer - WSO2 Inc.* > *email: shameera AT wso2.com , shameera AT apache.org > * > *phone: +9471 922 1454 <%2B9471%20922%201454>* > > *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 > *Twitter : *https://twitter.com/Shameera_R > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?
Hi Miyuru/Kasun, On Mon, Mar 3, 2014 at 10:54 PM, Kasun Gajasinghe wrote: > > On Mon, Mar 3, 2014 at 10:50 PM, Miyuru Wanninayaka wrote: > >> How about during startup, log a message telling that >> Starting as a manager|worker node. >> >> So less chance of missing proper configuration and also by just looking >> at logs anyone can say that log in from worker/manager node. >> > +1 for logging the type, but not the worker or manager, as now we are supporting multiple profile with carbon kernel , best way is log the profile name. WDYS? @Kasun, Can you explain how you gonna add this to carbon.xml ? what is the element name? Thanks, Shameera. > >> > +1. I will do that as well. > > >> >> On Monday, March 3, 2014, Kasun Gajasinghe wrote: >> >>> Hi, >>> >>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable >>> workerNode mode by modifying the startup script itself, instead of passing >>> -DworkerNode=true property via command-line? >>> >>> We have noticed that lot of users are passing the said property via the >>> command-line, but they sometimes miss to set that. That might lead to lot >>> of issues especially in DepSync. If we set as above, we can lower the human >>> errors. WDYT? >>> >>> Thanks, >>> KasunG >>> >>> -- >>> *Kasun Gajasinghe* >>> Software Engineer; >>> WSO2 Inc.; http://wso2.com >>> >>> >>> , >>> *email: * >>> *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) >>> 678-0813 <%2B94%20%2877%29%20678-0813>* >>> *linked-in: *http://lk.linkedin.com/in/gajasinghe >>> >>> >>> >>> *blog: **http://kasunbg.org* <http://kasunbg.org> >>> >>> >>> >>> *twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> >>> >>> >>> >>> >> >> -- >> Sent from my iPad >> > > > > -- > *Kasun Gajasinghe* > Software Engineer; > WSO2 Inc.; http://wso2.com > > > , > *email: * > *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) > 678-0813 <%2B94%20%2877%29%20678-0813>* > *linked-in: *http://lk.linkedin.com/in/gajasinghe > > > > *blog: **http://kasunbg.org* <http://kasunbg.org> > > > > *twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> > > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?
Hi On Mon, Mar 3, 2014 at 10:45 PM, Sagara Gunathunga wrote: > >> Shall we $subject from Carbon 4.3.0? And then, force the users to enable >> workerNode mode by modifying the startup script itself, instead of passing >> -DworkerNode=true property via command-line? >> >> We have noticed that lot of users are passing the said property via the >> command-line, but they sometimes miss to set that. That might lead to lot >> of issues especially in DepSync. If we set as above, we can lower the human >> errors. WDYT? >> > > + 1 IMHO we can support for both options like we support for portOffset. > +1 for having both options, otherwise the one how you addicted to commadline will need to figure it out again :). Thanks, Shameera. > > Thanks ! > >> >> Thanks, >> KasunG >> >> -- >> *Kasun Gajasinghe* >> Software Engineer; >> WSO2 Inc.; http://wso2.com >> >> >> , >> *email: * >> *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) >> 678-0813 <%2B94%20%2877%29%20678-0813>* >> *linked-in: *http://lk.linkedin.com/in/gajasinghe >> >> >> >> *blog: **http://kasunbg.org* <http://kasunbg.org> >> >> >> >> *twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> >> >> >> >> > > > -- > 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Chunk-08 build failure] Tenant Aware LoadBalance Endpoint
SKIPPED >>> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module >>> SKIPPED >>> [INFO] WSO2 Business Activity Monitor SKIPPED >>> [INFO] WSO2 Business Activity Monitor Styles Parent .. SKIPPED >>> [INFO] WSO2 BAM UI styles SKIPPED >>> [INFO] WSO2 BAM UI styles SKIPPED >>> [INFO] WSO2 Stratos - Cloud BAM Login User Interface . SKIPPED >>> [INFO] WSO2 Stratos - Cloud BAM Dashboard User Interface . SKIPPED >>> [INFO] WSO2 Business Activity Monitor Features Parent SKIPPED >>> [INFO] WSO2 BAM - Features Aggregator Module . SKIPPED >>> [INFO] WSO2 BAM - Style Features . SKIPPED >>> [INFO] WSO2 BAM - Style Features . SKIPPED >>> [INFO] WSO2 Carbon - Cloud BAM UI Feature SKIPPED >>> [INFO] WSO2 Carbon - Cloud BAM Dashboard UI Feature .. SKIPPED >>> [INFO] WSO2 BAM - Features Aggregator Module . SKIPPED >>> [INFO] WSO2 Business Activity Monitor P2 Profile Generation SKIPPED >>> [INFO] WSO2 BAM Sample ... SKIPPED >>> [INFO] WSO2 BAM Toolbox .. SKIPPED >>> [INFO] WSO2 BAM Migration SKIPPED >>> [INFO] migration . SKIPPED >>> [INFO] WSO2 Business Activity Monitor - Product .. SKIPPED >>> [INFO] WSO2 BAM Integration .. SKIPPED >>> [INFO] WSO2 BAM - Integration Test ... SKIPPED >>> [INFO] WSO2 Carbon - Releases - products - Aggregator Module SKIPPED >>> [INFO] >>> >>> [INFO] BUILD FAILURE >>> [INFO] >>> ---- >>> [INFO] Total time: 39:48.482s >>> [INFO] Finished at: Mon Mar 03 11:34:27 IST 2014 >>> [INFO] Final Memory: 151M/494M >>> [INFO] >>> >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile >>> (default-compile) on project org.wso2.carbon.lb.endpoint: Compilation >>> failure >>> [ERROR] >>> /home/gihan/wso2/carbon/platform/4.2.0/components/load-balancer/lb-endpoint/org.wso2.carbon.lb.endpoint/4.2.1/src/main/java/org/wso2/carbon/lb/endpoint/group/mgt/GroupMgtAgentBuilder.java:[45,73] >>> cannot find symbol >>> [ERROR] symbol : method getPrimaryHazelcastConfig() >>> [ERROR] location: class >>> org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent >>> [ERROR] -> [Help 1] >>> [ERROR] >>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>> -e switch. >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> [ERROR] >>> [ERROR] For more information about the errors and possible solutions, >>> please read the following articles: >>> [ERROR] [Help 1] >>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >>> [ERROR] >>> [ERROR] After correcting the problems, you can resume the build with the >>> command >>> [ERROR] mvn -rf :org.wso2.carbon.lb.endpoint >>> >>> >>> -- >>> W.G. Gihan Anuruddha >>> Senior Software Engineer | WSO2, Inc. >>> M: +94772272595 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> > > > -- > W.G. Gihan Anuruddha > Senior Software Engineer | WSO2, Inc. > M: +94772272595 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Chunk Releases]
Hi Gayan, As you know when we release a chunk we get a snapshot of the current branch at the moment and move it to tag directory, The possible ways are having chunk 08 under the chunk 07 tag is, someone has created chunk 08 before we release chunk 7 , or there are two active chunks at the moment which is not the correct procedure IMO. Thanks, Shameera. On Fri, Feb 28, 2014 at 10:44 PM, Gayan Gunawardana wrote: > Hi All, > > If we take a released chunk as an example chunk 7 [1], under > turing-chunk07/product-releases/ again we get chunk (01-08). Is there any > special reason to put chunk 08 also without putting only chunk (01-07). > > [1] https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk07 > > -- > Gayan Gunawardana > Software Engineer; WSO2mobile Inc.; http://wso2mobile.com/ > Email: ga...@wso2.com > Mobile: +94 (71) 8020933 > Blog: http://gayanj2ee.blogspot.com/ > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] JAXB for XML parsing in C5.
+1 Thanks, Shameera. On Mon, Feb 24, 2014 at 1:51 PM, Sameera Jayasoma wrote: > Hi Devs, > > Now that we are defining schemas for our XML based configuration files, we > planning to use JAXB for XML parsing. > > Thanks, > Sameera. > -- > 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Using Semantic Versioning as C5 versioning schema.
Hi Dev, How about we adopt to Semantic Versionning Sec http://semver.org/ in C5 releases( major , minor , patch and pre-releases). The author of above spec is Tom Preston-Werner and he is co-founder of GitHub. Thanks, Shameera. -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Isuruwan Herath
Congrat Isuruwan !!! Thanks, Shameera. On Fri, Jan 24, 2014 at 1:38 PM, Chan wrote: > Congratz Isuruwan > > > On Fri, Jan 24, 2014 at 1:31 PM, Gayan Dhanushka wrote: > >> Congratzzz Isuruwan...!!! >> >> Gayan Dhanuska >> Software Engineer >> http://wso2.com/ >> Lean Enterprise Middleware >> >> Mobile >> 071 666 2327 >> >> Office >> Tel : 94 11 214 5345 >> Fax : 94 11 214 5300 >> >> Twitter : https://twitter.com/gayanlggd >> >> >> On Fri, Jan 24, 2014 at 12:48 PM, Malintha Adikari wrote: >> >>> Congratulations Isuruwan ... !!! >>> >>> Regards, >>> Malintha >>> >>> >>> On Fri, Jan 24, 2014 at 12:47 PM, Waruna Jayaweera wrote: >>> >>>> Congratzz Isuruwan >>>> >>>> >>>> On Fri, Jan 24, 2014 at 12:37 PM, Ramith Jayasinghe wrote: >>>> >>>>> Congrats Isuru1! >>>>> >>>>> >>>>> >>>>> On Fri, Jan 24, 2014 at 12:23 PM, Senaka Fernando wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> Its my pleasure to welcome Isuruwan Herath as a WSO2 Committer. >>>>>> Isuruwan has made some great contributions to our platform during the >>>>>> last >>>>>> few months and in recognition of his commitment and contributions he has >>>>>> been voted as a committer. >>>>>> >>>>>> Isuruwan, welcome aboard and keep up the good work. >>>>>> >>>>>> Best Regards, >>>>>> Senaka. >>>>>> >>>>>> -- >>>>>> >>>>>> >>>>>> *[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.org>E-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 >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Ramith Jayasinghe >>>>> Technical Lead >>>>> WSO2 Inc., http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> E: ram...@wso2.com >>>>> P: +94 776715671 >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> >>>> Waruna Lakshitha Jayaweera >>>> Software Engineer >>>> WSO2 Inc; http://wso2.com >>>> phone: +94713255198 >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Malintha Adikari* >>> Software Engineer >>> >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: +94 71 2312958 >>> >>> ___ >>> 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 >> >> > > > -- > Chan (Dulitha Wijewantha) > Software Engineer - Mobile Development > WSO2Mobile > Lean.Enterprise.Mobileware > * ~Email duli...@wso2.com * > * ~Mobile +94712112165 <%2B94712112165>* > > * ~Website dulithawijewantha.com <http://dulithawijewantha.com/> * > > * ~Blog blog.dulithawijewantha.com > <http://dulichan.github.io/chan/>* > * ~Twitter @dulitharw <https://twitter.com/dulitharw>* > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Proper way of patching an OSGi bundle (without restarting the runtime)?
Hi Azeez, Sameera, Senaka, In PoC, I could able to get the bundle dependency closure( Bundle which import packages from updated bundle) of updated bundle and refresh it pragmatically. This will solve wiring issue with hot update. According to the offline dicussion had with Senaka, we need to check this with critical bundle as well and check how it works at runtime. Critical bundle in the sense bundle(like carbon core, registry bundles) which export common packages. However we need to design this hot update and hot deployment models ( patching also goes under this) considering all possibilities that can be happened in OSGi runtime. One assumption I made in this PoC is, it is not required to use older objects in runtime once the package is updated. May be that is not always correct. Thanks, Shameera. On Tue, Jan 21, 2014 at 7:53 AM, Afkham Azeez wrote: > With C5, our dependency on Axis2 will be minimal. > > Azeez > > > On Mon, Jan 20, 2014 at 7:59 PM, Kasun Gajasinghe wrote: > >> Hi Azeez, >> >> I have used the said method of updating a bundle, and it worked for me >> sometimes. But there can be issues when doing this. One issue I have faced >> is that, if a bundle contained an admin service, then that service gets >> re-added during a bundle update. Then, Axis2 started complaining two >> services cannot have the same name. >> >> The said issue won't be there in C5 since we will not be using axis2 >> based admin services. But there can be other issues like this when the >> initialization logic happens inside the service component. IMO it's better >> to do a restart of the server for bundle updates. >> >> Thanks, >> KasunG >> >> >> On Mon, Jan 20, 2014 at 7:42 PM, Afkham Azeez wrote: >> >>> Folks, >>> Our patching strategy has been to make an exact copy of the patched jar, >>> and then during startup, do a bundle replacement. >>> >>> With Carbon 5, our aim is to be able to patch bundles without requiring >>> a full restart of the OSGi runtime. I read somewhere that; >>> >>> >>> update file:patches/ >>> >>> >>> is one way of patching a bundle. >>> >>> So say we are patching org.wso2.carbon.core-4.2.0.jar, we could have a >>> patched jar called org.wso2.carbon.core-4.2.0.p0001.jar and then do; >>> >>> >>> update 23 file:patches/p0001/org.wso2.carbon.core-4.2.0.p0001.jar >>> >>> >>> >>> Will this strategy work? >>> >>> -- >>> *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* >>> * 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 >>> >>> >> > > > -- > *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* > * 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454 <%2B9471%20922%201454>* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Proper way of patching an OSGi bundle (without restarting the runtime)?
Hi Senaka, On Mon, Jan 20, 2014 at 10:26 PM, Senaka Fernando wrote: > Hi all, > > Can we try this out for some well known bundles (covering different types) > and see whether it works or not? > > For example, what happens if you use this approach to patch the > Registry/UM kernel in Carbon 4.2.x? If it works fine, if not, what are the > problems that we need to fix? Then, what happens if you use the same > approach for a UI bundle? and so on... > I implemented a PoC to check this, as i mentioned above we need to restart(refresh) the all bundles which has been wired with old bundle to reflect the bundle update. Then only those bundle get wired with updated bundle. OSGi service update is reflect correctly. On Mon, Jan 20, 2014 at 10:11 PM, Sameera Jayasoma wrote: > Hi Azeez, > > This is the standard way of updating an OSGi bundle using the command line > console. It is possible to do updates using OSGi APIs. > > I guess we need to re-think about our patching strategy. I mean where to > place patches etc. Because to update an OSGi bundle, AFAIK you simply have > to replace the existing bundle with the new bundle in the filesystem and > invoke the update call. > > This is also related to dynamic bundle loading. So I think we need to > design our hot deployment bundle and the patching strategy properly first. > +1 ,I already implemented a PoC to check bundle hot update and hot deployment. Hot deployment works fine but same issue with bundle wiring when we do hot update. I am searching a way to solve this. thanks, Shameera. > >> Thanks, >> Sameera. >> >> >> On Mon, Jan 20, 2014 at 6:12 AM, Afkham Azeez wrote: >> >>> Folks, >>> Our patching strategy has been to make an exact copy of the patched jar, >>> and then during startup, do a bundle replacement. >>> >>> With Carbon 5, our aim is to be able to patch bundles without requiring >>> a full restart of the OSGi runtime. I read somewhere that; >>> >>> >>> update file:patches/ >>> >>> >>> is one way of patching a bundle. >>> >>> So say we are patching org.wso2.carbon.core-4.2.0.jar, we could have a >>> patched jar called org.wso2.carbon.core-4.2.0.p0001.jar and then do; >>> >>> >>> update 23 file:patches/p0001/org.wso2.carbon.core-4.2.0.p0001.jar >>> >>> >>> >>> Will this strategy work? >>> >>> -- >>> *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* >>> * 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 >>> >>> >> >> >> -- >> 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 >> >> > > > -- > > > *[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.org>E-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 > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Proper way of patching an OSGi bundle (without restarting the runtime)?
Hi Azeez, As we know in OSGi world we have tow types of dependencies 1) OSGi services, 2) Bundle wiring . updating a bundle with new bundle we can solve OSGi services dependencies correctly but when we come to bundle wiring we need to find out correct dependency closure and refresh that OSGi bundles. If not the bundle which already wired with old bundle will not get wired with the update osgi bundle. Hence we need to carefully thing about this process. Thanks, Shameera. n Mon, Jan 20, 2014 at 7:42 PM, Afkham Azeez wrote: > Folks, > Our patching strategy has been to make an exact copy of the patched jar, > and then during startup, do a bundle replacement. > > With Carbon 5, our aim is to be able to patch bundles without requiring a > full restart of the OSGi runtime. I read somewhere that; > > update file:patches/ > > > is one way of patching a bundle. > > So say we are patching org.wso2.carbon.core-4.2.0.jar, we could have a > patched jar called org.wso2.carbon.core-4.2.0.p0001.jar and then do; > > update 23 file:patches/p0001/org.wso2.carbon.core-4.2.0.p0001.jar > > > > Will this strategy work? > > -- > *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* > * 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 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Equinox Luna will redesign the equinox framework and core compare to equinox kepler
Hi Eranda, On Tue, Jan 14, 2014 at 10:48 PM, Eranda Sooriyabandara wrote: > Hi Sameera, Shameera, > Sorry for the late reply. > I think it's better we go ahead with Kepler because the issues related to > that are somewhat known and the architecture is somewhat familier > considered to the unreleased version. IMO if we use a library to C5 which > considerably new it's always better to do a quick feasible study with the > comments and feedback of other users. WDYT? > Yes , plan is to go ahead with kepler and keep the momentum going. But we really need to move to Luna once it comes to a stable. IMO with the new C5 plan we can touch this before our fully functional major release. As sameera has mentioned Luna is revamp of kepler. So kepler will go outdate as soon as Luna comes. Better to stick with new releases(new features and bug fixes) and make C5 handy and live long in industry. Thanks, Shameera. > > Thanks > Eranda > > > On Sunday, January 12, 2014, Sameera Jayasoma wrote: > >> Hi Shameera, >> >> Looks like Equinox Luna is a complete revamp of the existing Equinox code >> base to fix the core issues in Equinox. This is just like implementing C5 >> to overcome the architectural issues in C4. >> >> We should consider Luna as the OSGi framework implementation for C5. But >> my only concern is the Luna release schedule[1]. It does not align with the >> C5 plan as of now. The scheduled release date of Luna is June 25th, 2014. >> >> I guess we should continue with Kepler for the moment. As Tom explained >> there will not be any impact to the APIs except for the hooks which we are >> yet to use. Once Luna is in a releasable state we should go for it. >> >> Thanks, >> Sameera. >> >> [1] https://projects.eclipse.org/projects/rt.equinox/releases/4.4.0 >> >> >> On Sun, Jan 12, 2014 at 11:49 AM, Shameera Rathnayaka >> wrote: >> >>> Hi devs, >>> >>> One of our major expectation with new Carbon 5 release is, use new >>> technologies which will last for another 10 years. Hence we are using newly >>> released version of equinox which is equinox kepler. But according to >>> equinox team, with next major release which is equinox Luna , they are >>> going to redesign the framework and core[1]. >>> >>> As we are planing to provide OSGi level multi-tenancy, which can be >>> implement with framework hooks going to be completely changed with >>> suggested framework redesign process. Not only the framework hooks there >>> are few more areas will be change with Luna release. There are few >>> limitations plus drawbacks in existing framework implementation. Tom Watson >>> have explained the background reason for this new redesigning >>> requirement[2]. >>> >>> If we go with kepler and migrate to Luna once it released , we need to >>> put the exact same effort again to adopt to new framework changes. >>> >>> According to me once the Equnox Luna released kepler will be outdated >>> equinox implantations. I would like to know your thoughts on what is the >>> best way to deal with this new equinox famework redesign. >>> >>> [1] http://wiki.eclipse.org/Equinox/Luna_Framework >>> [2] >>> http://www.eclipsecon.org/2013/sites/eclipsecon.org.2013/files/EclipseCon%202013%20-%20Equinox_0.pdf >>> >>> >>> >>> >>> * Thanks, Shameera.Software Engineer - WSO2 Inc.* >>> *email: shameera AT wso2.com , shameera AT apache.org* >>> *phone: +9471 922 1454 <%2B9471%20922%201454>* >>> >>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>> *Twitter : *https://twitter.com/Shameera_R >>> >> >> >> >> -- >> 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 >> > > > -- > > *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/ > > > > > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Equinox Luna will redesign the equinox framework and core compare to equinox kepler
Hi Sameera, +1 for use Equniox Luna as C5 OSGi framework, Yes considering the C5 release schedule with Luna, we can't hold our works that far. BTW I will play little bit with Equinox kepler framework hooks implementation to get an idea on how could we achive osgi level multi tenancy in C5. That will be a good background knowledge when we migrate to Equinox Luna. Thanks, Shameera. On Sun, Jan 12, 2014 at 6:30 PM, Sameera Jayasoma wrote: > Hi Shameera, > > Looks like Equinox Luna is a complete revamp of the existing Equinox code > base to fix the core issues in Equinox. This is just like implementing C5 > to overcome the architectural issues in C4. > > We should consider Luna as the OSGi framework implementation for C5. But > my only concern is the Luna release schedule[1]. It does not align with the > C5 plan as of now. The scheduled release date of Luna is June 25th, 2014. > > I guess we should continue with Kepler for the moment. As Tom explained > there will not be any impact to the APIs except for the hooks which we are > yet to use. Once Luna is in a releasable state we should go for it. > > Thanks, > Sameera. > > [1] https://projects.eclipse.org/projects/rt.equinox/releases/4.4.0 > > > On Sun, Jan 12, 2014 at 11:49 AM, Shameera Rathnayaka > wrote: > >> Hi devs, >> >> One of our major expectation with new Carbon 5 release is, use new >> technologies which will last for another 10 years. Hence we are using newly >> released version of equinox which is equinox kepler. But according to >> equinox team, with next major release which is equinox Luna , they are >> going to redesign the framework and core[1]. >> >> As we are planing to provide OSGi level multi-tenancy, which can be >> implement with framework hooks going to be completely changed with >> suggested framework redesign process. Not only the framework hooks there >> are few more areas will be change with Luna release. There are few >> limitations plus drawbacks in existing framework implementation. Tom Watson >> have explained the background reason for this new redesigning >> requirement[2]. >> >> If we go with kepler and migrate to Luna once it released , we need to >> put the exact same effort again to adopt to new framework changes. >> >> According to me once the Equnox Luna released kepler will be outdated >> equinox implantations. I would like to know your thoughts on what is the >> best way to deal with this new equinox famework redesign. >> >> [1] http://wiki.eclipse.org/Equinox/Luna_Framework >> [2] >> http://www.eclipsecon.org/2013/sites/eclipsecon.org.2013/files/EclipseCon%202013%20-%20Equinox_0.pdf >> >> >> >> >> * Thanks, Shameera.Software Engineer - WSO2 Inc.* >> *email: shameera AT wso2.com , shameera AT apache.org >> * >> *phone: +9471 922 1454 <%2B9471%20922%201454>* >> >> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >> *Twitter : *https://twitter.com/Shameera_R >> > > > > -- > 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
[Dev] Equinox Luna will redesign the equinox framework and core compare to equinox kepler
Hi devs, One of our major expectation with new Carbon 5 release is, use new technologies which will last for another 10 years. Hence we are using newly released version of equinox which is equinox kepler. But according to equinox team, with next major release which is equinox Luna , they are going to redesign the framework and core[1]. As we are planing to provide OSGi level multi-tenancy, which can be implement with framework hooks going to be completely changed with suggested framework redesign process. Not only the framework hooks there are few more areas will be change with Luna release. There are few limitations plus drawbacks in existing framework implementation. Tom Watson have explained the background reason for this new redesigning requirement[2]. If we go with kepler and migrate to Luna once it released , we need to put the exact same effort again to adopt to new framework changes. According to me once the Equnox Luna released kepler will be outdated equinox implantations. I would like to know your thoughts on what is the best way to deal with this new equinox famework redesign. [1] http://wiki.eclipse.org/Equinox/Luna_Framework [2] http://www.eclipsecon.org/2013/sites/eclipsecon.org.2013/files/EclipseCon%202013%20-%20Equinox_0.pdf * Thanks, Shameera.Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454 <%2B9471%20922%201454>* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] contributing to wso2 carbon on github
Hi Chris, Yes of course, Carbon 5 is an open source project and anyone can contribute to it. Thanks, Shameera. *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R On Fri, Jan 10, 2014 at 11:58 PM, chris snow wrote: > Hi Guys, > > Are you accepting outside contributions for carbon on github [1][2]? > > Many thanks, > > Chris > > [1] > http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-C5-Kernel-codebase-is-now-moved-to-GitHub-td89010.html > [2] https://github.com/wso2/carbon-kernel > > ___ > 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] WSO2 Committers += SumedhaS
Congratzzz Sumedha !!! Thanks, Shameera. *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R On Fri, Jan 3, 2014 at 2:20 PM, Malintha Adikari wrote: > Congratulations Sumedha ..!! > > > On Fri, Jan 3, 2014 at 2:13 PM, Nufail Mohamed wrote: > >> Congrats Sumedha! >> >> >> On Fri, Jan 3, 2014 at 2:01 PM, Manoj Kumara wrote: >> >>> Congratulations Sumedha !!! >>> >>> Best Regards.. >>> >>> >>> Manoj Kumara >>> Software Engineer >>> WSO2, Inc.; http://wso2.com >>> >>> Twitter: http://twitter.com/ManKuma >>> Mobile: +94713448188 >>> >>> >>> On Fri, Jan 3, 2014 at 1:58 PM, Amila Maha Arachchi wrote: >>> >>>> >>>> Hi All, >>>> >>>> It's my pleasure to welcome Sumedha Kodithuwakku as a WSO2 Committer. >>>> SumedhaS has been a valuable contributor to the Cloud team during the last >>>> few months. He worked on the Cloud Preview deployment and also developed >>>> the HeartBeat tool for it. In addition to that he has worked on many other >>>> Cloud related development work. In recognition of his contributions, >>>> SumedhaS has been voted as a WSO2 committer. >>>> >>>> SumedhaS, Welcome aboard and keep up the good work! >>>> >>>> Regards, >>>> AmilaM. >>>> -- >>>> *Amila Maharachchi* >>>> Senior Technical Lead >>>> WSO2, Inc.; http://wso2.com >>>> >>>> Blog: http://maharachchi.blogspot.com >>>> Mobile: +94719371446 >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Malintha Adikari* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 71 2312958 > > ___ > 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] WSO2 Committers += Shani
2 Inc. ; http://wso2.com >>>>>>>>>>>> lean . enterprise . middleware >>>>>>>>>>>> >>>>>>>>>>>> phone : +94 715381915 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Dec 16, 2013 at 10:55 AM, Prabath Abeysekera < >>>>>>>>>>>> praba...@wso2.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi All, >>>>>>>>>>>>> >>>>>>>>>>>>> It's my pleasure to welcome Shani Ranasinghe as a WSO2 >>>>>>>>>>>>> Committer. Shani has been a key member of the team since she >>>>>>>>>>>>> joined SS and >>>>>>>>>>>>> has contributed greatly to SS related developments with a great >>>>>>>>>>>>> deal of >>>>>>>>>>>>> enthusiasm over the last couple of months. In recognition of her >>>>>>>>>>>>> contributions, Shani's been voted as a WSO2 comitter. >>>>>>>>>>>>> >>>>>>>>>>>>> Shani, Welcome aboard and keep up the good work! >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> Thanks & regards, >>>>>>>>>>> Nirmal >>>>>>>>>>> >>>>>>>>>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc. >>>>>>>>>>> Mobile: +94715779733 >>>>>>>>>>> Blog: http://nirmalfdo.blogspot.com/ >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ___ >>>>>>>>>>> Dev mailing list >>>>>>>>>>> Dev@wso2.org >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ___ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> >>>>>>>> *Nuwan Silva* >>>>>>>> *Senior Software Engineer - QA* >>>>>>>> Mobile: +94779804543 >>>>>>>> >>>>>>>> WSO2 Inc. >>>>>>>> lean . enterprise . middlewear. >>>>>>>> http://www.wso2.com >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Bhathiya Jayasekara* >>>>>>> *Software Engineer,* >>>>>>> *WSO2 inc., http://wso2.com <http://wso2.com>* >>>>>>> >>>>>>> *Phone: +94715478185 <%2B94715478185>* >>>>>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj >>>>>>> <http://www.linkedin.com/in/bhathiyaj>* >>>>>>> *Twitter: https://twitter.com/bhathiyax >>>>>>> <https://twitter.com/bhathiyax>* >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> Thayalan Sivapaleswararajah >>>>>> Associate Technical Lead - QA >>>>>> Mob: +94(0)777872485 >>>>>> Tel : +94(0)(11)2145345 >>>>>> Fax : +94(0)(11)2145300 >>>>>> Email: thaya...@wso2.com >>>>>> >>>>>> *Disclaimer*: *This communication may contain privileged or other >>>>>> confidential information and is intended exclusively for the addressee/s. >>>>>> If you are not the intended recipient/s, or believe that you may have >>>>>> received this communication in error, please reply to the sender >>>>>> indicating >>>>>> that fact and delete the copy you received and in addition, you should >>>>>> not >>>>>> print, copy, retransmit, disseminate, or otherwise use the information >>>>>> contained in this communication. Internet communications cannot be >>>>>> guaranteed to be timely, secure, error or virus-free. The sender does not >>>>>> accept liability for any errors or omissions.* >>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Thanks >>>>> *, Sajith Ravindra* >>>>> >>>>> Senior Software Engineer >>>>> WSO2 Inc.; http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> mobile: +94 77 2273550 >>>>> <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Best Regards.. >>>> >>>> Chanika Geeganage >>>> Software Engineer >>>> WSO2, Inc.; http://wso2.com >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Ishara Premasada >>> Software Engineer, >>> WSO2 Inc. http://wso2.com/ >>> >>> >>> *Blog : http://isharapremadasa.blogspot.com/ >>> <http://isharapremadasa.blogspot.com/>Twitter : >>> https://twitter.com/ishadil <https://twitter.com/ishadil> Mobile : >>> +94 714445832 <%2B94%20714445832>* >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Regards, >> >> Dunith Dhanushka, >> Senior Software Engineer - BAM, >> WSO2 Inc, >> >> Mobile - +94 71 8615744 >> Blog - dunithd.wordpress.com <http://blog.dunith.com> >> Twitter - @dunithd <http://twitter.com/dunithd> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thanks and Regards, > > Punnadi Gunarathna > Senior Software Engineer, > WSO2, Inc.; http://wso2.com <http://wso2> > Blog: http://hi-my-world.blogspot.com/ > Tel : 94 11 214 5345 > Fax :94 11 2145300 > > > > <http://lalajisureshika.blogspot.com/> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Unacceptable starting delays due to patch verification in different environments
Hi Pradeep, Is this happen continuously or at very first startup? which OS you are experiencing this? Because if there are patches available it will do lot of copy past operation which will cause startup delay in OS like Windows. Currently there is no way to stop patch application process, This process will be triggered if and only if there are new patches available in patches or service pack directories. We can patch this to read system parameter(we can define this in startup script ) and start the process. Thanks, Shameera. On Mon, Oct 14, 2013 at 12:07 PM, Pradeep Fernando wrote: > Hi, > > We are starting carbon servers in CentOS env. It takes around ~5 mins to > complete patch verification process.. > > this is not acceptable, since this affects the deployment prcess at times. > Can we please have a way to disable the functionality if we want. (advanced > user scenario) > > thanks, > --Pradeep > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Start up errors - ConcurrentModificationException from CarbonDeploymentSchedulerTask
Hi Manoj, On Thu, Sep 26, 2013 at 7:49 AM, Manoj Kumara wrote: > Hi, > > With the help of Azeez and Sameera we figure out the root cause for the > problem. This was due to some previous fix by Adding the CApp deployer > separately in the code. > Great this is the real fix i think BTW wonder why we didn't get thhis issue with App Server?, root cause is not the one i explain, in a flow we are calling deployers twice If i am right. Thanks, Shameera. > Will commit the fix shortly. > > Thanks, > > Best Regards.. > > > Manoj Kumara > Software Engineer > WSO2, Inc.; http://wso2.com > > Twitter: http://twitter.com/ManKuma > Mobile: +94713448188 > > > On Thu, Sep 26, 2013 at 2:09 PM, Manoj Kumara wrote: > >> Hi, >> >> The problem here is as Shameera mentioned on [1] the Map used inside the >> concurrentHashMap is not thread safe. >> >> >> private Map> deployerMap = new >> ConcurrentHashMap>(); >> >> I think we can relove this by making this Map thread safe as given on [2]. >> >> [1] https://wso2.org/jira/browse/CARBON-14275 >> [2] >> http://docs.oracle.com/javase/7/docs/api/java/util/Collections.html#synchronizedMap(java.util.Map) >> >> Mean time I will try to patch this and find this get solved. >> >> Thanks, >> Manoj >> >> Best Regards.. >> >> >> Manoj Kumara >> Software Engineer >> WSO2, Inc.; http://wso2.com >> >> Twitter: http://twitter.com/ManKuma >> Mobile: +94713448188 >> >> >> On Thu, Sep 26, 2013 at 10:36 AM, Manoj Kumara wrote: >> >>> Hi Shameera, >>> >>> Thanks for the info. I'll check. >>> >>> Thanks, >>> Manoj >>> >>> Best Regards.. >>> >>> >>> Manoj Kumara >>> Software Engineer >>> WSO2, Inc.; http://wso2.com >>> >>> Twitter: http://twitter.com/ManKuma >>> Mobile: +94713448188 >>> >>> >>> On Wed, Sep 25, 2013 at 7:08 PM, Shameera Rathnayaka >>> wrote: >>> >>>> Hi Ajith, >>>> >>>> Could you able to check whether this is a problem of HumenTask call >>>> twice in execution flow? >>>> >>>> Hi Manoj, >>>> >>>> I have created a JIRA for this issue[1] and added my finding there >>>> please have a look at that. As i explain in the JIRA we could solve it by >>>> making innere map to ConcurrentHashMap.This will produce another issue >>>> becuase we can't put null as a key or value to a Concurrent HashMap and we >>>> do this in above map in such a case where we don't have extension for a >>>> particular deployer (eg: jaggery deployer doesn't has any extension >>>> associate it hence it is registered with null as it extension). >>>> >>>> [1] https://wso2.org/jira/browse/CARBON-14275 >>>> >>>> >>>> Thanks, >>>> Shameera. >>>> >>>> >>>> >>>> On Wed, Sep 25, 2013 at 8:37 AM, Manoj Kumara wrote: >>>> >>>>> Hi, >>>>> >>>>> Tried to reproduce with 21st Sept GReg pack but could not reproduced. >>>>> I will keep on looking to this. >>>>> >>>>> Thanks, >>>>> Manoj >>>>> >>>>> Best Regards.. >>>>> >>>>> >>>>> Manoj Kumara >>>>> Software Engineer >>>>> WSO2, Inc.; http://wso2.com >>>>> >>>>> Twitter: http://twitter.com/ManKuma >>>>> Mobile: +94713448188 >>>>> >>>>> >>>>> On Wed, Sep 25, 2013 at 10:49 AM, Manoj Kumara wrote: >>>>> >>>>>> Hi Sumedha, >>>>>> >>>>>> I'll work on this. >>>>>> >>>>>> Thanks, >>>>>> Manoj >>>>>> >>>>>> Best Regards.. >>>>>> >>>>>> >>>>>> Manoj Kumara >>>>>> Software Engineer >>>>>> WSO2, Inc.; http://wso2.com >>>>>> >>>>>> Twitter: http://twitter.com/ManKuma >>>>>> Mobile: +94713448188 >>>>>> >>>>>> >>>>>> On Wed, Sep 25, 2013 at 10:32 AM, Sumedha Rubasinghe < >>>>>> sume...@wso2.com> wrote: >>>>&g
Re: [Dev] Start up errors - ConcurrentModificationException from CarbonDeploymentSchedulerTask
Hi Ajith,
Could you able to check whether this is a problem of HumenTask call twice
in execution flow?
Hi Manoj,
I have created a JIRA for this issue[1] and added my finding there please
have a look at that. As i explain in the JIRA we could solve it by making
innere map to ConcurrentHashMap.This will produce another issue becuase we
can't put null as a key or value to a Concurrent HashMap and we do this in
above map in such a case where we don't have extension for a particular
deployer (eg: jaggery deployer doesn't has any extension associate it hence
it is registered with null as it extension).
[1] https://wso2.org/jira/browse/CARBON-14275
Thanks,
Shameera.
On Wed, Sep 25, 2013 at 8:37 AM, Manoj Kumara wrote:
> Hi,
>
> Tried to reproduce with 21st Sept GReg pack but could not reproduced. I
> will keep on looking to this.
>
> Thanks,
> Manoj
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter: http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Wed, Sep 25, 2013 at 10:49 AM, Manoj Kumara wrote:
>
>> Hi Sumedha,
>>
>> I'll work on this.
>>
>> Thanks,
>> Manoj
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter: http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>>
>> On Wed, Sep 25, 2013 at 10:32 AM, Sumedha Rubasinghe wrote:
>>
>>> Sameera,
>>> Can we have someone to attend to this pls?
>>>
>>>
>>> On Fri, Sep 13, 2013 at 3:57 PM, Ajith Vitharana wrote:
>>>
>>>> Hi All,
>>>>
>>>> Observed the following error in the latest pack (G-Reg) - chunk02
>>>>
>>>> [2013-09-13 15:52:39,357] ERROR
>>>> {org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} - Error
>>>> while running deployment scheduler..
>>>> java.util.ConcurrentModificationException
>>>> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
>>>> at java.util.HashMap$EntryIterator.next(HashMap.java:834)
>>>> at java.util.HashMap$EntryIterator.next(HashMap.java:832)
>>>> at
>>>> org.apache.axis2.deployment.RepositoryListener.loadOtherDirectories(RepositoryListener.java:270)
>>>> at
>>>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:253)
>>>> 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:65)
>>>> at
>>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:110)
>>>> 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
>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>>>> at
>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>>> at java.lang.Thread.run(Thread.java:662)
>>>> [2013-09-13 15:52:39,614] INFO
>>>> {org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
>>>>
>>>> --
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> /sumedha
>>> m: +94 773017743
>>> b : bit.ly/sumedha
>>>
>>> ___
>>> 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
>
>
--
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com , shameera AT
apache.org
*
*phone: +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Build Failure] [kernal patch0001]
e the full stack trace of the errors, re-run Maven with >>>> the -e switch. >>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>>> [ERROR] >>>> [ERROR] For more information about the errors and possible solutions, >>>> please read the following articles: >>>> [ERROR] [Help 1] >>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >>>> [ERROR] >>>> [ERROR] After correcting the problems, you can resume the build with >>>> the command >>>> [ERROR] mvn -rf :org.wso2.carbon.core >>>> >>>> >>>> Thanks & Regards >>>> Danushka Fernando >>>> Software Engineer >>>> WSO2 inc. http://wso2.com/ >>>> Mobile : +94716332729 >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Build Failure] [kernal patch0001]
-- >>>>>> [INFO] >>>>>> >>>>>> [INFO] Reactor Summary: >>>>>> [INFO] >>>>>> [INFO] Apache Axis2 - Transport - HTTP ... SUCCESS >>>>>> [42.587s] >>>>>> [INFO] axis2.wso2 SUCCESS >>>>>> [33.812s] >>>>>> [INFO] WSO2 Carbon - User Manager Kernel . SUCCESS >>>>>> [40.392s] >>>>>> [INFO] WSO2 Carbon - Registry Kernel . SUCCESS >>>>>> [1:41.534s] >>>>>> [INFO] WSO2 Carbon - Kernel .. FAILURE >>>>>> [15.086s] >>>>>> [INFO] WSO2 Carbon Kernel Kernel Patch 0001 .. SKIPPED >>>>>> [INFO] Distribution-Aggregate SKIPPED >>>>>> [INFO] >>>>>> >>>>>> [INFO] BUILD FAILURE >>>>>> [INFO] >>>>>> >>>>>> [INFO] Total time: 4:07.806s >>>>>> [INFO] Finished at: Tue Sep 17 10:03:22 IST 2013 >>>>>> [INFO] Final Memory: 95M/1312M >>>>>> [INFO] >>>>>> >>>>>> [ERROR] Failed to execute goal >>>>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile >>>>>> (default-compile) on project org.wso2.carbon.core: Compilation failure >>>>>> [ERROR] >>>>>> /home/wdfdo1986/Source_Code/kernel/4.2.0/patches/patch0001/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/clustering/hazelcast/HazelcastDistributedMapProvider.java:[48,4] >>>>>> method does not override or implement a method from a supertype >>>>>> [ERROR] -> [Help 1] >>>>>> [ERROR] >>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with >>>>>> the -e switch. >>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>>>>> [ERROR] >>>>>> [ERROR] For more information about the errors and possible solutions, >>>>>> please read the following articles: >>>>>> [ERROR] [Help 1] >>>>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >>>>>> [ERROR] >>>>>> [ERROR] After correcting the problems, you can resume the build with >>>>>> the command >>>>>> [ERROR] mvn -rf :org.wso2.carbon.core >>>>>> >>>>>> >>>>>> Thanks & Regards >>>>>> Danushka Fernando >>>>>> Software Engineer >>>>>> WSO2 inc. http://wso2.com/ >>>>>> Mobile : +94716332729 >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB 4.8.0 Milestone 2 - Worker Profile is not working
Hi isuru,
To start the server as worker node you must have profile call worker in
repository/components/ . please check it.
Thanks,
Shameera
Hi Vanji,
On Tue, Sep 17, 2013 at 4:46 PM, Vanjikumaran Sivajothy wrote:
> Hi Issuru,
> It seems profile is not configured for DworkerNode, Nevertheless you can
> use the ESB with out the WorkNode while you working on ELB
>
Yes, I can proceed with my testing with out the worker profile for now.
Anyway, I didn't see a JIRA for this issue. Shall I create one?
I hope you guys will fix the worker profile for next milestone release.
>
> Best regards,
> Vanji
>
>
> On Tue, Sep 17, 2013 at 3:41 PM, Isuru Perera wrote:
>
>> I get following error when I run the server as "./wso2server.sh
>> -DworkerNode=true"
>>
>> JAVA_HOME environment variable is set to /usr/lib/jvm/jdk1.6.0_45
>> CARBON_HOME environment variable is set to
>> /home/isuru/test/elb-release/esb/wso2esb-4.8.0-worker
>> [2013-09-17 15:35:14,559] FATAL {org.wso2.carbon.server.Main} - OSGi
>> runtime worker profile not found
>> java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
>> at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)
>> Caused by: java.lang.RuntimeException: worker profile not found
>> at org.wso2.carbon.server.Main.main(Main.java:86)
>> ... 6 more
>>
>> Please check.
>>
>> Thanks!
>>
>> --
>> 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
>>
>>
>
>
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)777219209**
> *[image: Facebook] [image:
> Twitter] [image:
> LinkedIn]
> [image:
> Blogger]
>
--
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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Patch for kernel. - chunk02 release.
Hi Ajith, We are working on it, BTW in you case, don't need to create 4.2.1 version of org.wso2.carbon.core only released *platform *components need that version increment. Your change will go with patch0001. Thanks, Shameera. On Fri, Sep 13, 2013 at 11:22 AM, Ajith Vitharana wrote: > Hi Carbon team, > > Please commit the kernel patches. Or grant commits rights :) > > Thanks > > > > On Thu, Sep 12, 2013 at 2:03 PM, Ajith Vitharana wrote: > >> Hi Shameera, >> >> Please apply the patch [1] for chunk02 release. >> >> [1]https://wso2.org/jira/browse/REGISTRY-1941 >> >> Thanks >> Ajith >> >> -- >> Ajith Vitharana. >> WSO2 Inc. - http://wso2.org >> Email : aji...@wso2.com >> Mobile : +94772217350 >> >> > > > -- > Ajith Vitharana. > WSO2 Inc. - http://wso2.org > Email : aji...@wso2.com > Mobile : +94772217350 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failure in 4.2.0 kernel branch {was : Build Failure Trunk}
Hi Ranga/Janaka, There is a relative path issue and we are trying to solve it. BTW we are encouraging people to not to build kernel 4.2.0 branch and platform/products-releases/chunk-01 ( actually you don't need to build those) as we have deployed all released jars to nexus repo. And also please start 4.2.0 branch chunk-02 or higher with clean repo unless you will face unexpected issues in build time as well as runtime. Thanks, Shameera. On Wed, Sep 11, 2013 at 2:51 PM, Ranga Siriwardena wrote: > Hi, > > I also getting this error. 4.2.0 Kernel build even does not starting. > > Thank You. > Ranga. > > > On Wed, Sep 11, 2013 at 1:45 PM, Janaka Ranabahu wrote: > >> The previous subject was misleading. Hence sending with the correct >> subject. Please note that Im getting the following error while building >> 4.2.0 kernel. >> >> janaka@janaka-T530:~/work/wso2/carbon/kernel/branches/4.2.0$ mvn clean >> install >> [INFO] Scanning for projects... >> [ERROR] The build could not read 1 project -> [Help 1] >> [ERROR] >> [ERROR] The project org.wso2.carbon:SecVerifier:4.2.0 >> (/home/janaka/work/wso2/carbon/kernel/branches/4.2.0/distribution/integration/security-verifier/pom.xml) >> has 1 error >> [ERROR] Non-resolvable parent POM: Failure to find >> org.wso2.carbon:carbon-products:pom:4.2.0 in >> http://repo.maven.apache.org/maven2 was cached in the local repository, >> resolution will not be reattempted until the update interval of central has >> elapsed or updates are forced and 'parent.relativePath' points at wrong >> local POM @ line 22, column 13 -> [Help 2] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the >> -e switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, >> please read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException >> [ERROR] [Help 2] >> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException >> janaka@janaka-T530:~/work/wso2/carbon/kernel/branches/4.2.0$ >> >> >> Thanks, >> Janaka >> >> -- Forwarded message -- >> From: Janaka Ranabahu >> Date: Wed, Sep 11, 2013 at 1:41 PM >> Subject: Re: [Dev] Build Failure Trunk >> To: Danushka Fernando , Shameera Rathnayaka < >> shame...@wso2.com>, Sameera Jayasoma , Prabath >> Siriwardana >> Cc: WSO2 Developers' List >> >> >> Hi Shameera, >> >> Please note that I'm getting the same build error on a clean repo. Please >> fix this. >> >> Thanks, >> Janaka >> >> >> On Tue, Sep 10, 2013 at 8:30 PM, Danushka Fernando wrote: >> >>> Hi I am getting this build failure at kernal >>> >>> wdfdo1986@wdfdo1986-ThinkPad-T530:~/Source_Code/kernel/4.2.0$ >>> oncleannotest >>> [INFO] Scanning for projects... >>> [ERROR] The build could not read 1 project -> [Help 1] >>> [ERROR] >>> [ERROR] The project org.wso2.carbon:SecVerifier:4.2.0 >>> (/home/wdfdo1986/Source_Code/kernel/4.2.0/distribution/integration/security-verifier/pom.xml) >>> has 1 error >>> [ERROR] Non-resolvable parent POM: Failure to find >>> org.wso2.carbon:carbon-products:pom:4.2.0 in >>> http://repo.maven.apache.org/maven2 was cached in the local repository, >>> resolution will not be reattempted until the update interval of central has >>> elapsed or updates are forced and 'parent.relativePath' points at wrong >>> local POM @ line 22, column 13 -> [Help 2] >>> [ERROR] >>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>> -e switch. >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> [ERROR] >>> [ERROR] For more information about the errors and possible solutions, >>> please read the following articles: >>> [ERROR] [Help 1] >>> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException >>> [ERROR] [Help 2] >>> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException >>> >>> I edited the security-verifier pom's parent details as follows to make >>> the build work >>> >>> org.wso2.carbon >>> integration >>> 4.2.0 >>> ../pom.xml >>> >>> >>> >>> Th
Re: [Dev] Build error kernal branch
Hi Danushka, This is fixed now please take a svn up and try. Thanks, Shameera. On Wed, Sep 11, 2013 at 2:19 AM, Lasantha Fernando wrote: > Hi Danushka, > > This seems to be due to the version tag being repeated twice in > patches/patch0001/org.wso2.carbon.registry.core/pom.xml - Line 29 and Line > 34. > > You can proceed with the build by deleting one of the duplicate tags (as a > temp workaround). > > HTH, > Lasantha > > > On 10 September 2013 21:03, Danushka Fernando wrote: > >> Hi I am getting following build error when I am trying to build kernel >> patch0001 >> [ERROR] The project >> >> (/home/wdfdo1986/Source_Code/kernel/4.2.0/patches/patch0001/org.wso2.carbon.registry.core/pom.xml) >> has 1 error >> [ERROR] Non-parseable POM >> /home/wdfdo1986/Source_Code/kernel/4.2.0/patches/patch0001/org.wso2.carbon.registry.core/pom.xml: >> Duplicated tag: 'version' (position: START_TAG seen ...\n >> ... @34:14) @ line 34, column 14 -> [Help 2] >> >> Thanks & Regards >> Danushka Fernando >> Software Engineer >> WSO2 inc. http://wso2.com/ >> Mobile : +94716332729 >> >> ___ >> 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 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Kernel trunk build failure
Hi Bhathiya, We have remove that 1.5.2-SNAPSHOT and renamed it to 1.5.4-SNAPSHOT , seems it is not reflected to above components, anyway all product teams suppose to work on 4.2.0 branch not in trunk. Is there any specific reason you are working on trunk ? Thanks, Shameera. On Tue, Sep 10, 2013 at 3:38 PM, Bhathiya Jayasekara wrote: > Same issue occurs with Student-manager sample too. > > > On Tue, Sep 10, 2013 at 3:03 PM, Bhathiya Jayasekara wrote: > >> *Seems like a version issue.* >> >> [INFO] Scanning for projects... >> [INFO] >> >> [INFO] >> >> [INFO] Building WSO2 Carbon - Carbon Common Feature 4.2.0-SNAPSHOT >> [INFO] >> >> [WARNING] The POM for org.wso2.maven:carbon-p2-plugin:jar:1.5.2-SNAPSHOT >> is missing, no dependency information available >> [INFO] >> >> [INFO] BUILD FAILURE >> [INFO] >> >> [INFO] Total time: 0.285s >> [INFO] Finished at: Tue Sep 10 02:30:55 PDT 2013 >> [INFO] Final Memory: 3M/119M >> [INFO] >> >> [ERROR] Plugin org.wso2.maven:carbon-p2-plugin:1.5.2-SNAPSHOT or one of >> its dependencies could not be resolved: Failed to read artifact descriptor >> for org.wso2.maven:carbon-p2-plugin:jar:1.5.2-SNAPSHOT: Failure to find >> org.wso2.maven:carbon-p2-plugin:pom:1.5.2-SNAPSHOT in >> http://dist.wso2.org/maven2 was cached in the local repository, >> resolution will not be reattempted until the update interval of >> wso2-maven2-repository-1 has elapsed or updates are forced -> [Help 1] >> >> -- >> *Bhathiya Jayasekara* >> *Software Engineer,* >> *WSO2 inc., http://wso2.com* >> * >> * >> *Phone: +94715478185* >> *LinkedIn: http://www.linkedin.com/in/bhathiyaj* >> *Twitter: https://twitter.com/bhathiyax* >> > > > > -- > *Bhathiya Jayasekara* > *Software Engineer,* > *WSO2 inc., http://wso2.com* > * > * > *Phone: +94715478185* > *LinkedIn: http://www.linkedin.com/in/bhathiyaj* > *Twitter: https://twitter.com/bhathiyax* > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Could not find artifact org.wso2.carbon:org.wso2.carbon.identity.authenticator.krb5.stub:jar:4.2.0 in central
Hi Shelan, The jar is available in repo see, http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.identity.authenticator.krb5.stub/4.2.0/.This may be network issue. Please try continuing the build. Thanks, Shameera. On Mon, Sep 9, 2013 at 5:35 PM, Shelan Perera wrote: > > [INFO] Registry TestNG Test Samples .. SKIPPED > [INFO] Backward association handler Sample ... SKIPPED > [INFO] Registry TestNG Test Module ... SKIPPED > [INFO] Registry Resources TestNG Test Module . SKIPPED > [INFO] Registry Metadata TestNG Test Module .. SKIPPED > [INFO] Registry Extensibility TestNG Test Module . SKIPPED > [INFO] Registry JIRA TestNG Test Module .. SKIPPED > [INFO] Registry Lifecycle TestNG Test Module . SKIPPED > [INFO] Registry Search and Versioning TestNG Test Module . SKIPPED > [INFO] Registry Permissions TestNG Test Module ... SKIPPED > [INFO] Registry Governance API TestNG Test Module SKIPPED > [INFO] Registry TestNG Test Module ... SKIPPED > [INFO] Registry UI Test Module ... SKIPPED > [INFO] Integration Test Reporting SKIPPED > [INFO] WSO2 CEP - Parent . SKIPPED > [INFO] WSO2 CEP - Style Parent ... SKIPPED > [INFO] WSO2 CEP - Styles . SKIPPED > [INFO] WSO2 Stratos CEP - Styles . SKIPPED > [INFO] WSO2 CEP - Samples Parent . SKIPPED > [INFO] WSO2 CEP - Samples Producers .. SKIPPED > [INFO] WSO2 CEP - Producer - Stock Quote Client .. SKIPPED > [INFO] WSO2 CEP - Producer - Service Stats Clients ... SKIPPED > [INFO] WSO2 CEP - Producer - Activity Monitoring Client .. SKIPPED > [INFO] WSO2 CEP - Producer - HTTPS Logs Clients .. SKIPPED > [INFO] WSO2 CEP - Producer - KPI Definition Clients .. SKIPPED > [INFO] WSO2 CEP - Producer - Mediation Stats Clients . SKIPPED > [INFO] performance-test-client ... SKIPPED > [INFO] WSO2 CEP - Producer - Purchase Order Client ... SKIPPED > [INFO] pizza-shop-client . SKIPPED > [INFO] WSO2 CEP - Producer - Twitter Feed Client . SKIPPED > [INFO] WSO2 CEP - Sample Consumers ... SKIPPED > [INFO] WSO2 CEP - Consumer - WSO2 Event Server ... SKIPPED > [INFO] WSO2 CEP - Consumer - JMS Consumer SKIPPED > [INFO] WSO2 CEP - Consumer - Log Service . SKIPPED > [INFO] WSO2 CEP - Feature Parent . SKIPPED > [INFO] WSO2 CEP - Features ... SKIPPED > [INFO] WSO2 CEP - Styles Features SKIPPED > [INFO] WSO2 Stratos CEP - Features ... SKIPPED > [INFO] WSO2 Stratos CEP - Styles Features SKIPPED > [INFO] WSO2 Stratos CEP - Dashboard UI ... SKIPPED > [INFO] WSO2 Stratos CEP - Dashboard UI Features .. SKIPPED > [INFO] WSO2 CEP - P2 Profile Generation .. SKIPPED > [INFO] WSO2 CEP - Distribution ... SKIPPED > [INFO] WSO2 CEP - Integration Tests .. SKIPPED > [INFO] WSO2 CEP - Integration Test Module SKIPPED > [INFO] WSO2 Carbon - Releases - products - Aggregator Module SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 3:46.081s > [INFO] Finished at: Mon Sep 09 17:27:38 IST 2013 > [INFO] Final Memory: 584M/1290M > [INFO] > > [ERROR] Failed to execute goal on project > org.wso2.carbon.identity.authenticator.krb5.ui: Could not resolve > dependencies for project > org.wso2.carbon:org.wso2.carbon.identity.authenticator.krb5.ui:bundle:4.2.0: > Could not find artifact > org.wso2.carbon:org.wso2.carbon.identity.authenticator.krb5.stub:jar:4.2.0 > in central (http://repo.maven.apache.org/maven2) -> [Help 1] > [ERROR] > > -- > *Shelan Perera* > > Senior Software Engineer > ** > Integration Technology Group > *WSO2, Inc. : wso2.com* > lean.enterprise.middleware. > > *Blog* : blog.shelan.org > *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 > *Twitter* :https://twitter.com/#!/shelan > > *Mobile* : +94 772 604 402 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 92
Re: [Dev] Corrupted artifact in nexus repo.
Hi Shelan, The issue is md5 file of pom.xml is not in the repo. Even we have configured to checksumPolicy of nexus repo to ignore it will not get reflect to above level, Sumedha have fixed this for temporary will check the real fix. Thanks, Shameera. On Mon, Sep 9, 2013 at 4:46 PM, Shelan Perera wrote: > Hi Shameera, > > Appreciate a quick look into this as chunk2 releases will be blocked > without a proper build. > > Thanks > > > On Mon, Sep 9, 2013 at 4:39 PM, Shelan Perera wrote: > >> >> Hi, >> >> Looks like a corrupted artifact please have a look. >> >> [ERROR] Failed to execute goal on project >> org.wso2.carbon.throttling.manager: Could not resolve dependencies for >> project org.wso2.carbon:org.wso2.carbon.throttling.manager:bundle:2.2.0: >> Failed to collect dependencies for >> [org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v10 (compile), >> log4j:log4j:jar:1.2.13 (compile), >> org.wso2.carbon:org.wso2.carbon.registry.core:jar:4.2.0 (compile), >> org.wso2.carbon:org.wso2.carbon.utils:jar:4.2.0 (compile), >> commons-logging:commons-logging:jar:1.1 (compile), >> org.wso2.carbon:org.wso2.carbon.registry.extensions:jar:4.2.0 (compile), >> org.wso2.carbon:org.wso2.carbon.registry.resource:jar:4.2.0 (compile), >> org.wso2.carbon:org.wso2.carbon.stratos.common:jar:2.2.0 (compile), >> org.wso2.carbon:org.wso2.carbon.usage:jar:2.2.0 (compile), >> org.wso2.carbon:org.wso2.carbon.billing.mgt:jar:2.2.0 (compile), >> org.wso2.carbon:org.wso2.carbon.rule.kernel:jar:4.2.0 (compile), >> org.wso2.carbon:org.wso2.carbon.rule.common:jar:4.2.0 (compile), >> org.wso2.carbon:org.wso2.carbon.rule.backend:jar:4.2.0 (compile), >> org.apache.synapse:synapse-tasks:jar:2.1.1-wso2v8 (compile), >> org.apache.synapse:synapse-commons:jar:2.1.1-wso2v8 (compile), >> org.wso2.carbon:org.wso2.carbon.throttling.agent:jar:2.2.0 (compile), >> org.wso2.carbon:org.wso2.carbon.usage.agent:jar:2.2.0 (compile)]: Failed to >> read artifact descriptor for >> org.eclipse.equinox:org.eclipse.equinox.http.servlet:jar:1.0.200.v20090520-1800: >> Could not transfer artifact >> org.eclipse.equinox:org.eclipse.equinox.http.servlet:pom:1.0.200.v20090520-1800 >> from/to wso2-nexus ( >> http://maven.wso2.org/nexus/content/groups/wso2-public/): Checksum >> validation failed, expected but is >> 62336f94161432092b380de7665aa6c0af3ac893 -> [Help 1] >> >> >> -- >> *Shelan Perera* >> >> Senior Software Engineer >> ** >> Integration Technology Group >> *WSO2, Inc. : wso2.com* >> lean.enterprise.middleware. >> >> *Blog* : blog.shelan.org >> *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 >> *Twitter* :https://twitter.com/#!/shelan >> >> *Mobile* : +94 772 604 402 >> >> > > > -- > *Shelan Perera* > > Senior Software Engineer > ** > Integration Technology Group > *WSO2, Inc. : wso2.com* > lean.enterprise.middleware. > > *Blog* : blog.shelan.org > *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 > *Twitter* :https://twitter.com/#!/shelan > > *Mobile* : +94 772 604 402 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIMANAGER-1494 requires a patch to kernel
Hi Sumedha, As we are following the same kernel patch process which we uses for 4.1.0, in 4.2.0 too. Therefore I have created patch0001[1] kernel patch and committed the diff provided by Nuwan Dias. [1] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0001/ Thanks, Shameera. On Fri, Sep 6, 2013 at 8:38 PM, Sumedha Rubasinghe wrote: > Kernel team, > Can we have following patch for chunk2 release please? > This is a blocker for Am 1.5.0 release. > > https://wso2.org/jira/browse/APIMANAGER-1494 > > > -- > /sumedha > b : bit.ly/sumedha > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Is the next API Manager release going to make use of the Carbon multi-profile support?
Hi Azeez, Can't we use p2 touchpoints to copy the relevant jaggery apps to deployment folder when publisher and store features are being installed? and remove when the feature is being uninstalled. Thanks, Shameera. On Fri, Sep 6, 2013 at 7:23 PM, Sumedha Rubasinghe wrote: > On Fri, Sep 6, 2013 at 3:54 PM, Afkham Azeez wrote: > >> But this means, when you are running publisher profile, you can access >> store UI, and vice-versa, which is not good. We need a solution for that. >> > > yeah.. something like linking profile with execution environment. > eg: on this particular case, in publisher profile, we should not allow > /store to be accessible. > > > >> >> On Fri, Sep 6, 2013 at 3:51 PM, Amila De Silva wrote: >> >>> For now, we can't remove the apps, since they are copied to the >>> distribution when creating the pack. In each of the profiles the jaggery >>> apps will be present, but they can only be accessed if the >>> org.wso2.carbon.apimgt.hostobjects bundle is present. And only publisher >>> and store profiles would have this bundle. >>> >>> >>> On Fri, Sep 6, 2013 at 3:36 PM, Afkham Azeez wrote: >>> >>>> So when you run with publisher profile, for example, how would the >>>> store app be removed? >>>> >>>> >>>> On Fri, Sep 6, 2013 at 3:34 PM, Amila De Silva wrote: >>>> >>>>> Hi Azeez, >>>>> Yes. We are already testing a distributed setup using the created >>>>> profiles. >>>>> >>>>> AmilaD >>>>> >>>>> >>>>> On Fri, Sep 6, 2013 at 3:09 PM, Afkham Azeez wrote: >>>>> >>>>>> $subject, just for my information >>>>>> >>>>>> -- >>>>>> *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* * 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* >>>>>> * >>>>>> * >>>>>> *Lean . Enterprise . Middleware* >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Amila De Silva* >>>>> * >>>>> * >>>>> *Software Engineer* >>>>> WSO2 Inc.* >>>>> * >>>>> mobile :(+94) 775119302 >>>>> >>>>> >>>> >>>> >>>> -- >>>> *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* * 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* >>>> * >>>> * >>>> *Lean . Enterprise . Middleware* >>>> >>> >>> >>> >>> -- >>> *Amila De Silva* >>> * >>> * >>> *Software Engineer* >>> WSO2 Inc.* >>> * >>> mobile :(+94) 775119302 >>> >>> >> >> >> -- >> *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* * 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* >> * >> * >> *Lean . Enterprise . Middleware* >> > > > > -- > /sumedha > b : bit.ly/sumedha > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Ayashkantha
Congratzzz Ayashkantha !!! On Thu, Sep 5, 2013 at 2:41 PM, Pulasthi Supun wrote: > Congrats Ayashkantha > > > On Thu, Sep 5, 2013 at 2:38 PM, Manula Chathurika Thantriwatte < > manu...@wso2.com> wrote: > >> Congratulations !!! >> >> >> On Thu, Sep 5, 2013 at 2:36 PM, Dhanuka Ranasinghe wrote: >> >>> Congratz... >>> >>> *Dhanuka Ranasinghe* >>> >>> Senior Software Engineer >>> WSO2 Inc. ; http://wso2.com >>> >>> lean . enterprise . middleware >>> >>> phone : +94 715381915 >>> >>> >>> On Thu, Sep 5, 2013 at 2:27 PM, Darshana Gunawardana >>> wrote: >>> >>>> Congratulations...!!! >>>> >>>> >>>> On Thu, Sep 5, 2013 at 2:25 PM, Dunith Dhanushka wrote: >>>> >>>>> Congrats Ayashkantha! >>>>> >>>>> >>>>> On Thu, Sep 5, 2013 at 2:13 PM, Anjana Fernando wrote: >>>>> >>>>>> Hi everyone, >>>>>> >>>>>> It's my pleasure to announce Ayashkantha as a WSO2 commiter. >>>>>> Ayashkantha has done many contributions to the BAM product, and I'm sure >>>>>> he >>>>>> will continue to be a valuable member to the team. Ayashkantha, welcome >>>>>> aboard and keep up the good work! .. >>>>>> >>>>>> >>>>>> Cheers, >>>>>> Anjana. >>>>>> >>>>>> -- >>>>>> *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 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> >>>>> Dunith Dhanushka, >>>>> Senior Software Engineer - BAM, >>>>> WSO2 Inc, >>>>> >>>>> Mobile - +94 71 8615744 >>>>> Blog - dunithd.wordpress.com <http://blog.dunith.com> >>>>> Twitter - @dunithd <http://twitter.com/dunithd> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> >>>> * >>>> Darshana Gunawardana >>>> *Software Engineer >>>> WSO2 Inc.; http://wso2.com* >>>> E-mail: darsh...@wso2.com >>>> **Mobile: +94718566859 >>>> *Lean . Enterprise . Middleware >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Regards, >> Manula Chathurika Thantriwatte >> Software Engineer >> WSO2 Inc. : http://wso2.com >> lean . enterprise . middleware >> >> email : manu...@wso2.com / man...@apache.org >> phone : +94 772492511 >> blog : http://manulachathurika.blogspot.com/ >> >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > -- > Pulasthi Supun > Software Engineer; WSO2 Inc.; http://wso2.com, > Email: pulas...@wso2.com > Mobile: +94 (71) 9258281 > Blog : http://pulasthisupun.blogspot.com/ > Git hub profile: https://github.com/pulasthi > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Kernel build failure
Hi, This has been fixed by Sameera, Please take a svn up. Thanks, Shameera. On Mon, Sep 2, 2013 at 12:51 PM, Amila Maha Arachchi wrote: > I too got this. Seems like jettison is removed from dependencies, but > still in the dependencies/pom,xml. > > > On Mon, Sep 2, 2013 at 12:49 PM, Sriskandarajah Suhothayan > wrote: > >> >> [INFO] Scanning for projects... >> [ERROR] The build could not read 1 project -> [Help 1] >> [ERROR] >> [ERROR] The project org.wso2.carbon:carbon-kernel-dependents:4.2.0 >> (/data/wso2/src/4.2.0/kernel/dependencies/pom.xml) has 1 error >> [ERROR] Child module >> /data/wso2/src/4.2.0/kernel/dependencies/jettison/jettison-1.3.4/pom.xml of >> /data/wso2/src/4.2.0/kernel/dependencies/pom.xml does not exist >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the >> -e switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, >> please read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException >> >> >> >> -- >> *S. Suhothayan >> * >> Associate Technical Lead, >> *WSO2 Inc. *http://wso2.com * >> <http://wso2.com/>* >> lean . enterprise . middleware >> >> *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ >> twitter: http://twitter.com/suhothayan | linked-in: >> http://lk.linkedin.com/in/suhothayan* >> * >> * >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Amila Maharachchi* > Senior Technical Lead > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] appserver cluster config
T
he one think i hadn't check is restarting ELB instance, Once i restart ELB
it seems Manager and worker doesn't get aware of it. ELB shows only one
member(ELB) in cluster. But manager and worker shows two members in their
logs. After restarting the instance cluster works.
Thanks,
Shameera.
On Sat, Aug 31, 2013 at 12:27 PM, Shameera Rathnayaka wrote:
> Hi,
>
> I have set up a cluster with 1 ELB + 2 AS manager nodes and 1 AS Worker
> node . It is running without any issues. I have down and up Managers and
> worker time to time it worked fine. I used RC5 packs for above set up ,
> Will check the same set up with RC6 packs too.
>
> Thanks,
> Shameera.
>
>
> On Sat, Aug 31, 2013 at 11:16 AM, Evanthika Amarasiri
> wrote:
>
>> We are trying this out locally now. Will update the thread with the
>> status in a while.
>>
>> Evanthika Amarasiri
>> Senior Technical Lead - Quality Assurance
>> Mobile: +94773125935
>> *
>> *
>> wso2.com Lean Enterprise Middleware
>>
>>
>> On Sat, Aug 31, 2013 at 1:35 AM, Afkham Azeez wrote:
>>
>>> I have tested the RC5 pack ELB + AS with clustering. ELB is the WKA
>>> member. After the ELB is restarted, AS gets added to the cluster. The
>>> relevant config files are attached.
>>>
>>> Let's test the same setup by running this on two machines. Simply change
>>> the relevant IP addresses (localMemberHost & well-known member IP)
>>>
>>>
>>> On Sat, Aug 31, 2013 at 1:04 AM, Sameera Jayasoma wrote:
>>>
>>>> appserver {
>>>> # multiple hosts should be separated by a comma.
>>>> # hosts appserver.cloud-test.wso2.com,
>>>> as.cloud-test.wso2.com;
>>>> #when using url mapping, url_suffix will be required. hosts should be
>>>> read first before url_suffix,
>>>> #in order to construct the host vs url-suffix pairs, hence keep the
>>>> logical order to of hosts and url_suffix as it is.
>>>>
>>>> #url_suffix as.wso2.com,appserver.wso2.com;
>>>> domains {
>>>> wso2.as.domain {
>>>> # for more info on Tenant aware load balancing please
>>>> refer to
>>>> #
>>>> http://sanjeewamalalgoda.blogspot.com/2012/05/tenant-aware-load-balancer.html
>>>> tenant_range *;
>>>> group_mgt_port 5000;
>>>> mgt {
>>>> hosts management.appserver.cloud-test.wso2.com;
>>>> }
>>>> worker {
>>>> hosts appserver.cloud-test.wso2.com;
>>>> }
>>>> }
>>>> }
>>>> }
>>>>
>>>> --
>>>> 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
>>>>
>>>
>>>
>>>
>>> --
>>> *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* * 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*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com , shameera AT
> apache.org
> *
> *phone: +9471 922 1454*
> *
> *
> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>
--
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com , shameera AT
apache.org
*
*phone: +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] appserver cluster config
Hi,
I have set up a cluster with 1 ELB + 2 AS manager nodes and 1 AS Worker
node . It is running without any issues. I have down and up Managers and
worker time to time it worked fine. I used RC5 packs for above set up ,
Will check the same set up with RC6 packs too.
Thanks,
Shameera.
On Sat, Aug 31, 2013 at 11:16 AM, Evanthika Amarasiri wrote:
> We are trying this out locally now. Will update the thread with the status
> in a while.
>
> Evanthika Amarasiri
> Senior Technical Lead - Quality Assurance
> Mobile: +94773125935
> *
> *
> wso2.com Lean Enterprise Middleware
>
>
> On Sat, Aug 31, 2013 at 1:35 AM, Afkham Azeez wrote:
>
>> I have tested the RC5 pack ELB + AS with clustering. ELB is the WKA
>> member. After the ELB is restarted, AS gets added to the cluster. The
>> relevant config files are attached.
>>
>> Let's test the same setup by running this on two machines. Simply change
>> the relevant IP addresses (localMemberHost & well-known member IP)
>>
>>
>> On Sat, Aug 31, 2013 at 1:04 AM, Sameera Jayasoma wrote:
>>
>>> appserver {
>>> # multiple hosts should be separated by a comma.
>>> # hosts appserver.cloud-test.wso2.com,
>>> as.cloud-test.wso2.com;
>>> #when using url mapping, url_suffix will be required. hosts should be
>>> read first before url_suffix,
>>> #in order to construct the host vs url-suffix pairs, hence keep the
>>> logical order to of hosts and url_suffix as it is.
>>>
>>> #url_suffix as.wso2.com,appserver.wso2.com;
>>> domains {
>>> wso2.as.domain {
>>> # for more info on Tenant aware load balancing please
>>> refer to
>>> #
>>> http://sanjeewamalalgoda.blogspot.com/2012/05/tenant-aware-load-balancer.html
>>> tenant_range *;
>>> group_mgt_port 5000;
>>> mgt {
>>> hosts management.appserver.cloud-test.wso2.com;
>>> }
>>> worker {
>>> hosts appserver.cloud-test.wso2.com;
>>> }
>>> }
>>> }
>>> }
>>>
>>> --
>>> 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
>>>
>>
>>
>>
>> --
>> *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* * 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*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com , shameera AT
apache.org
*
*phone: +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Maintaining Synapse Versions in 4.2.0 Branch
Hi Ishan, Is there any reason to have this in branch instead of turnk? Thanks, Shameera. On Mon, Aug 26, 2013 at 2:01 PM, Ishan Jayawardena wrote: > Hi, > We created a new version of Synapse here[1] and we will continue to > develop it from now on. Mainly we are adding ESB Connector related fixes to > this version of Synapse. > > If ELB or APIM requires a new Synapse version we suggest that you create > the v2.1.1-wso2v9. Please make sure to apply any fixes that you work on to > both versions. > > We will also apply any significant fixes that should go to ELB, and APIM > in v2.1.1-wso2v9 at the same time. > > > [1] > https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/2.2.0-wso2v1 > > > Thanks, > Ishan. > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why we have two synapse version in 4.2.0 platform branch?
Hi Nuwan/Isuru, Thansk for explanation. Shouldn't this goes to trunk only ? can we remove it from branch ? Thanks, Shameera. On Thu, Aug 29, 2013 at 4:20 PM, Isuru Udana wrote: > Hi Shameera, > > This is explained in following thread. > [Dev] Maintaining Synapse Versions in 4.2.0 Branch > > Thanks. > > > On Thu, Aug 29, 2013 at 4:10 PM, Shameera Rathnayaka wrote: > >> Hi, >> >> There are two version for synapse in 4.2.0 branch, >> >>- >> 2.1.1-wso2v8/<https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/2.1.1-wso2v8/> >>- >> 2.2.0-wso2v1/<https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/2.2.0-wso2v1/> >> >> Only 2.1.1-wso2v8 is used. Is there any reason that we have new version >> 2.2.0-wso2v1 there? or we can remove it? BTW why we use older version other >> than new version? >> >> Thanks, >> Shameera. >> >> [1] >> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/ >> >> -- >> *Software Engineer - WSO2 Inc.* >> *email: shameera AT wso2.com , shameera AT >> apache.org >> * >> *phone: +9471 922 1454* >> * >> * >> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >> *Twitter : *https://twitter.com/Shameera_R >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Isuru Udana* > * > * > Senior * > Software Engineer > * > WSO2 Inc.; http://wso2.com > email: isu...@wso2.com cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > twitter: http://twitter.com/isudana > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Why we have two synapse version in 4.2.0 platform branch?
Hi, There are two version for synapse in 4.2.0 branch, - 2.1.1-wso2v8/<https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/2.1.1-wso2v8/> - 2.2.0-wso2v1/<https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/2.2.0-wso2v1/> Only 2.1.1-wso2v8 is used. Is there any reason that we have new version 2.2.0-wso2v1 there? or we can remove it? BTW why we use older version other than new version? Thanks, Shameera. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/ -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com , shameera AT apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Getting the NPE while deploying Deployers in 4.2.0 branch
Hi All,
There are few Deployers which get registered with Null extension, For an
example
org.jaggeryjs.jaggery.deployer.JaggeryDeployer,
org.wso2.carbon.webapp.deployer.WebappDeployer,
org.wso2.carbon.stratos.landing.page.deployer.LandingPageWebappDeployer
We need to fix this but this is not the correct time to do such a fix as we
are on edge of 4.2.0 release. Therefore the change done to
CARBON-14447<https://wso2.org/jira/browse/CARBON-14447>has been
reverted(r183547) for now.
Thanks,
Shameera.
On Thu, Aug 29, 2013 at 11:03 AM, Shameera Rathnayaka wrote:
> Hi Janaka,
>
> This is due to recent fix done for
> https://wso2.org/jira/browse/CARBON-14447, ConcurrentHashMap doesn't
> allow Null key/value but HashMap does. Need to find when and why we add
> null key/value for deployer map. I am working on this.
>
> Thanks,
> Shameera.
>
>
> On Thu, Aug 29, 2013 at 10:27 AM, Janaka Ranabahu wrote:
>
>> Hi Sameera,
>>
>> Got the following exception in AppFactory pack built from 4.2.0
>> branch(latest kernel). Please check.
>>
>> [2013-08-29 10:14:18,572] INFO
>> {org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent} - Carbon
>> UserStoreMgtDSComponent activated successfully.
>> [2013-08-29 10:14:26,108] INFO
>> {org.apache.axis2.deployment.ClusterBuilder} - Clustering has been disabled
>> [2013-08-29 10:14:26,224] ERROR
>> {org.wso2.carbon.utils.deployment.Axis2DeployerRegistry} - Error while
>> deploying the Deployer from bunlde :
>> org.jaggeryjs.jaggery.deployer-0.9.0.ALPHA4_wso2v1
>> java.lang.NullPointerException
>> at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:882)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.addDeployer(DeploymentEngine.java:1436)
>> at
>> org.wso2.carbon.utils.deployment.Axis2DeployerRegistry.register(Axis2DeployerRegistry.java:108)
>> at
>> org.wso2.carbon.utils.deployment.Axis2DeployerRegistry.register(Axis2DeployerRegistry.java:55)
>> at
>> org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:204)
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
>> at
>> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:290)
>> at
>> org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:118)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
>> [2013-08-29 10:14:26,240] ERROR
>> {org.wso2.carbon.utils.deployment.Axis2DeployerRegistry} - Error while
>> deploying the Deployer from bunlde : org.wso2.carbon.webapp.deployer-4.2.0
>> java.lang.NullPointerException
>> at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:882)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.addDeployer(DeploymentEngine.java:1436)
>> at
>> org.wso2.carbon.utils.deployment.Axis2DeployerRegistry.register(Axis2DeployerRegistry.java:108)
>> at
>> org.wso2.carbon.utils.deployment.Axis2DeployerRegistry.register(Axis2DeployerRegistry.java:55)
>> at
>> org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:204)
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
>> at
>> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:290)
>> at
>> org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:118)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager$Eve
