date:20120117

Re: [Carbon-dev] Microsft excel adapters

2012-01-17 Thread Sumedha Rubasinghe

On Wed, Jan 18, 2012 at 12:59 PM, Sanjiva Weerawarana wrote:

> Don't we have a feature in DS to support this? We have it for Google docs
> ..


Dinusha has replied saying so at the top. Anjana will reply pointing to
sample.
/sumedha

>
>
> On Tue, Jan 17, 2012 at 10:06 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Tue, Jan 17, 2012 at 2:20 PM,  wrote:
>>
>>>  Hi 
>>>
>>> ** **
>>>
>>> I am in a scenario where I need to extract and push data from Excel
>>> Sheets. I preferred wso2 for this. In what way WSO2 ESB supports this. You
>>> have any specific adapter for this?
>>>
>>
>> You can use VFS transport with a custom message builder to read Excel
>> sheets.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>  
>>>
>>> ** **
>>>
>>> Please help out.
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> Regards
>>>
>>> Guru
>>>
>>> * Please do not print this email unless it is absolutely necessary. 
>>> *
>>>
>>> The information contained in this electronic message and any attachments
>>> to this message are intended for the exclusive use of the addressee(s) and
>>> may contain proprietary, confidential or privileged information. If you are
>>> not the intended recipient, you should not disseminate, distribute or copy
>>> this e-mail. Please notify the sender immediately and destroy all copies of
>>> this message and any attachments.
>>>
>>> WARNING: Computer viruses can be transmitted via email. The recipient
>>> should check this email and any attachments for the presence of viruses.
>>> The company accepts no liability for any damage caused by any virus
>>> transmitted by this email.
>>>
>>> www.wipro.com
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Associate Technical Lead;
>> 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
>> http://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: +94 11 763 9614; 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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
/sumedha
+94 773017743
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Microsft excel adapters

2012-01-17 Thread Anjana Fernando

Hi Sanjiva,

On Wed, Jan 18, 2012 at 12:59 PM, Sanjiva Weerawarana wrote:

> Don't we have a feature in DS to support this? We have it for Google docs
> ..


Yes, as Dinusha mentioned in her reply, we do have the feature in data
services. The user guide section for Excel data source can be found here
[1], and also a sample at [2].

[1] http://wso2.org/project/data-services/2.6.3/docs/excel.html
[2]
http://wso2.org/project/data-services/2.6.3/docs/samples/excel_sample.html

Cheers,
Anjana.


>
> On Tue, Jan 17, 2012 at 10:06 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Tue, Jan 17, 2012 at 2:20 PM,  wrote:
>>
>>>  Hi 
>>>
>>> ** **
>>>
>>> I am in a scenario where I need to extract and push data from Excel
>>> Sheets. I preferred wso2 for this. In what way WSO2 ESB supports this. You
>>> have any specific adapter for this?
>>>
>>
>> You can use VFS transport with a custom message builder to read Excel
>> sheets.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>  
>>>
>>> ** **
>>>
>>> Please help out.
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> Regards
>>>
>>> Guru
>>>
>>> * Please do not print this email unless it is absolutely necessary. 
>>> *
>>>
>>> The information contained in this electronic message and any attachments
>>> to this message are intended for the exclusive use of the addressee(s) and
>>> may contain proprietary, confidential or privileged information. If you are
>>> not the intended recipient, you should not disseminate, distribute or copy
>>> this e-mail. Please notify the sender immediately and destroy all copies of
>>> this message and any attachments.
>>>
>>> WARNING: Computer viruses can be transmitted via email. The recipient
>>> should check this email and any attachments for the presence of viruses.
>>> The company accepts no liability for any damage caused by any virus
>>> transmitted by this email.
>>>
>>> www.wipro.com
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Associate Technical Lead;
>> 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
>> http://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: +94 11 763 9614; 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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Anjana Fernando*
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Bamboo scheduled build for trunk will be not available today.

2012-01-17 Thread Krishantha Samaraweera

Hi Charith,

Will let you know once we finish with test framework deployment.

Thanks,
Krishantha.

On Wed, Jan 18, 2012 at 11:52 AM, Charith Wickramarachchi
wrote:

> Hi ,
>
> I've disabled the Bamboo scheduled build for trunk till we get the
> Automation test to work with the trunk .
>
> thanks,
> Charith
>
> --
> Charith Dhanushka Wickramarachchi
> Software Engineer
> WSO2 Inc
> http://wso2.com/
> http://wso2.org/
>
> blog
> http://charithwiki.blogspot.com/
>
> twitter
> http://twitter.com/charithwiki
>
> Mobile : 0776706568
>
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] system test framework and product integration tests

2012-01-17 Thread Krishantha Samaraweera

Your are correct. We came across the same issue when designing the
framework. Since system tests runs with different configurations (e.g with
registry mounts and different DBs) we need to run all most all
product integration tests on top of product platform as well. We can not
directly have dependencies to product integration tests because of the way
we have written those tests. And, The tests architecture is also differ. We
have written the system-test-framework to address the distributed nature of
a platform deployment. Currently as what we can do is to duplicate
integration tests inside system tests. May be in future we can find a
better way to do it.

Thanks,
Krishantha.

On Wed, Jan 18, 2012 at 10:57 AM, KasunG Gajasinghe  wrote:

>  I have a little question about System-Test-Framework. Does the objective
 of it is to complement the integration tests of products,
 or will it be integrated in to the product integration tests in future?

>>>
>>> What current integration test does is test the individual components
>>> combined and grouped into a so called product. It doesn't have platform
>>> wide tests cases. For an example, It doesn't test a scenario run on ESB,
>>> BPS and G-Reg with registry mounts and clustering. What we does in
>>> system-test-framework is test the platform as a whole.
>>>
>>
>>> Nope system-test-framework will not be integrated in to integration
>>> tests.
>>>
>>
>> Understood. But, talking from viewpoint of AS, it seems that the boundary
>> of this framework's tests and product intg tests is somewhat blur. For
>> example, AS needs to test the security scenarios of Axis2 services
>> something which also done by the system-test-framework. May be we need to
>> come to a common ground on this.
>>
>
>
>
> We are going off the topic here. Lets discuss this on carbon-dev. Please
>> ask all the question you have in there.
>
>
> +1. forwarded to carbon-dev.
>
>
>> Thanks,
>> --KasunG
>>
>>
>>>
>>> Thanks,
>>> Krishantha.
>>>
>>>
>>>

 I'm asking this because I feel like things may get duplicated between
 product integration tests, and STF!

 Thanks,
 --KasunG


>
> Thanks,
> Krishantha.
>



 --
 *Kasun Gajasinghe*
 Software Engineer; WSO2 Inc.; http://wso2.com

 ,
 *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
 *blog: **http://blog.kasunbg.org* 

 *
 twitter: **http://twitter.com/kasunbg* 

 *
 *


>>>
>>
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer; WSO2 Inc.; http://wso2.com
>>
>> ,
>> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
>> *blog: **http://blog.kasunbg.org* 
>>
>> *
>> twitter: **http://twitter.com/kasunbg* 
>>
>> *
>> *
>>
>>
>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer; WSO2 Inc.; http://wso2.com
>
> ,
> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
> *blog: **http://blog.kasunbg.org* 
>
> *
> twitter: **http://twitter.com/kasunbg* 
>
> *
> *
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Microsft excel adapters

2012-01-17 Thread Sanjiva Weerawarana

Don't we have a feature in DS to support this? We have it for Google docs ..

On Tue, Jan 17, 2012 at 10:06 PM, Hiranya Jayathilaka wrote:

>
>
> On Tue, Jan 17, 2012 at 2:20 PM,  wrote:
>
>>  Hi 
>>
>> ** **
>>
>> I am in a scenario where I need to extract and push data from Excel
>> Sheets. I preferred wso2 for this. In what way WSO2 ESB supports this. You
>> have any specific adapter for this?
>>
>
> You can use VFS transport with a custom message builder to read Excel
> sheets.
>
> Thanks,
> Hiranya
>
>
>>  
>>
>> ** **
>>
>> Please help out.
>>
>> ** **
>>
>> ** **
>>
>> Regards
>>
>> Guru
>>
>> * Please do not print this email unless it is absolutely necessary. *
>>
>> The information contained in this electronic message and any attachments
>> to this message are intended for the exclusive use of the addressee(s) and
>> may contain proprietary, confidential or privileged information. If you are
>> not the intended recipient, you should not disseminate, distribute or copy
>> this e-mail. Please notify the sender immediately and destroy all copies of
>> this message and any attachments.
>>
>> WARNING: Computer viruses can be transmitted via email. The recipient
>> should check this email and any attachments for the presence of viruses.
>> The company accepts no liability for any damage caused by any virus
>> transmitted by this email.
>>
>> www.wipro.com
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Associate Technical Lead;
> 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
> http://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: +94 11 763 9614; 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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Test failure in dependencies/commons/xmlschema/1.4.7-wso2v1

