Re: [Dev] Monitoring cassandra cluster through JMX
On Fri, Jun 29, 2012 at 5:12 PM, Harsha Kumara har...@wso2.com wrote: Hi! I have a requirement to monitor and manage cassandra cluster.Cassandra offer JMX support.I able to get mBean server connection for local running instance via ManagementFactory.getPlatformMBeanServer().But I need to connect external cassandra cluster node to perform operations.For a JMX disabled carbon deployment,I won't be able to connect external cassandra cluster node.Is there's any alternatives which can overcome this problem? In a normal deployment we my not deploy the admin UI in the nodes running Cassandra service. Best practice is to monitor the Cassandra cluster from outside. If devops decide to close JMX ports in the deployment there will be no method to manage the Cassandra cluster. Therefore it is always good to implement management function through web services. Thanks, Deependra. Thanks. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Deependra Ariyadewa WSO2, Inc. http://wso2.com/ http://wso2.org email d...@wso2.com; cell +94 71 403 5996 ; Blog http://risenfall.wordpress.com/ PGP info: KeyID: 'DC627E6F' ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Monitoring cassandra cluster through JMX
Deep has exactly put his finger on the nail. The reason we disallow JMX from Stratos is for security reasons. So the workaround is to create a *properly secured* admin service that runs locally, exposes the JMX with the right multi-tenant security controls, and can be called remotely. Paul On 3 July 2012 11:27, Deependra Ariyadewa d...@wso2.com wrote: On Fri, Jun 29, 2012 at 5:12 PM, Harsha Kumara har...@wso2.com wrote: Hi! I have a requirement to monitor and manage cassandra cluster.Cassandra offer JMX support.I able to get mBean server connection for local running instance via ManagementFactory.getPlatformMBeanServer().But I need to connect external cassandra cluster node to perform operations.For a JMX disabled carbon deployment,I won't be able to connect external cassandra cluster node.Is there's any alternatives which can overcome this problem? In a normal deployment we my not deploy the admin UI in the nodes running Cassandra service. Best practice is to monitor the Cassandra cluster from outside. If devops decide to close JMX ports in the deployment there will be no method to manage the Cassandra cluster. Therefore it is always good to implement management function through web services. Thanks, Deependra. Thanks. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Deependra Ariyadewa WSO2, Inc. http://wso2.com/ http://wso2.org email d...@wso2.com; cell +94 71 403 5996 ; Blog http://risenfall.wordpress.com/ PGP info: KeyID: 'DC627E6F' ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware 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
Re: [Dev] Throwing Exceptions from OSGi Component #activate methods
Hi, no you should not do that. framework itself catches the thrown exception and things will start to behave weird. --Pradeep ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] CXF JSON support
On Mon, Jul 2, 2012 at 2:29 PM, Afkham Azeez az...@wso2.com wrote: Hi Isuru, Have we tested $subject? Yes, we've already got JAX-RS JSON samples in AS.. Thanks, ~Isuru -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Isuru Suriarachchi Senior Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] CXF JSON support
Azeez, The BAM REST API demo you saw consumed/produced json. On Tue, Jul 3, 2012 at 7:05 PM, Isuru Suriarachchi is...@wso2.com wrote: On Mon, Jul 2, 2012 at 2:29 PM, Afkham Azeez az...@wso2.com wrote: Hi Isuru, Have we tested $subject? Yes, we've already got JAX-RS JSON samples in AS.. Thanks, ~Isuru -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Isuru Suriarachchi Senior Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Clarity tests daily report?
Shall we have $subject sent to dev@? Are we running Clarity tests daily based on the previous successful build? -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Throwing Exceptions from OSGi Component #activate methods
On Tue, Jul 3, 2012 at 6:48 PM, Pradeep Fernando prad...@wso2.com wrote: Hi, no you should not do that. framework itself catches the thrown exception and things will start to behave weird. OK. Then, I'll just log it, and continue as I've seen in other components. Thanks, --KasunG --Pradeep -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* http://blog.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
Re: [Dev] CXF JSON support
Yes, that is JAXRS. Do we have a JSON + CXF JAXWS sample/test? Does that combination make sense? On Tue, Jul 3, 2012 at 7:12 PM, Tharindu Mathew thari...@wso2.com wrote: Azeez, The BAM REST API demo you saw consumed/produced json. On Tue, Jul 3, 2012 at 7:05 PM, Isuru Suriarachchi is...@wso2.com wrote: On Mon, Jul 2, 2012 at 2:29 PM, Afkham Azeez az...@wso2.com wrote: Hi Isuru, Have we tested $subject? Yes, we've already got JAX-RS JSON samples in AS.. Thanks, ~Isuru -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Isuru Suriarachchi Senior Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarity tests daily report?
On Tue, Jul 3, 2012 at 7:41 PM, Tharindu Mathew thari...@wso2.com wrote: Shall we have $subject sent to dev@? If this is run on top of a set of successfully built packs, it is meaningless to run it for more than once IMO. May be we should manually run this once when we have a successful build. Regards, AmilaM. Are we running Clarity tests daily based on the previous successful build? -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG 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
Re: [Dev] Clarity tests daily report?
On Tue, Jul 3, 2012 at 9:45 PM, Amila Maha Arachchi ami...@wso2.com wrote: On Tue, Jul 3, 2012 at 7:41 PM, Tharindu Mathew thari...@wso2.com wrote: Shall we have $subject sent to dev@? If this is run on top of a set of successfully built packs, it is meaningless to run it for more than once IMO. May be we should manually run this once when we have a successful build. Yes, I got the $subject wrong. This is what I meant. It is similar to the bamboo mail we get. If bamboo is successful, I'd like to get Clarity tests run and receive a report. This is possibly the only way we can truly automate BAM tests, as BAM needs other servers to be up to properly test end to end. Regards, AmilaM. Are we running Clarity tests daily based on the previous successful build? -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Storing duplicate data in AM DB and governance registry
Hi Hiranya, Some of the meta data related to API is store in both AM DB (AM_API table) and governance registry at org.wso2.carbon.apimgt.impl.APIProviderImpl#addAPI. Is there a reason to persist those data in AM DB rather just manage them only inside the registry? https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/impl/APIProviderImpl.java -- Thanks, Denis -- *Denis Weerasiri* Senior Software Engineer Integration Technologies Team, WSO2 Inc.; http://wso2.com, *email: denis http://goog_277208233/** [AT] wso2.com http://wso2.com/* *phone: +94117639629 * *site: **https://sites.google.com/site/ddweerasiri/*https://sites.google.com/site/ddweerasiri/ *blog: **http://ddweerasiri.blogspot.com* http://ddweerasiri.blogspot.com/ * twitter: **http://twitter.com/ddweerasiri* http://twitter.com/ddweerasiri* linked-in: **http://lk.linkedin.com/in/ddweerasiri*http://lk.linkedin.com/in/ddweerasiri ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] G-REG Test Cycle 2
Hi, We are starting G-REG test cycle 2 from today. Plan is to test and verify JIRAs that we reported during last testing cycle and then proceed to remaining test scenarios. @Senaka and G-REg team, Can we have a new pack which have most fixes. Meanwhile we will proceed with kernal beta2 packs[1]. [1] - http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-JOB1-255/artifachttp://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-JOB1-255/artifact t Thanks, Yumani -- * * * Yumani Ranaweera* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Carbon trunk (revision 131585) branched for API Manager 1.0.0-beta release
Please note branch[1] has been created for API Manager 1.0.0-beta release. [1] https://svn.wso2.org/repos/wso2/branches/apimgt/1.0.0-beta/ -- /sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] G-REG Test Cycle 2
On Wed, Jul 4, 2012 at 9:21 AM, Yumani Ranaweera yum...@wso2.com wrote: Hi, We are starting G-REG test cycle 2 from today. Plan is to test and verify JIRAs that we reported during last testing cycle and then proceed to remaining test scenarios. @Senaka and G-REg team, Can we have a new pack which have most fixes. Meanwhile we will proceed with kernal beta2 packs[1]. [1] - http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-JOB1-255/artifachttp://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-JOB1-255/artifact t Hi Yumani, We have fixed more than 30 issues after the beta2 packs. Therefore, we can use last successful G-Reg pack for second round of testing . [2]http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-262/artifact Thanks Ajith Thanks, Yumani -- * * * Yumani Ranaweera* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Carbon trunk (revision 131585) branched for API Manager 1.0.0-beta release
When is the beta? On Wed, Jul 4, 2012 at 9:29 AM, Sumedha Rubasinghe sume...@wso2.com wrote: Please note branch[1] has been created for API Manager 1.0.0-beta release. [1] https://svn.wso2.org/repos/wso2/branches/apimgt/1.0.0-beta/ -- /sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Carbon trunk (revision 131585) branched for API Manager 1.0.0-beta release
On Wed, Jul 4, 2012 at 10:03 AM, Sumedha Rubasinghe sume...@wso2.comwrote: Plan ( https://wso2.org/jira/browse/APISTORE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel) is to have it by this Friday. When I looked at it this morning, it was something else ;) Also, when is GA? We have laid out plans on C4 this morning, and you guys can sync with those as well as BAM plans. On Wed, Jul 4, 2012 at 9:49 AM, Samisa Abeysinghe sam...@wso2.com wrote: When is the beta? On Wed, Jul 4, 2012 at 9:29 AM, Sumedha Rubasinghe sume...@wso2.comwrote: Please note branch[1] has been created for API Manager 1.0.0-beta release. [1] https://svn.wso2.org/repos/wso2/branches/apimgt/1.0.0-beta/ -- /sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org -- /sumedha +94 773017743 Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Carbon trunk (revision 131585) branched for API Manager 1.0.0-beta release
On Wed, Jul 4, 2012 at 10:28 AM, Samisa Abeysinghe sam...@wso2.com wrote: On Wed, Jul 4, 2012 at 10:03 AM, Sumedha Rubasinghe sume...@wso2.comwrote: Plan ( https://wso2.org/jira/browse/APISTORE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel) is to have it by this Friday. When I looked at it this morning, it was something else ;) ;) .. was bit out of synched... updated little while ago. Also, when is GA? We have laid out plans on C4 this morning, and you guys can sync with those as well as BAM plans. Apart from 6 issues open, we are feature frozen. But we need Carbon, G-Reg, IS, ESB, Jaggery BAM features released. GA date will be discussed during a review meeting scheduled for today. On Wed, Jul 4, 2012 at 9:49 AM, Samisa Abeysinghe sam...@wso2.comwrote: When is the beta? On Wed, Jul 4, 2012 at 9:29 AM, Sumedha Rubasinghe sume...@wso2.comwrote: Please note branch[1] has been created for API Manager 1.0.0-beta release. [1] https://svn.wso2.org/repos/wso2/branches/apimgt/1.0.0-beta/ -- /sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org -- /sumedha +94 773017743 Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org -- /sumedha +94 773017743 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Build Error - Test Failures : jaxws-integration
Running org.apache.axis2.jaxws.proxy.ProxyNonWrappedTests Tests run: 4, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 4.322 sec FAILURE! Running org.apache.axis2.jaxws.dispatch.SOAP12DispatchTest Tests run: 3, Failures: 1, Errors: 2, Skipped: 0, Time elapsed: 1.872 sec FAILURE! Running org.apache.axis2.jaxws.provider.AddressingProviderTests Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.8 sec FAILURE! Running org.apache.axis2.jaxws.sample.HeadersHandlerTests Tests run: 4, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 4.329 sec FAILURE! Running org.apache.axis2.jaxws.xmlhttp.clientTests.dispatch.source.DispatchXMessageSourceTests Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.628 sec FAILURE! Running org.apache.axis2.jaxws.sample.BareTests Tests run: 7, Failures: 2, Errors: 4, Skipped: 0, Time elapsed: 2.312 sec FAILURE! Running org.apache.axis2.jaxws.sample.AddNumbersTests Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 2.02 sec FAILURE! Running org.apache.axis2.jaxws.sample.DocLitBareMinTests Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.008 sec FAILURE! Running org.apache.axis2.jaxws.proxy.GorillaDLWProxyTests Tests run: 10, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 2.454 sec FAILURE! Running org.apache.axis2.jaxws.dispatch.ParamTests Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.513 sec Running org.apache.axis2.jaxws.type_substitution.tests.TypeSubstitutionTests Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.613 sec FAILURE! Running org.apache.axis2.jaxws.handler.header.tests.HandlerTests Tests run: 5, Failures: 2, Errors: 3, Skipped: 0, Time elapsed: 1.873 sec FAILURE! Running org.apache.axis2.jaxws.sample.NonWrapTests Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 4.017 sec FAILURE! Running org.apache.axis2.jaxws.sample.MtomSampleByteArrayTests Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.205 sec FAILURE! Running org.apache.axis2.jaxws.sample.AsyncExecutorTests Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 4.108 sec FAILURE! Running org.apache.axis2.jaxws.dispatch.SOAPMessageDispatchTests Tests run: 3, Failures: 1, Errors: 2, Skipped: 0, Time elapsed: 3.702 sec FAILURE! Running org.apache.axis2.jaxws.jaxb.string.JAXBStringUTF8Tests Tests run: 12, Failures: 12, Errors: 0, Skipped: 0, Time elapsed: 2.496 sec FAILURE! Running org.apache.axis2.jaxws.sample.AddressBookTests Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 1.953 sec FAILURE! Running org.apache.axis2.jaxws.provider.SourceMessageProviderTests Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.755 sec FAILURE! Running org.apache.axis2.jaxws.client.CustomHTTPHeaderTests Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.708 sec FAILURE! Running org.apache.axis2.jaxws.xmlhttp.clientTests.dispatch.source.DispatchXPayloadSourceTests Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.563 sec FAILURE! Running org.apache.axis2.jaxws.dispatch.JAXBDispatchTests Tests run: 6, Failures: 2, Errors: 2, Skipped: 0, Time elapsed: 4.238 sec FAILURE! Running org.apache.axis2.jaxws.provider.SourceProviderTests Tests run: 13, Failures: 4, Errors: 8, Skipped: 0, Time elapsed: 2.373 sec FAILURE! Running org.apache.axis2.jaxws.sample.FaultyWebServiceTests Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 6.728 sec FAILURE! Running org.apache.axis2.jaxws.sample.WrapTests Tests run: 16, Failures: 15, Errors: 0, Skipped: 0, Time elapsed: 2.942 sec FAILURE! Running org.apache.axis2.jaxws.sample.DLWMinTests Tests run: 15, Failures: 5, Errors: 10, Skipped: 0, Time elapsed: 2.594 sec FAILURE! Running org.apache.axis2.jaxws.provider.SoapMessageNullProviderTests Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.689 sec Running org.apache.axis2.jaxws.provider.OMProviderTests Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.935 sec FAILURE! Running org.apache.axis2.jaxws.sample.AddNumbersHandlerTests Tests run: 18, Failures: 12, Errors: 0, Skipped: 0, Time elapsed: 18.893 sec FAILURE! Running org.apache.axis2.jaxws.sample.MTOMFeatureTests Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 1.954 sec FAILURE! Running org.apache.axis2.jaxws.provider.soapbinding.tests.SOAPBindingProviderTests Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 1.639 sec FAILURE! Running org.apache.axis2.jaxws.dispatch.JAXBSourceDispatchTests Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.677 sec Running org.apache.axis2.jaxws.jaxb.string.JAXBStringUTF16Tests Tests run: 12, Failures: 12, Errors: 0, Skipped: 0, Time elapsed: 2.293 sec FAILURE! Running org.apache.axis2.jaxws.sample.ResourceInjectionTests Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.738 sec FAILURE! Running
Re: [Dev] Clarity tests daily report?
Hi Tharindu, It is possible to send a report to dev@ for successful product build by running Clarity framework. As we are engaged with few other high priority tasks, will add this to automation future plans. Thanks, Krishantha. On Tue, Jul 3, 2012 at 10:43 PM, Tharindu Mathew thari...@wso2.com wrote: On Tue, Jul 3, 2012 at 9:45 PM, Amila Maha Arachchi ami...@wso2.comwrote: On Tue, Jul 3, 2012 at 7:41 PM, Tharindu Mathew thari...@wso2.comwrote: Shall we have $subject sent to dev@? If this is run on top of a set of successfully built packs, it is meaningless to run it for more than once IMO. May be we should manually run this once when we have a successful build. Yes, I got the $subject wrong. This is what I meant. It is similar to the bamboo mail we get. If bamboo is successful, I'd like to get Clarity tests run and receive a report. This is possibly the only way we can truly automate BAM tests, as BAM needs other servers to be up to properly test end to end. Regards, AmilaM. Are we running Clarity tests daily based on the previous successful build? -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ 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] Carbon 4 Kernel Release Plans
Hi all, Please note that we will be releasing orbits as planned this week - 06th July Friday. We are planning for Carbon 4 Kernel RC1 to be on 20th July. Until that we will be iteratively fixing and putting beta releases. C4 release is going to be on 27th July. Thanks, dimuthu ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
