Re: [Carbon-dev] G-Reg Server startup fails - trunk build

[Subash Chaturanga]

il.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
>  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)
> [2012-03-05 16:54:30,146] ERROR
> {org.wso2.carbon.registry.indexing.AsyncIndexer} -  Error while indexing.
> java.lang.LinkageError: loader constraint violation: when resolving method
> "javax.xml.parsers.SAXParser.parse(Ljava/io/InputStream;Lorg/xml/sax/helpers/DefaultHandler;)V"
> the class loader (instance of
> org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current
> class, org/wso2/carbon/registry/indexing/indexer/XMLIndexer, and the class
> loader (instance of ) for resolved class,
> javax/xml/parsers/SAXParser, have different Class objects for the type
> org/xml/sax/helpers/DefaultHandler used in the signature
>  at
> org.wso2.carbon.registry.indexing.indexer.XMLIndexer.getIndexedDocument(XMLIndexer.java:41)
> at
> org.wso2.carbon.registry.indexing.solr.SolrClient.indexDocument(SolrClient.java:215)
>  at
> org.wso2.carbon.registry.indexing.AsyncIndexer.run(AsyncIndexer.java:84)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>  at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
>  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)
>
>
> Thanks,
> Krishantha.
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] product build failures due to registry core feature

[Subash Chaturanga]

Hi Senaka,Pradeep

On Sun, Mar 4, 2012 at 7:26 PM, Senaka Fernando  wrote:

> Hi Subash,
>
> Let's try to do a build on a clean repo tomorrow and see whether this can
> be reproduced. If we cannot, we can clean the repo of the builder and try.
>

I use the same src revision 121949 which the builder used to give this
failure and was able to build greg-p2 in a clean repo. No such errors
occurred.
This should not be reproduced on the builder in a clean repo.



> I too did not get this when I last tried, but I have a feeling that my
> repo might have things that have accumulated. Also, please build with tests
> from the beginning and if anything fails, let's get people to fix that
> first, if not we'll never get the build stabilized and sort these issues in
> a manner that is consistent.
>
> Thanks,
> Senaka.
> On Sun, Mar 4, 2012 at 10:37 AM, Pradeep Fernando wrote:
>
>> Hi,
>>
>> refer the build log.
>>
>>
>> http://builder4.us1.wso2.org:/bamboo/download/WSO2CARBONKERNEL-CARBONPRODUCTS-JOB1/build_logs/WSO2CARBONKERNEL-CARBONPRODUCTS-JOB1-32.log
>>
>> --Pradeep
>>
>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Build Failure : graphite/components//axis2-repo-mgt

[Subash Chaturanga]

Hi,

This can be skipped when building from graphite level instead of building
each module separately.

On Mon, Mar 5, 2012 at 3:44 PM, Subash Chaturanga  wrote:

> Hi,
>
> I am experiencing this in a clean repo build from the src
>  revision 121949. Have any body came across with this ?
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 8.872s
> [INFO] Finished at: Mon Mar 05 15:41:18 IST 2012
> [INFO] Final Memory: 18M/490M
> [INFO]
> 
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.repomanager.axis2.ui: Could not resolve dependencies for
> project
> org.wso2.carbon:org.wso2.carbon.repomanager.axis2.ui:bundle:4.0.0-SNAPSHOT:
> Failed to collect dependencies for
> [org.wso2.carbon:org.wso2.carbon.ui:jar:4.0.0-SNAPSHOT (compile),
> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v5 (compile),
> org.wso2.carbon:org.wso2.carbon.repomanager.axis2.stub:jar:4.0.0-SNAPSHOT
> (compile)]: Failed to read artifact descriptor for
> org.wso2.carbon:org.wso2.carbon.repomanager.axis2.stub:jar:4.0.0-SNAPSHOT:
> Failure to find org.wso2.carbon:graphite-parent: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 org.wso2.carbon.repomanager.axis2.ui: Could not resolve
> dependencies for project
> org.wso2.carbon:org.wso2.carbon.repomanager.axis2.ui:bundle:4.0.0-SNAPSHOT:
> Failed to collect dependencies for
> [org.wso2.carbon:org.wso2.carbon.ui:jar:4.0.0-SNAPSHOT (compile),
> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v5 (compile),
> org.wso2.carbon:org.wso2.carbon.repomanager.axis2.stub:jar:4.0.0-SNAPSHOT
> (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:org.wso2.carbon.repomanager.axis2.ui:bundle:4.0.0-SNAPSHOT:
> Failed to collect dependencies for
> [org.wso2.carbon:org.wso2.carbon.ui:jar:4.0.0-SNAPSHOT (compile),
> org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v5 (compile),
> org.wso2.carbon:org.wso2.carbon.repomanager.axis2.stub:jar:4.0.0-SNAPSHOT
> (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.ae

[Carbon-dev] Build Failure : graphite/components//axis2-repo-mgt

[Subash Chaturanga]

lve(DefaultProjectDependenciesResolver.java:131)
... 23 more
Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException:
Failed to read artifact descriptor for
org.wso2.carbon:org.wso2.carbon.repomanager.axis2.stub:jar:4.0.0-SNAPSHOT
at
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:317)
at
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:172)
at
org.sonatype.aether.impl.internal.DefaultDependencyCollector.process(DefaultDependencyCollector.java:419)
at
org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:243)
... 25 more
Caused by: org.apache.maven.model.resolution.UnresolvableModelException:
Failure to find org.wso2.carbon:graphite-parent: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
at
org.apache.maven.repository.internal.DefaultModelResolver.resolveModel(DefaultModelResolver.java:126)
at
org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:819)
at
org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:670)
at
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:308)
at
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
at
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:308)
... 28 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
Failure to find org.wso2.carbon:graphite-parent: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
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:541)
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:220)
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:197)
at
org.apache.maven.repository.internal.DefaultModelResolver.resolveModel(DefaultModelResolver.java:122)
... 33 more
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure
to find org.wso2.carbon:graphite-parent: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
at
org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:190)
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:430)
... 36 more
[ERROR]


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] product build failures due to registry core feature

[Subash Chaturanga]

On Mon, Mar 5, 2012 at 1:42 PM, Subash Chaturanga  wrote:

> Hi Sameera,
>
> On Mon, Mar 5, 2012 at 12:57 PM, Sameera Jayasoma wrote:
>
>> Hi Subash,
>>
>> What is the status of this error? Would you be able to have a look?
>>
>
Mistaken the thread for governance api test failures.
For this issue, I was not able to reproduce it in weekend. And today
morning I started to build it in a clean repo as I already mentioned.
Will update you soon.

>
> I was able to reproduce Endpoint test failures initially. And couldn't
> find a exact reason for the failures after going through.  I thought may be
> it's due to that particular revision taken from the builder for that
> failure(which also may be a reason for the registry core feature bundle
> issues). On Saturday I took a an update and I was able to build governance
> api with tests (Having including the Endpoint Tests).
>
> I didn't update the thread as I wanted to make sure it in a clean repo.
> Currently building service stubs. And it should probably fine then.
> Will update when it builds successfully and include Endpoint tests.
>
>
>>
>> Thanks,
>> Sameera.
>>
>> On Sun, Mar 4, 2012 at 7:48 PM, Subash Chaturanga wrote:
>>
>>>
>>>
>>> On Sun, Mar 4, 2012 at 7:26 PM, Senaka Fernando  wrote:
>>>
>>>> Hi Subash,
>>>>
>>>> Let's try to do a build on a clean repo tomorrow and see whether this
>>>> can be reproduced. If we cannot, we can clean the repo of the builder and
>>>> try. I too did not get this when I last tried, but I have a feeling that my
>>>> repo might have things that have accumulated. Also, please build with tests
>>>> from the beginning and if anything fails, let's get people to fix that
>>>> first, if not we'll never get the build stabilized and sort these issues in
>>>> a manner that is consistent.
>>>>
>>>
>>> +1,
>>> Some such p2 failures earlier has occurred due to the particular  svn
>>> revision triggered by the builder machine,
>>> and I am giving a last try before going to a clean repo build.
>>>
>>> Thanks
>>>
>>>>
>>>> Thanks,
>>>> Senaka.
>>>> On Sun, Mar 4, 2012 at 10:37 AM, Pradeep Fernando wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> refer the build log.
>>>>>
>>>>>
>>>>> http://builder4.us1.wso2.org:/bamboo/download/WSO2CARBONKERNEL-CARBONPRODUCTS-JOB1/build_logs/WSO2CARBONKERNEL-CARBONPRODUCTS-JOB1-32.log
>>>>>
>>>>> --Pradeep
>>>>
>>>>
>>>>
>>>> --
>>>> *Senaka Fernando*
>>>> Product Manager - WSO2 Governance Registry;
>>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>>>> Member; Apache Software Foundation; http://apache.org
>>>>
>>>> E-mail: senaka AT wso2.com
>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>>> Linked-In: http://linkedin.com/in/senakafernando
>>>>
>>>> *Lean . Enterprise . Middleware
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Subash Chaturanga
>>> Software Engineer
>>> WSO2 Inc. http://wso2.com
>>>
>>> email - sub...@wso2.com
>>> phone - 077 2225922
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma
>> Technical Lead and Product Manager, WSO2 Carbon
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://tech.jayasoma.org
>>
>>
>> Lean . Enterprise . Middleware
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
>
> Subash Chaturanga
> Software Engineer
> WSO2 Inc. http://wso2.com
>
> email - sub...@wso2.com
> phone - 077 2225922
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] product build failures due to registry core feature

[Subash Chaturanga]

Hi Sameera,

On Mon, Mar 5, 2012 at 12:57 PM, Sameera Jayasoma  wrote:

> Hi Subash,
>
> What is the status of this error? Would you be able to have a look?
>

I was able to reproduce Endpoint test failures initially. And couldn't find
a exact reason for the failures after going through.  I thought may be it's
due to that particular revision taken from the builder for that
failure(which also may be a reason for the registry core feature bundle
issues). On Saturday I took a an update and I was able to build governance
api with tests (Having including the Endpoint Tests).

I didn't update the thread as I wanted to make sure it in a clean repo.
Currently building service stubs. And it should probably fine then.
Will update when it builds successfully and include Endpoint tests.