2012-01-17 Thread Denis Weerasiri

On Wed, Jan 18, 2012 at 12:08 PM, Thilini Ishaka  wrote:

>
>
> On Wed, Jan 18, 2012 at 11:20 AM, Denis Weerasiri  wrote:
>
>> Hi,
>> Does anyone having this test-case failure in trunk/dependencies?
>>
>
> This test passed. Having no issue.
>
Thanks Thilini,
Harshana and I had the same test failure.
What's the JDK do you use?

>
>
>>
>> ---
>> Test set: tests.customext.attrib.CustomExtensionSerializerTest
>>
>> ---
>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
>> <<< FAILURE!
>> testSerialization(tests.customext.attrib.CustomExtensionSerializerTest)
>>  Time elapsed: 0.01 sec  <<< FAILURE!
>> junit.framework.AssertionFailedError
>> at junit.framework.Assert.fail(Assert.java:47)
>> at junit.framework.Assert.assertTrue(Assert.java:20)
>>  at junit.framework.Assert.assertNotNull(Assert.java:217)
>> at junit.framework.Assert.assertNotNull(Assert.java:210)
>>  at
>> tests.customext.attrib.CustomExtensionSerializerTest.testSerialization(CustomExtensionSerializerTest.java:80)
>>
>>
>> --
>> Thanks,
>> Denis
>> --
>> *Denis Weerasiri*
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> *email: denis ** [AT] wso2.com 
>> *
>> *phone: +94117639629
>> *
>> *site: 
>> **https://sites.google.com/site/ddweerasiri/*
>> *blog: **http://ddweerasiri.blogspot.com*
>> *
>> twitter: **http://twitter.com/ddweerasiri*
>> *
>> linked-in: 
>> **http://lk.linkedin.com/in/ddweerasiri*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Regards
>
> Thilini Ishaka
> WSO2 Inc
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thanks,
Denis
--
*Denis Weerasiri*
Software Engineer; WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com *
*phone: +94117639629
*
*site: 
**https://sites.google.com/site/ddweerasiri/*
*blog: **http://ddweerasiri.blogspot.com* 
*
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Test failure in dependencies/commons/xmlschema/1.4.7-wso2v1

2012-01-17 Thread Thilini Ishaka

On Wed, Jan 18, 2012 at 11:20 AM, Denis Weerasiri  wrote:

> Hi,
> Does anyone having this test-case failure in trunk/dependencies?
>

This test passed. Having no issue.


>
> ---
> Test set: tests.customext.attrib.CustomExtensionSerializerTest
>
> ---
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
> <<< FAILURE!
> testSerialization(tests.customext.attrib.CustomExtensionSerializerTest)
>  Time elapsed: 0.01 sec  <<< FAILURE!
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
>  at junit.framework.Assert.assertNotNull(Assert.java:217)
> at junit.framework.Assert.assertNotNull(Assert.java:210)
>  at
> tests.customext.attrib.CustomExtensionSerializerTest.testSerialization(CustomExtensionSerializerTest.java:80)
>
>
> --
> Thanks,
> Denis
> --
> *Denis Weerasiri*
> Software Engineer; WSO2 Inc.; http://wso2.com,
> *email: denis ** [AT] wso2.com *
> *phone: +94117639629
> *
> *site: 
> **https://sites.google.com/site/ddweerasiri/*
> *blog: **http://ddweerasiri.blogspot.com*
> *
> twitter: **http://twitter.com/ddweerasiri*
> *
> linked-in: 
> **http://lk.linkedin.com/in/ddweerasiri*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Regards

Thilini Ishaka
WSO2 Inc
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Templates for Carbon Components and Features

2012-01-17 Thread Chethiya Abeysinghe

Hi,

I've drafted an OT article. Meanwhile it get published, you can try out the
carbon-template wizard plugin following these instructions:

*1. install and configure mvn in your system. Try running mvn --version at
command prompt to verify.

2. You have to copy following settings to settings.xml in your local maven
repo at,

   - ~/.m2/settings.xml - in Unix systems (Linux, Mac OS X)
   - C:\Users\$USER$\.m2\settings.xml  - Wndows 7 / Vista
   - C:\Document and Settings\$USER$\.m2\settings.xml  -  Windows XP



This is one time process. Once you add these settings to your settings.xml
you don’t have to do it every time you run the plugin. *

http://maven.apache.org/SETTINGS/1.0.0";
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
  http://maven.apache.org/xsd/settings-1.0.0.xsd";>

 
org.wso2.carbon
 
  
   
  carbon plugin
 
true
 
  
   
http://maven.wso2.org/nexus/content/repositories/wso2archtype/archetype-catalog.xml

  
 

 carbon-plugin-repo
  carbon nexus Repository
 http://maven.wso2.org/nexus/content/repositories/wso2archtype


 
  
   
  carbon-repo
 carbon Nexus Repository
  http://maven.wso2.org/nexus/content/repositories/wso2archtype

  
   true
  
   
  
   
  



3. Once you are done with settings, you are ready to run the
carbon-template wizard maven plugin. You just have to change directory at
the command prompt wherever you want to create the new project and hit
follow command.

mvn org.wso2.carbon:carbon-template:generate -U

Then provide the necessary parameters to create the project. Further
details will be elaborated in the article.


Thanks,
 - Chethiya

On Mon, Jan 16, 2012 at 1:27 PM, Srinath Perera  wrote:

> ah got it ... --Srinath
>
> On Mon, Jan 16, 2012 at 12:19 PM, Chethiya Abeysinghe 
> wrote:
> >
> > On Mon, Jan 16, 2012 at 11:11 AM, Srinath Perera 
> wrote:
> >>
> >> article should point to samples .. either at SVN or as downloadable  ..
> >
> >
> > The maven plugin will be hosted in a nexus repo. Therefore no need to
> > download the carbon-template project. Once adding repo details to
> > ~/.m2/settings.xml file, the plugin can be used similar to
> > archetype:generate.. Command will be something like,
> > mvn org.wso2.carbon:carbon-template:generate
> >
> >>
> >>
> >>
> >> SVN might be better
> >>
> >> --Srinath
> >>
> >> On Fri, Jan 13, 2012 at 4:56 PM, Dasunpriya Anuradha  >
> >> wrote:
> >> > Even you can attach samples (if any) as compress files to your OT
> >> > article
> >> > itself.
> >> >
> >> > Thanks.
> >> >
> >> >
> >> > On Fri, Jan 13, 2012 at 4:46 PM, Chethiya Abeysinghe <
> cheth...@wso2.com>
> >> > wrote:
> >> >>
> >> >>
> >> >>
> >> >> On Fri, Jan 13, 2012 at 4:22 PM, Srinath Perera 
> >> >> wrote:
> >> >>>
> >> >>> We should check this in to our SVN .. and maintain in the future
> >> >>
> >> >>
> >> >> +1. And I expect people to try out this template with their real life
> >> >> requirements and provide feedback on critical changes to be done
> before
> >> >> deploying it with masses.
> >> >>
> >> >>>
> >> >>> Chethiya, can you write a OT article describing how to use these
> >> >>> templates?
> >> >>
> >> >>
> >> >> +1. I'll start working on it with the options we have now.
> >> >>
> >> >>
> >> >> Thanks,
> >> >>  - Chethiya
> >> >>
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Fri, Jan 13, 2012 at 3:57 PM, Chethiya Abeysinghe
> >> >>> 
> >> >>> wrote:
> >> >>> > Hi,
> >> >>> >
> >> >>> > I've extended above, including service-stubs, features and
> >> >>> > repository
> >> >>> > along
> >> >>> > with the already existing backend-end and front-end carbon
> >> >>> > component.
> >> >>> > Therefore, any project you create using this new template will be
> an
> >> >>> > all-in-one package where you can run off the shelf at somewhere
> like
> >> >>> > application server. You just have to do a 'mvn clean install' in
> the
> >> >>> > created
> >> >>> > project and install the created feature using the repository.
> >> >>> >
> >> >>> > Here are the instruction to use the new template. Note that it's
> not
> >> >>> > archetype anymore, I've created a maven plugin to overcome some
> >> >>> > limitation
> >> >>> > of archetype with folder naming and parameter formatting, and now
> it
> >> >>> > got
> >> >>> > great deal of customizability.
> >> >>> >
> >> >>> > 1. Extract the attachment and do a 'mvn clean install' within the
> >> >>> > 'carbon-template' folder.
> >> >>> > 2. Go to the place you want to create the project and then hit
> >> >>> > 'mvn org.wso2.carbon:carbon-template:1.0.0-SNAPSHOT:generate'
> >> >>> > 3. Provide the necessary parameters (artifactId, groupId, etc)...
> >> >>> > This
> >> >>> > runs
> >> >>> > in interactive mode. But should be possible to run in
> >> >>> > non-interactive
> >> >>> > mode
> >> >>> > also

[Carbon-dev] Bamboo scheduled build for trunk will be not available today.

2012-01-17 Thread Charith Wickramarachchi

