Re: [Carbon-dev] Carbon-3.0.0 Iridium - RC26
Is it possible to get a new BAM build. There are some critical issue fixes that we need to verify. Thanks, Krishantha. On Mon, Jun 21, 2010 at 6:37 PM, Dumindu Pallewela dumi...@wso2.com wrote: Updated the RC26 build with latest fixes. http://builder.wso2.org/~carbon/releases/carbon/3.0.0/5RC26.1/http://builder.wso2.org/%7Ecarbon/releases/carbon/3.0.0/5RC26.1/ Thanks, Dumindu. On Mon, Jun 21, 2010 at 2:45 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Thanks for the build Samisa. Seems like some fixes are not there in the build. Fixes done for reporting component and dashboard gadgets are not available. May be you forgot to update those components [?] Thanks, Krishantha. On Mon, Jun 21, 2010 at 8:05 AM, Samisa Abeysinghe sam...@wso2.comwrote: http://builder.wso2.org/~carbon/releases/carbon/3.0.0/5RC26/http://builder.wso2.org/%7Ecarbon/releases/carbon/3.0.0/5RC26/ http://builder.wso2.org/%7Ecarbon/releases/carbon/3.0.0/5RC26/ Samisa... On Thu, Jun 17, 2010 at 4:40 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Dumindu, Is it possible to get a new BAM build. There are several fixes that we need to verify. Thanks, Krishantha. On Fri, Jun 11, 2010 at 6:05 PM, Dumindu Pallewela dumi...@wso2.comwrote: http://builder.wso2.org/~carbon/releases/carbon/3.0.0/5RC25/http://builder.wso2.org/%7Ecarbon/releases/carbon/3.0.0/5RC25/ Thanks, Dumindu. -- Dumindu Pallewela WSO2 | Lean . Enterprise . Middleware | http://wso2.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Dumindu Pallewela WSO2 | Lean . Enterprise . Middleware | http://wso2.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev 338.png___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Eclipse code style committed
Hi Devs, We've been using default eclipse codestyle when working on tooling projects. By default eclipse uses a line width of 80 which is bit uneasy, I've changed this to 100 (as this seems to be the default here) and committed the codestyle configuration at [1]. If we have any guidelines on codestyle I can update this definition file to reflect those. Thanks. - Asiri [1] http://svn.wso2.org/repos/wso2/trunk/tools/ide/eclipse/carbonstudio-eclipse-codestyle.xml ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ESB native tool project progress
On Thu, Jun 24, 2010 at 10:31 AM, Samisa Abeysinghe sam...@wso2.com wrote: When was the last time we did a milestone on ESB tools stuff that is in progress? Samisa, As agreed, First iteration of ESB tooling is the simple XML editor. This has been included in all Carbon Studio milestone releases. Now IsuruU Asiri have begun the next iteration of ESB tooling, which is the graphical editor mentioned previously on this thread. Next week, - We will be doing(Monday) a point release of Carbon studio with all existing features. This will be out from a branch created for this. - And there will be a milestone release from trunk including latest ESB tooling features (Wednesday) /sumedha Samisa... On Thu, Jun 24, 2010 at 10:11 AM, Sumedha Rubasinghe sume...@wso2.comwrote: Samisa, We will be sending a summary of all aspects of tooling (this will include Carbon studio, ESB,BPS) today. /sumedha On Thu, Jun 24, 2010 at 9:33 AM, Asiri Rathnayake asiri.rathnay...@gmail.com wrote: Hi, We finally decided to continue the EMF approach as it takes less amount of time to implement all three editors (sequence, endpoint, proxy) according to Asiri's estimation. Choosing the EMF approach has some disadvantages as well. We've discussed about these and a summary email will follow. The reason for choosing the EMF approach is mainly because of time constraints; we need to ship out a working and complete esb toolset along with the first release of carbon studio. Note that some of the existing work (registry integration, xml editor etc.) will be integrated into EMF plugin. Thanks. - Asiri ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Eclipse code style committed
Hi Asiri, FYI http://markmail.org/message/amlydyuhwxb2n46x On Thu, Jun 24, 2010 at 12:45 PM, Asiri Rathnayake asiri.rathnay...@gmail.com wrote: Hi Devs, We've been using default eclipse codestyle when working on tooling projects. By default eclipse uses a line width of 80 which is bit uneasy, I've changed this to 100 (as this seems to be the default here) and committed the codestyle configuration at [1]. If we have any guidelines on codestyle I can update this definition file to reflect those. Thanks. - Asiri [1] http://svn.wso2.org/repos/wso2/trunk/tools/ide/eclipse/carbonstudio-eclipse-codestyle.xml ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Regards, Heshan Suriyaarachchi Software Engineer WSO2 Inc.; http://wso2.com/ Blog: http://heshans.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Eclipse code style committed
On Thu, Jun 24, 2010 at 1:05 PM, Heshan Suriyaarachchi hes...@wso2.comwrote: Hi Asiri, FYI http://markmail.org/message/amlydyuhwxb2n46x Argh! I should've searched the archive before asking around :) I'll remove the committed file and use the one provided on that email instead. Thanks. - Asiri On Thu, Jun 24, 2010 at 12:45 PM, Asiri Rathnayake asiri.rathnay...@gmail.com wrote: Hi Devs, We've been using default eclipse codestyle when working on tooling projects. By default eclipse uses a line width of 80 which is bit uneasy, I've changed this to 100 (as this seems to be the default here) and committed the codestyle configuration at [1]. If we have any guidelines on codestyle I can update this definition file to reflect those. Thanks. - Asiri [1] http://svn.wso2.org/repos/wso2/trunk/tools/ide/eclipse/carbonstudio-eclipse-codestyle.xml ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Regards, Heshan Suriyaarachchi Software Engineer WSO2 Inc.; http://wso2.com/ Blog: http://heshans.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ESB native tool project progress
On Thu, Jun 24, 2010 at 12:46 PM, Sumedha Rubasinghe sume...@wso2.comwrote: On Thu, Jun 24, 2010 at 10:31 AM, Samisa Abeysinghe sam...@wso2.comwrote: When was the last time we did a milestone on ESB tools stuff that is in progress? Samisa, As agreed, First iteration of ESB tooling is the simple XML editor. This has been included in all Carbon Studio milestone releases. This is for CStudio Now IsuruU Asiri have begun the next iteration of ESB tooling, which is the graphical editor mentioned previously on this thread. This is the native tool CStudio plan and native ESB tool plan are completely independent. My question is on ESB native tools. It has nothing to do with CStudio. Do we not have a separate milestone plan on native ESB tool? Samisa... Next week, - We will be doing(Monday) a point release of Carbon studio with all existing features. This will be out from a branch created for this. - And there will be a milestone release from trunk including latest ESB tooling features (Wednesday) /sumedha Samisa... On Thu, Jun 24, 2010 at 10:11 AM, Sumedha Rubasinghe sume...@wso2.comwrote: Samisa, We will be sending a summary of all aspects of tooling (this will include Carbon studio, ESB,BPS) today. /sumedha On Thu, Jun 24, 2010 at 9:33 AM, Asiri Rathnayake asiri.rathnay...@gmail.com wrote: Hi, We finally decided to continue the EMF approach as it takes less amount of time to implement all three editors (sequence, endpoint, proxy) according to Asiri's estimation. Choosing the EMF approach has some disadvantages as well. We've discussed about these and a summary email will follow. The reason for choosing the EMF approach is mainly because of time constraints; we need to ship out a working and complete esb toolset along with the first release of carbon studio. Note that some of the existing work (registry integration, xml editor etc.) will be integrated into EMF plugin. Thanks. - Asiri ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Eclipse code style committed
On Thu, Jun 24, 2010 at 1:26 PM, Asiri Rathnayake asiri.rathnay...@gmail.com wrote: On Thu, Jun 24, 2010 at 1:05 PM, Heshan Suriyaarachchi hes...@wso2.comwrote: Hi Asiri, FYI http://markmail.org/message/amlydyuhwxb2n46x Argh! I should've searched the archive before asking around :) I'll remove the committed file and use the one provided on that email instead. I had some trouble with the earlier code style configuration where how a line are broken to several when the length exceeds 100. That needs fixing in the earlier one. +1 for committing the code style configuration to the svn. how about committing the most updated one to http://svn.wso2.org/repos/wso2/trunk/tools/ide/eclipse/ide-configuration/wso2-eclipse-codestyle.xml ? Saminda Thanks. - Asiri On Thu, Jun 24, 2010 at 12:45 PM, Asiri Rathnayake asiri.rathnay...@gmail.com wrote: Hi Devs, We've been using default eclipse codestyle when working on tooling projects. By default eclipse uses a line width of 80 which is bit uneasy, I've changed this to 100 (as this seems to be the default here) and committed the codestyle configuration at [1]. If we have any guidelines on codestyle I can update this definition file to reflect those. Thanks. - Asiri [1] http://svn.wso2.org/repos/wso2/trunk/tools/ide/eclipse/carbonstudio-eclipse-codestyle.xml ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Regards, Heshan Suriyaarachchi Software Engineer WSO2 Inc.; http://wso2.com/ Blog: http://heshans.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ESB native tool project progress
On Thu, Jun 24, 2010 at 1:21 PM, Samisa Abeysinghe sam...@wso2.com wrote: On Thu, Jun 24, 2010 at 12:46 PM, Sumedha Rubasinghe sume...@wso2.comwrote: On Thu, Jun 24, 2010 at 10:31 AM, Samisa Abeysinghe sam...@wso2.comwrote: When was the last time we did a milestone on ESB tools stuff that is in progress? Samisa, As agreed, First iteration of ESB tooling is the simple XML editor. This has been included in all Carbon Studio milestone releases. This is for CStudio Now IsuruU Asiri have begun the next iteration of ESB tooling, which is the graphical editor mentioned previously on this thread. This is the native tool CStudio plan and native ESB tool plan are completely independent. My question is on ESB native tools. It has nothing to do with CStudio. Are we giving out ESB native tool as a separate download? If not, wouldn't it be nice to have ESB tool integrated to CStudio right from the beginning? Of course we can make the ESB tool as a separate download (development PM work happen separately already). But I believe it should be presented along with the complete tooling story offered by CStudio rather than that of a separate tool. This integration between ESB tool CStudio is a one time thing there after it's just a matter of releasing CStudio with latest set of new features. Then CStudio milestone/release will include all the new features of respective sub projects. And approach does not add additional overhead when doing a release/milestone either. We have followed the same approach for BPEL plugin its working out nicely. We do have milestones for every sub tooling project. /sumedha Do we not have a separate milestone plan on native ESB tool? Samisa... Next week, - We will be doing(Monday) a point release of Carbon studio with all existing features. This will be out from a branch created for this. - And there will be a milestone release from trunk including latest ESB tooling features (Wednesday) /sumedha Samisa... On Thu, Jun 24, 2010 at 10:11 AM, Sumedha Rubasinghe sume...@wso2.comwrote: Samisa, We will be sending a summary of all aspects of tooling (this will include Carbon studio, ESB,BPS) today. /sumedha On Thu, Jun 24, 2010 at 9:33 AM, Asiri Rathnayake asiri.rathnay...@gmail.com wrote: Hi, We finally decided to continue the EMF approach as it takes less amount of time to implement all three editors (sequence, endpoint, proxy) according to Asiri's estimation. Choosing the EMF approach has some disadvantages as well. We've discussed about these and a summary email will follow. The reason for choosing the EMF approach is mainly because of time constraints; we need to ship out a working and complete esb toolset along with the first release of carbon studio. Note that some of the existing work (registry integration, xml editor etc.) will be integrated into EMF plugin. Thanks. - Asiri ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Carbon-3.0.0 Iridium - RC27
On Thu, Jun 24, 2010 at 11:49 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Is it possible to get a new BAM build. There are some critical issue fixes that we need to verify. http://builder.wso2.org/~carbon/releases/carbon/3.0.0/5RC27/ -- Dumindu Pallewela WSO2 | Lean . Enterprise . Middleware | http://wso2.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Error While Checking Out Trunk
On Thu, Jun 24, 2010 at 11:09 AM, Sumedha Rubasinghe sume...@wso2.comwrote: Kalpanie, Didn't we fix this? This is fixed now. Thanks. Kalpanie /sumedha On Thu, Jun 24, 2010 at 11:07 AM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi Folks, While taking a fresh checkout of the carbon trunk I got the following error: Fetching external item into 'new-trunk/products/ds/modules/features/etc' svn: 'new-trunk/products/ds/modules/features/etc' is already a working copy for a different URL Any idea what's wrong? Thanks -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Compilation error building Axis2
Hi, While i'm building axis i got the following error. I've searched a little in the internet and only thing that i can find is have you build axiom question and my answer is yes i did. Does anyone has an idea about this?? Thanks [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/description/InOutAxisOperation.java:[22,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/description/TwoChannelAxisOperation.java:[22,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/description/AxisOperation.java:[30,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/context/ServiceContext.java:[23,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/client/Options.java:[24,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/client/OperationClient.java:[23,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/context/MessageContext.java:[28,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/context/OperationContext.java:[23,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/addressing/EndpointReference.java:[31,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/context/ServiceGroupContext.java:[23,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/description/RobustOutOnlyAxisOperation.java:[23,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/description/OutInAxisOperation.java:[28,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/description/OutOnlyAxisOperation.java:[22,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/util/MessageContextBuilder.java:[40,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/builder/SOAPBuilder.java:[24,31] cannot find symbol symbol : class StAXParserConfiguration location: package org.apache.axiom.om.util /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/description/InOnlyAxisOperation.java:[22,28] package org.apache.axiom.util does not exist /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/builder/BuilderUtil.java:[35,31] cannot find symbol symbol : class StAXParserConfiguration location: package org.apache.axiom.om.util /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/description/AxisOperation.java:[90,68] cannot find symbol symbol : variable UIDGenerator location: class org.apache.axis2.description.AxisOperation /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/description/TwoChannelAxisOperation.java:[46,68] cannot find symbol symbol : variable UIDGenerator location: class org.apache.axis2.description.TwoChannelAxisOperation /home/foo/DEVELOPMENT/LIB/WSO2/wso2-stratos-1.0.0-alpha1-src/carbon/dependencies/axis2/modules/kernel/src/org/apache/axis2/description/InOutAxisOperation.java:[39,68] cannot find symbol symbol : variable UIDGenerator location: class org.apache.axis2.description.InOutAxisOperation
Re: [Carbon-dev] Events that can be analysed by the MessageExchangeInterceptor of a BPEL process
Hi All The progress update of the project Has been able to complete some major phases of the project. 1. The new data publisher for bpel is completed. which is the BpelStatsPublisher 2. Did necessary changes to add BPS server successfully to BAM to be able to monitor. 3. Events generated at BPS is successfully being received to the BAM side and populated the database. 4. Creating new data service to retrieve BPS related data from the data base. 5. First gadget to represent BPEL stats is almost on completion. The work to be done 1. few modifications and issues to be solved on the data receiving part of BAM, will be completed on next week. 2. design gadgets in the best way to analyse bpel event data. Thank You IsuruW ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