>
> Thanks,
> Sameera.
>
> On Sun, Mar 4, 2012 at 7:48 PM, Subash Chaturanga  wrote:
>
>>
>>
>> On Sun, Mar 4, 2012 at 7:26 PM, Senaka Fernando  wrote:
>>
>>> Hi Subash,
>>>
>>> Let's try to do a build on a clean repo tomorrow and see whether this
>>> can be reproduced. If we cannot, we can clean the repo of the builder and
>>> try. I too did not get this when I last tried, but I have a feeling that my
>>> repo might have things that have accumulated. Also, please build with tests
>>> from the beginning and if anything fails, let's get people to fix that
>>> first, if not we'll never get the build stabilized and sort these issues in
>>> a manner that is consistent.
>>>
>>
>> +1,
>> Some such p2 failures earlier has occurred due to the particular  svn
>> revision triggered by the builder machine,
>> and I am giving a last try before going to a clean repo build.
>>
>> Thanks
>>
>>>
>>> Thanks,
>>> Senaka.
>>> On Sun, Mar 4, 2012 at 10:37 AM, Pradeep Fernando wrote:
>>>
>>>> Hi,
>>>>
>>>> refer the build log.
>>>>
>>>>
>>>> http://builder4.us1.wso2.org:/bamboo/download/WSO2CARBONKERNEL-CARBONPRODUCTS-JOB1/build_logs/WSO2CARBONKERNEL-CARBONPRODUCTS-JOB1-32.log
>>>>
>>>> --Pradeep
>>>
>>>
>>>
>>> --
>>> *Senaka Fernando*
>>> Product Manager - WSO2 Governance Registry;
>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>>> Member; Apache Software Foundation; http://apache.org
>>>
>>> E-mail: senaka AT wso2.com
>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>> Linked-In: http://linkedin.com/in/senakafernando
>>>
>>> *Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>>
>> Subash Chaturanga
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>>
>> email - sub...@wso2.com
>> phone - 077 2225922
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Sameera Jayasoma
> Technical Lead and Product Manager, WSO2 Carbon
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
>
> Lean . Enterprise . Middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] product build failures due to registry core feature

[Subash Chaturanga]

On Sun, Mar 4, 2012 at 7:26 PM, Senaka Fernando  wrote:

> Hi Subash,
>
> Let's try to do a build on a clean repo tomorrow and see whether this can
> be reproduced. If we cannot, we can clean the repo of the builder and try.
> I too did not get this when I last tried, but I have a feeling that my repo
> might have things that have accumulated. Also, please build with tests from
> the beginning and if anything fails, let's get people to fix that first, if
> not we'll never get the build stabilized and sort these issues in a manner
> that is consistent.
>

+1,
Some such p2 failures earlier has occurred due to the particular  svn
revision triggered by the builder machine,
and I am giving a last try before going to a clean repo build.

Thanks

>
> Thanks,
> Senaka.
> On Sun, Mar 4, 2012 at 10:37 AM, Pradeep Fernando wrote:
>
>> Hi,
>>
>> refer the build log.
>>
>>
>> http://builder4.us1.wso2.org:/bamboo/download/WSO2CARBONKERNEL-CARBONPRODUCTS-JOB1/build_logs/WSO2CARBONKERNEL-CARBONPRODUCTS-JOB1-32.log
>>
>> --Pradeep
>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] product build failures due to registry core feature

[Subash Chaturanga]

Hi Pradeep,

On Sun, Mar 4, 2012 at 12:35 AM, Subash Chaturanga  wrote:

>
>
> On Sat, Mar 3, 2012 at 11:00 PM, Senaka Fernando  wrote:
>
>> Hi Subash,
>>
>> Please have a look.
>>
>
> Sure. Will look into this.
>

I took a full update and build from the beginning until greg p2 profile
gen. And couldn't reproduce this. I was able to build the product.
Did this failure occurred in greg profile gen ?



>> Thanks,
>> Senaka.
>> On Sat, Mar 3, 2012 at 10:36 PM, Pradeep Fernando wrote:
>>
>>> Hi Greg team,
>>>
>>> getting the below build failure during the product profile generation.
>>> Can you guys please have a look.
>>>
>>> Cannot complete the install because one or more required items could not be 
>>> found.
>>> error   03-Mar-2012 08:46:07 Software being installed: WSO2 Carbon 
>>> - Registry Core Feature 4.0.0.SNAPSHOT 
>>> (org.wso2.carbon.registry.core.feature.group 4.0.0.SNAPSHOT)
>>> error   03-Mar-2012 08:46:07 Missing requirement: 
>>> org.wso2.carbon.registry.resource 4.0.0.SNAPSHOT 
>>> (org.wso2.carbon.registry.resource 4.0.0.SNAPSHOT) requires 'package 
>>> org.apache.commons.io [2.0.0,3.0.0)' but it could not be found
>>> error   03-Mar-2012 08:46:07 Cannot satisfy dependency:
>>> error   03-Mar-2012 08:46:07  From: WSO2 Carbon - Registry Core 
>>> Feature 4.0.0.SNAPSHOT (org.wso2.carbon.registry.core.feature.group 
>>> 4.0.0.SNAPSHOT)
>>> error   03-Mar-2012 08:46:07  To: 
>>> org.wso2.carbon.registry.core.server.feature.group [4.0.0.SNAPSHOT]
>>> error   03-Mar-2012 08:46:07 Cannot satisfy dependency:
>>> error   03-Mar-2012 08:46:07  From: WSO2 Carbon - Registry Core 
>>> Server Feature 4.0.0.SNAPSHOT 
>>> (org.wso2.carbon.registry.core.server.feature.group 4.0.0.SNAPSHOT)
>>> error   03-Mar-2012 08:46:07  To: org.wso2.carbon.registry.resource 
>>> [4.0.0.SNAPSHOT]
>>>
>>>
>>> --Pradeep
>>>
>>>
>>>
>>> --
>>> Pradeep Fernando
>>> Software Engineer
>>> Member, Management Committee - Platform & Cloud Technologies
>>> WSO2 Inc; http://wso2.com/
>>>
>>> blog: http://pradeepfernando.blogspot.com/
>>> m: +94776603662
>>>
>>
>>
>>
>> --
>> *Senaka Fernando*
>> Product Manager - WSO2 Governance Registry;
>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>>
>
>
> --
>
> Subash Chaturanga
> Software Engineer
> WSO2 Inc. http://wso2.com
>
> email - sub...@wso2.com
> phone - 077 2225922
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] product build failures due to registry core feature

[Subash Chaturanga]

On Sat, Mar 3, 2012 at 11:00 PM, Senaka Fernando  wrote:

> Hi Subash,
>
> Please have a look.
>

Sure. Will look into this.

>
> Thanks,
> Senaka.
> On Sat, Mar 3, 2012 at 10:36 PM, Pradeep Fernando wrote:
>
>> Hi Greg team,
>>
>> getting the below build failure during the product profile generation.
>> Can you guys please have a look.
>>
>> Cannot complete the install because one or more required items could not be 
>> found.
>> error03-Mar-2012 08:46:07 Software being installed: WSO2 Carbon 
>> - Registry Core Feature 4.0.0.SNAPSHOT 
>> (org.wso2.carbon.registry.core.feature.group 4.0.0.SNAPSHOT)
>> error03-Mar-2012 08:46:07 Missing requirement: 
>> org.wso2.carbon.registry.resource 4.0.0.SNAPSHOT 
>> (org.wso2.carbon.registry.resource 4.0.0.SNAPSHOT) requires 'package 
>> org.apache.commons.io [2.0.0,3.0.0)' but it could not be found
>> error03-Mar-2012 08:46:07 Cannot satisfy dependency:
>> error03-Mar-2012 08:46:07  From: WSO2 Carbon - Registry Core 
>> Feature 4.0.0.SNAPSHOT (org.wso2.carbon.registry.core.feature.group 
>> 4.0.0.SNAPSHOT)
>> error03-Mar-2012 08:46:07  To: 
>> org.wso2.carbon.registry.core.server.feature.group [4.0.0.SNAPSHOT]
>> error03-Mar-2012 08:46:07 Cannot satisfy dependency:
>> error03-Mar-2012 08:46:07  From: WSO2 Carbon - Registry Core 
>> Server Feature 4.0.0.SNAPSHOT 
>> (org.wso2.carbon.registry.core.server.feature.group 4.0.0.SNAPSHOT)
>> error03-Mar-2012 08:46:07  To: org.wso2.carbon.registry.resource 
>> [4.0.0.SNAPSHOT]
>>
>>
>> --Pradeep
>>
>>
>>
>> --
>> Pradeep Fernando
>> Software Engineer
>> Member, Management Committee - Platform & Cloud Technologies
>> WSO2 Inc; http://wso2.com/
>>
>> blog: http://pradeepfernando.blogspot.com/
>> m: +94776603662
>>
>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Carbon Integration Test Framework : Excluding axis2 jar from SecVerifier.aar

[Subash Chaturanga]

On Thu, Mar 1, 2012 at 11:21 AM, Subash Chaturanga  wrote:

> Hi Azeez,
>
> On Thu, Mar 1, 2012 at 9:52 AM, Afkham Azeez  wrote:
>
>> Go ahead. Can you check & exclude other unnecessary jars as well?
>>
> Done. Removed carbon core dependencies as well. Tested and worked fine.


> +1,
> There are only two dependencies in security-verifier module (axis2 and
> carbon core). As maven axis2 aar plugin adds all the jars in maven classpath
> in to the lib dir, the only way I could find to exclude a dependency from
> being packaged inside lib is to give a scope to the dependency (which will
> exclude all its related child dependencies)
>
> Because of that, if I do the same to carbon core dependency, all carbon
> core and axis2 dependencies will not get populated into service/lib, which
> is still should be fine as I feel. Isn't it? Is there any usage of having
> carbon core dependencies inside a service/lib ?
>
>
>>  --
>> Afkham Azeez
>> Sent from my phone
>> On Feb 29, 2012 10:55 PM, "Subash Chaturanga"  wrote:
>>
>>> Hi Azeez,
>>> For some reason GReg has enabled child first class loading and having
>>> problems in deploying axis2 web services. Though any carbon server
>>> is expected to be able to deploy axis2 web services, greg is not capable
>>> of deploying  SecVerifier.aar  due to above reason.
>>>
>>> To get rid from problems due to unnecessary class loading from
>>> SecVerifier/lib, I have changed the integration/security-verifier/pom to
>>> exclude axis2 jar from packaging inside the aar, but to use that only in
>>> compile time.
>>> And I tested it to BRS as well. Shall I commit it to trunk ?
>>>
>>> Thanks
>>> --
>>>
>>> Subash Chaturanga
>>> Software Engineer
>>> WSO2 Inc. http://wso2.com
>>>
>>> email - sub...@wso2.com
>>> phone - 077 2225922
>>>
>>>
>
>
> --
>
> Subash Chaturanga
> Software Engineer
> WSO2 Inc. http://wso2.com
>
> email - sub...@wso2.com
> phone - 077 2225922
>
>

