Re: [Carbon-dev] Data Services performance test results using performance testing framework

Eranda, You need to compare 2.5.0 with 2.0.0. AFAIR these are the two versions we discussed to compare. /sumedha On Tue, Jun 1, 2010 at 5:16 PM, Eranda Sooriyabandara wrote: > This test was done for the Data Services team to compare the performance of > the Data Services servers 2.2.0 and 2.5.0

Re: [Carbon-dev] Data Services performance test results using performance testing framework

Hi Eranda; If you need more than average, right way to go is drawing confidence intervals (http://en.wikipedia.org/wiki/Confidence_interval)/ error bars, which will let you draw both servers on same graph. But in general, only average is good. Also what are X/Y axis? Thanks Srinath On Tue, Ju

Re: [Carbon-dev] Data Services performance test results using performance testing framework

Anjana Fernando wrote: > Hi, > > Yeah, you will not see any performance difference between 2.2.0 and > 2.5.0 versions because, the core is basically the same, only > additional features are added to 2.5.0. The major difference came with > 2.2.0. So the two version you should be testing for performa

Re: [Carbon-dev] Data Services performance test results using performance testing framework

Hi, Yeah, you will not see any performance difference between 2.2.0 and 2.5.0 versions because, the core is basically the same, only additional features are added to 2.5.0. The major difference came with 2.2.0. So the two version you should be testing for performance should be 2.0.0 and the 2.2.0/

Re: [Carbon-dev] Data services broken on trunk

Fixed. Sorry, earlier I forgot to do an "svn add" on a file. Cheers, Anjana. On Tue, Jun 1, 2010 at 5:37 PM, Samisa Abeysinghe wrote: > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Compilation failure > /home/carbon/stratos/ca

Re: [Carbon-dev] Events that can be analysed by the MessageExchangeInterceptor of a BPEL process

Hi all I changed the xml message format of the message related to events. Just like Dumindu and Ratha suggested here I organized the message as Key/Value pairs of server level data. And here I also used a unique Id to identify a one particular life cycle of events of a process. The message looks a

[Carbon-dev] Data services broken on trunk

[ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/carbon/stratos/carbon/components/data-services/org.wso2.carbon.dataservices.core/src/main/java/org/wso2/carbon/dataservices/core/tools/DSTools.java:[29,41] cannot

Re: [Carbon-dev] WSO2Constants.CONFIG_SYSTEM_REGISTRY_INSTANCE deprecated?

I deprecated the WSO2Constants class to discourage people from using it. At present, we have CarbonConstants, WSO2Constants, ServerConstants , MultitenantConstants and so many more. We will have to sit down & review these constants & properly cleanup the code. Azeez On Tue, Jun 1, 2010 at 12:57 P

Re: [Carbon-dev] mediation-initializer broken on trunk

Fixed. On Tue, Jun 1, 2010 at 4:20 PM, Kasun Indrasiri wrote: > I'll have a look. > > On Tue, Jun 1, 2010 at 3:38 PM, Samisa Abeysinghe wrote: > >> [ERROR] BUILD FAILURE >> [INFO] >> >> [INFO] Compilation failure >> >> /ho

Re: [Carbon-dev] mediation-initializer broken on trunk

I'll have a look. On Tue, Jun 1, 2010 at 3:38 PM, Samisa Abeysinghe wrote: > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Compilation failure > > /home/carbon/stratos/carbon/components/mediation-initializer/org.wso2.carbon.med

[Carbon-dev] mediation-initializer broken on trunk

[ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/carbon/stratos/carbon/components/mediation-initializer/org.wso2.carbon.mediation.initializer/src/main/java/org/wso2/carbon/mediation/initializer/ServiceBusInitiali

Re: [Carbon-dev] Carbon-3.0.0 Iridium - RC19

Please add BAM packs, p2 repo and svn info. Samisa... On Tue, Jun 1, 2010 at 3:07 PM, Milinda Pathirage wrote: > http://builder.wso2.org/~carbon/releases/carbon/3.0.0/4RC19/ > > Thanks > -- > Milinda Pathirage > Technical Lead and

Re: [Carbon-dev] Reliable Messaging Persistence

Thanks ... On Tue, Jun 1, 2010 at 1:28 PM, Charitha Kankanamge wrote: > Replied > > > Thanks > Charitha > > > On Tue, Jun 1, 2010 at 11:57 AM, Indika Kumara wrote: > >> Hi folks >> >> $subject is in http://wso2.org/forum/thread/9739 may someone has the >> time for answering it ?...

[Carbon-dev] Carbon-3.0.0 Iridium - RC19

http://builder.wso2.org/~carbon/releases/carbon/3.0.0/4RC19/ Thanks -- Milinda Pathirage Technical Lead and Product Manager, Business Process Server - WSO2 Inc; http://wso2.com Blog: http://blog.mpathirage.com Lean Enterprise Middlewa

Re: [Carbon-dev] Carbon core build failure on trunk

Fixed Thanks, Hiranya On Tue, Jun 1, 2010 at 11:35 AM, Indika Kumara wrote: > Hiranya , I have attached required changes as a patch ... There are some > changes related to the securing password ... can you please review and apply > the patch? .. > > Thanks > Indika > > On Tue, Jun 1, 2010 at 11

Re: [Carbon-dev] Reliable Messaging Persistence

Replied Thanks Charitha On Tue, Jun 1, 2010 at 11:57 AM, Indika Kumara wrote: > Hi folks > > $subject is in http://wso2.org/forum/thread/9739 may someone has the > time for answering it ?... > > Thanks > > Indika > > ___ > Carbon-dev mailing li

Re: [Carbon-dev] WSO2Constants.CONFIG_SYSTEM_REGISTRY_INSTANCE deprecated?

Hi, Thanks Nuwan. Yeah, actually my need was to use it inside an admin service, "getConfigSystemRegistry" will do fine. As for the "WSO2Constants.CONFIG_SYSTEM_REGISTRY_INSTANCE", that was my initial problem, that is where to find an non-deprecated version of that constant. Because I see that it i

Re: [Carbon-dev] WSO2Constants.CONFIG_SYSTEM_REGISTRY_INSTANCE deprecated?

Hi Anjana, There are several ways to get the registry, in Dashboard we use two methods in different contexts, [1] Via a declarative service we can obtain the registry service (If you need the registry at bundle startup) * @scr.reference name="registry.service" * interface="org.wso2.carbon.regi