Hi ,

I've disabled the Bamboo scheduled build for trunk till we get the
Automation test to work with the trunk .

thanks,
Charith

-- 
Charith Dhanushka Wickramarachchi
Software Engineer
WSO2 Inc
http://wso2.com/
http://wso2.org/

blog
http://charithwiki.blogspot.com/

twitter
http://twitter.com/charithwiki

Mobile : 0776706568
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Test failure in dependencies/commons/xmlschema/1.4.7-wso2v1

2012-01-17 Thread Denis Weerasiri

Hi,
Does anyone having this test-case failure in trunk/dependencies?

---
Test set: tests.customext.attrib.CustomExtensionSerializerTest
---
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
<<< FAILURE!
testSerialization(tests.customext.attrib.CustomExtensionSerializerTest)
 Time elapsed: 0.01 sec  <<< FAILURE!
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
 at junit.framework.Assert.assertNotNull(Assert.java:217)
at junit.framework.Assert.assertNotNull(Assert.java:210)
 at
tests.customext.attrib.CustomExtensionSerializerTest.testSerialization(CustomExtensionSerializerTest.java:80)


-- 
Thanks,
Denis
--
*Denis Weerasiri*
Software Engineer; WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com *
*phone: +94117639629
*
*site: 
**https://sites.google.com/site/ddweerasiri/*
*blog: **http://ddweerasiri.blogspot.com* 
*
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Issue in ESB Smooks Mediator Streaming Improvements

2012-01-17 Thread Lakmali Baminiwatta

Hi,

I am working on enabling streaming xml events from OMElement inside ESB
Smooks Mediator. This is to process large messages through Smooks mediator.
Previously Smooks mediator used to build the message envelop as
*synCtx.getEnvelope().build()
*(synCtx is the MessageContext ) before processing the message. Since it
builds the element inside memory, I removed that step.

I used to test the new streaming implementation with two scenarios.

Scenario 1 :- Input message is read from the VFS transport, and streamed to
Smooks mediator. Inside that message is processed by smooks and child
elements from the MessageContext is detached & transformed element it added
to MessageContext. This worked successfully. The ESB configuration sequence
is,









Scenario 2 :- A proxy service to a DSS endpoint and its response is
processed by smooks mediator in outSequence.

   http://localhost:9765/services/OrderDetails"; />


   


   
   
  

After smooks processing the message, the child elements from the
MessageContext envelop is detached and new transformed message is added.
But when iterating through the MessageContext and calling next(),
OMException is thrown as follows.

*org.apache.axiom.om.OMException
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:212)
at
org.apache.axiom.soap.impl.llom.SOAPBodyImpl.buildNext(SOAPBodyImpl.java:171)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.getNextOMSibling(OMNodeImpl.java:122)
at
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:343)
at
org.apache.axiom.om.impl.traverse.OMChildElementIterator.next(OMChildElementIterator.java:104)
at
org.wso2.carbon.mediator.transform.Output.setXMLPayload(Output.java:208)
at org.wso2.carbon.mediator.transform.Output.process(Output.java:84)
at
org.wso2.carbon.mediator.transform.SmooksMediator.mediate(SmooksMediator.java:94)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:219)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:370)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:160)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:275)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)*

The issue is why only the second scenario can not access the MessageContext
after smooks has processed the message. Adding back the
*synCtx.getEnvelope().build()
*solves this issue, but large messages can not be processed that way. Can
anybody kindly look into this issue and explain why is it required to build
up the message?

Thanks,
Lakmali


-- 
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Bootup self test component for carbon

2012-01-17 Thread Dileepa Jayakody

Hi all,

As per the offline discussion had with Pradeep and Azeez few days back, I
have implemented the bootup-validator component's framework to be
extensible.

The component can be extended with new bootup validation tests by adding
new ConfigurationValidator classes with relevant parameters to validate; in
the config_recommendations.xml (the newly introduced xml in repository/conf)

A sample config_recommendations.xml:

800
1000

6000
4000
1
2000

The system data collection can also be extended in the same manner.
At the moment I'm having trouble with Sigar API to retrieve HW
configuration data (CPU, RAM), will update the thread with progress.

Thanks,
Dileepa

On Fri, Jan 13, 2012 at 1:01 PM, Pradeep Fernando  wrote:

> Hi,
>
> are we going to allow users to implement their own bootup tests, using
> somekind of extension mechanism. (we are providing all the gathered info,
> they decide on what to do with those). Is it a overkill ?
>
> are we doing any native calls within the carbon-env (Now). ?
>
> thanks,
> --Pradeep
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

-- 
Dileepa Jayakody,
Software Engineer, WSO2 Inc.
Lean . Enterprise . Middleware

Mobile : +94777-857616
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #129 was SUCCESSFUL (with 7598 tests). Change made by rajika.

2012-01-17 Thread Bamboo


---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #129 was successful.
---
Code has been updated by rajika.
7598 tests in total.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-129/


--
Code Changes
--
rajika (119117):

>Updated the admin service.

rajika (119118):

>Fixed move between manual and automatic.



--
This message is automatically generated by Atlassian Bamboo___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] system test framework and product integration tests

2012-01-17 Thread KasunG Gajasinghe

>
>  I have a little question about System-Test-Framework. Does the objective
>>> of it is to complement the integration tests of products,
>>> or will it be integrated in to the product integration tests in future?
>>>
>>
>> What current integration test does is test the individual components
>> combined and grouped into a so called product. It doesn't have platform
>> wide tests cases. For an example, It doesn't test a scenario run on ESB,
>> BPS and G-Reg with registry mounts and clustering. What we does in
>> system-test-framework is test the platform as a whole.
>>
>
>> Nope system-test-framework will not be integrated in to integration tests.
>>
>
> Understood. But, talking from viewpoint of AS, it seems that the boundary
> of this framework's tests and product intg tests is somewhat blur. For
> example, AS needs to test the security scenarios of Axis2 services
> something which also done by the system-test-framework. May be we need to
> come to a common ground on this.
>



We are going off the topic here. Lets discuss this on carbon-dev. Please
> ask all the question you have in there.


+1. forwarded to carbon-dev.


> Thanks,
> --KasunG
>
>
>>
>> Thanks,
>> Krishantha.
>>
>>
>>
>>>
>>> I'm asking this because I feel like things may get duplicated between
>>> product integration tests, and STF!
>>>
>>> Thanks,
>>> --KasunG
>>>
>>>

 Thanks,
 Krishantha.

>>>
>>>
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>>
>>> ,
>>> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
>>> *blog: **http://blog.kasunbg.org* 
>>>
>>> *
>>> twitter: **http://twitter.com/kasunbg* 
>>>
>>> *
>>> *
>>>
>>>
>>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer; WSO2 Inc.; http://wso2.com
>
> ,
> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
> *blog: **http://blog.kasunbg.org* 
>
> *
> twitter: **http://twitter.com/kasunbg* 
>
> *
> *
>
>



-- 
*Kasun Gajasinghe*
Software Engineer; WSO2 Inc.; http://wso2.com

,
*email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
*blog: **http://blog.kasunbg.org* 

*
twitter: **http://twitter.com/kasunbg* 

*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #128 was SUCCESSFUL (with 7598 tests). Change made by 4 authors.

2012-01-17 Thread Bamboo


---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #128 was successful.
---
Code has been updated by krishantha, rajika, manjular, deep.
7598 tests in total.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-128/


--
Code Changes
--
manjular (119114):

>Updating passive sts documentations in context sensitive help pages

deep (119097):

>HDFS Name Node
>

rajika (119109):

>Added the initial logic for auto-matic publishing.



--
Tests
--
Fixed Tests (1)
   - ServerAdminTestCase: Retrieve server info

--
This message is automatically generated by Atlassian Bamboo___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #127 has FAILED (1 tests failed). Change made by 5 authors.

2012-01-17 Thread Bamboo


---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #127 failed.
---
Code has been updated by janaka, supunm, amila, sanjayav, lalaji.
1/7599 tests failed.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-127/


--
Failing Jobs
--
  - WSO2 Carbon Trunk Build Process (Default Stage): 1 of 7599 tests failed.


--
Code Changes
--
amila (119094):

>apply the patch for CARBON-12203

janaka (119085):

>Adding fix for CARBON-11429
>

sanjayav (119089):

>Fixed carbon port offset value not being considered at humant task server 
>config initialization.



--
Tests
--
New Test Failures (1)
   - ServerAdminTestCase: Retrieve server info
Fixed Tests (1)
   - TestRuleSet: Rule set

--
This message is automatically generated by Atlassian Bamboo___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] can i add to controls like innodb constraint with dbs on data services server

2012-01-17 Thread Anjana Fernando

Hi Ercan,

On Tue, Jan 17, 2012 at 8:11 PM, Ercan Can  wrote:

> Hi all, i have a mysql database with innodb engine. i must to change
> database engine set to ndbcluster. In this case, i lost primary key and
> foreing key relation. So, can i make relation between tables with dbs on
> dss server? Thanks.
>