Thanks
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel > Carbon-Platform > #96 has FAILED (3 tests failed, no failures were new). Change made by 8 authors.

[Subash Chaturanga]

On Thu, Mar 1, 2012 at 9:32 AM, Subash Chaturanga  wrote:

>
>
> On Wed, Feb 29, 2012 at 10:56 PM, Shammi Jayasinghe wrote:
>
>> Hi Greg Team,
>>
>>  We are experiencing the build failure due to some governance test
>> failures. Could you please have a look.
>>
>
> I am looking in to this.
>

I have commented Endpoint test temporary. Forgot to update the thread ;)

>
>
>>
>> Thanks
>> Shammi
>>
>> On Wed, Feb 29, 2012 at 9:07 PM, Bamboo  wrote:
>>
>>>  [image: Failed]  
>>> Carbon-Kernel<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL/>›
>>> Carbon-Platform<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD/>›
>>> #96<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/>
>>> failed
>>>
>>> Code has been updated by 
>>> krishantha<http://builder4.us1.wso2.org:/bamboo/browse/author/krishantha>,
>>> chamath <http://builder4.us1.wso2.org:/bamboo/browse/author/chamath>,
>>> madhuka <http://builder4.us1.wso2.org:/bamboo/browse/author/madhuka>,
>>> tharindu<http://builder4.us1.wso2.org:/bamboo/browse/author/tharindu>,
>>> shammi <http://builder4.us1.wso2.org:/bamboo/browse/author/shammi>,
>>> thilinab<http://builder4.us1.wso2.org:/bamboo/browse/author/thilinab>,
>>> amila <http://builder4.us1.wso2.org:/bamboo/browse/author/amila>,
>>> nuwan <http://builder4.us1.wso2.org:/bamboo/browse/author/nuwan>.
>>>
>>> *3/4829* tests failed.
>>>   Failing 
>>> Jobs<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/>
>>> Job
>>> Duration Tests[image: Failed]  Default 
>>> Job<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/>
>>>  (Default
>>> Stage)  109 minutes  3 of 4829 failed  
>>> Logs<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/log>|
>>> Artifacts<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/artifact>
>>>  Code
>>> Changes<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/commit/>
>>>   View
>>> all 19 code 
>>> changes<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/commit/>
>>> madhuka <http://builder4.us1.wso2.org:/bamboo/browse/author/madhuka>
>>> make OSGI level fixed and Make it runing on new Pack of Greg (trunk) and
>>> Jaggery M3 (Trunk) - need new pack for test
>>> This is tested and work fine  121756
>>> amila<http://builder4.us1.wso2.org:/bamboo/browse/author/amila>
>>> making event type processing configurable  121754
>>> amila<http://builder4.us1.wso2.org:/bamboo/browse/author/amila>
>>> change the interface  121753   16 more 
>>> changes…<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/commit>
>>> Tests<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/test>
>>>   View
>>> full test 
>>> details<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/test>
>>>3
>>> Existing Test Failures   Test Job EndpointTest
>>> testDetachEndpointsToService<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test/case/7638559>
>>>   Default
>>> Job<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test>
>>> EndpointTest 
>>> testAddServiceWithEndpoints<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test/case/7640934>
>>>   Default
>>> Job<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test>
>>> EndpointTest 
>>> testAttachEndpointsToService<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test/case/7640764>
>>>   Default
>>> Job<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test>
>>>  View
>>> Online<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96>
>>> | Add 
>>> Comments<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96?commentMode=true>
>>>
>

Re: [Carbon-dev] Carbon Integration Test Framework : Excluding axis2 jar from SecVerifier.aar

[Subash Chaturanga]

Hi Azeez,

On Thu, Mar 1, 2012 at 9:52 AM, Afkham Azeez  wrote:

> Go ahead. Can you check & exclude other unnecessary jars as well?
>
+1,
There are only two dependencies in security-verifier module (axis2 and
carbon core). As maven axis2 aar plugin adds all the jars in maven classpath
in to the lib dir, the only way I could find to exclude a dependency from
being packaged inside lib is to give a scope to the dependency (which will
exclude all its related child dependencies)

Because of that, if I do the same to carbon core dependency, all carbon
core and axis2 dependencies will not get populated into service/lib, which
is still should be fine as I feel. Isn't it? Is there any usage of having
carbon core dependencies inside a service/lib ?


>  --
> Afkham Azeez
> Sent from my phone
> On Feb 29, 2012 10:55 PM, "Subash Chaturanga"  wrote:
>
>> Hi Azeez,
>> For some reason GReg has enabled child first class loading and having
>> problems in deploying axis2 web services. Though any carbon server
>> is expected to be able to deploy axis2 web services, greg is not capable
>> of deploying  SecVerifier.aar  due to above reason.
>>
>> To get rid from problems due to unnecessary class loading from
>> SecVerifier/lib, I have changed the integration/security-verifier/pom to
>> exclude axis2 jar from packaging inside the aar, but to use that only in
>> compile time.
>> And I tested it to BRS as well. Shall I commit it to trunk ?
>>
>> Thanks
>> --
>>
>> Subash Chaturanga
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>>
>> email - sub...@wso2.com
>> phone - 077 2225922
>>
>>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel > Carbon-Platform > #96 has FAILED (3 tests failed, no failures were new). Change made by 8 authors.

[Subash Chaturanga]

On Wed, Feb 29, 2012 at 10:56 PM, Shammi Jayasinghe  wrote:

> Hi Greg Team,
>
>  We are experiencing the build failure due to some governance test
> failures. Could you please have a look.
>

I am looking in to this.


>
> Thanks
> Shammi
>
> On Wed, Feb 29, 2012 at 9:07 PM, Bamboo  wrote:
>
>>  [image: Failed]  
>> Carbon-Kernel<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL/>›
>> Carbon-Platform<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD/>›
>> #96<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/>
>> failed
>>
>> Code has been updated by 
>> krishantha<http://builder4.us1.wso2.org:/bamboo/browse/author/krishantha>,
>> chamath <http://builder4.us1.wso2.org:/bamboo/browse/author/chamath>,
>> madhuka <http://builder4.us1.wso2.org:/bamboo/browse/author/madhuka>,
>> tharindu<http://builder4.us1.wso2.org:/bamboo/browse/author/tharindu>,
>> shammi <http://builder4.us1.wso2.org:/bamboo/browse/author/shammi>,
>> thilinab<http://builder4.us1.wso2.org:/bamboo/browse/author/thilinab>,
>> amila <http://builder4.us1.wso2.org:/bamboo/browse/author/amila>,
>> nuwan <http://builder4.us1.wso2.org:/bamboo/browse/author/nuwan>.
>>
>> *3/4829* tests failed.
>>   Failing 
>> Jobs<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/>
>> Job
>> Duration Tests[image: Failed]  Default 
>> Job<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/>
>>  (Default
>> Stage)  109 minutes  3 of 4829 failed  
>> Logs<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/log>|
>> Artifacts<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/artifact>
>>  Code
>> Changes<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/commit/>
>>   View
>> all 19 code 
>> changes<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/commit/>
>> madhuka <http://builder4.us1.wso2.org:/bamboo/browse/author/madhuka>
>> make OSGI level fixed and Make it runing on new Pack of Greg (trunk) and
>> Jaggery M3 (Trunk) - need new pack for test
>> This is tested and work fine  121756
>> amila<http://builder4.us1.wso2.org:/bamboo/browse/author/amila>
>> making event type processing configurable  121754
>> amila<http://builder4.us1.wso2.org:/bamboo/browse/author/amila>
>> change the interface  121753   16 more 
>> changes…<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/commit>
>> Tests<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/test>
>>   View
>> full test 
>> details<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96/test>
>>3
>> Existing Test Failures   Test Job EndpointTest
>> testDetachEndpointsToService<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test/case/7638559>
>>   Default
>> Job<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test>
>> EndpointTest 
>> testAddServiceWithEndpoints<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test/case/7640934>
>>   Default
>> Job<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test>
>> EndpointTest 
>> testAttachEndpointsToService<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test/case/7640764>
>>   Default
>> Job<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-96/test>
>>  View
>> Online<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96>
>> | Add 
>> Comments<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-96?commentMode=true>
>>
>> This message was sent by Atlassian 
>> Bamboo<http://builder4.us1.wso2.org:/bamboo>
>> .
>>
>> If you wish to stop receiving these emails edit your user 
>> profile<http://builder4.us1.wso2.org:/bamboo/profile/userNotifications.action>or
>>  notify
>> your 
>> administrator<http://builder4.us1.wso2.org:/bamboo/viewAdministrators.action>
>> .
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Best Regards,*
>
> Shammi Jayasinghe*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Carbon Integration Test Framework : Excluding axis2 jar from SecVerifier.aar

[Subash Chaturanga]

Hi Azeez,
For some reason GReg has enabled child first class loading and having
problems in deploying axis2 web services. Though any carbon server
is expected to be able to deploy axis2 web services, greg is not capable of
deploying  SecVerifier.aar  due to above reason.

To get rid from problems due to unnecessary class loading from
SecVerifier/lib, I have changed the integration/security-verifier/pom to
exclude axis2 jar from packaging inside the aar, but to use that only in
compile time.
And I tested it to BRS as well. Shall I commit it to trunk ?

Thanks
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Axis2-aar maven plugin : How to exclude a particular dependency from a AAR file

[Subash Chaturanga]

Hi,
$subject ?
I tried to use excludes in the plugin and it does not affects for
dependencies. Also just tried by setting
 false and then the lib not get
created.
Is there a way to do this ?

Thanks
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] TestNG tests fails due to:Port 9443 is not open

[Subash Chaturanga]

Hi Azeez,

On Tue, Feb 28, 2012 at 5:35 PM, Afkham Azeez  wrote:

> The HTTP/S ports are not open due to some reason. We need to investigate
> why the server is not properly starting up. May be it is waiting for
> required OSGi services, and not starting up due to OSGi dependency issues.
> Try manually starting up the respective servers.


You are quite right.!! This has nothing to do with integration tests. It's
due to the problem of the trunk pack.
Server hangs and waits for org.wso2.carbon.registry.ws.api bundle.

Hi Senaka,
We have to first fix the trunk GReg pack issue. I will start working on it.


