Re: [Carbon-dev] Trunk orbit/commons.vfs build error
WRT to the builds, Orbit depends on the VFS trunk, and the dependencies has a stale version, which has been deployed onto our Maven repos already. So, on the builder, we build, [1] as well. Rajika, can you look into this and come up with a better solution? [1] https://svn.apache.org/repos/asf/commons/proper/vfs/trunk Thanks, Senaka. On Tue, Aug 3, 2010 at 10:57 AM, Amila Jayasekara ami...@wso2.com wrote: Hi All, I am still facing the issue in $subject. To alleviate this issue, in a previous build i change orbit/common-vfs/pom.xml dependency versions to 2.0-wso2v1 (for commons-vfs-sandbox and commons-vfs). Now i took a fresh copy and try to build again. But still the trunk version of orbit/common-vfs/pom.xml depends on commons-vfs-2.0-SNAPSHOT and commons-vfs-sandbox-2.0-SNAPSHOT. Thus dependencies/commons-vfs/core/pom.xml and dependencies/commons-vfs/sandbox/pom.xml builds commons-vfs-2.0-wso2v1 and commons-vfs-sandbox-2.0-wso2v1. Please let me know what should be the correct version to use ? Thank you AmilaJ Hi, $ subject. I built dependencies/common-vfs (version 2.0-wso2v1)successfully. Which is the right version? -Ratha. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.commons:commons-vfs:jar:2.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.commons -DartifactId=commons -vfs -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.commons -DartifactId=commons-v fs -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drep ositoryId=[id] Path to dependency: 1) org.apache.commons.wso2:commons-vfs:bundle:2.0-wso2v1 2) org.apache.commons:commons-vfs:jar:2.0-SNAPSHOT 2) org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.commons -DartifactId=commons -vfs-sandbox -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.commons -DartifactId=commons-v fs-sandbox -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[ur l] -DrepositoryId=[id] Path to dependency: 1) org.apache.commons.wso2:commons-vfs:bundle:2.0-wso2v1 2) org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT -- 2 required artifacts are missing. ___ 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 -- Senaka Fernando Associate Technical Lead WSO2 Inc. E-mail: senaka AT wso2.com; Mobile: +94 77 322 1818 http://www.wso2.com/ - Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Trunk orbit/commons.vfs build error
I have fixed the orbit bundle version in trunk. If you are building with a clean repo you'll need to build the commons-vfs dependency with test because commos-vfs building tests for the first time. Rajika On Tue, Aug 3, 2010 at 10:57 AM, Amila Jayasekara ami...@wso2.com wrote: Hi All, I am still facing the issue in $subject. To alleviate this issue, in a previous build i change orbit/common-vfs/pom.xml dependency versions to 2.0-wso2v1 (for commons-vfs-sandbox and commons-vfs). Now i took a fresh copy and try to build again. But still the trunk version of orbit/common-vfs/pom.xml depends on commons-vfs-2.0-SNAPSHOT and commons-vfs-sandbox-2.0-SNAPSHOT. Thus dependencies/commons-vfs/core/pom.xml and dependencies/commons-vfs/sandbox/pom.xml builds commons-vfs-2.0-wso2v1 and commons-vfs-sandbox-2.0-wso2v1. Please let me know what should be the correct version to use ? Thank you AmilaJ Hi, $ subject. I built dependencies/common-vfs (version 2.0-wso2v1)successfully. Which is the right version? -Ratha. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.commons:commons-vfs:jar:2.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.commons -DartifactId=commons -vfs -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.commons -DartifactId=commons-v fs -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drep ositoryId=[id] Path to dependency: 1) org.apache.commons.wso2:commons-vfs:bundle:2.0-wso2v1 2) org.apache.commons:commons-vfs:jar:2.0-SNAPSHOT 2) org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.commons -DartifactId=commons -vfs-sandbox -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.commons -DartifactId=commons-v fs-sandbox -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[ur l] -DrepositoryId=[id] Path to dependency: 1) org.apache.commons.wso2:commons-vfs:bundle:2.0-wso2v1 2) org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT -- 2 required artifacts are missing. ___ 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] Trunk orbit/commons.vfs build error
Senaka, We had to clone commons-vfs into our repo since we had some fixes that need to go into the commons-vfs. This was done in 3.0.0 release. That is available in[2]. So the trunk orbit should point to cloned version[2] not the apache commons-vfs trunk[1]. Rajika [2] - https://svn.wso2.org/repos/wso2/branches/carbon/3.0.0/dependencies/commons-vfs On Tue, Aug 3, 2010 at 12:20 PM, Senaka Fernando sen...@wso2.com wrote: WRT to the builds, Orbit depends on the VFS trunk, and the dependencies has a stale version, which has been deployed onto our Maven repos already. So, on the builder, we build, [1] as well. Rajika, can you look into this and come up with a better solution? [1] https://svn.apache.org/repos/asf/commons/proper/vfs/trunk Thanks, Senaka. On Tue, Aug 3, 2010 at 10:57 AM, Amila Jayasekara ami...@wso2.com wrote: Hi All, I am still facing the issue in $subject. To alleviate this issue, in a previous build i change orbit/common-vfs/pom.xml dependency versions to 2.0-wso2v1 (for commons-vfs-sandbox and commons-vfs). Now i took a fresh copy and try to build again. But still the trunk version of orbit/common-vfs/pom.xml depends on commons-vfs-2.0-SNAPSHOT and commons-vfs-sandbox-2.0-SNAPSHOT. Thus dependencies/commons-vfs/core/pom.xml and dependencies/commons-vfs/sandbox/pom.xml builds commons-vfs-2.0-wso2v1 and commons-vfs-sandbox-2.0-wso2v1. Please let me know what should be the correct version to use ? Thank you AmilaJ Hi, $ subject. I built dependencies/common-vfs (version 2.0-wso2v1)successfully. Which is the right version? -Ratha. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.commons:commons-vfs:jar:2.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.commons -DartifactId=commons -vfs -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.commons -DartifactId=commons-v fs -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drep ositoryId=[id] Path to dependency: 1) org.apache.commons.wso2:commons-vfs:bundle:2.0-wso2v1 2) org.apache.commons:commons-vfs:jar:2.0-SNAPSHOT 2) org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.commons -DartifactId=commons -vfs-sandbox -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.commons -DartifactId=commons-v fs-sandbox -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[ur l] -DrepositoryId=[id] Path to dependency: 1) org.apache.commons.wso2:commons-vfs:bundle:2.0-wso2v1 2) org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT -- 2 required artifacts are missing. ___ 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 -- Senaka Fernando Associate Technical Lead WSO2 Inc. E-mail: senaka AT wso2.com; Mobile: +94 77 322 1818 http://www.wso2.com/ - Lean . Enterprise . Middleware ___ 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] Batch mode Activity data publishing
In order to solve the problem of message volume burst in in case of message level data collection like in the case of counting activity ID, we are going to introduce a batch mode, where we collect information on several messages and fire an event together for all those based on a message count threshold. This is the simplest and the fastest solution to burst problem we have now. Advanced solutions like queue based models can be take up later, but I doubt the need of those if this works well for us. Thanks, Samisa... 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
Re: [Carbon-dev] XPath on message for BAM stats
Axiom has built in support for XPath using Jaxen. Wouldn't that be the one to use? Sanjiva. On Wed, Aug 4, 2010 at 6:20 AM, Samisa Abeysinghe sam...@wso2.com wrote: We are planning to provide XPath based BAM data collection to users. For e.g., if the payload is supposed to have a PO, the user can specify the path to PO ID in payload and collect a count of POs that pass through. The question is... Do we have an XPath component, or a handler or something like that we can reuse to facilitate this? Also, how to do this for WSAS vs ESB. I think WSAS case is tivial, in that we can evaluate the XPath in a handler. What about the ESB? Note that, in case of ESB, we do not collect our own data, rather we bank on the stat data provided by the ESB itself. I know that we have XPath used in ESB etc, but the idea is to use minimal dependencies here for BAM Thanks, Samisa... 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 -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +1 408 754 7388 x51726; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Batch mode Activity data publishing
On Wed, Aug 4, 2010 at 7:42 AM, Srinath Perera srin...@wso2.com wrote: Hi Samisa, +1, in any case to support monitoring reasonable large number of servers with BAM we should create the batch mode. Basically get the data publishers cache all collected data, and publisher sends them in only once few seconds. In a more advanced version, high priority events will trigger a immediate transfer while low priority events are transfer in batch fashion. Sometimes it is tough to provide true real time data with BAM. However we can provide near real time data. Thanks Srinath On Wed, Aug 4, 2010 at 6:23 AM, Samisa Abeysinghe sam...@wso2.com wrote: In order to solve the problem of message volume burst in in case of message level data collection like in the case of counting activity ID, we are going to introduce a batch mode, where we collect information on several messages and fire an event together for all those based on a message count threshold. This is the simplest and the fastest solution to burst problem we have now. Advanced solutions like queue based models can be take up later, but I doubt the need of those if this works well for us. Thanks, Samisa... 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 -- Srinath Perera, Ph.D. WSO2 Inc. http://wso2.com Blog: http://srinathsview.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Thanks, Samisa... 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] Activity monitoring for mediation
I think we only have activity support for service invocations. Ratha? So we need to implement $subject as well. I hope we can re-use the same Axis2 handler. Thanks, Samisa... 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
Re: [Carbon-dev] [Stratos-dev] Removed bam.client jar
Why is the client module commented in bam component's root pom? Since it is commented, the nightly builds do not build it On Mon, Aug 2, 2010 at 8:44 PM, Ajith Vitharana aji...@wso2.com wrote: Hi all, I have removed org.wso2.carbon.bam.client jar from trunk/component/bam after refactoring bam component. And removed that bundle from dependencies (trunk/feature/bam , trunk/product/bam ,trunk/stratos/services/bam ) Thanks ajithn ___ Stratos-dev mailing list stratos-...@wso2.org https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev Thanks, Samisa... 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
Re: [Carbon-dev] XPath on message for BAM stats
Sumedha Rubasinghe wrote: On Wed, Aug 4, 2010 at 6:20 AM, Samisa Abeysinghe sam...@wso2.com mailto:sam...@wso2.com wrote: We are planning to provide XPath based BAM data collection to users. For e.g., if the payload is supposed to have a PO, the user can specify the path to PO ID in payload and collect a count of POs that pass through. The question is... Do we have an XPath component, or a handler or something like that we can reuse to facilitate this? Also, how to do this for WSAS vs ESB. I think WSAS case is tivial, in that we can evaluate the XPath in a handler. What about the ESB? Note that, in case of ESB, we do not collect our own data, rather we bank on the stat data provided by the ESB itself. I know that we have XPath used in ESB etc, but the idea is to use minimal dependencies here for BAM Generally speaking, reusing things from ESB comes with considerable number of dependencies size in MBs. Synapse/ESB has a set of Xpath extension functions which shouldn't be required outside of Synapse runtime, so the ideal should be to use the Jaxen Xpath implementation which is there in AXIOM. Ruwan /sumedha Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto: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 -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Governance registry product build failed
I think this is in trunk ? I got the same error on branch (3.0.0) ! Was able to fix this by removing maven-project-info-report part from distribution pom. Lahiru On Wed, Aug 4, 2010 at 5:29 AM, Samisa Abeysinghe sam...@wso2.com wrote: [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please update this plugin. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] 1 [INFO] [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableHeaderCell(XhtmlSink.java:777) at org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeaderCell(AbstractMavenReportRenderer.java:267) at org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeader(AbstractMavenReportRenderer.java:356) at org.apache.maven.report.projectinfo.MailingListsReport$MailingListsRenderer.renderBody(MailingListsReport.java:165) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79) at org.apache.maven.report.projectinfo.MailingListsReport.executeReport(MailingListsReport.java:66) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) Thanks, Samisa... 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 -- Lahiru Gunathilake Senior Software Engineer - WSO2 Inc. www.wso2.com Email:lah...@wso2.com email%3alah...@wso2.com Blog: www.lahiru.org Mobile: +94716381143 Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] BPEL Component removed from the build
Hi All, I removed BPEL component from the build until refactoring work is over. I am doing some changes to BPEL component structure and internals of the BPEL component. BPEL will be added to build once the all changes are committed into trunk. Thanks Milinda -- Milinda Pathirage Technical Lead and Product Manager, Business Process Server - WSO2 Inc; http://wso2.com Blog: http://blog.mpathirage.com Lean Enterprise Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