We don't really have any special inbuilt support for defining/foreign key
constraints like that, if that requirement is a must, what you can do is,
create a custom validator [1] to check the input values to see if they meet
the necessary constraints, for example, too see if a specific input
parameter is existent, in another table's primary key and so on. This would
require to write some JDBC code in the custom validator though.

[1] http://wso2.org/project/data-services/2.6.3/docs/validation.html#custom

Cheers,
Anjana.

>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

-- 
*Anjana Fernando*
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Microsft excel adapters

2012-01-17 Thread Hiranya Jayathilaka

On Tue, Jan 17, 2012 at 2:20 PM,  wrote:

>  Hi 
>
> ** **
>
> I am in a scenario where I need to extract and push data from Excel
> Sheets. I preferred wso2 for this. In what way WSO2 ESB supports this. You
> have any specific adapter for this?
>

You can use VFS transport with a custom message builder to read Excel
sheets.

Thanks,
Hiranya


> 
>
> ** **
>
> Please help out.
>
> ** **
>
> ** **
>
> Regards
>
> Guru
>
> * Please do not print this email unless it is absolutely necessary. *
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Hiranya Jayathilaka
Associate Technical Lead;
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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Microsft excel adapters

2012-01-17 Thread Dinusha Senanayaka

Hi Guru,

On Tue, Jan 17, 2012 at 2:20 PM,  wrote:

>  Hi 
>
> ** **
>
> I am in a scenario where I need to extract and push data from Excel
> Sheets. I preferred wso2 for this. In what way WSO2 ESB supports this. You
> have any specific adapter for this?
>

ESB does not contain inbuilt feature to do this. But you can write your own
Custom mediator to achieve this through ESB.  Rather writing a custom
mediator, WSO2 Data Services Server itself contains inbuilt feature to use
Excel as a data-source and extract the data. So you can use either WSO2 DSS
product or you can install data-services feature within ESB and use it from
there.

Regards,
Dinusha.

> 
>
> ** **
>
> Please help out.
>
> ** **
>
> ** **
>
> Regards
>
> Guru
>
> * Please do not print this email unless it is absolutely necessary. *
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] can i add to controls like innodb constraint with dbs on data services server

2012-01-17 Thread Ercan Can

Hi all, i have a mysql database with innodb engine. i must to change database 
engine set to ndbcluster. In this case, i lost primary key and foreing key 
relation. So, can i make relation between tables with dbs on dss server? Thanks.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Build failure in service-stubs/ under Maven 3

2012-01-17 Thread Buddhika Chamith

We can use -N option to skip building sub projects.

-N,--non-recursive Do not recurse into sub-projects

Regards
Buddhika

On Tue, Jan 17, 2012 at 7:06 PM, KasunG Gajasinghe  wrote:

>
>
> On Tue, Jan 17, 2012 at 6:21 PM, Subash Chaturanga wrote:
>
>> Hi ,
>> Today i got a full trunk update and got a build failure when building
>> service stubs which is $subject .
>>
>
> Hi Subash,
> The conclusion we came up was that either trunk should be built from root,
> or you need to manually copy the carbon-platform pom to the relevant
> directory in M2 repo. I think this issue was surfaced again because the
> trunk project.version got  upgraded to 4.0.0-SNAPSHOT from 3.2.0-SNAPSHOT.
>
> Regards,
> --KasunG
>
>
>>
>> Here is the error log.
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 1.972s
>> [INFO] Finished at: Tue Jan 17 17:55:50 IST 2012
>> [INFO] Final Memory: 18M/490M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project service-stubs: Could not
>> resolve dependencies for project
>> org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT: Failed to collect
>> dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2 (compile),
>> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
>> org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
>> org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
>> commons-logging:commons-logging:jar:1.1.1 (compile),
>> org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1 (compile)]: Failed
>> to read artifact descriptor for
>> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4: Failure to find
>> org.wso2.carbon:carbon-platform:pom:4.0.0-SNAPSHOT in
>> http://maven.wso2.org/nexus/content/groups/wso2-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 -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal on project service-stubs: Could not resolve dependencies for project
>> org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT: Failed to collect
>> dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2 (compile),
>> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
>> org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
>> org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
>> commons-logging:commons-logging:jar:1.1.1 (compile),
>> org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1 (compile)]
>>  at
>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:196)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:108)
>>  at
>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>  at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>  at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>  at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>  at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>  at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>  at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>  at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>> Caused by: org.apache.maven.project.DependencyResolutionException: Could
>> not resolve dependencies for project
>> org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT: Failed to collect
>> dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2 (compile),
>> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (comp

Re: [Carbon-dev] Build failure in service-stubs/ under Maven 3

2012-01-17 Thread Lahiru Sandaruwan

Got the same error. Building from root solved the problem.

On Tue, Jan 17, 2012 at 7:20 PM, Afkham Azeez  wrote:
> If pom relative paths are properly defined, you will not see this error
>
> --
> Afkham Azeez
> Sent from my phone
>
> On Jan 17, 2012 6:36 PM, "KasunG Gajasinghe"  wrote:
>>
>>
>>
>> On Tue, Jan 17, 2012 at 6:21 PM, Subash Chaturanga 
>> wrote:
>>>
>>> Hi ,
>>> Today i got a full trunk update and got a build failure when building
>>> service stubs which is $subject .
>>
>>
>> Hi Subash,
>> The conclusion we came up was that either trunk should be built from root,
>> or you need to manually copy the carbon-platform pom to the relevant
>> directory in M2 repo. I think this issue was surfaced again because the
>> trunk project.version got  upgraded to 4.0.0-SNAPSHOT from 3.2.0-SNAPSHOT.
>>
>> Regards,
>> --KasunG
>>
>>>
>>>
>>> Here is the error log.
>>>
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 1.972s
>>> [INFO] Finished at: Tue Jan 17 17:55:50 IST 2012
>>> [INFO] Final Memory: 18M/490M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal on project service-stubs: Could not
>>> resolve dependencies for project
>>> org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT: Failed to collect
>>> dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2 (compile),
>>> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
>>> org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
>>> org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
>>> commons-logging:commons-logging:jar:1.1.1 (compile),
>>> org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1 (compile)]: Failed
>>> to read artifact descriptor for
>>> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4: Failure to find
>>> org.wso2.carbon:carbon-platform:pom:4.0.0-SNAPSHOT in
>>> http://maven.wso2.org/nexus/content/groups/wso2-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 -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>> goal on project service-stubs: Could not resolve dependencies for project
>>> org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT: Failed to collect
>>> dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2 (compile),
>>> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
>>> org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
>>> org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
>>> commons-logging:commons-logging:jar:1.1.1 (compile),
>>> org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1 (compile)]
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:196)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:108)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>>> Caused by: org.apache.maven.project.DependencyResolutionException: Could
>>> not resolve dependencies for proje

[Carbon-dev] Event broker is registered after the message "WSO2 Carbon started in ...." when starting DSS in trunk build

2012-01-17 Thread Nuwan Wimalasekara

Hi
There is a issue in server start up sequence. even if message is log
"WSO2 Carbon started in 38 sec". HTTPS port is not listening until event
broker is registered. that scenario found with carbon trunk build.
it takes 3 to 6 seconds to up HTTPS port after message "WSO2 Carbon started
in 38 sec".

Environment : wso2dataservices-2.6.0-SNAPSHOT

Refer : https://wso2.org/jira/browse/CARBON-12227


Server log:

[2012-01-17 11:09:36,423]  INFO {org.quartz.impl.StdSchedulerFactory} -
 Quartz scheduler 'DefaultQuartzScheduler' initialized from default
resource file in Quartz package: 'quartz.properties'
[2012-01-17 11:09:36,423]  INFO {org.quartz.impl.StdSchedulerFactory} -
 Quartz scheduler version: 2.1.1
[2012-01-17 11:09:36,423]  INFO {org.quartz.core.QuartzScheduler} -
 Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
[2012-01-17 11:09:36,641]  INFO
{org.wso2.carbon.ntask.core.internal.TasksDSComponent} -  Task service
started
[2012-01-17 11:09:36,892]  INFO
{org.wso2.carbon.core.init.CarbonServerManager} -
 ConfigurationContextService registered in 591ms
[2012-01-17 11:09:36,905]  INFO
{org.wso2.carbon.core.transports.http.HttpsTransportListener} -  HTTPS port
  : 9446
[2012-01-17 11:09:36,905]  INFO
{org.wso2.carbon.core.transports.http.HttpTransportListener} -  HTTP port
 : 9766
[2012-01-17 11:09:37,124]  INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Started
Transport Listener Manager
[2012-01-17 11:09:37,124]  INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Server
  :  WSO2 Data Services Server-2.6.0-SNAPSHOT