>
>
> On Tue, Feb 28, 2012 at 5:32 PM, Subash Chaturanga wrote:
>
>> Hi Azeez,
>>
>> I tried to instantiate the Socket in a separate client class after debug
>> gets hold in the same corresponding place in ClientConnectionUtil class.
>> Same result.
>>
>> java.net.ConnectException: Connection refused
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
>>  at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
>> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
>>  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>> at java.net.Socket.connect(Socket.java:529)
>>  at java.net.Socket.connect(Socket.java:478)
>> at java.net.Socket.(Socket.java:375)
>>  at java.net.Socket.(Socket.java:218)
>> at Main.main(Main.java:23)
>>  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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
>>
>> On Tue, Feb 28, 2012 at 10:40 AM, Afkham Azeez  wrote:
>>
>>> Increasing the timeout will not help. For some reason, the server is not
>>> successfully starting up.
>>>
>>>
>>> On Tue, Feb 28, 2012 at 9:11 AM, Achala Aponso  wrote:
>>>
>>>> Hi,
>>>>
>>>> I also got the same issue with GS integration tests. Increasing the
>>>> timeout didn't work for me too.
>>>>
>>>>
>>>> On Mon, Feb 27, 2012 at 4:31 PM, Subash Chaturanga wrote:
>>>>
>>>>>
>>>>>
>>>>> On Mon, Feb 27, 2012 at 3:35 PM, Nirmal Fernando wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Feb 27, 2012 at 3:26 PM, Subash Chaturanga 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> I am getting GReg integration recent test failures due to "Port 9443
>>>>>>> is not open". Happens at server startup in RegistryTestServerManager.
>>>>>>>
>>>>>>> Here is the sure fire report log. Any reason for this to happen ?
>>>>>>>
>>>>>>
>>>>>> This happens when it failed to open the port (9443) within the time
>>>>>> out (6 ms).
>>>>>> Increasing it might solve the problem!!
>>>>>>
>>>>> I increased the delay 8 times longer than earlier (in
>>>>> ClientConnectionUtil class in integration framework.). It didn't worked
>>>>> Not sure what exactly causing this.
>>>>>
>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Tests run: 270, Failures: 2, Errors: 0, Skipped: 268, Time elapsed:
>>>>>>> 324.265 sec <<< FAILURE!
>>>>>>> startServer(org.wso2.carbon.registry.RegistryTestServerManager)
>>>>>>>  Time elapsed: 0 sec  <<< FAILURE!
>>>>>>> org.testng.internal.thread.ThreadExecutionException:
>>>>>>> org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
>>>>>>> java.lang.RuntimeException: Port 9443 is not open
>>>>>>> at
>>>>>>> org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25)
>>>>>>> at
>>>>>>> org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242)
>>>>>>> at
>>>>>>> org.testng.

Re: [Carbon-dev] TestNG tests fails due to:Port 9443 is not open

[Subash Chaturanga]

Hi Azeez,

I tried to instantiate the Socket in a separate client class after debug
gets hold in the same corresponding place in ClientConnectionUtil class.
Same result.

java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.(Socket.java:375)
at java.net.Socket.(Socket.java:218)
at Main.main(Main.java:23)
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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)

On Tue, Feb 28, 2012 at 10:40 AM, Afkham Azeez  wrote:

> Increasing the timeout will not help. For some reason, the server is not
> successfully starting up.
>
>
> On Tue, Feb 28, 2012 at 9:11 AM, Achala Aponso  wrote:
>
>> Hi,
>>
>> I also got the same issue with GS integration tests. Increasing the
>> timeout didn't work for me too.
>>
>>
>> On Mon, Feb 27, 2012 at 4:31 PM, Subash Chaturanga wrote:
>>
>>>
>>>
>>> On Mon, Feb 27, 2012 at 3:35 PM, Nirmal Fernando wrote:
>>>
>>>>
>>>>
>>>> On Mon, Feb 27, 2012 at 3:26 PM, Subash Chaturanga wrote:
>>>>
>>>>> Hi,
>>>>> I am getting GReg integration recent test failures due to "Port 9443
>>>>> is not open". Happens at server startup in RegistryTestServerManager.
>>>>>
>>>>> Here is the sure fire report log. Any reason for this to happen ?
>>>>>
>>>>
>>>> This happens when it failed to open the port (9443) within the time out
>>>> (6 ms).
>>>> Increasing it might solve the problem!!
>>>>
>>> I increased the delay 8 times longer than earlier (in
>>> ClientConnectionUtil class in integration framework.). It didn't worked
>>> Not sure what exactly causing this.
>>>
>>>
>>>>
>>>>>
>>>>>
>>>>> Tests run: 270, Failures: 2, Errors: 0, Skipped: 268, Time elapsed:
>>>>> 324.265 sec <<< FAILURE!
>>>>> startServer(org.wso2.carbon.registry.RegistryTestServerManager)  Time
>>>>> elapsed: 0 sec  <<< FAILURE!
>>>>> org.testng.internal.thread.ThreadExecutionException:
>>>>> org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
>>>>> java.lang.RuntimeException: Port 9443 is not open
>>>>> at
>>>>> org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25)
>>>>> at
>>>>> org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242)
>>>>> at
>>>>> org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:200)
>>>>> at
>>>>> org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:528)
>>>>> at
>>>>> org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
>>>>> at
>>>>> org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
>>>>> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277)
>>>>> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>>>>> at
>>>>> org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
>>>>> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
>>>>> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
>>>>> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
>>>>> at org.testng.TestNG.run(TestNG.java:999)
>>>>> at
>>>>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:60)
>>>>> at
>>>>> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:153)
>>>>> at
>>>>> org.apache.maven.surefire.testng.TestNGDirectoryTes

Re: [Carbon-dev] TestNG tests fails due to:Port 9443 is not open

[Subash Chaturanga]

On Mon, Feb 27, 2012 at 3:35 PM, Nirmal Fernando  wrote:

>
>
> On Mon, Feb 27, 2012 at 3:26 PM, Subash Chaturanga wrote:
>
>> Hi,
>> I am getting GReg integration recent test failures due to "Port 9443 is
>> not open". Happens at server startup in RegistryTestServerManager.
>>
>> Here is the sure fire report log. Any reason for this to happen ?
>>
>
> This happens when it failed to open the port (9443) within the time out
> (6 ms).
> Increasing it might solve the problem!!
>
I increased the delay 8 times longer than earlier (in ClientConnectionUtil
class in integration framework.). It didn't worked
Not sure what exactly causing this.


>
>>
>>
>> Tests run: 270, Failures: 2, Errors: 0, Skipped: 268, Time elapsed:
>> 324.265 sec <<< FAILURE!
>> startServer(org.wso2.carbon.registry.RegistryTestServerManager)  Time
>> elapsed: 0 sec  <<< FAILURE!
>> org.testng.internal.thread.ThreadExecutionException:
>> org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
>> java.lang.RuntimeException: Port 9443 is not open
>> at
>> org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25)
>> at
>> org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242)
>> at
>> org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:200)
>> at
>> org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:528)
>> at
>> org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
>> at
>> org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
>> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277)
>> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>> at
>> org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
>> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
>> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
>> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
>> at org.testng.TestNG.run(TestNG.java:999)
>> at
>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:60)
>> at
>> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:153)
>> at
>> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
>> at
>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
>> 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.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
>> at $Proxy0.invoke(Unknown Source)
>> at
>> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
>> at
>> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
>> Caused by:
>> org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
>> java.lang.RuntimeException: Port 9443 is not open
>> at
>> org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:49)
>> at
>> org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>> at
>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> 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)
>> Caused by: java.lang.RuntimeException: Port 9443 is not open
>> at
>> org.wso2.carbon.integration.framework.ClientConnectionUtil.waitForPort(ClientConnectionUtil.java:106)
>> at
>> org.wso2.carbon.integration.framework.utils.Server

[Carbon-dev] TestNG tests fails due to:Port 9443 is not open

[Subash Chaturanga]

Hi,
I am getting GReg integration recent test failures due to "Port 9443 is not
open". Happens at server startup in RegistryTestServerManager.

Here is the sure fire report log. Any reason for this to happen ?


Tests run: 270, Failures: 2, Errors: 0, Skipped: 268, Time elapsed: 324.265
sec <<< FAILURE!
startServer(org.wso2.carbon.registry.RegistryTestServerManager)  Time
elapsed: 0 sec  <<< FAILURE!
org.testng.internal.thread.ThreadExecutionException:
org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
java.lang.RuntimeException: Port 9443 is not open
at
org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25)
at
org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242)
at
org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:200)
at
org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:528)
at
org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
at
org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:60)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:153)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
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.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at $Proxy0.invoke(Unknown Source)
at
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
Caused by: org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
java.lang.RuntimeException: Port 9443 is not open
at
org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:49)
at
org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
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)
Caused by: java.lang.RuntimeException: Port 9443 is not open
at
org.wso2.carbon.integration.framework.ClientConnectionUtil.waitForPort(ClientConnectionUtil.java:106)
at
org.wso2.carbon.integration.framework.utils.ServerUtils.startServerUsingCarbonHome(ServerUtils.java:99)




Thanks
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel > Carbon-Platform > #64 has FAILED (11 tests failed). Change made by 8 authors.

[Subash Chaturanga]

On Fri, Feb 24, 2012 at 9:45 AM, Subash Chaturanga  wrote:

>
>
> On Fri, Feb 24, 2012 at 7:51 AM, Pradeep Fernando wrote:
>
>> Hi Senaka,
>>
>> As I beleive, these test failures are due to "intermittent registry test
>> failures in the  builder machines". AFAIR, we fixed all the externals
>> during svn restructuring.
>>
>> Any way, since Subash is looking in to it, hope we can get rid of the
>> test failures EOD today.
>
>
Fixed under revision 121460.

>
> I took an up and started to reproduce the failures .
> Thanks
>
>>
>>
>> --Pradeep
>>
>
>
>
> --
>
> Subash Chaturanga
> Software Engineer
> WSO2 Inc. http://wso2.com
>
> email - sub...@wso2.com
> phone - 077 2225922
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel > Carbon-Platform > #64 has FAILED (11 tests failed). Change made by 8 authors.

[Subash Chaturanga]

On Fri, Feb 24, 2012 at 7:51 AM, Pradeep Fernando  wrote:

> Hi Senaka,
>
> As I beleive, these test failures are due to "intermittent registry test
> failures in the  builder machines". AFAIR, we fixed all the externals
> during svn restructuring.
>
> Any way, since Subash is looking in to it, hope we can get rid of the test
> failures EOD today.


I took an up and started to reproduce the failures .
Thanks

>
>
> --Pradeep
>



-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Regarding geronimo-stax-api_1.0_spec-1.0.1.wso2v1.jar

[Subash Chaturanga]

Hi,
We already have geronimo-stax-api_1.0_spec-1.0.1.wso2v1.jar  bundle inside
CARBON_HOME/repository/components/plugins.
Why the same jar is  added as a jar to be endorsed
inside CARBON_HOME/lib/endorsed

Thanks
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Agent component build failure

[Subash Chaturanga]

Hi,

On Tue, Feb 21, 2012 at 11:05 AM, Rajika Kumarasiri  wrote:

> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 Carbon - Agent ... SUCCESS [0.472s]
> [INFO] WSO2 Carbon - Agent Thrift Commons  SUCCESS [3.948s]
> [INFO] WSO2 Carbon - Agent Commons ... SUCCESS [0.534s]
> [INFO] WSO2 Carbon - Agent Client  FAILURE [0.726s]
> [INFO] WSO2 Carbon - Agent Server  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 7.069s
> [INFO] Finished at: Tue Feb 21 10:59:36 IST 2012
> [INFO] Final Memory: 22M/92M
> [INFO]
> 
> [ERROR] Failed to execute goal on project org.wso2.carbon.agent: Could not
> resolve dependencies for project
> org.wso2.carbon:org.wso2.carbon.agent:bundle:4.0.0-SNAPSHOT: The following
> artifacts could not be resolved:
> org.wso2.carbon:org.wso2.carbon.agent.commons:jar:1.0.0-SNAPSHOT,
> org.wso2.carbon:org.wso2.carbon.agent.commons.thrift:jar:1.0.0-SNAPSHOT:
> Failure to find
> org.wso2.carbon:org.wso2.carbon.agent.commons:jar:1.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]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.carbon.agent
> [rajika@localhost agent]$
>
>
I also encountered the same build failure .


>
> I think this component doesn't have good name. It doesn't reveal any
> domain name.
>
> Rajika
>
> _______
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Making GReg JCR API 100% JCR compliant : Progress Update

[Subash Chaturanga]

Hi all,
JCR* javax.jcr.security* is now *100%* JCR compliant. GReg now supports all
TCK access control management scenarios through JCR layer.
(Passed all 79 test cases under seven TCK scenarios.)

On Sun, Feb 5, 2012 at 8:08 PM, Subash Chaturanga  wrote:

> Hi all,
> I started working on $subject couple of weeks back.
>
> JCR javax.jcr.nodetype is now 100% JCR compliant (under revision 120113).
>
> Node type management is one of the most key features of JCR, where it
> applies to almost all places in JCR. Now GReg supports all JCR predefined
> node types (>30)
> and all JCR node type management functionality. There, we specifically
> support to register node types through an XML file where you do not need to
> do them through API.
>
> Thanks
> --
>
> Subash Chaturanga
> Software Engineer
> WSO2 Inc. http://wso2.com
>
> email - sub...@wso2.com
> phone - 077 2225922
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Making GReg JCR API 100% JCR compliant : Progress Update

[Subash Chaturanga]

Hi Senaka,

On Sun, Feb 5, 2012 at 9:04 PM, Senaka Fernando  wrote:

> Hi Subash,
>
> Awesome. That's good progress. Now from the TCK PoV, where are we?


I did a run on the TCK for the whole JCR impl initially(There were same as
final results in 2010) but not quite recently . For javax.jcr.nodetype TCK
passes in 100%.
And it should fix some 20-30 more test failures in javax.jcr also. What
I've planned is(as specified in the milestone plan), go to each module,
make it 100% compliant and move to the next. Will update the progress of
others when finished.


>

Thanks,
> Senaka.
>
>
> On Sun, Feb 5, 2012 at 8:08 PM, Subash Chaturanga  wrote:
>
>> Hi all,
>> I started working on $subject couple of weeks back.
>>
>> JCR javax.jcr.nodetype is now 100% JCR compliant (under revision 120113).
>>
>> Node type management is one of the most key features of JCR, where it
>> applies to almost all places in JCR. Now GReg supports all JCR predefined
>> node types (>30)
>> and all JCR node type management functionality. There, we specifically
>> support to register node types through an XML file where you do not need to
>> do them through API.
>>
>> Thanks
>> --
>>
>> Subash Chaturanga
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>>
>> email - sub...@wso2.com
>> phone - 077 2225922
>>
>>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Making GReg JCR API 100% JCR compliant : Progress Update

[Subash Chaturanga]

Hi all,
I started working on $subject couple of weeks back.

JCR javax.jcr.nodetype is now 100% JCR compliant (under revision 120113).

Node type management is one of the most key features of JCR, where it
applies to almost all places in JCR. Now GReg supports all JCR predefined
node types (>30)
and all JCR node type management functionality. There, we specifically
support to register node types through an XML file where you do not need to
do them through API.

Thanks
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Progress on integration tests

[Subash Chaturanga]

On Sat, Feb 4, 2012 at 2:39 PM, Senaka Fernando  wrote:

> Hi Subash,
>
> Please work on this and get this up and running, after your support work.
>

Sure, will do


>
> Thanks,
> Senaka.
>
>
> On Sat, Feb 4, 2012 at 2:04 PM, Afkham Azeez  wrote:
>
>> The whole integration module has been commented out it seems.
>>
>> --
>> Afkham Azeez
>> Sent from my phone
>> On Feb 4, 2012 11:29 AM, "Subash Chaturanga"  wrote:
>>
>>> Hi Senaka
>>>
>>> On Sat, Feb 4, 2012 at 2:16 AM, Senaka Fernando  wrote:
>>>
>>>> Hi Subash,
>>>>
>>>> Where are we with the integration tests? Is this work complete?
>>>>
>>>
>>> Yes, its completely migrated and our integration tests were running fine
>>> with the product build. (I have excluded the old JUnit tests from pom
>>> without removing the source)
>>>
>>> But couple of days back, probably due to some change, one integration
>>> test was failing when building in a clean repo (Bamboo) and we couldn't
>>> reproduce locally. Until we fix that, Shammi excluded the integration test
>>> from the build.
>>>
>>> Thanks
>>>
>>>
>>>>
>>>> Thanks,
>>>> Senaka.
>>>>
>>>>
>>>> On Sat, Jan 21, 2012 at 8:34 AM, Subash Chaturanga wrote:
>>>>
>>>>>
>>>>>
>>>>> On Fri, Jan 20, 2012 at 6:34 AM, Afkham Azeez  wrote:
>>>>>
>>>>>> Folks, how is this progressing? I didn't see many updates during the
>>>>>> past couple of weeks. Some products are still being built without
>>>>>> integration tests.
>>>>>>
>>>>> In GReg, all integration tests have migrated to testng and fixed all
>>>>> the the broken tests except three test cases due to some known issues and
>>>>> need some work around to fix them. (currently I have excluded them from
>>>>> testng pom).
>>>>>
>>>>>
>>>>>>  --
>>>>>> Afkham Azeez
>>>>>> Sent from my phone
>>>>>>
>>>>>> ___
>>>>>> Carbon-dev mailing list
>>>>>> Carbon-dev@wso2.org
>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Subash Chaturanga
>>>>> Software Engineer
>>>>> WSO2 Inc. http://wso2.com
>>>>>
>>>>> email - sub...@wso2.com
>>>>> phone - 077 2225922
>>>>>
>>>>>
>>>>> ___
>>>>> Carbon-dev mailing list
>>>>> Carbon-dev@wso2.org
>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Senaka Fernando*
>>>> Product Manager - WSO2 Governance Registry;
>>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>>>> Member; Apache Software Foundation; http://apache.org
>>>>
>>>> E-mail: senaka AT wso2.com
>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>>> Linked-In: http://linkedin.com/in/senakafernando
>>>>
>>>> *
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Subash Chaturanga
>>> Software Engineer
>>> WSO2 Inc. http://wso2.com
>>>
>>> email - sub...@wso2.com
>>> phone - 077 2225922
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Progress on integration tests

[Subash Chaturanga]

Hi Senaka

On Sat, Feb 4, 2012 at 2:16 AM, Senaka Fernando  wrote:

> Hi Subash,
>
> Where are we with the integration tests? Is this work complete?
>

Yes, its completely migrated and our integration tests were running fine
with the product build. (I have excluded the old JUnit tests from pom
without removing the source)

But couple of days back, probably due to some change, one integration test
was failing when building in a clean repo (Bamboo) and we couldn't
reproduce locally. Until we fix that, Shammi excluded the integration test
from the build.

Thanks


>
> Thanks,
> Senaka.
>
>
> On Sat, Jan 21, 2012 at 8:34 AM, Subash Chaturanga wrote:
>
>>
>>
>> On Fri, Jan 20, 2012 at 6:34 AM, Afkham Azeez  wrote:
>>
>>> Folks, how is this progressing? I didn't see many updates during the
>>> past couple of weeks. Some products are still being built without
>>> integration tests.
>>>
>> In GReg, all integration tests have migrated to testng and fixed all the
>> the broken tests except three test cases due to some known issues and need
>> some work around to fix them. (currently I have excluded them from testng
>> pom).
>>
>>
>>>  --
>>> Afkham Azeez
>>> Sent from my phone
>>>
>>> ___________
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>>
>> Subash Chaturanga
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>>
>> email - sub...@wso2.com
>> phone - 077 2225922
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *
> Lean . Enterprise . Middleware
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
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 > #162 has FAILED (1 tests failed). Change made by 9 authors.

[Subash Chaturanga]

t;> Carbon Trunk Build 
>> Process<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test>
>> ServiceTest 
>> testServiceAttachments<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test/case/1618952>
>>   WSO2
>> Carbon Trunk Build 
>> Process<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test>
>> ServiceTest 
>> testServiceSearch<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test/case/1619440>
>>   WSO2
>> Carbon Trunk Build 
>> Process<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test>
>> WSDLTest 
>> testEditWSDL<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test/case/1618949>
>>   WSO2
>> Carbon Trunk Build 
>> Process<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test>
>> WSDLTest 
>> testAddWSDL<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test/case/1618950>
>>   WSO2
>> Carbon Trunk Build 
>> Process<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test>
>> XMLResourceAddTestCase 
>> testTemplate<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test/case/5932761>
>>   WSO2
>> Carbon Trunk Build 
>> Process<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-162/test>
>>  View
>> Online<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-162>
>> | Add 
>> Comments<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-162?commentMode=true>
>>
>> This message was sent by Atlassian 
>> Bamboo<http://builder4.us1.wso2.org:/bamboo>
>> .
>>
>> If you wish to stop receiving these emails edit your user 
>> profile<http://builder4.us1.wso2.org:/bamboo/profile/userNotifications.action>or
>>  notify
>> your 
>> administrator<http://builder4.us1.wso2.org:/bamboo/viewAdministrators.action>
>> .
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Best Regards,*
>
> Shammi Jayasinghe*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
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 > #161 has FAILED (9 tests failed, no failures were new). Change made by 4 authors.