[2012-01-17 11:09:37,125]  INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  WSO2
Carbon started in 34 sec
[Broker] BRK-1006 : Using configuration :
/home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
[2012-01-17 11:09:39,555]  INFO {qpid.message.broker.listening} -  [Broker]
BRK-1002 : Starting : Listening on TCP port 5675
[2012-01-17 11:09:39,558]  INFO {qpid.message.broker.listening} -  [Broker]
BRK-1002 : Starting : Listening on TCP/SSL port 8675
[2012-01-17 11:09:39,559]  INFO
{org.wso2.carbon.qpid.internal.QpidServiceComponent} -  Successfully
connected to the server on port 5675
[2012-01-17 11:09:39,784]  INFO
{org.wso2.carbon.registry.eventing.internal.RegistryEventingServiceComponent}
-  Successfully Initialized Eventing on Registry
[2012-01-17 11:09:39,801]  INFO
{org.wso2.carbon.event.core.internal.builder.EventBrokerHandler} -
 Successfully registered the event broker
[2012-01-17 11:09:40,056]  INFO
{org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
 : https://10.100.3.39:9446/carbon/


Thanks
NuwanW

--
Nuwan Wimalasekara
Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #126 has FAILED (1 tests failed, no failures were new). Change made by janaka, dimuthul and buddhikac.

2012-01-17 Thread Bamboo


---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #126 failed.
---
Code has been updated by janaka, dimuthul, buddhikac.
1/6676 tests failed, no failures were new.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-126/


--
Failing Jobs
--
  - WSO2 Carbon Trunk Build Process (Default Stage): 1 of 6676 tests failed.


--
Code Changes
--
dimuthul (119078):

>Removing openid4java from the build.
>
>

buddhikac (119080):

>Adds facility to query values for a given index + index ui improvments.
>

dimuthul (119081):

>Removing openid4java since it is not used in the build anymomre.
>
>



--
Tests
--
Existing Test Failures (1)
   - TestRuleSet: Rule set

--
This message is automatically generated by Atlassian Bamboo___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #125 has FAILED (1 tests failed, no failures were new). Change made by janaka and thilini.

2012-01-17 Thread Ishara Karunarathna

Hi,

I have attach[01] the patch (
05_12203.patch.txt)to
resolve the issue.

Thanks
Ishara

[01] https://wso2.org/jira/secure/ManageAttachments.jspa?id=32549
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Build failure in service-stubs/ under Maven 3

2012-01-17 Thread KasunG Gajasinghe

On Tue, Jan 17, 2012 at 6:21 PM, Subash Chaturanga  wrote:

> Hi ,
> Today i got a full trunk update and got a build failure when building
> service stubs which is $subject .
>

Hi Subash,
The conclusion we came up was that either trunk should be built from root,
or you need to manually copy the carbon-platform pom to the relevant
directory in M2 repo. I think this issue was surfaced again because the
trunk project.version got  upgraded to 4.0.0-SNAPSHOT from 3.2.0-SNAPSHOT.

Regards,
--KasunG


>
> Here is the error log.
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 1.972s
> [INFO] Finished at: Tue Jan 17 17:55:50 IST 2012
> [INFO] Final Memory: 18M/490M
> [INFO]
> 
> [ERROR] Failed to execute goal on project service-stubs: Could not resolve
> dependencies for project org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT:
> Failed to collect dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2
> (compile), org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
> org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
> org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
> commons-logging:commons-logging:jar:1.1.1 (compile),
> org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1 (compile)]: Failed
> to read artifact descriptor for
> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4: Failure to find
> org.wso2.carbon:carbon-platform:pom:4.0.0-SNAPSHOT in
> http://maven.wso2.org/nexus/content/groups/wso2-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 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project service-stubs: Could not resolve dependencies for project
> org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT: Failed to collect
> dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2 (compile),
> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
> org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
> org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
> commons-logging:commons-logging:jar:1.1.1 (compile),
> org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1 (compile)]
>  at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:196)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:108)
>  at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>  at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>  at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>  at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>  at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>  at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>  at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>  at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could
> not resolve dependencies for project
> org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT: Failed to collect
> dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2 (compile),
> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
> org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
> org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
> commons-logging:commons-logging:jar:1.1.1 (compile),
> org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1 (compile)]
>  at
> org.apache.maven.pro

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #125 has FAILED (1 tests failed, no failures were new). Change made by janaka and thilini.

2012-01-17 Thread Amila Suriarachchi

On Tue, Jan 17, 2012 at 9:43 AM, Srinath Perera  wrote:

> Hi Amila,
>
> Could you (I mean the team) check this? TestRuleSet 
> testRuleSet
>  failing
> often .. could that be something that can fix in the test?
>

yes that is a bug in the test case. we fix this soon.

thanks,
Amila.

>
> --Srinath
>
>
>
> On Tue, Jan 17, 2012 at 1:14 PM, Bamboo  wrote:
>
>>  [image: Failed]  WSO2 Carbon 
>> Trunk› WSO2
>> Carbon - Platform 
>> Trunk›
>> #125
>> failed
>>
>> This build was manually triggered by 
>> BambooBuilder
>> .
>>
>> *1/7696* tests failed.
>>Failing 
>> Jobs
>> Job
>> Duration Tests[image: Failed]  WSO2 Carbon Trunk Build 
>> Process
>>  (Default
>> Stage)  260 minutes  1 of 7696 failed  
>> Logs|
>> Artifacts
>>  Code
>> Changes
>>   View
>> full change 
>> details
>> janaka 
>> Fixing test failures
>>  119075
>> thilini
>> ui msg customization and add label to add archive page  119074 
>> Tests
>>   View
>> full test 
>> details
>>1
>> Existing Test Failures   Test Job TestRuleSet 
>> testRuleSet
>>   WSO2
>> Carbon Trunk Build 
>> Process
>>7
>> Fixed Tests   Test Job EndpointTest
>> testServiceAddingEndpointsWithWsdl
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> EndpointTest 
>> testAddWsdlWithEndpoints
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> ServiceTest 
>> testServiceRename
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> ServiceTest 
>> testServiceAttachments
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> ServiceTest 
>> testServiceSearch
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> WSDLTest 
>> testEditWSDL
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> WSDLTest 
>> testAddWSDL
>>   WSO2
>> Carbon Trunk Build 
>> Process
>>  View
>> Online
>> | Add 
>> Comments

Re: [Carbon-dev] Build failure in service-stubs/ under Maven 3

2012-01-17 Thread Subash Chaturanga

Hi ,
Today i got a full trunk update and got a build failure when building
service stubs which is $subject .

Here is the error log.

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 1.972s
[INFO] Finished at: Tue Jan 17 17:55:50 IST 2012
[INFO] Final Memory: 18M/490M
[INFO]

[ERROR] Failed to execute goal on project service-stubs: Could not resolve
dependencies for project org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT:
Failed to collect dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2
(compile), org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
commons-logging:commons-logging:jar:1.1.1 (compile),
org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1 (compile)]: Failed
to read artifact descriptor for
org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4: Failure to find
org.wso2.carbon:carbon-platform:pom:4.0.0-SNAPSHOT in
http://maven.wso2.org/nexus/content/groups/wso2-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 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal on project service-stubs: Could not resolve dependencies for project
org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT: Failed to collect
dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2 (compile),
org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
commons-logging:commons-logging:jar:1.1.1 (compile),
org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1 (compile)]
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:196)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:108)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.project.DependencyResolutionException: Could
not resolve dependencies for project
org.wso2.carbon:service-stubs:pom:4.0.0-SNAPSHOT: Failed to collect
dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2 (compile),
org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
commons-logging:commons-logging:jar:1.1.1 (compile),
org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1 (compile)]
at
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:139)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:171)
... 22 more
Caused by: org.sonatype.aether.collection.DependencyCollectionException:
Failed to collect dependencies for [wsdl4j.wso2:wsdl4j:jar:1.6.2.wso2v2
(compile), org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v4 (compile),
org.apache.neethi.wso2:neethi:jar:2.0.4.wso2v3 (compile),
org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1 (compile),
com

[Carbon-dev] Moving trunk/dependency/ode to ode 1.3.5 public branch

2012-01-17 Thread Denis Weerasiri

Hi Waruna,
There're some bugs[1],[2], in existing dependency/ode trunk which we have
forked from 1.3.5 branch before it was released. Will it be a good to move
to ode 1.3.5 tag at [3]?.

[1] - https://wso2.org/jira/browse/CARBON-11151
[2] - https://wso2.org/jira/browse/CARBON-11208
[3] - https://svn.apache.org/repos/asf/ode/tags/APACHE_ODE_1.3.5

-- 
Thanks,
Denis
--
*Denis Weerasiri*
Software Engineer; WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com *
*phone: +94117639629
*
*site: 
**https://sites.google.com/site/ddweerasiri/*
*blog: **http://ddweerasiri.blogspot.com* 
*
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Unable to start BPS server when set offset value - trunk build

2012-01-17 Thread Sanjaya Vithanagama

This is fixed with rev 119089.

On Tue, Jan 17, 2012 at 3:07 PM, Sanjaya Vithanagama wrote:

> Hi Krishantha,
>
> I'll have a look into this.
>
> Regards,
> SanjayaV.
>
> On Tue, Jan 17, 2012 at 2:49 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi,
>>
>> I was trying to start BPS server (trunk build) and got the following
>> error. Further investigation reveals that issue caused after changing
>> default offset value. Our system automation tests are failing due to this
>> error. Please have a look.
>>
>> Exception
>> =
>>
>> [2012-01-17 14:40:35,699] ERROR - Database - Failed to resolved external
>> DataSource at htds
>> javax.naming.ServiceUnavailableException [Root exception is
>> java.rmi.ConnectException: Connection refused to host: localhost; nested
>> exception is:
>>  java.net.ConnectException: Connection refused]
>> at
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
>>  at
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:107)
>> at
>> org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContext.lookup(CarbonContextHolder.java:1034)
>>  at javax.naming.InitialContext.lookup(InitialContext.java:392)
>> at
>> org.wso2.carbon.humantask.core.db.Database.lookupInJndi(Database.java:156)
>>  at
>> org.wso2.carbon.humantask.core.db.Database.initExternalDb(Database.java:127)
>> at
>> org.wso2.carbon.humantask.core.db.Database.initDataSource(Database.java:122)
>>  at org.wso2.carbon.humantask.core.db.Database.start(Database.java:77)
>> at
>> org.wso2.carbon.humantask.core.HumanTaskServer.initDataSource(HumanTaskServer.java:92)
>>  at
>> org.wso2.carbon.humantask.core.HumanTaskServer.init(HumanTaskServer.java:61)
>> at
>> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.initHumanTaskServer(HumanTaskServiceComponent.java:83)
>>  at
>> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.activate(HumanTaskServiceComponent.java:63)
>> 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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>>  at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
>>  at
>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
>> at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
>>  at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
>> 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.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
>>  at
>> org.wso2.carbon.datasource.internal.DataSourceServiceComponent.activate(DataSourceServiceComponent.java:140)
>> 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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>>  at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.bu

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #125 has FAILED (1 tests failed, no failures were new). Change made by janaka and thilini.