[Subash Chaturanga]

On Wed, Feb 1, 2012 at 7:37 PM, Waruna Ranasinghe  wrote:

> sent from my mobile.
>
> On Feb 1, 2012 7:30 PM, "Subash Chaturanga"  wrote:
> >
> >
> >
> > On Wed, Feb 1, 2012 at 6:21 PM, Shammi Jayasinghe 
> wrote:
> >>
> >> Hi Greg team,
> >>
> >>  I build with a clean repo locally. In that also  two testes were
> failed. I have attached the sure-fire rports of them with this.
> >
> >
> > Hi I took a complete up on trunk and still couldn't reproduce those test
> failures. Still trying to reproduce.
> Have a look at the surefire reports. It will give you an idea.
>

I already did. It occurs when adding a wsdl through Resource Admin Service,
where AddResourceUtil will hit at the back end. Cannot exactly identify
without reproduce and debug.

> >
> >
> >>
> >>
> >> Thanks
> >> Shammi
> >>
> >>
> >> On Wed, Feb 1, 2012 at 3:52 PM, Shammi Jayasinghe 
> wrote:
> >>>
> >>> Hi Greg Team,
> >>>
> >>>
> >>> Please fix the following test fails.
> >>>
> >>> Thanks
> >>> Shammi
> >>>
> >>> On Wed, Feb 1, 2012 at 3:41 PM, Bamboo  wrote:
> >>>>
> >>>> WSO2 Carbon Trunk › WSO2 Carbon - Platform Trunk › #161 failed
> >>>>
> >>>> This build was manually triggered by BambooBuilder.
> >>>>
> >>>> 9/7661 tests failed.
> >>>>
> >>>> Failing Jobs
> >>>> Job
> >>>> Duration
> >>>> Tests
> >>>> WSO2 Carbon Trunk Build Process (Default Stage)
> >>>> 365 minutes
> >>>> 9 of 7661 failed
> >>>> Logs | Artifacts
> >>>> Code Changes
> >>>> View all 5 code changes
> >>>> nuwan
> >>>> doc changes
> >>>> 119935
>
> >>>> supunm
> >>>> correcting parent pom.
> >>>> 119934
> >>>> anjana
> >>>> setting quartz to WARN debug level
> >>>> 119933
> >>>> 2 more changes…
> >>>> Tests
> >>>> View full test details
> >>>> 9 Existing Test Failures
> >>>> 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
> >>>> RegistryTestServerManager startServer
> >>>> WSO2 Carbon Trunk Build Process
> >>>> XMLResourceAddTestCase testTemplate
> >>>> 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 or
> notify your administrator.
> >>>>
> >>>>
> >>>> ___
> >>>> Carbon-dev mailing list
> >>>> Carbon-dev@wso2.org
> >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Best Regards,
> >>>
> >>> Shammi Jayasinghe
> >>> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> >>> mobile: +94 71 4493085
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Best Regards,
> >>
> >> Shammi Jayasinghe
> >> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> >> mobile: +94 71 4493085
> >>
> >>
> >
> >
> >
> > --
> >
> > Subash Chaturanga
> > Software Engineer
> > WSO2 Inc. http://wso2.com
> >
> > email - sub...@wso2.com
> > phone - 077 2225922
> >
> >
> > ___
> > 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
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
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 > #161 has FAILED (9 tests failed, no failures were new). Change made by 4 authors.

[Subash Chaturanga]

rowse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-161/test>
>>> WSDLTest 
>>> testEditWSDL<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-161/test/case/1618949>
>>>   WSO2
>>> Carbon Trunk Build 
>>> Process<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-161/test>
>>> WSDLTest 
>>> testAddWSDL<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-161/test/case/1618950>
>>>   WSO2
>>> Carbon Trunk Build 
>>> Process<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-161/test>
>>> RegistryTestServerManager 
>>> startServer<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-161/test/case/5932964>
>>>   WSO2
>>> Carbon Trunk Build 
>>> Process<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-161/test>
>>> XMLResourceAddTestCase 
>>> testTemplate<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-161/test/case/5932761>
>>>   WSO2
>>> Carbon Trunk Build 
>>> Process<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-161/test>
>>>  View
>>> Online<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-161>
>>> | Add 
>>> Comments<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-161?commentMode=true>
>>>
>>> This message was sent by Atlassian 
>>> Bamboo<http://builder4.us1.wso2.org:/bamboo>
>>> .
>>>
>>> If you wish to stop receiving these emails edit your user 
>>> profile<http://builder4.us1.wso2.org:/bamboo/profile/userNotifications.action>or
>>>  notify
>>> your 
>>> administrator<http://builder4.us1.wso2.org:/bamboo/viewAdministrators.action>
>>> .
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Best Regards,*
>>
>> Shammi Jayasinghe*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
>> mobile: +94 71 4493085
>>
>>
>>
>
>
> --
> Best Regards,*
>
> Shammi Jayasinghe*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Greg test failure - Trunk - Bamboo build #161

[Subash Chaturanga]

Hi

On Wed, Feb 1, 2012 at 2:10 PM, Shammi Jayasinghe  wrote:

> Hi Greg Team,
>
>
I am looking into it.


>  There are two tests failed in the current bamboo build (#161).  Please
> fix them
>
>
> http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-161/log
>
>
> Thanks
> Shammi
>
>
> build31-Jan-2012 23:56:35[2012-01-31 23:56:35,125]  INFO
> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -  ...
> 44 more
> build31-Jan-2012 23:56:57Importing Code Coverage Details...
> build31-Jan-2012 23:56:58Imported Code Coverage Details.
> build31-Jan-2012 23:56:59Tests run: 270, Failures: 2, Errors: 0,
> Skipped: 268, Time elapsed: 80.816 sec <<< FAILURE!
> build31-Jan-2012 23:56:59
> build31-Jan-2012 23:56:59Results :
> build31-Jan-2012 23:56:59
> build31-Jan-2012 23:56:59Failed tests:
> build31-Jan-2012 23:56:59
> startServer(org.wso2.carbon.registry.RegistryTestServerManager):
> org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
> java.lang.AssertionError: Unable to get file content:
> org.apache.axis2.AxisFault: Failed to add resource
> /_system/governance/trunk/wsdls/eu/dataaccess/footballpool/sample.wsdl. An
> exception occurred while executing handler chain. null
> build31-Jan-2012 23:56:59  testTemplate on instance
> testTemplate(org.wso2.carbon.registry.resource.test.XMLResourceAddTestCase)(org.wso2.carbon.registry.resource.test.XMLResourceAddTestCase):
> Unable to start server
> build31-Jan-2012 23:56:59
> build31-Jan-2012 23:56:59Tests run: 270, Failures: 2, Errors: 0,
> Skipped: 268
> buil
>
> --
> Best Regards,*
>
> Shammi Jayasinghe*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>
>
> ___________
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Cannot invoke a service when it manually deployed as an aar in GReg.

[Subash Chaturanga]

On Thu, Jan 26, 2012 at 6:13 AM, Afkham Azeez  wrote:

> Yeah, there is no need to add redundant jars into the AAR. Perhaps we can
> exclude these jars during AAR creation.
>
+1

>  --
> Afkham Azeez
> Sent from my phone
> On Jan 25, 2012 10:30 PM, "Subash Chaturanga"  wrote:
>
>>
>>
>> On Wed, Jan 25, 2012 at 7:02 PM, Amila Suriarachchi wrote:
>>
>>>
>>>
>>> On Fri, Jan 20, 2012 at 2:09 PM, Afkham Azeez  wrote:
>>>
>>>> It is very strange that MessageContext.getCurrentContext returns null
>>>> only in G-Reg.
>>>>
>>>
>>> this is a classloading issue. this .aar file contains an axis2 jar in
>>> the lib folder and GReg has set child first class loading true.
>>>
>>>
>> Yes, it worked fine when set child first class loading to false in greg
>> axis2.xml, due to above mentioned reason. In GReg it was set to true, which
>> I didn't see in other products (i.e as).
>>
>> Hi Azeez, isn't it suppose to include only service specific jars in the
>> lib, as those other jars are available from the platform dependencies ?
>>
>>
>>> thanks,
>>> Amila.
>>>
>>>>
>>>> On Fri, Jan 20, 2012 at 12:44 PM, Subash Chaturanga wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I came across with this issue when running the GReg testng
>>>>> SecurityVetification test case as it invokes
>>>>> the org.wso2.carbon.integration.secverifier.SecurityVerifierService.
>>>>> There was a NPE as axis2 MessageContext gets null.
>>>>>
>>>>> This can be reproduced when you manually drop a service aar  to
>>>>> GREG_HOME/repository/deployments/server/axis2Services/ and try to invoke
>>>>> it.
>>>>> Any idea ?
>>>>>
>>>>> Here is the error log.
>>>>>
>>>>> [2012-01-20 12:41:14,321] ERROR
>>>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -  Exception occurred
>>>>> while trying to invoke service method verifyAdminServices
>>>>> java.lang.reflect.InvocationTargetException
>>>>>  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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>>>>> at
>>>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>>>>>  at
>>>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>>>> at
>>>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>>>>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
>>>>> at
>>>>> org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:144)
>>>>>  at
>>>>> org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:139)
>>>>> at
>>>>> org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:837)
>>>>>  at
>>>>> org.wso2.carbon.core.transports.CarbonServlet.handleRestRequest(CarbonServlet.java:233)
>>>>> at
>>>>> org.wso2.carbon.core.transports.CarbonServlet.doGet(CarbonServlet.java:131)
>>>>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>>>>  at
>>>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
>>>>> at
>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
>>>>>  at
>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>>>>  at
>>>>> org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:164)
>>>>> at javax.servlet.http.HttpServlet.servi

Re: [Carbon-dev] Cannot invoke a service when it manually deployed as an aar in GReg.

[Subash Chaturanga]

On Wed, Jan 25, 2012 at 7:02 PM, Amila Suriarachchi  wrote:

>
>
> On Fri, Jan 20, 2012 at 2:09 PM, Afkham Azeez  wrote:
>
>> It is very strange that MessageContext.getCurrentContext returns null
>> only in G-Reg.
>>
>
> this is a classloading issue. this .aar file contains an axis2 jar in the
> lib folder and GReg has set child first class loading true.
>
>
Yes, it worked fine when set child first class loading to false in greg
axis2.xml, due to above mentioned reason. In GReg it was set to true, which
I didn't see in other products (i.e as).