2012-01-17 Thread Srinath Perera

Amila, sorry I did not saw the mail --Srinath

On Tue, Jan 17, 2012 at 3:13 PM, Srinath Perera  wrote:

> Hi Amila,
>
> Could you (I mean the team) check this? TestRuleSet 
> testRuleSet
>  failing
> often .. could that be something that can fix in the test?
>
> --Srinath
>
>
>
> On Tue, Jan 17, 2012 at 1:14 PM, Bamboo  wrote:
>
>>  [image: Failed]  WSO2 Carbon 
>> Trunk› WSO2
>> Carbon - Platform 
>> Trunk›
>> #125
>> failed
>>
>> This build was manually triggered by 
>> BambooBuilder
>> .
>>
>> *1/7696* tests failed.
>>Failing 
>> Jobs
>> Job
>> Duration Tests[image: Failed]  WSO2 Carbon Trunk Build 
>> Process
>>  (Default
>> Stage)  260 minutes  1 of 7696 failed  
>> Logs|
>> Artifacts
>>  Code
>> Changes
>>   View
>> full change 
>> details
>> janaka 
>> Fixing test failures
>>  119075
>> thilini
>> ui msg customization and add label to add archive page  119074 
>> Tests
>>   View
>> full test 
>> details
>>1
>> Existing Test Failures   Test Job TestRuleSet 
>> testRuleSet
>>   WSO2
>> Carbon Trunk Build 
>> Process
>>7
>> Fixed Tests   Test Job EndpointTest
>> testServiceAddingEndpointsWithWsdl
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> EndpointTest 
>> testAddWsdlWithEndpoints
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> ServiceTest 
>> testServiceRename
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> ServiceTest 
>> testServiceAttachments
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> ServiceTest 
>> testServiceSearch
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> WSDLTest 
>> testEditWSDL
>>   WSO2
>> Carbon Trunk Build 
>> Process
>> WSDLTest 
>> testAddWSDL
>>   WSO2
>> Carbon Trunk Build 
>> Process
>>  View
>> Online
>> | Add 
>> Comments

Re: [Carbon-dev] Unable to start BPS server when set offset value - trunk build

2012-01-17 Thread Krishantha Samaraweera

On Tue, Jan 17, 2012 at 3:15 PM, Waruna Ranasinghe  wrote:

> Hi krishantha,
>
> this happens when the Registry and the BPEL databases are out of sync.
>

Thanks Waruna, you are correct.

-Krishantha.

> sent from my mobile.
> On Jan 17, 2012 3:11 PM, "Krishantha Samaraweera" 
> wrote:
>
>> Hi,
>>
>> I see the following error when starting BPS trunk build with registry
>> mounts.
>>
>> [2012-01-17 14:53:51,247] ERROR - TenantProcessStoreImpl - Cannot find
>> DeploymentUnitDAO instance for package LoanService-8.
>> [2012-01-17 14:53:51,247] ERROR - BPELDeployer - Error deploying BPEL
>> package: LoanService.zip
>> org.wso2.carbon.bpel.core.ode.integration.store.BPELDeploymentException:
>> Cannot find DeploymentUnitDAO instance for package LoanService-8.
>>  at
>> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.loadExistingBPELPackage(TenantProcessStoreImpl.java:645)
>> at
>> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.reloadExistingVersionsOfBPELPackage(TenantProcessStoreImpl.java:506)
>>  at
>> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deploy(TenantProcessStoreImpl.java:210)
>> at org.wso2.carbon.bpel.deployer.BPELDeployer.deploy(BPELDeployer.java:94)
>>  at
>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>> at
>> org.wso2.carbon.utils.deployment.GhostDeployer.deploy(GhostDeployer.java:126)
>>  at
>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>>  at
>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>> at
>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:371)
>>  at
>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139)
>>  at
>> org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:434)
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
>>  at
>> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:359)
>>  at
>> org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:257)
>> at
>> org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117)
>>  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)
>>
>> Thanks,
>> Krishantha.
>>
>>
>> On Tue, Jan 17, 2012 at 2:49 PM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I was trying to start BPS server (trunk build) and got the following
>>> error. Further investigation reveals that issue caused after changing
>>> default offset value. Our system automation tests are failing due to this
>>> error. Please have a look.
>>>
>>> Exception
>>> =n
>>> [2012-01-17 14:40:35,699] ERROR - Database - Failed to resolved
>>> external DataSource at htds
>>> javax.naming.ServiceUnavailableException [Root exception is
>>> java.rmi.ConnectException: Connection refused to host: localhost; nested
>>> exception is:
>>>  java.net.ConnectException: Connection refused]
>>> at
>>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
>>>  at
>>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:107)
>>> at
>>> org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContext.lookup(CarbonContextHolder.java:1034)
>>>  at javax.naming.InitialContext.lookup(InitialContext.java:392)
>>> at
>>> org.wso2.carbon.humantask.core.db.Database.lookupInJndi(Database.java:156)
>>>  at
>>> org.wso2.carbon.humantask.core.db.Database.initExternalDb(Database.java:127)
>>> at
>>> org.wso2.carbon.humantask.core.db.Database.initDataSource(Database.java:122)
>>>  at org.wso2.carbon.humantask.core.db.Database.start(Database.java:77)
>>> at
>>> org.wso2.carbon.humantask.core.HumanTaskServer.initDataSource(HumanTaskServer.java:92)
>>>  at
>>> org.wso2.carbon.humantask.core.HumanTaskServer.init(HumanTaskServer.java:61)
>>> at
>>> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.initHumanTaskServer(HumanTaskServiceComponent.java:83)
>>>  at
>>> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.activate(HumanTaskServiceComponent.java:63)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>  at
>>> sun.reflect.NativeM

Re: [Carbon-dev] Unable to start BPS server when set offset value - trunk build

2012-01-17 Thread Waruna Ranasinghe

Hi krishantha,

this happens when the Registry and the BPEL databases are out of sync.

sent from my mobile.
On Jan 17, 2012 3:11 PM, "Krishantha Samaraweera" 
wrote:

> Hi,
>
> I see the following error when starting BPS trunk build with registry
> mounts.
>
> [2012-01-17 14:53:51,247] ERROR - TenantProcessStoreImpl - Cannot find
> DeploymentUnitDAO instance for package LoanService-8.
> [2012-01-17 14:53:51,247] ERROR - BPELDeployer - Error deploying BPEL
> package: LoanService.zip
> org.wso2.carbon.bpel.core.ode.integration.store.BPELDeploymentException:
> Cannot find DeploymentUnitDAO instance for package LoanService-8.
>  at
> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.loadExistingBPELPackage(TenantProcessStoreImpl.java:645)
> at
> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.reloadExistingVersionsOfBPELPackage(TenantProcessStoreImpl.java:506)
>  at
> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deploy(TenantProcessStoreImpl.java:210)
> at org.wso2.carbon.bpel.deployer.BPELDeployer.deploy(BPELDeployer.java:94)
>  at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.wso2.carbon.utils.deployment.GhostDeployer.deploy(GhostDeployer.java:126)
>  at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>  at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:371)
>  at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> at
> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139)
>  at
> org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:434)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
>  at
> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:359)
>  at
> org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:257)
> at
> org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117)
>  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)
>
> Thanks,
> Krishantha.
>
>
> On Tue, Jan 17, 2012 at 2:49 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi,
>>
>> I was trying to start BPS server (trunk build) and got the following
>> error. Further investigation reveals that issue caused after changing
>> default offset value. Our system automation tests are failing due to this
>> error. Please have a look.
>>
>> Exception
>> =n
>> [2012-01-17 14:40:35,699] ERROR - Database - Failed to resolved external
>> DataSource at htds
>> javax.naming.ServiceUnavailableException [Root exception is
>> java.rmi.ConnectException: Connection refused to host: localhost; nested
>> exception is:
>>  java.net.ConnectException: Connection refused]
>> at
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
>>  at
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:107)
>> at
>> org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContext.lookup(CarbonContextHolder.java:1034)
>>  at javax.naming.InitialContext.lookup(InitialContext.java:392)
>> at
>> org.wso2.carbon.humantask.core.db.Database.lookupInJndi(Database.java:156)
>>  at
>> org.wso2.carbon.humantask.core.db.Database.initExternalDb(Database.java:127)
>> at
>> org.wso2.carbon.humantask.core.db.Database.initDataSource(Database.java:122)
>>  at org.wso2.carbon.humantask.core.db.Database.start(Database.java:77)
>> at
>> org.wso2.carbon.humantask.core.HumanTaskServer.initDataSource(HumanTaskServer.java:92)
>>  at
>> org.wso2.carbon.humantask.core.HumanTaskServer.init(HumanTaskServer.java:61)
>> at
>> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.initHumanTaskServer(HumanTaskServiceComponent.java:83)
>>  at
>> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.activate(HumanTaskServiceComponent.java:63)
>> 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
>> or

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #125 has FAILED (1 tests failed, no failures were new). Change made by janaka and thilini.

2012-01-17 Thread Srinath Perera

Hi Amila,

Could you (I mean the team) check this? TestRuleSet
testRuleSet
failing
often .. could that be something that can fix in the test?

--Srinath



On Tue, Jan 17, 2012 at 1:14 PM, Bamboo  wrote:

>  [image: Failed]  WSO2 Carbon 
> Trunk› WSO2
> Carbon - Platform 
> Trunk›
> #125
> failed
>
> This build was manually triggered by 
> BambooBuilder
> .
>
> *1/7696* tests failed.
>   Failing 
> Jobs
> Job Duration Tests[image: Failed]  WSO2 Carbon Trunk Build 
> Process
>  (Default
> Stage)  260 minutes  1 of 7696 failed  
> Logs|
> Artifacts
>  Code
> Changes
>   View
> full change 
> details
> janaka 
> Fixing test failures
>  119075
> thilini
> ui msg customization and add label to add archive page  119074 
> Tests
>   View
> full test 
> details
>1
> Existing Test Failures  Test Job TestRuleSet 
> testRuleSet
>   WSO2
> Carbon Trunk Build 
> Process
>7
> Fixed Tests  Test Job EndpointTest 
> testServiceAddingEndpointsWithWsdl
>   WSO2
> Carbon Trunk Build 
> Process
> EndpointTest 
> testAddWsdlWithEndpoints
>   WSO2
> Carbon Trunk Build 
> Process
> ServiceTest 
> testServiceRename
>   WSO2
> Carbon Trunk Build 
> Process
> ServiceTest 
> testServiceAttachments
>   WSO2
> Carbon Trunk Build 
> Process
> ServiceTest 
> testServiceSearch
>   WSO2
> Carbon Trunk Build 
> Process
> WSDLTest 
> testEditWSDL
>   WSO2
> Carbon Trunk Build 
> Process
> WSDLTest 
> testAddWSDL
>   WSO2
> Carbon Trunk Build 
> Process
>  View
> Online
> | Add 
> Comments
>
> This message was sent by Atlassian 
> Bamboo
> .
>
> If you wish to stop receiving these emails edit your user 
> profile

Re: [Carbon-dev] Unable to start BPS server when set offset value - trunk build

2012-01-17 Thread Krishantha Samaraweera

Hi,

I see the following error when starting BPS trunk build with registry
mounts.

[2012-01-17 14:53:51,247] ERROR - TenantProcessStoreImpl - Cannot find
DeploymentUnitDAO instance for package LoanService-8.
[2012-01-17 14:53:51,247] ERROR - BPELDeployer - Error deploying BPEL
package: LoanService.zip
org.wso2.carbon.bpel.core.ode.integration.store.BPELDeploymentException:
Cannot find DeploymentUnitDAO instance for package LoanService-8.
at
org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.loadExistingBPELPackage(TenantProcessStoreImpl.java:645)
at
org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.reloadExistingVersionsOfBPELPackage(TenantProcessStoreImpl.java:506)
at
org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deploy(TenantProcessStoreImpl.java:210)
at org.wso2.carbon.bpel.deployer.BPELDeployer.deploy(BPELDeployer.java:94)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.wso2.carbon.utils.deployment.GhostDeployer.deploy(GhostDeployer.java:126)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:371)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139)
at
org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:434)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:359)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:257)
at
org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117)
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)

Thanks,
Krishantha.

On Tue, Jan 17, 2012 at 2:49 PM, Krishantha Samaraweera  wrote:

> Hi,
>
> I was trying to start BPS server (trunk build) and got the following
> error. Further investigation reveals that issue caused after changing
> default offset value. Our system automation tests are failing due to this
> error. Please have a look.
>
> Exception
> =n
> [2012-01-17 14:40:35,699] ERROR - Database - Failed to resolved external
> DataSource at htds
> javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: localhost; nested
> exception is:
>  java.net.ConnectException: Connection refused]
> at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
>  at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:107)
> at
> org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContext.lookup(CarbonContextHolder.java:1034)
>  at javax.naming.InitialContext.lookup(InitialContext.java:392)
> at
> org.wso2.carbon.humantask.core.db.Database.lookupInJndi(Database.java:156)
>  at
> org.wso2.carbon.humantask.core.db.Database.initExternalDb(Database.java:127)
> at
> org.wso2.carbon.humantask.core.db.Database.initDataSource(Database.java:122)
>  at org.wso2.carbon.humantask.core.db.Database.start(Database.java:77)
> at
> org.wso2.carbon.humantask.core.HumanTaskServer.initDataSource(HumanTaskServer.java:92)
>  at
> org.wso2.carbon.humantask.core.HumanTaskServer.init(HumanTaskServer.java:61)
> at
> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.initHumanTaskServer(HumanTaskServiceComponent.java:83)
>  at
> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.activate(HumanTaskServiceComponent.java:63)
> 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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.build

Re: [Carbon-dev] Unable to start BPS server when set offset value - trunk build

2012-01-17 Thread Sanjaya Vithanagama

Hi Krishantha,

I'll have a look into this.

Regards,
SanjayaV.

On Tue, Jan 17, 2012 at 2:49 PM, Krishantha Samaraweera  wrote:

> Hi,
>
> I was trying to start BPS server (trunk build) and got the following
> error. Further investigation reveals that issue caused after changing
> default offset value. Our system automation tests are failing due to this
> error. Please have a look.
>
> Exception
> =
>
> [2012-01-17 14:40:35,699] ERROR - Database - Failed to resolved external
> DataSource at htds
> javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: localhost; nested
> exception is:
>  java.net.ConnectException: Connection refused]
> at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
>  at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:107)
> at
> org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContext.lookup(CarbonContextHolder.java:1034)
>  at javax.naming.InitialContext.lookup(InitialContext.java:392)
> at
> org.wso2.carbon.humantask.core.db.Database.lookupInJndi(Database.java:156)
>  at
> org.wso2.carbon.humantask.core.db.Database.initExternalDb(Database.java:127)
> at
> org.wso2.carbon.humantask.core.db.Database.initDataSource(Database.java:122)
>  at org.wso2.carbon.humantask.core.db.Database.start(Database.java:77)
> at
> org.wso2.carbon.humantask.core.HumanTaskServer.initDataSource(HumanTaskServer.java:92)
>  at
> org.wso2.carbon.humantask.core.HumanTaskServer.init(HumanTaskServer.java:61)
> at
> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.initHumanTaskServer(HumanTaskServiceComponent.java:83)
>  at
> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.activate(HumanTaskServiceComponent.java:63)
> 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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
>  at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
>  at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
> 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.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
>  at
> org.wso2.carbon.datasource.internal.DataSourceServiceComponent.activate(DataSourceServiceComponent.java:140)
> 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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
>  at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
>  at
> org.eclipse.o

[Carbon-dev] Unable to start BPS server when set offset value - trunk build

2012-01-17 Thread Krishantha Samaraweera

Hi,

I was trying to start BPS server (trunk build) and got the following error.
Further investigation reveals that issue caused after changing default
offset value. Our system automation tests are failing due to this error.
Please have a look.

Exception
=

[2012-01-17 14:40:35,699] ERROR - Database - Failed to resolved external
DataSource at htds
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: localhost; nested
exception is:
java.net.ConnectException: Connection refused]
at
com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
at
com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:107)
at
org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContext.lookup(CarbonContextHolder.java:1034)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at
org.wso2.carbon.humantask.core.db.Database.lookupInJndi(Database.java:156)
at
org.wso2.carbon.humantask.core.db.Database.initExternalDb(Database.java:127)
at
org.wso2.carbon.humantask.core.db.Database.initDataSource(Database.java:122)
at org.wso2.carbon.humantask.core.db.Database.start(Database.java:77)
at
org.wso2.carbon.humantask.core.HumanTaskServer.initDataSource(HumanTaskServer.java:92)
at
org.wso2.carbon.humantask.core.HumanTaskServer.init(HumanTaskServer.java:61)
at
org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.initHumanTaskServer(HumanTaskServiceComponent.java:83)
at
org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.activate(HumanTaskServiceComponent.java:63)
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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
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.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.datasource.internal.DataSourceServiceComponent.activate(DataSourceServiceComponent.java:140)
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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
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.dispatc

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #125 has FAILED (1 tests failed, no failures were new). Change made by janaka and thilini.

2012-01-17 Thread Amila Suriarachchi

Ishara working on this.

thanks,
Amila.

On Tue, Jan 17, 2012 at 1:14 PM, Bamboo  wrote:

>  [image: Failed]  WSO2 Carbon 
> Trunk› WSO2
> Carbon - Platform 
> Trunk›
> #125
> failed
>
> This build was manually triggered by 
> BambooBuilder
> .
>
> *1/7696* tests failed.
>   Failing 
> Jobs
> Job Duration Tests[image: Failed]  WSO2 Carbon Trunk Build 
> Process
>  (Default
> Stage)  260 minutes  1 of 7696 failed  
> Logs|
> Artifacts
>  Code
> Changes
>   View
> full change 
> details
> janaka 
> Fixing test failures
>  119075
> thilini
> ui msg customization and add label to add archive page  119074 
> Tests
>   View
> full test 
> details
>1
> Existing Test Failures  Test Job TestRuleSet 
> testRuleSet
>   WSO2
> Carbon Trunk Build 
> Process
>7
> Fixed Tests  Test Job EndpointTest 
> testServiceAddingEndpointsWithWsdl
>   WSO2
> Carbon Trunk Build 
> Process
> EndpointTest 
> testAddWsdlWithEndpoints
>   WSO2
> Carbon Trunk Build 
> Process
> ServiceTest 
> testServiceRename
>   WSO2
> Carbon Trunk Build 
> Process
> ServiceTest 
> testServiceAttachments
>   WSO2
> Carbon Trunk Build 
> Process
> ServiceTest 
> testServiceSearch
>   WSO2
> Carbon Trunk Build 
> Process
> WSDLTest 
> testEditWSDL
>   WSO2
> Carbon Trunk Build 
> Process
> WSDLTest 
> testAddWSDL
>   WSO2
> Carbon Trunk Build 
> Process
>  View
> Online
> | Add 
> Comments
>
> This message was sent by Atlassian 
> Bamboo
> .
>
> If you wish to stop receiving these emails edit your user 
> profileor
>  notify
> your 
> administrator
> .
>
> ___
> Carbon-dev mailing

[Carbon-dev] Microsft excel adapters

2012-01-17 Thread gnanaguru.sattanathan

Hi

I am in a scenario where I need to extract and push data from Excel Sheets. I 
preferred wso2 for this. In what way WSO2 ESB supports this. You have any 
specific adapter for this?

Please help out.


Regards
Guru

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

www.wipro.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Getting compilation errors for generated stub classes in a sample in AS

2012-01-17 Thread Supun Malinga

Hi,

I got same error(below) once and build from a clean repo. Then didn't get
the error. Now I'm getting it again. Seems generated stubs are not whats
expected by the client code.
Anyone else got this? or any idea how to resolve?

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project wso2appserver-samples-commodityquote:
Compilation failure: Compilation failure:
[ERROR]
/home/disk1/carbon_builds/trunk/products/as/modules/samples/product/CommodityQuote/target/generated/src/org/wso2/appserver/sample/commodityquote/client/CommodityQuoteStub.java:[202,58]
fromOM(org.apache.axiom.om.OMElement,java.lang.Class,java.util.Map) in
org.wso2.appserver.sample.commodityquote.client.CommodityQuoteStub cannot
be applied to
(org.apache.axiom.om.OMElement,java.lang.Class)
[ERROR]
[ERROR]
/home/disk1/carbon_builds/trunk/products/as/modules/samples/product/CommodityQuote/target/generated/src/org/wso2/appserver/sample/commodityquote/client/CommodityQuoteStub.java:[222,57]
fromOM(org.apache.axiom.om.OMElement,java.lang.Class,java.util.Map) in
org.wso2.appserver.sample.commodityquote.client.CommodityQuoteStub cannot
be applied to (org.apache.axiom.om.OMElement,java.lang.Class)
[ERROR]
[ERROR]
/home/disk1/carbon_builds/trunk/products/as/modules/samples/product/CommodityQuote/target/generated/src/org/wso2/appserver/sample/commodityquote/client/CommodityQuoteStub.java:[315,66]
fromOM(org.apache.axiom.om.OMElement,java.lang.Class,java.util.Map) in
org.wso2.appserver.sample.commodityquote.client.CommodityQuoteStub cannot
be applied to
(org.apache.axiom.om.OMElement,java.lang.Class)
[ERROR]
[ERROR]
/home/disk1/carbon_builds/trunk/products/as/modules/samples/product/CommodityQuote/target/generated/src/org/wso2/appserver/sample/commodityquote/client/CommodityQuoteStub.java:[339,46]
fromOM(org.apache.axiom.om.OMElement,java.lang.Class,java.util.Map) in
org.wso2.appserver.sample.commodityquote.client.CommodityQuoteStub cannot
be applied to (org.apache.axiom.om.OMElement,java.lang.Class)
[ERROR]
[ERROR]
/home/disk1/carbon_builds/trunk/products/as/modules/samples/product/CommodityQuote/target/generated/src/org/wso2/appserver/sample/commodityquote/client/CommodityQuoteStub.java:[463,58]
fromOM(org.apache.axiom.om.OMElement,java.lang.Class,java.util.Map) in
org.wso2.appserver.sample.commodityquote.client.CommodityQuoteStub cannot
be applied to
(org.apache.axiom.om.OMElement,java.lang.Class)
[ERROR]
[ERROR]
/home/disk1/carbon_builds/trunk/products/as/modules/samples/product/CommodityQuote/target/generated/src/org/wso2/appserver/sample/commodityquote/client/CommodityQuoteStub.java:[483,57]
fromOM(org.apache.axiom.om.OMElement,java.lang.Class,java.util.Map) in
org.wso2.appserver.sample.commodityquote.client.CommodityQuoteStub cannot
be applied to (org.apache.axiom.om.OMElement,java.lang.Class)
[ERROR]
[ERROR]
/home/disk1/carbon_builds/trunk/products/as/modules/samples/product/CommodityQuote/target/generated/src/org/wso2/appserver/sample/commodityquote/client/CommodityQuoteStub.java:[570,66]
fromOM(org.apache.axiom.om.OMElement,java.lang.Class,java.util.Map) in
org.wso2.appserver.sample.commodityquote.client.CommodityQuoteStub cannot
be applied to
(org.apache.axiom.om.OMElement,java.lang.Class)
[ERROR]
[ERROR]
/home/disk1/carbon_builds/trunk/products/as/modules/samples/product/CommodityQuote/target/generated/src/org/wso2/appserver/sample/commodityquote/client/CommodityQuoteStub.java:[594,46]
fromOM(org.apache.axiom.om.OMElement,java.lang.Class,java.util.Map) in
org.wso2.appserver.sample.commodityquote.client.CommodityQuoteStub cannot
be applied to (org.apache.axiom.om.OMElement,java.lang.Class)
[ERROR]
[ERROR]
/home/disk1/carbon_builds/trunk/products/as/modules/samples/product/CommodityQuote/target/generated/src/org/wso2/appserver/sample/commodityquote/services/CommodityQuoteMessageReceiverInOut.java:[44,106]
fromOM(org.apache.axiom.om.OMElement,java.lang.Class,java.util.Map) in
org.wso2.appserver.sample.commodityquote.services.CommodityQuoteMessageReceiverInOut
cannot be applied to
(org.apache.axiom.om.OMElement,java.lang.Class)

thanks,
-- 
Supun Malinga,

Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 
mobile - 071 56 91 321
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

40 matches

Mail list logo