Hi Azeez, isn't it suppose to include only service specific jars in the
lib, as those other jars are available from the platform dependencies ?


> thanks,
> Amila.
>
>>
>> On Fri, Jan 20, 2012 at 12:44 PM, Subash Chaturanga wrote:
>>
>>> Hi all,
>>>
>>> I came across with this issue when running the GReg testng
>>> SecurityVetification test case as it invokes
>>> the org.wso2.carbon.integration.secverifier.SecurityVerifierService.
>>> There was a NPE as axis2 MessageContext gets null.
>>>
>>> This can be reproduced when you manually drop a service aar  to
>>> GREG_HOME/repository/deployments/server/axis2Services/ and try to invoke
>>> it.
>>> Any idea ?
>>>
>>> Here is the error log.
>>>
>>> [2012-01-20 12:41:14,321] ERROR
>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -  Exception occurred
>>> while trying to invoke service method verifyAdminServices
>>> java.lang.reflect.InvocationTargetException
>>>  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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>>>  at
>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>> at
>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
>>> at
>>> org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:144)
>>>  at
>>> org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:139)
>>> at
>>> org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:837)
>>>  at
>>> org.wso2.carbon.core.transports.CarbonServlet.handleRestRequest(CarbonServlet.java:233)
>>> at
>>> org.wso2.carbon.core.transports.CarbonServlet.doGet(CarbonServlet.java:131)
>>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>>  at
>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
>>>  at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>>  at org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:164)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>>  at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>  at
>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
>>> at
>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164)
>>>  at
>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
>>> at
>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
>>>  at
>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
>>> at
>>> org.wso2.carbon.server.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:154)
>>>  at org.wso2.carbon.

Re: [Carbon-dev] Progress on integration tests

[Subash Chaturanga]

On Fri, Jan 20, 2012 at 6:34 AM, Afkham Azeez  wrote:

> Folks, how is this progressing? I didn't see many updates during the past
> couple of weeks. Some products are still being built without integration
> tests.
>
In GReg, all integration tests have migrated to testng and fixed all the
the broken tests except three test cases due to some known issues and need
some work around to fix them. (currently I have excluded them from testng
pom).


>  --
> Afkham Azeez
> Sent from my phone
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Cannot invoke a service when it manually deployed as an aar in GReg.

[Subash Chaturanga]

Hi

I debug in axis2  level and the reason for this issue is;

The thread which set the axis2 message context to the ThreadLocal, cannot
acquire it in the service. Its a null. When debugging I kept tracking on
the thread ids and the thread which set the message context to its thread
local get removed before reaching to the service.

Hi Senaka,
has this done for some fix  ?


On Fri, Jan 20, 2012 at 2:09 PM, Afkham Azeez  wrote:

> It is very strange that MessageContext.getCurrentContext returns null only
> in G-Reg.
>
> On Fri, Jan 20, 2012 at 12:44 PM, Subash Chaturanga wrote:
>
>> Hi all,
>>
>> I came across with this issue when running the GReg testng
>> SecurityVetification test case as it invokes
>> the org.wso2.carbon.integration.secverifier.SecurityVerifierService.
>> There was a NPE as axis2 MessageContext gets null.
>>
>> This can be reproduced when you manually drop a service aar  to
>> GREG_HOME/repository/deployments/server/axis2Services/ and try to invoke
>> it.
>> Any idea ?
>>
>> Here is the error log.
>>
>> [2012-01-20 12:41:14,321] ERROR
>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -  Exception occurred
>> while trying to invoke service method verifyAdminServices
>> java.lang.reflect.InvocationTargetException
>>  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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>> at
>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>>  at
>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>> at
>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
>> at
>> org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:144)
>>  at
>> org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:139)
>> at
>> org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:837)
>>  at
>> org.wso2.carbon.core.transports.CarbonServlet.handleRestRequest(CarbonServlet.java:233)
>> at
>> org.wso2.carbon.core.transports.CarbonServlet.doGet(CarbonServlet.java:131)
>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>  at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
>>  at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>  at org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:164)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>  at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>  at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164)
>>  at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
>>  at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
>> at
>> org.wso2.carbon.server.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:154)
>>  at org.wso2.carbon.server.TomcatServer$1.invoke(TomcatServer.java:257)
>> at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
>>  at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:399)
>>  at
>> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:396)
>> at
>> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtoc

[Carbon-dev] Cannot invoke a service when it manually deployed as an aar in GReg.

[Subash Chaturanga]

Hi all,

I came across with this issue when running the GReg testng
SecurityVetification test case as it invokes
the org.wso2.carbon.integration.secverifier.SecurityVerifierService.
There was a NPE as axis2 MessageContext gets null.

This can be reproduced when you manually drop a service aar  to
GREG_HOME/repository/deployments/server/axis2Services/ and try to invoke
it.
Any idea ?

Here is the error log.

[2012-01-20 12:41:14,321] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} -  Exception occurred
while trying to invoke service method verifyAdminServices
java.lang.reflect.InvocationTargetException
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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:144)
at
org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:139)
at
org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:837)
at
org.wso2.carbon.core.transports.CarbonServlet.handleRestRequest(CarbonServlet.java:233)
at
org.wso2.carbon.core.transports.CarbonServlet.doGet(CarbonServlet.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
at
org.wso2.carbon.server.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:154)
at org.wso2.carbon.server.TomcatServer$1.invoke(TomcatServer.java:257)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:399)
at
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:396)
at
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:356)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1534)
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)
Caused by: java.lang.NullPointerException
at
org.wso2.carbon.integration.secverifier.SecurityVerifierService.verifyAdminServices(SecurityVerifierService.java:42)


Thanks
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
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

[Subash Chaturanga]

>>>>>>>> As I found out, the issue was that Maven3 doesn't identify the
>>>>>>>> carbon root pom, ie. org.wso2.carbon:carbon-platform. A workaround for 
>>>>>>>> this
>>>>>>>> problem is to build the carbon root pom first with all the 
>>>>>>>> declarations in its pom.xml commented out. And then, remove the added
>>>>>>>> comments in the copied carbon-platform pom in the M2 repo. But I think 
>>>>>>>> this
>>>>>>>> needs to be fixed to minimize this inconvenience, and isn't
>>>>>>>> straight-forward for a new builder.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> --Kasun
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>> 
>>>>>>>> [INFO] Building WSO2 Carbon - Service Stubs - Aggregator Module
>>>>>>>> 3.2.0-SNAPSHOT
>>>>>>>> [INFO]
>>>>>>>> 
>>>>>>>> Downloading:
>>>>>>>> http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/carbon-platform/3.2.0-SNAPSHOT/maven-metadata.xml
>>>>>>>> Downloading:
>>>>>>>> http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/carbon-platform/3.2.0-SNAPSHOT/carbon-platform-3.2.0-SNAPSHOT.pom
>>>>>>>> [INFO]
>>>>>>>> 
>>>>>>>> [INFO] Reactor Summary:
>>>>>>>> [INFO]
>>>>>>>> [INFO] WSO2 Carbon - Service Stubs - Aggregator Module ... FAILURE
>>>>>>>> [1.273s]
>>>>>>>> [INFO] WSO2 Carbon - Stratos Common Stubs  SKIPPED
>>>>>>>> [INFO] WSO2 Carbon - Tenant Registration GApp Stub ... SKIPPED
>>>>>>>> [INFO] WSO2 Carbon - Data Admin Console Stub . SKIPPED
>>>>>>>> ---
>>>>>>>> ---
>>>>>>>> [INFO] WSO2 Carbon - Qpid Stub ... SKIPPED
>>>>>>>> [INFO] WSO2 Carbon - Tenant activity Stub  SKIPPED
>>>>>>>> [INFO] WSO2 Carbon - Load Balance Agent Stub . SKIPPED
>>>>>>>> [INFO]
>>>>>>>> 
>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>> [INFO]
>>>>>>>> 
>>>>>>>> [INFO] Total time: 2.870s
>>>>>>>> [INFO] Finished at: Tue Dec 06 14:23:26 IST 2011
>>>>>>>> [INFO] Final Memory: 19M/618M
>>>>>>>> [INFO]
>>>>>>>> 
>>>>>>>> [ERROR] Failed to execute goal on project service-stubs: Could not
>>>>>>>> resolve dependencies for project
>>>>>>>> org.wso2.carbon:service-stubs:pom:3.2.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.wso2v1 (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.wso2v1: *Could not find
>>>>>>>> artifact org.wso2.carbon:carbon-platform:pom:3.2.0-SNAPSHOT *in
>>>>>>>> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
>>>>>>>> -> [Help 1]
>>>>>>>> [ERROR]
>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>>>>>>>> with the -e switch.
>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>>>>>>> logging.
>>>>>>>> [ERROR]
>>>>>>>> [ERROR] For more information about the errors and possible
>>>>>>>> solutions, please read the following articles:
>>>>>>>> [ERROR] [Help 1]
>>>>>>>> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>>>>>>>>
>>>>>>>>
>>>>>>>> ___
>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks,
>>>>> Shariq.
>>>>>
>>>>>
>>>>> ___
>>>>> 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 mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Keheliya Gallaba
>> Software Engineer
>> WSO2 Inc.
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Kathiravelu Pradeeban.
> Software Engineer.
> WSO2 Inc.
>
> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Carbon-commits] [Carbon] svn commit r118913 - trunk/carbon/products/greg/modules/integration/registry/tests/src/test/java/org/wso2/carbon/registry/ws/client/test/general

[Subash Chaturanga]

On Fri, Jan 13, 2012 at 4:42 PM, Afkham Azeez  wrote:

>
>
> On Thu, Jan 12, 2012 at 2:19 PM,  wrote:
>
>> Author: subash
>> Date: Thu Jan 12 00:49:03 2012
>> New Revision: 118913
>> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=118913
>>
>> Log:
>> Added a test for the issue CARBON-12200
>>
>> Modified:
>>
>> trunk/carbon/products/greg/modules/integration/registry/tests/src/test/java/org/wso2/carbon/registry/ws/client/test/general/CollectionChildCountWSTestCase.java
>>
>> Modified:
>> trunk/carbon/products/greg/modules/integration/registry/tests/src/test/java/org/wso2/carbon/registry/ws/client/test/general/CollectionChildCountWSTestCase.java
>> URL:
>> http://wso2.org/svn/browse/wso2/trunk/carbon/products/greg/modules/integration/registry/tests/src/test/java/org/wso2/carbon/registry/ws/client/test/general/CollectionChildCountWSTestCase.java?rev=118913&r1=118912&r2=118913&view=diff
>>
>> ==
>> ---
>> trunk/carbon/products/greg/modules/integration/registry/tests/src/test/java/org/wso2/carbon/registry/ws/client/test/general/CollectionChildCountWSTestCase.java
>> (original)
>> +++
>> trunk/carbon/products/greg/modules/integration/registry/tests/src/test/java/org/wso2/carbon/registry/ws/client/test/general/CollectionChildCountWSTestCase.java
>> Thu Jan 12 00:49:03 2012
>> @@ -34,6 +34,7 @@
>> // super.runSuccessCase();
>> try {
>> getChildCountForCollection();
>> +doPagedGet();
>> } catch (RegistryException e) {
>> e.printStackTrace();
>> fail("Get child count for collection test failed ");
>> @@ -48,4 +49,12 @@
>> Collection collection = (Collection) resource;
>> assertTrue(true, "Child count is " + collection.getChildCount());
>> }
>> +
>> +public void doPagedGet() throws RegistryException {
>> +String path = "/_system";
>> +Resource resource = registry.get(path, 1, 1);
>> +assertTrue((resource instanceof Collection), "resource is not a
>> collection");
>> +Collection collection = (Collection) resource;
>> +assertTrue(true, "Child count is " + collection.getChildCount());
>>
>
> This type of assertTrue(true) statement does not add any value to a test.
> I think it should be;
>
> assertEquals(n, collection.getChildCount());
>

+1 and Fixed under revision 119003.

>
>
>> +}
>>  }
>> ___
>> Carbon-commits mailing list
>> carbon-comm...@wso2.org
>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-commits
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] "HttpConnectionManager is null. Connection cannot be released." warnings occurs when running integration tests

[Subash Chaturanga]

015]  WARN
{org.apache.commons.httpclient.HttpConnection} -  HttpConnectionManager is
null.  Connection cannot be released.
[2012-01-04 12:36:20,015]  WARN
{org.apache.commons.httpclient.HttpConnection} -  HttpConnectionManager is
null.  Connection cannot be released.
[2012-01-04 12:36:20,040]  WARN
{org.apache.commons.httpclient.HttpConnection} -  HttpConnectionManager is
null.  Connection cannot be released.
[2012-01-04 12:36:20,040]  WARN
{org.apache.commons.httpclient.HttpConnection} -  HttpConnectionManager is
null.  Connection cannot be released.
[2012-01-04 12:36:20,061]  WARN
{org.apache.commons.httpclient.HttpConnection} -  HttpConnectionManager is
null.  Connection cannot be released.
[2012-01-04 12:36:20,061]  WARN
{org.apache.commons.httpclient.HttpConnection} -  HttpConnectionManager is
null.  Connection cannot be released.
[2012-01-04 12:36:20,199]  WARN
{org.apache.commons.httpclient.HttpConnection} -  HttpConnectionManager is
null.  Connection cannot be released.
[2012-01-04 12:36:20,199]  WARN
{org.apache.commons.httpclient.HttpConnection} -  HttpConnectionManager is
null.  Connection cannot be released.
[2012-01-04 12:36:20,236]  INFO
{org.wso2.carbon.registry.ws.client.test.general.TestSetup} -  Initializing
WS-API Tests
[2012-01-04 12:36:20,442]  INFO
{org.apache.axis2.deployment.ModuleDeployer} -  Deploying module:
addressing-1.6.1-wso2v1 -
file:/home/subash/development/trunk/carbon/products/greg/modules/integration/registry/tests/target/./carbontmp/wso2greg-4.0.0-SNAPSHOT/repository/deployment/client/modules/addressing-1.6.1-wso2v1.mar
[2012-01-04 12:36:20,442]  INFO
{org.apache.axis2.deployment.ModuleDeployer} -  Deploying module:
addressing-1.6.1-wso2v1 -
file:/home/subash/development/trunk/carbon/products/greg/modules/integration/registry/tests/target/./carbontmp/wso2greg-4.0.0-SNAPSHOT/repository/deployment/client/modules/addressing-1.6.1-wso2v1.mar
[2012-01-04 12:36:20,449]  INFO
{org.apache.axis2.deployment.ModuleDeployer} -  Deploying module:
ComponentMgtModule-3.2.0-SNAPSHOT -
file:/home/subash/.m2/repository/org/wso2/carbon/org.wso2.carbon.feature.mgt.services/3.2.0-SNAPSHOT/org.wso2.carbon.feature.mgt.services-3.2.0-SNAPSHOT.jar
[2012-01-04 12:36:20,449]  INFO
{org.apache.axis2.deployment.ModuleDeployer} -  Deploying module:
ComponentMgtModule-3.2.0-SNAPSHOT -
file:/home/subash/.m2/repository/org/wso2/carbon/org.wso2.carbon.feature.mgt.services/3.2.0-SNAPSHOT/org.wso2.carbon.feature.mgt.services-3.2.0-SNAPSHOT.jar
[2012-01-04 12:36:20,452]  INFO
{org.apache.axis2.deployment.ModuleDeployer} -  Deploying module:
uddiversionmodule-3.2.0-SNAPSHOT -
file:/home/subash/.m2/repository/org/wso2/carbon/org.wso2.carbon.registry.uddi/3.2.0-
.

Thanks
/subash
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] TestNG migration : Which API is preferred ?

[Subash Chaturanga]

On Mon, Jan 2, 2012 at 12:15 PM, Afkham Azeez  wrote:

> Use
>
> import static org.testng.Assert.*
>

+1

>
> Don't use the JUnit stuff. Just migrate the Junit stuff. Putting an import
> static will fix the compilation errors.
>
>
> On Mon, Jan 2, 2012 at 12:01 PM, Subash Chaturanga wrote:
>
>> Hi Azeez,
>>
>> When migrating to TestNG from JUnit, there are slight changes in the APIs
>> (in Assertions). I have already started re-factoring most of them.
>> But I just saw that there is an alternative JUnit compatible
>> testng.AssertJUnit class. Which one is preferred ?
>> (As we're completely moving away from JUnit, I thought of using the pure
>> org.testng.Assert class and re-factor our tests accordingly).
>>
>> WDYT ?
>>
>> Thanks
>> /subash
>> --
>>
>> Subash Chaturanga
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>>
>> email - sub...@wso2.com
>> phone - 077 2225922
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] TestNG migration : Which API is preferred ?

[Subash Chaturanga]

Hi Azeez,

When migrating to TestNG from JUnit, there are slight changes in the APIs
(in Assertions). I have already started re-factoring most of them.
But I just saw that there is an alternative JUnit compatible
testng.AssertJUnit class. Which one is preferred ?
(As we're completely moving away from JUnit, I thought of using the pure
org.testng.Assert class and re-factor our tests accordingly).

WDYT ?

Thanks
/subash
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Regarding GReg JUnit test migration to TestNG

[Subash Chaturanga]

Hi, Senaka

In GReg old integration model, we have a resource package for each module.
But in TestNG migration, we are going with one "tests" module. Shall we
maintain one resource directory for all testng packages.Because all
existing tests points to a similar relative path
../src/test/java/resources, which means, if we do so, no need to change
each and every hard coded resource paths(but we may have to rename some
resources).?   Or shall we maintain a separate resource package for each
testng package ?
WDYT ?

On Wed, Dec 21, 2011 at 11:14 PM, Senaka Fernando  wrote:

> Hi Subash,
>

Please follow the model of the other products, based on what Azeez did.

Thanks,
> Senaka


>
> On Wed, Dec 21, 2011 at 7:05 PM, Subash Chaturanga wrote:
>
>> Hi Senaka,
>>
>> Currently GReg have 4 integration test modules inside
>>  HOME/modules/integration/registry.
>> Shall we add new TestNG modules directly as peers of old ones or put them
>> inside a new parent module ?
>>
>>
>> Thanks
>> /subash
>> --
>>
>> Subash Chaturanga
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>>
>> email - sub...@wso2.com
>> phone - 077 2225922
>>
>>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Integration test team

[Subash Chaturanga]

gt;>>>> Team, please make this an opportunity to learn & master the art of
>>>>> unit & integration testing.
>>>>>
>>>>> Thanks
>>>>> Azeez
>>>>>
>>>>> 0.
>>>>> http://www.exubero.com/junit/antipatterns.html#Catching_Unexpected_Exceptions
>>>>> 1.
>>>>> http://testng.org/javadoc/org/testng/annotations/ExpectedExceptions.html
>>>>>
>>>>>
>>>>> --
>>>>> *Afkham Azeez*
>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>> * <http://www.apache.org/>**
>>>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>>> twitter: 
>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>> *
>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>>>> *
>>>>> *
>>>>> *Lean . Enterprise . Middleware*
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Afkham Azeez*
>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>> * <http://www.apache.org/>**
>>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>> twitter: 
>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>> *
>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>>> *
>>>> *
>>>> *Lean . Enterprise . Middleware*
>>>>
>>>>
>>>> ___
>>>> Carbon-dev mailing list
>>>> Carbon-dev@wso2.org
>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Keheliya Gallaba
>>> Software Engineer
>>> WSO2 Inc.
>>>
>>> E-mail: keheliya AT wso2.com
>>> M: +94 71 551 8881
>>>
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> *Shelan Perera*
>
> Software Engineer
> **
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Home Page*  :shelan.org
> *Blog* : blog.shelan.org
> *Linked-i*n  :http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

Thanks
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Regarding GReg JUnit test migration to TestNG

[Subash Chaturanga]

Hi Senaka,

Currently GReg have 4 integration test modules inside
 HOME/modules/integration/registry.
Shall we add new TestNG modules directly as peers of old ones or put them
inside a new parent module ?


Thanks
/subash
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] G-Reg docgen error causes build failure

[Subash Chaturanga]

Hi Senaka,

Shall we also exclude  **/impactAnalysis/**  from greg product/pom.xml ?

On Wed, Dec 21, 2011 at 9:22 AM, Afkham Azeez  wrote:

> I have fixed this
>
> On Tue, Dec 20, 2011 at 4:31 PM, Afkham Azeez  wrote:
>
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 3:28:22.476s
>> [INFO] Finished at: Tue Dec 20 15:53:02 IST 2011
>> [INFO] Final Memory: 1136M/1967M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-site-plugin:3.0:site (default) on project
>> wso2greg: Error during page generation: Error parsing
>> '/Users/azeez/projects/wso2/org/trunk/carbon2/products/greg/modules/distribution/product/src/site/xdoc/impactAnalysis/impact.xml':
>> line [61] Error parsing the model: end tag name  must be the same as
>> start tag  from line 33 (position: TEXT seen
>> ..._wso2_carbon_registry_resource_ui_tmpPairs);\n\n...
>> @61:8) -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>**
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev