[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon/products/appserver"

[WSO2 Builder]

[INFO]   WSO2 AppServer - Distribution
[INFO]   WSO2 Stratos AppServer - Distribution
[INFO]   WSO2 AS - Integration Tests
[INFO]   WSO2 AS - Login Test Module
[INFO]   WSO2 AS - Samples Integration
[INFO] 
[INFO] Building WSO2 AppServer - Parent
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 3 seconds
[INFO] Finished at: Fri Apr 15 07:12:23 UTC 2011
[INFO] Final Memory: 17M/330M
[INFO]  

 SVN Log  

r91827 | azeez | 2011-04-15 06:58:35 + (Fri, 15 Apr 2011) | 2 lines

Updated main class to Bootstrap class since now we have switched to the 
bootstrap mechanism


r91826 | azeez | 2011-04-15 06:26:44 + (Fri, 15 Apr 2011) | 5 lines

Introduced bootstrapping mechanism for starting up Tomcat. 

See http://wso2.org/mailarchive/carbon-dev/2011-April/054927.html



r91808 | azeez | 2011-04-13 20:30:30 + (Wed, 13 Apr 2011) | 3 lines

Removed lib/realm jar signing since that directory has been removed



r91778 | harshana | 2011-04-12 13:08:40 + (Tue, 12 Apr 2011) | 1 line

Adding Maven clean plugin to force cleaning up distribution and p2-profile-gen

r91748 | isuru | 2011-04-07 06:00:54 + (Thu, 07 Apr 2011) | 1 line

Adding webapp mgt doc link

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

[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon/products/brs"

[WSO2 Builder]

[INFO]   WSO2 AppServer - Distribution
[INFO]   WSO2 Stratos AppServer - Distribution
[INFO]   WSO2 AS - Integration Tests
[INFO]   WSO2 AS - Login Test Module
[INFO]   WSO2 AS - Samples Integration
[INFO] 
[INFO] Building WSO2 AppServer - Parent
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 3 seconds
[INFO] Finished at: Fri Apr 15 07:12:23 UTC 2011
[INFO] Final Memory: 17M/330M
[INFO] 
products/brs
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   WSO2 BRS
[INFO]   WSO2 BRS Styles Parent
[INFO]   WSO2 BRS Styles
[INFO]   WSO2 Stratos BRS - Styles
[INFO]   WSO2 BRS Samples Parent
[INFO]   WSO2 BRS Samples
[INFO]   WSO2 Stratos BRS - Samples
[INFO]   WSO2 BRS Features Parent
[INFO]   WSO2 BRS Features Aggregator Module
[INFO]   WSO2 BRS - Styles Features
[INFO]   WSO2 Stratos BRS - Features Aggregator Module
[INFO]   WSO2 Stratos BRS - Styles Features
[INFO]   WSO2 Stratos BRS - Login User Interface
[INFO]   WSO2 Stratos BRS - Deployment Features
[INFO]   WSO2 Stratos BRS - Dashboard UI
[INFO]   WSO2 Stratos BRS - Dashboard UI Features
[INFO]   WSO2 Stratos BRS - Deployment
[INFO]   WSO2 Stratos BRS - Deployment Features
[INFO]   WSO2 BRS P2 Profile Generation Parent
[INFO]   WSO2 BRS - P2 Profile Generation
[INFO]   WSO2 Stratos BRS - P2 Profile Generation
[INFO]   WSO2 BRS Distribution Parent
[INFO]   WSO2 BRS Distribution
[INFO]   WSO2 Stratos BRS - Distribution
[INFO]   WSO2 BRS - Integration Tests
[INFO]   WSO2 BRS - Greeting Test Module
[INFO]   WSO2 BRS - Samples Wizard Test Module
[INFO] 
[INFO] Building WSO2 BRS
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 second
[INFO] Finished at: Fri Apr 15 07:12:31 UTC 2011
[INFO] Final Memory: 8M/145M
[INFO]  

 SVN Log  

r91827 | azeez | 2011-04-15 06:58:35 + (Fri, 15 Apr 2011) | 2 lines

Updated main class to Bootstrap class since now we have switched to the 
bootstrap mechanism


r91826 | azeez | 2011-04-15 06:26:44 + (Fri, 15 Apr 2011) | 5 lines

Introduced bootstrapping mechanism for starting up Tomcat. 

See http://wso2.org/mailarchive/carbon-dev/2011-April/054927.html



r91820 | azeez | 2011-04-14 14:36:03 + (Thu, 14 Apr 2011) | 3 lines

Removed lib/realm jar signing from poms since this directory is no longer used



r91782 | harshana | 2011-04-12 13:13:14 + (Tue, 12 Apr 2011) | 1 line

Adding Maven clean plugin to force cleaning up distribution and p2-profile-gen

r91645 | shammi | 2011-04-04 15:24:32 + (Mon, 04 Apr 2011) | 1 line

Adding integration tests

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

[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon/products/cep"

[WSO2 Builder]

[INFO]   WSO2 AppServer - Distribution
[INFO]   WSO2 Stratos AppServer - Distribution
[INFO]   WSO2 AS - Integration Tests
[INFO]   WSO2 AS - Login Test Module
[INFO]   WSO2 AS - Samples Integration
[INFO] 
[INFO] Building WSO2 AppServer - Parent
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 3 seconds
[INFO] Finished at: Fri Apr 15 07:12:23 UTC 2011
[INFO] Final Memory: 17M/330M
[INFO] 
products/brs
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   WSO2 BRS
[INFO]   WSO2 BRS Styles Parent
[INFO]   WSO2 BRS Styles
[INFO]   WSO2 Stratos BRS - Styles
[INFO]   WSO2 BRS Samples Parent
[INFO]   WSO2 BRS Samples
[INFO]   WSO2 Stratos BRS - Samples
[INFO]   WSO2 BRS Features Parent
[INFO]   WSO2 BRS Features Aggregator Module
[INFO]   WSO2 BRS - Styles Features
[INFO]   WSO2 Stratos BRS - Features Aggregator Module
[INFO]   WSO2 Stratos BRS - Styles Features
[INFO]   WSO2 Stratos BRS - Login User Interface
[INFO]   WSO2 Stratos BRS - Deployment Features
[INFO]   WSO2 Stratos BRS - Dashboard UI
[INFO]   WSO2 Stratos BRS - Dashboard UI Features
[INFO]   WSO2 Stratos BRS - Deployment
[INFO]   WSO2 Stratos BRS - Deployment Features
[INFO]   WSO2 BRS P2 Profile Generation Parent
[INFO]   WSO2 BRS - P2 Profile Generation
[INFO]   WSO2 Stratos BRS - P2 Profile Generation
[INFO]   WSO2 BRS Distribution Parent
[INFO]   WSO2 BRS Distribution
[INFO]   WSO2 Stratos BRS - Distribution
[INFO]   WSO2 BRS - Integration Tests
[INFO]   WSO2 BRS - Greeting Test Module
[INFO]   WSO2 BRS - Samples Wizard Test Module
[INFO] 
[INFO] Building WSO2 BRS
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 second
[INFO] Finished at: Fri Apr 15 07:12:31 UTC 2011
[INFO] Final Memory: 8M/145M
[INFO] 
products/cep
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Styles
[INFO]   WSO2 Stratos CEP - Styles
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Features Aggregator Module
[INFO]   WSO2 CEP - Styles Features
[INFO]   WSO2 Stratos CEP Features Aggregator Module
[INFO]   WSO2 Stratos CEP - Styles Features
[INFO]   WSO2 Stratos CEP - Login User Interface
[INFO]   WSO2 Stratos CEP - Deployment Features
[INFO]   WSO2 Stratos CEP - Dashboard UI
[INFO]   WSO2 Stratos CEP - Dashboard UI Features
[INFO]   WSO2 Stratos CEP - Deployment
[INFO]   WSO2 Stratos CEP - Deployment Features
[INFO]   WSO2 CEP P2 Profile Generation Parent
[INFO]   WSO2 CEP - P2 Profile Generation
[INFO]   WSO2 Stratos CEP - P2 Profile Generation
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Distribution
[INFO]   Stratos CEP Distribution
[INFO] 
[INFO] Building WSO2 CEP
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Apr 15 07:12:44 UTC 2011
[INFO] Final Memory: 9M/205M
[INFO] --

[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon/products/esb"

[WSO2 Builder]

[INFO]   WSO2 AppServer - Distribution
[INFO]   WSO2 Stratos AppServer - Distribution
[INFO]   WSO2 AS - Integration Tests
[INFO]   WSO2 AS - Login Test Module
[INFO]   WSO2 AS - Samples Integration
[INFO] 
[INFO] Building WSO2 AppServer - Parent
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 3 seconds
[INFO] Finished at: Fri Apr 15 07:12:23 UTC 2011
[INFO] Final Memory: 17M/330M
[INFO] 
products/brs
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   WSO2 BRS
[INFO]   WSO2 BRS Styles Parent
[INFO]   WSO2 BRS Styles
[INFO]   WSO2 Stratos BRS - Styles
[INFO]   WSO2 BRS Samples Parent
[INFO]   WSO2 BRS Samples
[INFO]   WSO2 Stratos BRS - Samples
[INFO]   WSO2 BRS Features Parent
[INFO]   WSO2 BRS Features Aggregator Module
[INFO]   WSO2 BRS - Styles Features
[INFO]   WSO2 Stratos BRS - Features Aggregator Module
[INFO]   WSO2 Stratos BRS - Styles Features
[INFO]   WSO2 Stratos BRS - Login User Interface
[INFO]   WSO2 Stratos BRS - Deployment Features
[INFO]   WSO2 Stratos BRS - Dashboard UI
[INFO]   WSO2 Stratos BRS - Dashboard UI Features
[INFO]   WSO2 Stratos BRS - Deployment
[INFO]   WSO2 Stratos BRS - Deployment Features
[INFO]   WSO2 BRS P2 Profile Generation Parent
[INFO]   WSO2 BRS - P2 Profile Generation
[INFO]   WSO2 Stratos BRS - P2 Profile Generation
[INFO]   WSO2 BRS Distribution Parent
[INFO]   WSO2 BRS Distribution
[INFO]   WSO2 Stratos BRS - Distribution
[INFO]   WSO2 BRS - Integration Tests
[INFO]   WSO2 BRS - Greeting Test Module
[INFO]   WSO2 BRS - Samples Wizard Test Module
[INFO] 
[INFO] Building WSO2 BRS
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 second
[INFO] Finished at: Fri Apr 15 07:12:31 UTC 2011
[INFO] Final Memory: 8M/145M
[INFO] 
products/cep
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Styles
[INFO]   WSO2 Stratos CEP - Styles
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Features Aggregator Module
[INFO]   WSO2 CEP - Styles Features
[INFO]   WSO2 Stratos CEP Features Aggregator Module
[INFO]   WSO2 Stratos CEP - Styles Features
[INFO]   WSO2 Stratos CEP - Login User Interface
[INFO]   WSO2 Stratos CEP - Deployment Features
[INFO]   WSO2 Stratos CEP - Dashboard UI
[INFO]   WSO2 Stratos CEP - Dashboard UI Features
[INFO]   WSO2 Stratos CEP - Deployment
[INFO]   WSO2 Stratos CEP - Deployment Features
[INFO]   WSO2 CEP P2 Profile Generation Parent
[INFO]   WSO2 CEP - P2 Profile Generation
[INFO]   WSO2 Stratos CEP - P2 Profile Generation
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Distribution
[INFO]   Stratos CEP Distribution
[INFO] 
[INFO] Building WSO2 CEP
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Apr 15 07:12:44 UTC 2011
[INFO] Final Memory: 9M/205M
[INFO] --

[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon/products/greg"

[WSO2 Builder]

[INFO]   WSO2 AppServer - Distribution
[INFO]   WSO2 Stratos AppServer - Distribution
[INFO]   WSO2 AS - Integration Tests
[INFO]   WSO2 AS - Login Test Module
[INFO]   WSO2 AS - Samples Integration
[INFO] 
[INFO] Building WSO2 AppServer - Parent
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 3 seconds
[INFO] Finished at: Fri Apr 15 07:12:23 UTC 2011
[INFO] Final Memory: 17M/330M
[INFO] 
products/brs
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   WSO2 BRS
[INFO]   WSO2 BRS Styles Parent
[INFO]   WSO2 BRS Styles
[INFO]   WSO2 Stratos BRS - Styles
[INFO]   WSO2 BRS Samples Parent
[INFO]   WSO2 BRS Samples
[INFO]   WSO2 Stratos BRS - Samples
[INFO]   WSO2 BRS Features Parent
[INFO]   WSO2 BRS Features Aggregator Module
[INFO]   WSO2 BRS - Styles Features
[INFO]   WSO2 Stratos BRS - Features Aggregator Module
[INFO]   WSO2 Stratos BRS - Styles Features
[INFO]   WSO2 Stratos BRS - Login User Interface
[INFO]   WSO2 Stratos BRS - Deployment Features
[INFO]   WSO2 Stratos BRS - Dashboard UI
[INFO]   WSO2 Stratos BRS - Dashboard UI Features
[INFO]   WSO2 Stratos BRS - Deployment
[INFO]   WSO2 Stratos BRS - Deployment Features
[INFO]   WSO2 BRS P2 Profile Generation Parent
[INFO]   WSO2 BRS - P2 Profile Generation
[INFO]   WSO2 Stratos BRS - P2 Profile Generation
[INFO]   WSO2 BRS Distribution Parent
[INFO]   WSO2 BRS Distribution
[INFO]   WSO2 Stratos BRS - Distribution
[INFO]   WSO2 BRS - Integration Tests
[INFO]   WSO2 BRS - Greeting Test Module
[INFO]   WSO2 BRS - Samples Wizard Test Module
[INFO] 
[INFO] Building WSO2 BRS
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 second
[INFO] Finished at: Fri Apr 15 07:12:31 UTC 2011
[INFO] Final Memory: 8M/145M
[INFO] 
products/cep
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Styles
[INFO]   WSO2 Stratos CEP - Styles
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Features Aggregator Module
[INFO]   WSO2 CEP - Styles Features
[INFO]   WSO2 Stratos CEP Features Aggregator Module
[INFO]   WSO2 Stratos CEP - Styles Features
[INFO]   WSO2 Stratos CEP - Login User Interface
[INFO]   WSO2 Stratos CEP - Deployment Features
[INFO]   WSO2 Stratos CEP - Dashboard UI
[INFO]   WSO2 Stratos CEP - Dashboard UI Features
[INFO]   WSO2 Stratos CEP - Deployment
[INFO]   WSO2 Stratos CEP - Deployment Features
[INFO]   WSO2 CEP P2 Profile Generation Parent
[INFO]   WSO2 CEP - P2 Profile Generation
[INFO]   WSO2 Stratos CEP - P2 Profile Generation
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Distribution
[INFO]   Stratos CEP Distribution
[INFO] 
[INFO] Building WSO2 CEP
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Apr 15 07:12:44 UTC 2011
[INFO] Final Memory: 9M/205M
[INFO] --

[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon/products/mb"

[WSO2 Builder]

[INFO]   WSO2 AppServer - Distribution
[INFO]   WSO2 Stratos AppServer - Distribution
[INFO]   WSO2 AS - Integration Tests
[INFO]   WSO2 AS - Login Test Module
[INFO]   WSO2 AS - Samples Integration
[INFO] 
[INFO] Building WSO2 AppServer - Parent
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 3 seconds
[INFO] Finished at: Fri Apr 15 07:12:23 UTC 2011
[INFO] Final Memory: 17M/330M
[INFO] 
products/brs
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   WSO2 BRS
[INFO]   WSO2 BRS Styles Parent
[INFO]   WSO2 BRS Styles
[INFO]   WSO2 Stratos BRS - Styles
[INFO]   WSO2 BRS Samples Parent
[INFO]   WSO2 BRS Samples
[INFO]   WSO2 Stratos BRS - Samples
[INFO]   WSO2 BRS Features Parent
[INFO]   WSO2 BRS Features Aggregator Module
[INFO]   WSO2 BRS - Styles Features
[INFO]   WSO2 Stratos BRS - Features Aggregator Module
[INFO]   WSO2 Stratos BRS - Styles Features
[INFO]   WSO2 Stratos BRS - Login User Interface
[INFO]   WSO2 Stratos BRS - Deployment Features
[INFO]   WSO2 Stratos BRS - Dashboard UI
[INFO]   WSO2 Stratos BRS - Dashboard UI Features
[INFO]   WSO2 Stratos BRS - Deployment
[INFO]   WSO2 Stratos BRS - Deployment Features
[INFO]   WSO2 BRS P2 Profile Generation Parent
[INFO]   WSO2 BRS - P2 Profile Generation
[INFO]   WSO2 Stratos BRS - P2 Profile Generation
[INFO]   WSO2 BRS Distribution Parent
[INFO]   WSO2 BRS Distribution
[INFO]   WSO2 Stratos BRS - Distribution
[INFO]   WSO2 BRS - Integration Tests
[INFO]   WSO2 BRS - Greeting Test Module
[INFO]   WSO2 BRS - Samples Wizard Test Module
[INFO] 
[INFO] Building WSO2 BRS
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 second
[INFO] Finished at: Fri Apr 15 07:12:31 UTC 2011
[INFO] Final Memory: 8M/145M
[INFO] 
products/cep
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Styles
[INFO]   WSO2 Stratos CEP - Styles
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Features Aggregator Module
[INFO]   WSO2 CEP - Styles Features
[INFO]   WSO2 Stratos CEP Features Aggregator Module
[INFO]   WSO2 Stratos CEP - Styles Features
[INFO]   WSO2 Stratos CEP - Login User Interface
[INFO]   WSO2 Stratos CEP - Deployment Features
[INFO]   WSO2 Stratos CEP - Dashboard UI
[INFO]   WSO2 Stratos CEP - Dashboard UI Features
[INFO]   WSO2 Stratos CEP - Deployment
[INFO]   WSO2 Stratos CEP - Deployment Features
[INFO]   WSO2 CEP P2 Profile Generation Parent
[INFO]   WSO2 CEP - P2 Profile Generation
[INFO]   WSO2 Stratos CEP - P2 Profile Generation
[INFO]   WSO2 CEP
[INFO]   WSO2 CEP Distribution
[INFO]   Stratos CEP Distribution
[INFO] 
[INFO] Building WSO2 CEP
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Apr 15 07:12:44 UTC 2011
[INFO] Final Memory: 9M/205M
[INFO] --

Re: [Carbon-dev] Latest ESB build is unusable due to Registry issues

[Samisa Abeysinghe]

On Fri, Apr 15, 2011 at 12:59 PM, Hiranya Jayathilaka wrote:

>
>
> On Fri, Apr 15, 2011 at 11:37 AM, Supun Kamburugamuva wrote:
>
>> But there is another problem with the UI. Sometimes when I click the
>> menu the corresponding UI appears very late.
>
>
> Yes I'm also getting this. It's random and I don't think it has anything to
> do with registry eventing stuff. Must be something else.
>

What have we changed in the UI framework as of late?

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] MB Memory Leak

[Samisa Abeysinghe]

This html file just shows empty. :(

On Fri, Apr 15, 2011 at 10:43 AM, Danushka Menikkumbura
wrote:

> According to what I have found, the culprit is a byte array as shown in the
> attached reference graph. Can someone please take a look at and provide some
> context?. I am kind of stuck at this point.
>
> I have omitted incoming reference to the class loader instance as there are
> some many of them that clutter the reference graph.
>
> Thanks,
> Danushka
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Repos - why are they not using nexus?

[Pradeep Fernando]

hi,

Commented out the poms without removing them, for easy rollback
purposes. Will remove them shortly. transitive dependencies + maven
plugins still download stuff from their usual repos.

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

[Carbon-dev] GReg - [ WebDAV - Configuring Editors ]

[Fazlan Sabar]

Hi Senaka,

I came across this strange behavior in GReg's webDAV feature, after adding a
resource via (Entries -> Add Resource -> Medthod -> Create Text content)
from the UI(this enables creation of resources without an extension),
irrespective of the specified media-type, it's always shown as plain/text at
client(even after setting the getcontenttype property), and editing them
with certain editors such as vim and gedit causes the media type information
is lost in the process at the server.

Why?
There behavior of these editors when saving a file not only does a PUT, but
also a DELETE request, similar discussion were found at
[1]and
[2]  .
Editors such as vim allows this behavior to be changed, where as gedit does
not. In situation such as this, the result at the server end is havoc,
because of the DELETE request, which cause the resource to be deleted from
the server end.

Note: The vi editor does not issue a DELETE operation when saving, hence
it's does not involve any tweaks.

Possible alternatives:
1)
We can set the media-type to 'text/plain' as default for resources created
WITHOUT an extension, and use editors like gedit(which does not allow to
change the behavior of save) to edit ONLY 'text/plain' type resources. No
issue with vim, because the behavior of save can be changed.
Impact: This causes some what a coupling between the mime-type and the
editor(gedit). However, if the user makes changes to non 'text/plain' type
files via gedit, the media-type of the file will get changed to
'text/plain', because it'll treat this file as a new file( since DELETE is
performed in the request before).

2)
We add the file extension to the requested resource using its media-type at
the server end.
Impact: The file name will get changed after the first PROPFIND request, but
now since the extension of the file is available, the above problem is
solved.
e.g:
we create a resource from UI: name --> xmlfile with Media type -->
application/xml
and after the webDAV request, its name changes to xmlfile.xml, media-type
remains the same.

3)
We ask the users to use only the editors such as vi and vim that can change
the default save behavior when editing files that has no extension, and
include these instruction(the ones from the associated links [1] and [2]) in
the User Guide of GReg documentation.
Impact: Restricts the available editors for modifying resources with no
extension.

WDYT?

[1]
http://stackoverflow.com/questions/607435/why-does-vim-save-files-with-a-extension
[2] http://platform.xwiki.org/xwiki/bin/view/Features/WebDAVDavFs2
-- 
Thanks,
Fazlan
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Architecture] Carbon Studio 1.0.5 Released

[Samisa Abeysinghe]

Please send this note to announce list as well

On Tue, Apr 12, 2011 at 8:50 AM, Saminda Wijeratne wrote:

> WSO2 Carbon Studio 1.0.5 Release Notes 6th April 2011
>
> We introduce WSO2 Carbon Studio, is a fully functioned tooling environment
> which facilitate you to develop, test, deploy and test WSO2 Carbon
> Artifacts. The tool is created as a plug-in for the popular IDE Eclipse.
>
> These tools are available under the Apache Software License (v2.0) 
> .
> This includes all of the extra integration and management functionality as
> well.
>  New Features
>
>- Carbon Application Tools
>   - Ability to create Registry Aspect class
>   - Allow creating the library artifact as a fragment bundle
>   - Create sequences and endpoints as registry resources
>   - Creating registry resources through templates
>- General
>   - Adding WSO2 related libraries when developing applications
>   - Other usability improvements
>- ESB tools
>   - Ability to specify references of ESB artifacts from a filtered
>   list of resources in the workspace
>   - Ability to create registry resource references on the fly for ESB
>   artifacts
>   - JBoss Smooks tools integration
>- Governance Registry Tools
>   - Enable/disable actions and update icons based on permissions for
>   registry resources for the specified user
>   - Upload wsdl resources to the registry as governance archives (GAR
>   support)
>- Introduced Carbon Studio contribution features [Documentation
>pending]
>   - Extensions to add custom proxy service templates
>   - Extensions to add registry resource templates
>   - Extensions to allow adding mediatype resolvers
>   - Extensions to specify new 3rd party libraries
>   - Extensions to specify resource providers for
>  - Registry Resources
>  - ESB Sequences
>  - ESB Endpoints
>  - ESB Local Entries
>
> Key Features
>
>- Application Server Tools
>   - Create and Edit Apache Axis2 Web Service
>   - Create WSDL for Apache Axis2 Web Service archive (aar file)
>   - Generate Web Service client
>   - Web Applications
>   - JAX-WS services
>- Enterprise Service Bus Tools
>   - Sequences
>   - Endpoints
>   - Proxy Services
>   - Local Entries
>   - Create custom mediators
>   - Registry Referencing
>- Governance Registry Tools
>   - Create and deploy registry resources
>   - Create, edit, debug and deploy registry handlers, filters and
>   registry aspects
>   - Manage your remote registry instance
>- Business Process Server Tools
>   - View, create and edit BPEL projects
>- Gadget Server Tools
>   - Create and edit gadgets
>- Data Services Server Tools
>   - Create and edit data services (XML configurations)
>   - Create and edit data services validators
>- Carbon Tools
>   - Create, edit, debug and deploy Carbon UI bundles
>   - Deploy third party libraries as bundles
>- Testing, Deploying and Redeploying
>
> You can find a more detailed version of all the features available in
> Carbon Studio from WSO2 Carbon Studio 
> Features
>  page. Project Resources
>
>1. *Home page :* WSO2 Carbon Studio
>2. *JIRA-Issue Tracker :* WSO2 Carbon Studio - JIRA 
> Issues
>
> Reporting ProblemsIssues can be reported using the public JIRA available
> at https://wso2.org/jira/browse/TOOLS Contact usWSO2 Tools developers can
> be contacted via the mailing lists:
>
> *For Users:* tools-u...@wso2.org
>
> *For Developers:* carbon-dev@wso2.org
>
> For details on subscriptions see http://wso2.org/projects/tools#mail
>
> Alternatively, questions can also be raised in the WSO2 Tools forum:
>
> *Forum* http://www.wso2.org/forum/194 
>
> SupportWe are committed to ensuring that your enterprise middleware
> deployment is completely supported from evaluation to production. Our unique
> approach ensures that all support leverages our open development methodology
> and is provided by the very same engineers who build the technology.
>
> For more details and to take advantage of this unique opportunity please
> visit http://wso2.com/support/
>
> For more information about WSO2 Carbon Studio please see,
> http://wso2.org/library/carbon-studio/. visit the WSO2 Oxygen Tank
> developer portal  for additional resources.
>
> Thank you for your interest in WSO2 Carbon Studio.
>
> *-The WSO2 Tooling Team*
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
__

Re: [Carbon-dev] GReg - [ WebDAV - Configuring Editors ]

[Senaka Fernando]

Hi Fazlan,

On Fri, Apr 15, 2011 at 4:05 PM, Fazlan Sabar  wrote:

> Hi Senaka,
>
> I came across this strange behavior in GReg's webDAV feature, after adding
> a resource via (Entries -> Add Resource -> Medthod -> Create Text content)
> from the UI(this enables creation of resources without an extension),
> irrespective of the specified media-type, it's always shown as plain/text at
> client(even after setting the getcontenttype property), and editing them
> with certain editors such as vim and gedit causes the media type information
> is lost in the process at the server.
>
> Why?
> There behavior of these editors when saving a file not only does a PUT, but
> also a DELETE request, similar discussion were found at 
> [1]and
> [2]  .
> Editors such as vim allows this behavior to be changed, where as gedit does
> not. In situation such as this, the result at the server end is havoc,
> because of the DELETE request, which cause the resource to be deleted from
> the server end.
>
> Note: The vi editor does not issue a DELETE operation when saving, hence
> it's does not involve any tweaks.
>
> Possible alternatives:
> 1)
> We can set the media-type to 'text/plain' as default for resources created
> WITHOUT an extension, and use editors like gedit(which does not allow to
> change the behavior of save) to edit ONLY 'text/plain' type resources. No
> issue with vim, because the behavior of save can be changed.
> Impact: This causes some what a coupling between the mime-type and the
> editor(gedit). However, if the user makes changes to non 'text/plain' type
> files via gedit, the media-type of the file will get changed to
> 'text/plain', because it'll treat this file as a new file( since DELETE is
> performed in the request before).
>

-1. This is not desirable. We cannot tie ourselves to a specific type of
editor on a specific OS. And, also, most OSs allow the existence of files
without a media type, and that's something valid.

>
> 2)
> We add the file extension to the requested resource using its media-type at
> the server end.
> Impact: The file name will get changed after the first PROPFIND request,
> but now since the extension of the file is available, the above problem is
> solved.
> e.g:
> we create a resource from UI: name --> xmlfile with Media type -->
> application/xml
> and after the webDAV request, its name changes to xmlfile.xml, media-type
> remains the same.
>

-1 again. This will break the concepts that we have been having so far in
G-Reg. We should not transform the file name into something manageable just
to solve an issue that occurs in the context of a specific type of client.

>
> 3)
> We ask the users to use only the editors such as vi and vim that can change
> the default save behavior when editing files that has no extension, and
> include these instruction(the ones from the associated links [1] and [2]) in
> the User Guide of GReg documentation.
> Impact: Restricts the available editors for modifying resources with no
> extension.
>
>

> WDYT?
>

This is partially correct. But, this should not be enforced in this manner.
At the WebDAV servlet, which is our last point-of-contact, we need to
validate the type of request being made against the current media type of
the resource and decide whether we allow that kind of operation or not. If
we cannot handle it, we throw an exception of a known type. When we do
something like that, it would not be possible to edit some type of file
using some type of application. This is normal. For example, if you try to
open a text file using an Archive Manager like file-roller, it will throw an
exception.

And, for a file of no media type, no editor might might be able to edit
that. But, normally, when someone creates a file through G-Reg's resource
UI, he/she would be giving it a media type (when creating text content), or
we'd be identifying it for him/her. Therefore, I smell some bug in the
WebDAV implementation that does not carry this information to the
client-side. Can you have a look into that aspect as well?

Thanks,
Senaka.

>
> [1]
> http://stackoverflow.com/questions/607435/why-does-vim-save-files-with-a-extension
> [2] http://platform.xwiki.org/xwiki/bin/view/Features/WebDAVDavFs2
> --
> Thanks,
> Fazlan
>
>


-- 
*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://www.linkedin.com/in/senakafernando

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

[Carbon-dev] Maven version changed on builder ?

[Sumedha Rubasinghe]

Did we change the maven version on builder?
/sumedha


On Fri, Apr 15, 2011 at 12:43 PM, WSO2 Builder  wrote:

> [INFO]   WSO2 AppServer - Distribution
> [INFO]   WSO2 Stratos AppServer - Distribution
> [INFO]   WSO2 AS - Integration Tests
> [INFO]   WSO2 AS - Login Test Module
> [INFO]   WSO2 AS - Samples Integration
> [INFO]
> 
> [INFO] Building WSO2 AppServer - Parent
> [INFO]task-segment: [clean, install]
> [INFO]
> 
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Error resolving version for
> 'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven
> version 2.0.9
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 3 seconds
> [INFO] Finished at: Fri Apr 15 07:12:23 UTC 2011
> [INFO] Final Memory: 17M/330M
> [INFO]
> 
> products/brs
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO]   WSO2 BRS
> [INFO]   WSO2 BRS Styles Parent
> [INFO]   WSO2 BRS Styles
> [INFO]   WSO2 Stratos BRS - Styles
> [INFO]   WSO2 BRS Samples Parent
> [INFO]   WSO2 BRS Samples
> [INFO]   WSO2 Stratos BRS - Samples
> [INFO]   WSO2 BRS Features Parent
> [INFO]   WSO2 BRS Features Aggregator Module
> [INFO]   WSO2 BRS - Styles Features
> [INFO]   WSO2 Stratos BRS - Features Aggregator Module
> [INFO]   WSO2 Stratos BRS - Styles Features
> [INFO]   WSO2 Stratos BRS - Login User Interface
> [INFO]   WSO2 Stratos BRS - Deployment Features
> [INFO]   WSO2 Stratos BRS - Dashboard UI
> [INFO]   WSO2 Stratos BRS - Dashboard UI Features
> [INFO]   WSO2 Stratos BRS - Deployment
> [INFO]   WSO2 Stratos BRS - Deployment Features
> [INFO]   WSO2 BRS P2 Profile Generation Parent
> [INFO]   WSO2 BRS - P2 Profile Generation
> [INFO]   WSO2 Stratos BRS - P2 Profile Generation
> [INFO]   WSO2 BRS Distribution Parent
> [INFO]   WSO2 BRS Distribution
> [INFO]   WSO2 Stratos BRS - Distribution
> [INFO]   WSO2 BRS - Integration Tests
> [INFO]   WSO2 BRS - Greeting Test Module
> [INFO]   WSO2 BRS - Samples Wizard Test Module
> [INFO]
> 
> [INFO] Building WSO2 BRS
> [INFO]task-segment: [clean, install]
> [INFO]
> 
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Error resolving version for
> 'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven
> version 2.0.9
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 1 second
> [INFO] Finished at: Fri Apr 15 07:12:31 UTC 2011
> [INFO] Final Memory: 8M/145M
> [INFO]
> 
> products/cep
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO]   WSO2 CEP
> [INFO]   WSO2 CEP
> [INFO]   WSO2 CEP Styles
> [INFO]   WSO2 Stratos CEP - Styles
> [INFO]   WSO2 CEP
> [INFO]   WSO2 CEP Features Aggregator Module
> [INFO]   WSO2 CEP - Styles Features
> [INFO]   WSO2 Stratos CEP Features Aggregator Module
> [INFO]   WSO2 Stratos CEP - Styles Features
> [INFO]   WSO2 Stratos CEP - Login User Interface
> [INFO]   WSO2 Stratos CEP - Deployment Features
> [INFO]   WSO2 Stratos CEP - Dashboard UI
> [INFO]   WSO2 Stratos CEP - Dashboard UI Features
> [INFO]   WSO2 Stratos CEP - Deployment
> [INFO]   WSO2 Stratos CEP - Deployment Features
> [INFO]   WSO2 CEP P2 Profile Generation Parent
> [INFO]   WSO2 CEP - P2 Profile Generation
> [INFO]   WSO2 Stratos CEP - P2 Profile Generation
> [INFO]   WSO2 CEP
> [INFO]   WSO2 CEP Distribution
> [INFO]   Stratos CEP Distribution
> [INFO]
> 
> [INFO] Building WSO2 CEP
> [INFO]task-segment: [clean, install]
> [INFO]
> 
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Error resolving version for
> 'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven
> version 2.0.9
> [INFO]
> --

Re: [Carbon-dev] Maven version changed on builder ?

[Samisa Abeysinghe]

It is using 2.2.1

On Fri, Apr 15, 2011 at 6:56 PM, Sumedha Rubasinghe wrote:

> Did we change the maven version on builder?
> /sumedha
>
>
> On Fri, Apr 15, 2011 at 12:43 PM, WSO2 Builder  wrote:
>
>> [INFO]   WSO2 AppServer - Distribution
>> [INFO]   WSO2 Stratos AppServer - Distribution
>> [INFO]   WSO2 AS - Integration Tests
>> [INFO]   WSO2 AS - Login Test Module
>> [INFO]   WSO2 AS - Samples Integration
>> [INFO]
>> 
>> [INFO] Building WSO2 AppServer - Parent
>> [INFO]task-segment: [clean, install]
>> [INFO]
>> 
>> [INFO]
>> 
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] Error resolving version for
>> 'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven
>> version 2.0.9
>> [INFO]
>> 
>> [INFO] For more information, run Maven with the -e switch
>> [INFO]
>> 
>> [INFO] Total time: 3 seconds
>> [INFO] Finished at: Fri Apr 15 07:12:23 UTC 2011
>> [INFO] Final Memory: 17M/330M
>> [INFO]
>> 
>> products/brs
>> [INFO] Scanning for projects...
>> [INFO] Reactor build order:
>> [INFO]   WSO2 BRS
>> [INFO]   WSO2 BRS Styles Parent
>> [INFO]   WSO2 BRS Styles
>> [INFO]   WSO2 Stratos BRS - Styles
>> [INFO]   WSO2 BRS Samples Parent
>> [INFO]   WSO2 BRS Samples
>> [INFO]   WSO2 Stratos BRS - Samples
>> [INFO]   WSO2 BRS Features Parent
>> [INFO]   WSO2 BRS Features Aggregator Module
>> [INFO]   WSO2 BRS - Styles Features
>> [INFO]   WSO2 Stratos BRS - Features Aggregator Module
>> [INFO]   WSO2 Stratos BRS - Styles Features
>> [INFO]   WSO2 Stratos BRS - Login User Interface
>> [INFO]   WSO2 Stratos BRS - Deployment Features
>> [INFO]   WSO2 Stratos BRS - Dashboard UI
>> [INFO]   WSO2 Stratos BRS - Dashboard UI Features
>> [INFO]   WSO2 Stratos BRS - Deployment
>> [INFO]   WSO2 Stratos BRS - Deployment Features
>> [INFO]   WSO2 BRS P2 Profile Generation Parent
>> [INFO]   WSO2 BRS - P2 Profile Generation
>> [INFO]   WSO2 Stratos BRS - P2 Profile Generation
>> [INFO]   WSO2 BRS Distribution Parent
>> [INFO]   WSO2 BRS Distribution
>> [INFO]   WSO2 Stratos BRS - Distribution
>> [INFO]   WSO2 BRS - Integration Tests
>> [INFO]   WSO2 BRS - Greeting Test Module
>> [INFO]   WSO2 BRS - Samples Wizard Test Module
>> [INFO]
>> 
>> [INFO] Building WSO2 BRS
>> [INFO]task-segment: [clean, install]
>> [INFO]
>> 
>> [INFO]
>> 
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] Error resolving version for
>> 'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven
>> version 2.0.9
>> [INFO]
>> 
>> [INFO] For more information, run Maven with the -e switch
>> [INFO]
>> 
>> [INFO] Total time: 1 second
>> [INFO] Finished at: Fri Apr 15 07:12:31 UTC 2011
>> [INFO] Final Memory: 8M/145M
>> [INFO]
>> 
>> products/cep
>> [INFO] Scanning for projects...
>> [INFO] Reactor build order:
>> [INFO]   WSO2 CEP
>> [INFO]   WSO2 CEP
>> [INFO]   WSO2 CEP Styles
>> [INFO]   WSO2 Stratos CEP - Styles
>> [INFO]   WSO2 CEP
>> [INFO]   WSO2 CEP Features Aggregator Module
>> [INFO]   WSO2 CEP - Styles Features
>> [INFO]   WSO2 Stratos CEP Features Aggregator Module
>> [INFO]   WSO2 Stratos CEP - Styles Features
>> [INFO]   WSO2 Stratos CEP - Login User Interface
>> [INFO]   WSO2 Stratos CEP - Deployment Features
>> [INFO]   WSO2 Stratos CEP - Dashboard UI
>> [INFO]   WSO2 Stratos CEP - Dashboard UI Features
>> [INFO]   WSO2 Stratos CEP - Deployment
>> [INFO]   WSO2 Stratos CEP - Deployment Features
>> [INFO]   WSO2 CEP P2 Profile Generation Parent
>> [INFO]   WSO2 CEP - P2 Profile Generation
>> [INFO]   WSO2 Stratos CEP - P2 Profile Generation
>> [INFO]   WSO2 CEP
>> [INFO]   WSO2 CEP Distribution
>> [INFO]   Stratos CEP Distribution
>> [INFO]
>> 
>> [INFO] Building WSO2 CEP
>> [INFO]task-segment: [clean, install]
>> [INFO]
>> 
>> [INFO]
>> 
>> [ERROR] BUILD ERROR
>> [INFO]
>> ---

Re: [Carbon-dev] GReg - [ WebDAV - Configuring Editors ]

[Fazlan Sabar]

Yes, I'll have a look.

On Fri, Apr 15, 2011 at 6:26 PM, Senaka Fernando  wrote:

> Hi Fazlan,
>
> On Fri, Apr 15, 2011 at 4:05 PM, Fazlan Sabar  wrote:
>
>> Hi Senaka,
>>
>> I came across this strange behavior in GReg's webDAV feature, after adding
>> a resource via (Entries -> Add Resource -> Medthod -> Create Text content)
>> from the UI(this enables creation of resources without an extension),
>> irrespective of the specified media-type, it's always shown as plain/text at
>> client(even after setting the getcontenttype property), and editing them
>> with certain editors such as vim and gedit causes the media type information
>> is lost in the process at the server.
>>
>> Why?
>> There behavior of these editors when saving a file not only does a PUT,
>> but also a DELETE request, similar discussion were found at 
>> [1]and
>> [2]  .
>> Editors such as vim allows this behavior to be changed, where as gedit does
>> not. In situation such as this, the result at the server end is havoc,
>> because of the DELETE request, which cause the resource to be deleted from
>> the server end.
>>
>> Note: The vi editor does not issue a DELETE operation when saving, hence
>> it's does not involve any tweaks.
>>
>> Possible alternatives:
>> 1)
>> We can set the media-type to 'text/plain' as default for resources created
>> WITHOUT an extension, and use editors like gedit(which does not allow to
>> change the behavior of save) to edit ONLY 'text/plain' type resources. No
>> issue with vim, because the behavior of save can be changed.
>> Impact: This causes some what a coupling between the mime-type and the
>> editor(gedit). However, if the user makes changes to non 'text/plain' type
>> files via gedit, the media-type of the file will get changed to
>> 'text/plain', because it'll treat this file as a new file( since DELETE is
>> performed in the request before).
>>
>
> -1. This is not desirable. We cannot tie ourselves to a specific type of
> editor on a specific OS. And, also, most OSs allow the existence of files
> without a media type, and that's something valid.
>
>>
>> 2)
>> We add the file extension to the requested resource using its media-type
>> at the server end.
>> Impact: The file name will get changed after the first PROPFIND request,
>> but now since the extension of the file is available, the above problem is
>> solved.
>> e.g:
>> we create a resource from UI: name --> xmlfile with Media type -->
>> application/xml
>> and after the webDAV request, its name changes to xmlfile.xml, media-type
>> remains the same.
>>
>
> -1 again. This will break the concepts that we have been having so far in
> G-Reg. We should not transform the file name into something manageable just
> to solve an issue that occurs in the context of a specific type of client.
>
>>
>> 3)
>> We ask the users to use only the editors such as vi and vim that can
>> change the default save behavior when editing files that has no extension,
>> and include these instruction(the ones from the associated links [1] and
>> [2]) in the User Guide of GReg documentation.
>> Impact: Restricts the available editors for modifying resources with no
>> extension.
>>
>>
>
>> WDYT?
>>
>
> This is partially correct. But, this should not be enforced in this manner.
> At the WebDAV servlet, which is our last point-of-contact, we need to
> validate the type of request being made against the current media type of
> the resource and decide whether we allow that kind of operation or not. If
> we cannot handle it, we throw an exception of a known type. When we do
> something like that, it would not be possible to edit some type of file
> using some type of application. This is normal. For example, if you try to
> open a text file using an Archive Manager like file-roller, it will throw an
> exception.
>
> And, for a file of no media type, no editor might might be able to edit
> that. But, normally, when someone creates a file through G-Reg's resource
> UI, he/she would be giving it a media type (when creating text content), or
> we'd be identifying it for him/her. Therefore, I smell some bug in the
> WebDAV implementation that does not carry this information to the
> client-side. Can you have a look into that aspect as well?
>
> Thanks,
> Senaka.
>
>>
>> [1]
>> http://stackoverflow.com/questions/607435/why-does-vim-save-files-with-a-extension
>> [2] http://platform.xwiki.org/xwiki/bin/view/Features/WebDAVDavFs2
>> --
>> Thanks,
>> Fazlan
>>
>>
>
>
> --
> *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://www.linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


-- 
Thanks,
Fazl

[Carbon-dev] What is Syslog configuration in Logging management UI?

[Charitha Kankanamge]

Hi all,

I see the following Syslog property config element in Logging management UI
of the latest AS pack. What is this supposed to do? Can someone please
explain or point me to the relevant discussion (or document/article)?

[image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]

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

Re: [Carbon-dev] [Important] Many jars from CARBON_HOME/lib/core/WEB-INF/lib have been moved to CARBON_HOME/lib/api

[Isuru Suriarachchi]

On Fri, Apr 15, 2011 at 12:08 PM, Afkham Azeez  wrote:

> Isuru,
> Please confirm that your test WARs which pick dependencies from webapp
> parent classloader as well as webapp classloader work. I have checked these,
> and it works, however it is better to double check.
>

Sure. Will build the trunk, test and let you know..

Thanks,
~Isuru


>
> Azeez
>
>
> On Fri, Apr 15, 2011 at 12:06 PM, Afkham Azeez  wrote:
>
>> Also review my commit in r91826
>>
>>
>> On Fri, Apr 15, 2011 at 12:03 PM, Afkham Azeez  wrote:
>>
>>> OK, I have committed the product changes. Product teams please take a
>>> look.
>>>
>>> Azeez
>>>
>>>
>>> On Fri, Apr 15, 2011 at 11:53 AM, Afkham Azeez  wrote:
>>>
 Don't commit now. I have local modifications.


 On Fri, Apr 15, 2011 at 11:49 AM, Supun Kamburugamuva 
 wrote:

> Thanks
>
> On Fri, Apr 15, 2011 at 11:48 AM, Afkham Azeez  wrote:
> > CARBON_HOME/lib/core/WEB-INF/classes
> >
> > On Fri, Apr 15, 2011 at 11:39 AM, Supun Kamburugamuva <
> su...@wso2.com>
> > wrote:
> >>
> >> Where should we place these configuration files?
> >>
> >> Thanks,
> >> Supun..
> >>
> >> On Fri, Apr 15, 2011 at 11:36 AM, Afkham Azeez 
> wrote:
> >> > ESB assembly has the following obsolete entries
> >> >  
> >> > src/main/conf/synapse.properties
> >> >
> >> >
> >> >
>  
> ${pom.artifactId}-${pom.version}/webapps/ROOT/WEB-INF/classes
> >> > synapse.properties
> >> > true
> >> > 
> >> > 
> >> > src/main/conf/datasources.properties
> >> >
> >> >
> >> >
>  
> ${pom.artifactId}-${pom.version}/webapps/ROOT/WEB-INF/classes
> >> > datasources.properties
> >> > true
> >> > 
> >> > 
> >> > src/main/conf/cipher-text.properties
> >> >
> >> >
> >> >
>  
> ${pom.artifactId}-${pom.version}/webapps/ROOT/WEB-INF/classes
> >> > cipher-text.properties
> >> > true
> >> > 
> >> > 
> >> > src/main/conf/nhttp.properties
> >> >
> >> >
> >> >
>  
> ${pom.artifactId}-${pom.version}/webapps/ROOT/WEB-INF/classes
> >> > nhttp.properties
> >> > true
> >> > 
> >> >
> >> > On Fri, Apr 15, 2011 at 11:27 AM, Afkham Azeez 
> wrote:
> >> >>
> >> >> Product teams,
> >> >> Please note $subject.
> >> >> We were doing a wrong thing by
> adding CARBON_HOME/lib/core/WEB-INF/lib
> >> >>  to
> >> >> the classpath, which makes these jars get loaded from the system
> >> >> classloader
> >> >> as well as the Carbon webapp's WebappClassloader. Now those jars
> have
> >> >> been
> >> >> moved to CARBON_HOME/lib/api, and those jars get loaded from the
> parent
> >> >> of
> >> >> the webapp classloader. The system classloader loads only the
> >> >> bootstrap.jar.
> >> >> Please check the scripts in your products. I have fixed many of
> those.
> >> >> I
> >> >> noticed the following in BPS:
> >> >>
> >> >>
> >> >>
> ./bps/modules/samples/product/sample-utils/src/main/scripts/axis2server.sh:for
> >> >> f in "$AXIS2_HOME"/../../lib/core/WEB-INF/lib/*.jar
> >> >> Please fix these as appropriate.
> >> >>
> >> >> --
> >> >> Afkham Azeez
> >> >> Senior Software Architect & Senior Manager; WSO2, Inc.;
> >> >> http://wso2.com,
> >> >>
> >> >> Member; Apache Software Foundation; http://www.apache.org/
> >> >> email: az...@wso2.com cell: +94 77 3320919
> >> >> blog: http://blog.afkham.org
> >> >> twitter: http://twitter.com/afkham_azeez
> >> >> linked-in: http://lk.linkedin.com/in/afkhamazeez
> >> >>
> >> >> Lean . Enterprise . Middleware
> >> >
> >> >
> >> >
> >> > --
> >> > Afkham Azeez
> >> > Senior Software Architect & Senior Manager; WSO2, Inc.;
> http://wso2.com,
> >> >
> >> > Member; Apache Software Foundation; http://www.apache.org/
> >> > email: az...@wso2.com cell: +94 77 3320919
> >> > blog: http://blog.afkham.org
> >> > twitter: 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
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Supun Kamburugamuva
> >> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
> >> Member, Apache Software Foundation; http://www.apache.org
> >> WSO2 Inc.;  http://wso2.org
> >> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
> >> Blog

Re: [Carbon-dev] What is Syslog configuration in Logging management UI?

[Samisa Abeysinghe]

And on a side note, all fields of this form are optional?

On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge wrote:

> Hi all,
>
> I see the following Syslog property config element in Logging management UI
> of the latest AS pack. What is this supposed to do? Can someone please
> explain or point me to the relevant discussion (or document/article)?
>
> [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]
>
> Regards
> Charitha
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
<>___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon/products/esb"

[WSO2 Builder]

[INFO]   Script Mediator Integration Tests
[INFO]   Send Mediator Integration Tests
[INFO]   Proxy Services Integration Tests
[INFO]   Sequence Module
[INFO]   WS-Discovery Integration Tests
[INFO] 
[INFO] Building WSO2 ESB - Aggregator Module
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Apr 15 15:21:32 UTC 2011
[INFO] Final Memory: 11M/207M
[INFO]  

 SVN Log  

r91828 | supun | 2011-04-15 14:59:16 + (Fri, 15 Apr 2011) | 1 line

adding a section to enable VFS transport in the axis2.xml

r91827 | azeez | 2011-04-15 06:58:35 + (Fri, 15 Apr 2011) | 2 lines

Updated main class to Bootstrap class since now we have switched to the 
bootstrap mechanism


r91826 | azeez | 2011-04-15 06:26:44 + (Fri, 15 Apr 2011) | 5 lines

Introduced bootstrapping mechanism for starting up Tomcat. 

See http://wso2.org/mailarchive/carbon-dev/2011-April/054927.html



r91820 | azeez | 2011-04-14 14:36:03 + (Thu, 14 Apr 2011) | 3 lines

Removed lib/realm jar signing from poms since this directory is no longer used



r91810 | hiranya | 2011-04-14 09:25:23 + (Thu, 14 Apr 2011) | 1 line

Fixing script mediator tests and adding it to the build

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

[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon/products/esb"

[WSO2 Builder]

[INFO]   Script Mediator Integration Tests
[INFO]   Send Mediator Integration Tests
[INFO]   Proxy Services Integration Tests
[INFO]   Sequence Module
[INFO]   WS-Discovery Integration Tests
[INFO] 
[INFO] Building WSO2 ESB - Aggregator Module
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Apr 15 15:21:32 UTC 2011
[INFO] Final Memory: 11M/207M
[INFO] 

grep products svn.up | cut -d ' ' -f5 | cut -d '/' -s -f1,2 | sort -u  > 
$CARBON_SRC_HOME/folders
build_in_loop
products/esb
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   WSO2 ESB - Aggregator Module
[INFO]   WSO2 ESB - Styles Parent
[INFO]   WSO2 ESB - Styles
[INFO]   WSO2 Stratos ESB - Styles
[INFO]   WSO2 ESB - Samples Parent
[INFO]   WSO2 ESB - Samples
[INFO]   WSO2 Stratos ESB - Samples
[INFO]   WSO2 ESB - Features Parent
[INFO]   WSO2 ESB - Features Aggregator Module
[INFO]   WSO2 ESB - Styles Features
[INFO]   WSO2 ESB - Samples Features
[INFO]   WSO2 Stratos ESB - Login User Interface
[INFO]   WSO2 Stratos ESB - Features Aggregator Module
[INFO]   WSO2 Stratos ESB - Login UI Feature
[INFO]   WSO2 Stratos ESB - Styles Features
[INFO]   WSO2 Stratos ESB - Samples Features
[INFO]   WSO2 ESB - P2 Profile Generation Parent
[INFO]   WSO2 ESB - P2 Profile Generation
[INFO]   WSO2 Stratos ESB - P2 Profile Generation
[INFO]   WSO2 ESB - Distribution Parent
[INFO]   WSO2 ESB - Distribution
[INFO]   WSO2 Stratos ESB - Distribution
[INFO]   WSO2 ESB - Integration Parent
[INFO]   WSO2 ESB Integration Test Core
[INFO]   Endpoint Integration Tests
--
[INFO]   Script Mediator Integration Tests
[INFO]   Send Mediator Integration Tests
[INFO]   Proxy Services Integration Tests
[INFO]   Sequence Module
[INFO]   WS-Discovery Integration Tests
[INFO] 
[INFO] Building WSO2 ESB - Aggregator Module
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Apr 15 15:21:39 UTC 2011
[INFO] Final Memory: 11M/205M
[INFO]  

 SVN Log  

r91828 | supun | 2011-04-15 14:59:16 + (Fri, 15 Apr 2011) | 1 line

adding a section to enable VFS transport in the axis2.xml

r91827 | azeez | 2011-04-15 06:58:35 + (Fri, 15 Apr 2011) | 2 lines

Updated main class to Bootstrap class since now we have switched to the 
bootstrap mechanism


r91826 | azeez | 2011-04-15 06:26:44 + (Fri, 15 Apr 2011) | 5 lines

Introduced bootstrapping mechanism for starting up Tomcat. 

See http://wso2.org/mailarchive/carbon-dev/2011-April/054927.html



r91820 | azeez | 2011-04-14 14:36:03 + (Thu, 14 Apr 2011) | 3 lines

Removed lib/realm jar signing from poms since this directory is no longer used



r91810 | hiranya | 2011-04-14 09:25:23 + (Thu, 14 Apr 2011) | 1 line

Fixing script mediator tests and adding it to the build

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

Re: [Carbon-dev] What is Syslog configuration in Logging management UI?

[Afkham Azeez]

Why is password starting with lower case p?
On Apr 15, 2011 8:23 PM, "Samisa Abeysinghe"  wrote:
> And on a side note, all fields of this form are optional?
>
> On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge wrote:
>
>> Hi all,
>>
>> I see the following Syslog property config element in Logging management
UI
>> of the latest AS pack. What is this supposed to do? Can someone please
>> explain or point me to the relevant discussion (or document/article)?
>>
>> [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]
>>
>> Regards
>> Charitha
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] What is Syslog configuration in Logging management UI?

[Deependra Ariyadewa]

On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge wrote:

> Hi all,
>
> I see the following Syslog property config element in Logging management UI
> of the latest AS pack. What is this supposed to do? Can someone please
> explain or point me to the relevant discussion (or document/article)?
>

This interface added to support Stratos remote logging feature.

We make available remotely collected logs via http or https to Stratos log
viewer. Supper tenant should fill these details to get remote log access.

I will forward the design doc Amani has created for Stratos remote logging.

Thanks,

Deependra.


> [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]
>
> Regards
> Charitha
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Deependra Ariyadewa
WSO2, Inc.;  http://wso2.com/
email: d...@wso2.com; cell: +94 71 403 5996 ; PGP: 'DC627E6F'
<>___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Logging Issues @ ESB startup

[Senaka Fernando]

Hi all,

Why do I get the following? This is from what was built on the 15th of April
on the Builder Machine.

+++
[Broker] BRK-1006 : Using configuration :
/home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
Logging configuration error: unable to read file
/home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/log4j.xml
Using the fallback internal log4j.properties configuration
[Broker] BRK-1001 : Startup : Version: 0.11 Build: 90784:90849
[Broker] MNG-1001 : Startup
[Broker] MNG-1004 : Ready : Using the platform JMX Agent
[Broker] BRK-1002 : Starting : Listening on TCP port 5672
[Broker] BRK-1004 : Qpid Broker Ready
+++

Thanks,
Senaka.

-- 
*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://www.linkedin.com/in/senakafernando

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

Re: [Carbon-dev] What is Syslog configuration in Logging management UI?

[Sumedha Rubasinghe]

On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge wrote:

> Hi all,
>
> I see the following Syslog property config element in Logging management UI
> of the latest AS pack. What is this supposed to do? Can someone please
> explain or point me to the relevant discussion (or document/article)?


Charitha,
How this fits into an enterprise deployment is as follows.

Syslog is a standard well known protocol where there is a syslog server &
clients (syslog event publishers). Most of the server software(OS, app
servers, email, database engines,web servers) support acting as syslog
clients. From a system administration PoV, it's very convenient to see all
the log events coming to a single server & ability to monitor everything
from a single console.

Log4j by default provides the capability of publishing to syslog servers. So
we had this capability b4. This UI is part of enhancement related to Stratos
logging.

Check [1] for additional info.
/sumedha

[1] http://www.monitorware.com/common/en/articles/syslog-described.php


> [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]
>
> Regards
> Charitha
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
<>___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] What is Syslog configuration in Logging management UI?

[Senaka Fernando]

Hi all,

Small question. Based on Amani's explanation, why do we have URL + Port?
Isn't Port redundant?

Thanks,
Senaka.

On Fri, Apr 15, 2011 at 10:43 PM, Sumedha Rubasinghe wrote:

>
>
> On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge wrote:
>
>> Hi all,
>>
>> I see the following Syslog property config element in Logging management
>> UI of the latest AS pack. What is this supposed to do? Can someone please
>> explain or point me to the relevant discussion (or document/article)?
>
>
> Charitha,
> How this fits into an enterprise deployment is as follows.
>
> Syslog is a standard well known protocol where there is a syslog server &
> clients (syslog event publishers). Most of the server software(OS, app
> servers, email, database engines,web servers) support acting as syslog
> clients. From a system administration PoV, it's very convenient to see all
> the log events coming to a single server & ability to monitor everything
> from a single console.
>
> Log4j by default provides the capability of publishing to syslog servers.
> So we had this capability b4. This UI is part of enhancement related to
> Stratos logging.
>
> Check [1] for additional info.
> /sumedha
>
> [1] http://www.monitorware.com/common/en/articles/syslog-described.php
>
>
>> [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]
>>
>> Regards
>> Charitha
>>
>> ___
>> 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
>
>


-- 
*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://www.linkedin.com/in/senakafernando

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

Re: [Carbon-dev] Logging Issues @ ESB startup

[Supun Kamburugamuva]

This is from QPid. We have to get rid of these System outs. I did
point this out before as well.

Thanks,
Supun..

On Fri, Apr 15, 2011 at 10:37 PM, Senaka Fernando  wrote:
> Hi all,
>
> Why do I get the following? This is from what was built on the 15th of April
> on the Builder Machine.
>
> +++
> [Broker] BRK-1006 : Using configuration :
> /home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
> Logging configuration error: unable to read file
> /home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/log4j.xml
> Using the fallback internal log4j.properties configuration
> [Broker] BRK-1001 : Startup : Version: 0.11 Build: 90784:90849
> [Broker] MNG-1001 : Startup
> [Broker] MNG-1004 : Ready : Using the platform JMX Agent
> [Broker] BRK-1002 : Starting : Listening on TCP port 5672
> [Broker] BRK-1004 : Qpid Broker Ready
> +++
>
> Thanks,
> Senaka.
>
> --
> 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://www.linkedin.com/in/senakafernando
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>



-- 
Supun Kamburugamuva
Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org
WSO2 Inc.;  http://wso2.org
E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
Blog: http://supunk.blogspot.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] What is Syslog configuration in Logging management UI?

[Sumedha Rubasinghe]

On Fri, Apr 15, 2011 at 10:48 PM, Senaka Fernando  wrote:

> Hi all,
>
> Small question. Based on Amani's explanation, why do we have URL + Port?
> Isn't Port redundant?
>
> I believe correct terminology should be server & port. That goes well with
Log4j Syslog-ng terminology[2] as well.
/sumedha
[2] http://wiki.apache.org/logging-log4j/syslog


> Thanks,
> Senaka.
>
>
> On Fri, Apr 15, 2011 at 10:43 PM, Sumedha Rubasinghe wrote:
>
>>
>>
>> On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge 
>> wrote:
>>
>>> Hi all,
>>>
>>> I see the following Syslog property config element in Logging management
>>> UI of the latest AS pack. What is this supposed to do? Can someone please
>>> explain or point me to the relevant discussion (or document/article)?
>>
>>
>> Charitha,
>> How this fits into an enterprise deployment is as follows.
>>
>> Syslog is a standard well known protocol where there is a syslog server &
>> clients (syslog event publishers). Most of the server software(OS, app
>> servers, email, database engines,web servers) support acting as syslog
>> clients. From a system administration PoV, it's very convenient to see all
>> the log events coming to a single server & ability to monitor everything
>> from a single console.
>>
>> Log4j by default provides the capability of publishing to syslog servers.
>> So we had this capability b4. This UI is part of enhancement related to
>> Stratos logging.
>>
>> Check [1] for additional info.
>> /sumedha
>>
>> [1] http://www.monitorware.com/common/en/articles/syslog-described.php
>>
>>
>>> [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]
>>>
>>> Regards
>>> Charitha
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> *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://www.linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] What is Syslog configuration in Logging management UI?

[Senaka Fernando]

On Fri, Apr 15, 2011 at 10:58 PM, Sumedha Rubasinghe wrote:

>
>
> On Fri, Apr 15, 2011 at 10:48 PM, Senaka Fernando  wrote:
>
>> Hi all,
>>
>> Small question. Based on Amani's explanation, why do we have URL + Port?
>> Isn't Port redundant?
>>
>> I believe correct terminology should be server & port. That goes well with
> Log4j Syslog-ng terminology[2] as well.
> /sumedha
> [2] http://wiki.apache.org/logging-log4j/syslog
>

I felt the same, initially. But Amani's explanation confused me a bit, since
the value for URL was, http://127.0.0.1/logs. That endpoint clearly has more
than the host name in it. So, I'm still in doubt.

Anyway in general, I'm +1 for using Host + Port instead of URL, since syslog
is something that's not directly bound to HTTP or something, AFAIK (correct
me if I'm wrong).

Thanks,
Senaka.


>
>> Thanks,
>> Senaka.
>>
>>
>> On Fri, Apr 15, 2011 at 10:43 PM, Sumedha Rubasinghe wrote:
>>
>>>
>>>
>>> On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge 
>>> wrote:
>>>
 Hi all,

 I see the following Syslog property config element in Logging management
 UI of the latest AS pack. What is this supposed to do? Can someone please
 explain or point me to the relevant discussion (or document/article)?
>>>
>>>
>>> Charitha,
>>> How this fits into an enterprise deployment is as follows.
>>>
>>> Syslog is a standard well known protocol where there is a syslog server &
>>> clients (syslog event publishers). Most of the server software(OS, app
>>> servers, email, database engines,web servers) support acting as syslog
>>> clients. From a system administration PoV, it's very convenient to see all
>>> the log events coming to a single server & ability to monitor everything
>>> from a single console.
>>>
>>> Log4j by default provides the capability of publishing to syslog servers.
>>> So we had this capability b4. This UI is part of enhancement related to
>>> Stratos logging.
>>>
>>> Check [1] for additional info.
>>> /sumedha
>>>
>>> [1] http://www.monitorware.com/common/en/articles/syslog-described.php
>>>
>>>
 [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]

 Regards
 Charitha

 ___
 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
>>>
>>>
>>
>>
>> --
>> *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://www.linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>>
>


-- 
*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://www.linkedin.com/in/senakafernando

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

Re: [Carbon-dev] Logging Issues @ ESB startup

[Kasun Indrasiri]

On Fri, Apr 15, 2011 at 10:53 PM, Supun Kamburugamuva wrote:

> This is from QPid. We have to get rid of these System outs. I did
> point this out before as well.
>
>
Also there are some  system outs from smooks.

>> Stopping Smooks Bundle [1.4.0.wso2v1]

Thanks,
> Supun..
>
> On Fri, Apr 15, 2011 at 10:37 PM, Senaka Fernando  wrote:
> > Hi all,
> >
> > Why do I get the following? This is from what was built on the 15th of
> April
> > on the Builder Machine.
> >
> > +++
> > [Broker] BRK-1006 : Using configuration :
> >
> /home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
> > Logging configuration error: unable to read file
> >
> /home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/log4j.xml
> > Using the fallback internal log4j.properties configuration
> > [Broker] BRK-1001 : Startup : Version: 0.11 Build: 90784:90849
> > [Broker] MNG-1001 : Startup
> > [Broker] MNG-1004 : Ready : Using the platform JMX Agent
> > [Broker] BRK-1002 : Starting : Listening on TCP port 5672
> > [Broker] BRK-1004 : Qpid Broker Ready
> > +++
> >
> > Thanks,
> > Senaka.
> >
> > --
> > 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://www.linkedin.com/in/senakafernando
> >
> > Lean . Enterprise . Middleware
> >
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
>
>
> --
> Supun Kamburugamuva
> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
> Member, Apache Software Foundation; http://www.apache.org
> WSO2 Inc.;  http://wso2.org
> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
> Blog: http://supunk.blogspot.com
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Kasun Indrasiri
Senior Software Engineer
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon/components/registry/org.wso2.carbon.registry.eventing"

[WSO2 Builder]

components/registry/org.wso2.carbon.registry.eventing
[INFO] Scanning for projects...
[INFO] 
[INFO] Building WSO2 Carbon - Registry - Eventing Implementation
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Apr 15 17:45:12 UTC 2011
[INFO] Final Memory: 6M/145M
[INFO]  

 SVN Log  

r91829 | senaka | 2011-04-15 17:31:13 + (Fri, 15 Apr 2011) | 1 line

doing async event generation.

r91729 | senaka | 2011-04-07 01:00:48 + (Thu, 07 Apr 2011) | 2 lines

Fixing JIRA Issues CARBON-9309, CARBON-9310 - Thanks Ajith.


r91612 | senaka | 2011-04-04 11:59:31 + (Mon, 04 Apr 2011) | 2 lines

Moving Registry Eventing Implementation to the new Event model.


r90919 | senaka | 2011-03-26 23:25:46 + (Sat, 26 Mar 2011) | 2 lines

Fixed some obvious bugs.


r88613 | sameera | 2011-03-01 19:05:31 + (Tue, 01 Mar 2011) | 1 line

Moved the DependencyManagement and properties sections to the component root pom

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

Re: [Carbon-dev] Logging Issues @ ESB startup

[Senaka Fernando]

On Fri, Apr 15, 2011 at 11:12 PM, Kasun Indrasiri  wrote:

>
>
> On Fri, Apr 15, 2011 at 10:53 PM, Supun Kamburugamuva wrote:
>
>> This is from QPid. We have to get rid of these System outs. I did
>> point this out before as well.
>>
>>
> Also there are some  system outs from smooks.
>
> >> Stopping Smooks Bundle [1.4.0.wso2v1]
>

There is an sout from smooks at Startup as well.

Starting Smooks Bundle [1.4.0.wso2v1]
Registered : org.milyn.Smooks

Thanks,
Senaka.

>
> Thanks,
>> Supun..
>>
>> On Fri, Apr 15, 2011 at 10:37 PM, Senaka Fernando 
>> wrote:
>> > Hi all,
>> >
>> > Why do I get the following? This is from what was built on the 15th of
>> April
>> > on the Builder Machine.
>> >
>> > +++
>> > [Broker] BRK-1006 : Using configuration :
>> >
>> /home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
>> > Logging configuration error: unable to read file
>> >
>> /home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/log4j.xml
>> > Using the fallback internal log4j.properties configuration
>> > [Broker] BRK-1001 : Startup : Version: 0.11 Build: 90784:90849
>> > [Broker] MNG-1001 : Startup
>> > [Broker] MNG-1004 : Ready : Using the platform JMX Agent
>> > [Broker] BRK-1002 : Starting : Listening on TCP port 5672
>> > [Broker] BRK-1004 : Qpid Broker Ready
>> > +++
>> >
>> > Thanks,
>> > Senaka.
>> >
>> > --
>> > 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://www.linkedin.com/in/senakafernando
>> >
>> > Lean . Enterprise . Middleware
>> >
>> >
>> > ___
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org
>> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>>
>>
>>
>> --
>> Supun Kamburugamuva
>> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
>> Member, Apache Software Foundation; http://www.apache.org
>> WSO2 Inc.;  http://wso2.org
>> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
>> Blog: http://supunk.blogspot.com
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> Kasun Indrasiri
> Senior Software Engineer
>
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> 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://www.linkedin.com/in/senakafernando

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

Re: [Carbon-dev] Logging Issues @ ESB startup

[Supun Kamburugamuva]

I've noticed this as well. I'm wondering how this comes.

Supun..

On Fri, Apr 15, 2011 at 11:19 PM, Senaka Fernando  wrote:
>
>
> On Fri, Apr 15, 2011 at 11:12 PM, Kasun Indrasiri  wrote:
>>
>>
>> On Fri, Apr 15, 2011 at 10:53 PM, Supun Kamburugamuva 
>> wrote:
>>>
>>> This is from QPid. We have to get rid of these System outs. I did
>>> point this out before as well.
>>>
>>
>> Also there are some  system outs from smooks.
>> >> Stopping Smooks Bundle [1.4.0.wso2v1]
>
> There is an sout from smooks at Startup as well.
>
> Starting Smooks Bundle [1.4.0.wso2v1]
> Registered : org.milyn.Smooks
>
> Thanks,
> Senaka.
>>
>>> Thanks,
>>> Supun..
>>>
>>> On Fri, Apr 15, 2011 at 10:37 PM, Senaka Fernando 
>>> wrote:
>>> > Hi all,
>>> >
>>> > Why do I get the following? This is from what was built on the 15th of
>>> > April
>>> > on the Builder Machine.
>>> >
>>> > +++
>>> > [Broker] BRK-1006 : Using configuration :
>>> >
>>> > /home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
>>> > Logging configuration error: unable to read file
>>> >
>>> > /home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/log4j.xml
>>> > Using the fallback internal log4j.properties configuration
>>> > [Broker] BRK-1001 : Startup : Version: 0.11 Build: 90784:90849
>>> > [Broker] MNG-1001 : Startup
>>> > [Broker] MNG-1004 : Ready : Using the platform JMX Agent
>>> > [Broker] BRK-1002 : Starting : Listening on TCP port 5672
>>> > [Broker] BRK-1004 : Qpid Broker Ready
>>> > +++
>>> >
>>> > Thanks,
>>> > Senaka.
>>> >
>>> > --
>>> > 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://www.linkedin.com/in/senakafernando
>>> >
>>> > Lean . Enterprise . Middleware
>>> >
>>> >
>>> > ___
>>> > Carbon-dev mailing list
>>> > Carbon-dev@wso2.org
>>> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Supun Kamburugamuva
>>> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
>>> Member, Apache Software Foundation; http://www.apache.org
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
>>> Blog: http://supunk.blogspot.com
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Senior Software Engineer
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> 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://www.linkedin.com/in/senakafernando
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>



-- 
Supun Kamburugamuva
Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org
WSO2 Inc.;  http://wso2.org
E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
Blog: http://supunk.blogspot.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon/components/registry/org.wso2.carbon.registry.eventing"

[WSO2 Builder]

components/registry/org.wso2.carbon.registry.eventing
[INFO] Scanning for projects...
[INFO] 
[INFO] Building WSO2 Carbon - Registry - Eventing Implementation
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 second
[INFO] Finished at: Fri Apr 15 19:50:14 UTC 2011
[INFO] Final Memory: 6M/145M
[INFO]  

 SVN Log  

r91830 | senaka | 2011-04-15 19:33:36 + (Fri, 15 Apr 2011) | 1 line

setting up Carbon Context information before generating event.

r91829 | senaka | 2011-04-15 17:31:13 + (Fri, 15 Apr 2011) | 1 line

doing async event generation.

r91729 | senaka | 2011-04-07 01:00:48 + (Thu, 07 Apr 2011) | 2 lines

Fixing JIRA Issues CARBON-9309, CARBON-9310 - Thanks Ajith.


r91612 | senaka | 2011-04-04 11:59:31 + (Mon, 04 Apr 2011) | 2 lines

Moving Registry Eventing Implementation to the new Event model.


r90919 | senaka | 2011-03-26 23:25:46 + (Sat, 26 Mar 2011) | 2 lines

Fixed some obvious bugs.


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

[Carbon-dev] Why do we use exec in wso2server.sh?

[Afkham Azeez]

Instead of simply doing; "java ..." we do "exec java ...". Why have we used
exec here? I'm trying to solve the restart issue using exit codes, and when
exec is used, the process exit code cannot be captured.

-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*
*
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **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

Re: [Carbon-dev] Why do we use exec in wso2server.sh?

[Sanjiva Weerawarana]

Its good to use exec so that the parent shell process doesn't hang around.
That's common practice for shell scripts which set up a bunch of stuff and
run something else right at the end.

But that should not be a problem as the process exit status should be that
of the exec'ed command IIRC (new command is run in the same process).

Here's a small test:

$ cat /tmp/foo.sh
#!/bin/sh

exit 79
$ sh -c "exec /tmp/foo.sh"
$ echo $?
79

Sanjiva.

On Sat, Apr 16, 2011 at 4:13 AM, Afkham Azeez  wrote:

> Instead of simply doing; "java ..." we do "exec java ...". Why have we used
> exec here? I'm trying to solve the restart issue using exit codes, and when
> exec is used, the process exit code cannot be captured.
>
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; 
> **http://www.apache.org/*
> *
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **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
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/

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

Re: [Carbon-dev] What is Syslog configuration in Logging management UI?

[Amani Soysa]

Hi



On Fri, Apr 15, 2011 at 11:11 PM, Senaka Fernando  wrote:

>
>
> On Fri, Apr 15, 2011 at 10:58 PM, Sumedha Rubasinghe wrote:
>
>>
>>
>> On Fri, Apr 15, 2011 at 10:48 PM, Senaka Fernando wrote:
>>
>>> Hi all,
>>>
>>> Small question. Based on Amani's explanation, why do we have URL + Port?
>>> Isn't Port redundant?
>>>
>>> I believe correct terminology should be server & port. That goes well
>> with Log4j Syslog-ng terminology[2] as well.
>>
>  Yes syslog-ng log url is where the log cluster is hosted .. (i will
change the names to server and port ).

> /sumedha
>> [2] http://wiki.apache.org/logging-log4j/syslog
>>
>
> I felt the same, initially. But Amani's explanation confused me a bit,
> since the value for URL was, http://127.0.0.1/logs. That endpoint clearly
> has more than the host name in it. So, I'm still in doubt.
>
> Anyway in general, I'm +1 for using Host + Port instead of URL, since
> syslog is something that's not directly bound to HTTP or something, AFAIK
> (correct me if I'm wrong).
>
> Thanks,
> Senaka.
>
>
>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Fri, Apr 15, 2011 at 10:43 PM, Sumedha Rubasinghe 
>>> wrote:
>>>


 On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge >>> > wrote:

> Hi all,
>
> I see the following Syslog property config element in Logging
> management UI of the latest AS pack. What is this supposed to do? Can
> someone please explain or point me to the relevant discussion (or
> document/article)?


 Charitha,
 How this fits into an enterprise deployment is as follows.

 Syslog is a standard well known protocol where there is a syslog server
 & clients (syslog event publishers). Most of the server software(OS, app
 servers, email, database engines,web servers) support acting as syslog
 clients. From a system administration PoV, it's very convenient to see all
 the log events coming to a single server & ability to monitor everything
 from a single console.

 Log4j by default provides the capability of publishing to syslog
 servers. So we had this capability b4. This UI is part of enhancement
 related to Stratos logging.

 Check [1] for additional info.
 /sumedha

 [1] http://www.monitorware.com/common/en/articles/syslog-described.php


> [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]
>
> Regards
> Charitha
>
> ___
> 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


>>>
>>>
>>> --
>>> *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://www.linkedin.com/in/senakafernando
>>>
>>> *Lean . Enterprise . Middleware
>>>
>>>
>>
>
>
> --
> *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://www.linkedin.com/in/senakafernando
>
> *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

Re: [Carbon-dev] What is Syslog configuration in Logging management UI?

[Charitha Kankanamge]

Thanks for the nice explanation Sumedha, Amani and Deep.

On Fri, Apr 15, 2011 at 10:43 PM, Sumedha Rubasinghe wrote:

>
>
> On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge wrote:
>
>> Hi all,
>>
>> I see the following Syslog property config element in Logging management
>> UI of the latest AS pack. What is this supposed to do? Can someone please
>> explain or point me to the relevant discussion (or document/article)?
>
>
> Charitha,
> How this fits into an enterprise deployment is as follows.
>
> Syslog is a standard well known protocol where there is a syslog server &
> clients (syslog event publishers). Most of the server software(OS, app
> servers, email, database engines,web servers) support acting as syslog
> clients. From a system administration PoV, it's very convenient to see all
> the log events coming to a single server & ability to monitor everything
> from a single console.
>
> Log4j by default provides the capability of publishing to syslog servers.
> So we had this capability b4. This UI is part of enhancement related to
> Stratos logging.
>
> Check [1] for additional info.
> /sumedha
>
> [1] http://www.monitorware.com/common/en/articles/syslog-described.php
>
>
>> [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]
>>
>> Regards
>> Charitha
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
<>___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Why do we use exec in wso2server.sh?

[Afkham Azeez]

Thanks!

sh -c "exec java ..."
worked!

Earlier the script only had "exec java ..."

On Sat, Apr 16, 2011 at 7:15 AM, Sanjiva Weerawarana wrote:

> Its good to use exec so that the parent shell process doesn't hang around.
> That's common practice for shell scripts which set up a bunch of stuff and
> run something else right at the end.
>
> But that should not be a problem as the process exit status should be that
> of the exec'ed command IIRC (new command is run in the same process).
>
> Here's a small test:
>
> $ cat /tmp/foo.sh
> #!/bin/sh
>
> exit 79
> $ sh -c "exec /tmp/foo.sh"
> $ echo $?
> 79
>
> Sanjiva.
>
> On Sat, Apr 16, 2011 at 4:13 AM, Afkham Azeez  wrote:
>
>> Instead of simply doing; "java ..." we do "exec java ...". Why have we
>> used exec here? I'm trying to solve the restart issue using exit codes, and
>> when exec is used, the process exit code cannot be captured.
>>
>> --
>> *Afkham Azeez*
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> *
>> *
>> *Member; Apache Software Foundation; 
>> **http://www.apache.org/*
>> *
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **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
>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
>



-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*
*
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **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

Re: [Carbon-dev] What is Syslog configuration in Logging management UI?

[Afkham Azeez]

It will be better to put all the stuff discussed on this thread into a doc.

Azeez

On Sat, Apr 16, 2011 at 8:02 AM, Charitha Kankanamge wrote:

> Thanks for the nice explanation Sumedha, Amani and Deep.
>
> On Fri, Apr 15, 2011 at 10:43 PM, Sumedha Rubasinghe wrote:
>
>>
>>
>> On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge 
>> wrote:
>>
>>> Hi all,
>>>
>>> I see the following Syslog property config element in Logging management
>>> UI of the latest AS pack. What is this supposed to do? Can someone please
>>> explain or point me to the relevant discussion (or document/article)?
>>
>>
>> Charitha,
>> How this fits into an enterprise deployment is as follows.
>>
>> Syslog is a standard well known protocol where there is a syslog server &
>> clients (syslog event publishers). Most of the server software(OS, app
>> servers, email, database engines,web servers) support acting as syslog
>> clients. From a system administration PoV, it's very convenient to see all
>> the log events coming to a single server & ability to monitor everything
>> from a single console.
>>
>> Log4j by default provides the capability of publishing to syslog servers.
>> So we had this capability b4. This UI is part of enhancement related to
>> Stratos logging.
>>
>> Check [1] for additional info.
>> /sumedha
>>
>> [1] http://www.monitorware.com/common/en/articles/syslog-described.php
>>
>>
>>> [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png]
>>>
>>> Regards
>>> Charitha
>>>
>>> ___
>>> 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
>
>


-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*
*
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **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

[Carbon-dev] "WSO2 Carbon Incremental Build has FAILED /home/carbon/carbon"

[WSO2 Builder]

[INFO] [install:install]
[INFO] Installing 
/home/carbon/carbon/dependencies/XmlSchema/target/XmlSchema-1.4.6-wso2v2.jar to 
/home/carbon/.m2/repository/org/apache/ws/commons/schema/XmlSchema/1.4.6-wso2v2/XmlSchema-1.4.6-wso2v2.jar
[INFO] [bundle:install]
[INFO] Installing 
org/apache/ws/commons/schema/XmlSchema/1.4.6-wso2v2/XmlSchema-1.4.6-wso2v2.jar
[INFO] Writing OBR metadata
[INFO] 
[INFO] Building Apache Axis2 - Parent
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error resolving version for 
'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 
2.0.9
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 9 minutes 17 seconds
[INFO] Finished at: Sat Apr 16 04:48:42 UTC 2011
[INFO] Final Memory: 530M/956M
[INFO]  

 SVN Log  

r91831 | isuru | 2011-04-16 04:20:26 + (Sat, 16 Apr 2011) | 1 line

adding org.wso2.carbon.bootstrap module into root pom.xml

r91830 | senaka | 2011-04-15 19:33:36 + (Fri, 15 Apr 2011) | 1 line

setting up Carbon Context information before generating event.

r91829 | senaka | 2011-04-15 17:31:13 + (Fri, 15 Apr 2011) | 1 line

doing async event generation.

r91828 | supun | 2011-04-15 14:59:16 + (Fri, 15 Apr 2011) | 1 line

adding a section to enable VFS transport in the axis2.xml

r91827 | azeez | 2011-04-15 06:58:35 + (Fri, 15 Apr 2011) | 2 lines

Updated main class to Bootstrap class since now we have switched to the 
bootstrap mechanism


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

Re: [Carbon-dev] Why do we use exec in wso2server.sh?

[Sanjiva Weerawarana]

No saying "sh -c .." means you're creating a new shell and then exec'ng in
there. In that case you might as well just say "java .." (without the exec
at all).

Doesn't having "exec java" at the end give the return code of the java
command to the calling shell? That's what's spsed to happen.

Sanjiva.

On Sat, Apr 16, 2011 at 9:53 AM, Afkham Azeez  wrote:

> Thanks!
>
> sh -c "exec java ..."
> worked!
>
> Earlier the script only had "exec java ..."
>
>
> On Sat, Apr 16, 2011 at 7:15 AM, Sanjiva Weerawarana wrote:
>
>> Its good to use exec so that the parent shell process doesn't hang around.
>> That's common practice for shell scripts which set up a bunch of stuff and
>> run something else right at the end.
>>
>> But that should not be a problem as the process exit status should be that
>> of the exec'ed command IIRC (new command is run in the same process).
>>
>> Here's a small test:
>>
>> $ cat /tmp/foo.sh
>> #!/bin/sh
>>
>> exit 79
>> $ sh -c "exec /tmp/foo.sh"
>> $ echo $?
>> 79
>>
>> Sanjiva.
>>
>> On Sat, Apr 16, 2011 at 4:13 AM, Afkham Azeez  wrote:
>>
>>> Instead of simply doing; "java ..." we do "exec java ...". Why have we
>>> used exec here? I'm trying to solve the restart issue using exit codes, and
>>> when exec is used, the process exit code cannot be captured.
>>>
>>> --
>>> *Afkham Azeez*
>>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com
>>> ,
>>> *
>>> *
>>> *Member; Apache Software Foundation; 
>>> **http://www.apache.org/*
>>> *
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: **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
>>>
>>>
>>
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
>> 650 265 8311
>> blog: http://sanjiva.weerawarana.org/
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; 
> **http://www.apache.org/*
> *
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/

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

Re: [Carbon-dev] Logging Issues @ ESB startup

[Hiranya Jayathilaka]

There's another issue. During the ESB startup the pattern layout of the
generated logs suddenly changes soon after the Qpid broker has initialized.
Looks like Qpid is messing with our standard log4j settings.

Thanks,
Hiranya

On Sat, Apr 16, 2011 at 12:56 AM, Supun Kamburugamuva wrote:

> I've noticed this as well. I'm wondering how this comes.
>
> Supun..
>
> On Fri, Apr 15, 2011 at 11:19 PM, Senaka Fernando  wrote:
> >
> >
> > On Fri, Apr 15, 2011 at 11:12 PM, Kasun Indrasiri 
> wrote:
> >>
> >>
> >> On Fri, Apr 15, 2011 at 10:53 PM, Supun Kamburugamuva 
> >> wrote:
> >>>
> >>> This is from QPid. We have to get rid of these System outs. I did
> >>> point this out before as well.
> >>>
> >>
> >> Also there are some  system outs from smooks.
> >> >> Stopping Smooks Bundle [1.4.0.wso2v1]
> >
> > There is an sout from smooks at Startup as well.
> >
> > Starting Smooks Bundle [1.4.0.wso2v1]
> > Registered : org.milyn.Smooks
> >
> > Thanks,
> > Senaka.
> >>
> >>> Thanks,
> >>> Supun..
> >>>
> >>> On Fri, Apr 15, 2011 at 10:37 PM, Senaka Fernando 
> >>> wrote:
> >>> > Hi all,
> >>> >
> >>> > Why do I get the following? This is from what was built on the 15th
> of
> >>> > April
> >>> > on the Builder Machine.
> >>> >
> >>> > +++
> >>> > [Broker] BRK-1006 : Using configuration :
> >>> >
> >>> >
> /home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
> >>> > Logging configuration error: unable to read file
> >>> >
> >>> >
> /home/senaka/Downloads/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/log4j.xml
> >>> > Using the fallback internal log4j.properties configuration
> >>> > [Broker] BRK-1001 : Startup : Version: 0.11 Build: 90784:90849
> >>> > [Broker] MNG-1001 : Startup
> >>> > [Broker] MNG-1004 : Ready : Using the platform JMX Agent
> >>> > [Broker] BRK-1002 : Starting : Listening on TCP port 5672
> >>> > [Broker] BRK-1004 : Qpid Broker Ready
> >>> > +++
> >>> >
> >>> > Thanks,
> >>> > Senaka.
> >>> >
> >>> > --
> >>> > 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://www.linkedin.com/in/senakafernando
> >>> >
> >>> > Lean . Enterprise . Middleware
> >>> >
> >>> >
> >>> > ___
> >>> > Carbon-dev mailing list
> >>> > Carbon-dev@wso2.org
> >>> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>> >
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> Supun Kamburugamuva
> >>> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
> >>> Member, Apache Software Foundation; http://www.apache.org
> >>> WSO2 Inc.;  http://wso2.org
> >>> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
> >>> Blog: http://supunk.blogspot.com
> >>> ___
> >>> Carbon-dev mailing list
> >>> Carbon-dev@wso2.org
> >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>
> >>
> >>
> >> --
> >> Kasun Indrasiri
> >> Senior Software Engineer
> >> WSO2, Inc.; http://wso2.com
> >> lean.enterprise.middleware
> >>
> >> cell: +94 71 536 4128
> >> Blog : http://kasunpanorama.blogspot.com/
> >>
> >> ___
> >> 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://www.linkedin.com/in/senakafernando
> >
> > Lean . Enterprise . Middleware
> >
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
>
>
> --
> Supun Kamburugamuva
> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
> Member, Apache Software Foundation; http://www.apache.org
> WSO2 Inc.;  http://wso2.org
> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
> Blog: http://supunk.blogspot.com
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Why do we use exec in wso2server.sh?

[Afkham Azeez]

If you do;

$ exec ./foo.sh

You will simply see the following line;
[Process completed]

and the control does not return to the current shell.


On Sat, Apr 16, 2011 at 10:21 AM, Sanjiva Weerawarana wrote:

> No saying "sh -c .." means you're creating a new shell and then exec'ng in
> there. In that case you might as well just say "java .." (without the exec
> at all).
>
> Doesn't having "exec java" at the end give the return code of the java
> command to the calling shell? That's what's spsed to happen.
>
> Sanjiva.
>
>
> On Sat, Apr 16, 2011 at 9:53 AM, Afkham Azeez  wrote:
>
>> Thanks!
>>
>> sh -c "exec java ..."
>> worked!
>>
>> Earlier the script only had "exec java ..."
>>
>>
>> On Sat, Apr 16, 2011 at 7:15 AM, Sanjiva Weerawarana wrote:
>>
>>> Its good to use exec so that the parent shell process doesn't hang
>>> around. That's common practice for shell scripts which set up a bunch of
>>> stuff and run something else right at the end.
>>>
>>> But that should not be a problem as the process exit status should be
>>> that of the exec'ed command IIRC (new command is run in the same process).
>>>
>>> Here's a small test:
>>>
>>> $ cat /tmp/foo.sh
>>> #!/bin/sh
>>>
>>> exit 79
>>> $ sh -c "exec /tmp/foo.sh"
>>> $ echo $?
>>> 79
>>>
>>> Sanjiva.
>>>
>>> On Sat, Apr 16, 2011 at 4:13 AM, Afkham Azeez  wrote:
>>>
 Instead of simply doing; "java ..." we do "exec java ...". Why have we
 used exec here? I'm trying to solve the restart issue using exit codes, and
 when exec is used, the process exit code cannot be captured.

 --
 *Afkham Azeez*
 Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com
 ,
 *
 *
 *Member; Apache Software Foundation; 
 **http://www.apache.org/*
 *
 email: **az...@wso2.com* * cell: +94 77 3320919
 blog: **http://blog.afkham.org* *
 twitter: 
 **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


>>>
>>>
>>> --
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>>> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 |
>>> +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> *
>> *
>> *Member; Apache Software Foundation; 
>> **http://www.apache.org/*
>> *
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
>



-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*
*
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **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

Re: [Carbon-dev] Why do we use exec in wso2server.sh?

[Afkham Azeez]

This is what I'm doing in the wso2server.sh. When I restart, I issue a
System.exit(121) command. So the shel will spawn a new Java process once the
current one exits. This can be done on Windows too with the ERRORLEVEL
variable. So, we are relying on the original process which spawned the java
process to spawn a new instance, instead of the dying java process spawning
a new java process just before it dies. That solution is not working on
certain Windows environments. The exit code based approach is guaranteed to
work since we are handing back the control to the original shell that
spawned the java process.

Here is the relevant code segment in wso2server.sh

START_EXIT_STATUS=121;
status=$START_EXIT_STATUS;

while [ "$status" = "$START_EXIT_STATUS" ]
do
sh -c "exec "$JAVACMD" \
-Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
-Xms256m -Xmx512m -XX:MaxPermSize=128m \
$JAVA_OPTS \
-Dimpl.prefix=Carbon \
-Dcom.sun.management.jmxremote \
-classpath "$CARBON_CLASSPATH" \
-Djava.endorsed.dirs="$CARBON_HOME/lib/endorsed":"$JAVA_HOME/jre/lib/endorsed":"$JAVA_HOME/lib/endorsed"
\
-Djava.io.tmpdir="$CARBON_HOME/tmp" \
-Dwso2.server.standalone=true \
-Dcarbon.registry.root=/ \
-Dcarbon.xbootclasspath="$CARBON_XBOOTCLASSPATH" \
-Djava.command="$JAVACMD" \
-Dcarbon.home="$CARBON_HOME" \
-Dwso2.transports.xml="$CARBON_HOME/repository/conf/mgt-transports.xml" \
-Djava.util.logging.config.file="$CARBON_HOME/lib/log4j.properties" \
-Dcarbon.config.dir.path="$CARBON_HOME/repository/conf" \
-Dcomponents.repo="$CARBON_HOME/repository/components/plugins" \
-Dcom.atomikos.icatch.file="$CARBON_HOME/lib/transactions.properties" \
-Dcom.atomikos.icatch.hide_init_file_path=true \
org.wso2.carbon.bootstrap.Bootstrap $*"

status=$?

done

On Sat, Apr 16, 2011 at 10:41 AM, Afkham Azeez  wrote:

> If you do;
>
> $ exec ./foo.sh
>
> You will simply see the following line;
> [Process completed]
>
> and the control does not return to the current shell.
>
>
> On Sat, Apr 16, 2011 at 10:21 AM, Sanjiva Weerawarana wrote:
>
>> No saying "sh -c .." means you're creating a new shell and then exec'ng in
>> there. In that case you might as well just say "java .." (without the exec
>> at all).
>>
>> Doesn't having "exec java" at the end give the return code of the java
>> command to the calling shell? That's what's spsed to happen.
>>
>> Sanjiva.
>>
>>
>> On Sat, Apr 16, 2011 at 9:53 AM, Afkham Azeez  wrote:
>>
>>> Thanks!
>>>
>>> sh -c "exec java ..."
>>> worked!
>>>
>>> Earlier the script only had "exec java ..."
>>>
>>>
>>> On Sat, Apr 16, 2011 at 7:15 AM, Sanjiva Weerawarana 
>>> wrote:
>>>
 Its good to use exec so that the parent shell process doesn't hang
 around. That's common practice for shell scripts which set up a bunch of
 stuff and run something else right at the end.

 But that should not be a problem as the process exit status should be
 that of the exec'ed command IIRC (new command is run in the same process).

 Here's a small test:

 $ cat /tmp/foo.sh
 #!/bin/sh

 exit 79
 $ sh -c "exec /tmp/foo.sh"
 $ echo $?
 79

 Sanjiva.

 On Sat, Apr 16, 2011 at 4:13 AM, Afkham Azeez  wrote:

> Instead of simply doing; "java ..." we do "exec java ...". Why have we
> used exec here? I'm trying to solve the restart issue using exit codes, 
> and
> when exec is used, the process exit code cannot be captured.
>
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.;
> http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; 
> **http://www.apache.org/*
> *
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: 
> **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
>
>


 --
 Sanjiva Weerawarana, Ph.D.
 Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
 email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880| +1
 650 265 8311
 blog: http://sanjiva.weerawarana.org/

 Lean . Enterprise . Middleware

>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com
>>> ,
>>> *
>>> *
>>> *Member; Apache Software Foundation; 
>>> **http://www.apache.org/*
>>> *
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: **http://twitter.com/afkham_azeez*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>

Re: [Carbon-dev] Why do we use exec in wso2server.sh?

[Afkham Azeez]

This solution is working on Windows as well! Here is the relevant change to
the wso2server.bat

:runJava
"%JAVA_HOME%\bin\java" -Xbootclasspath/a:%CARBON_XBOOTCLASSPATH% -Xms256m
-Xmx512m -XX:MaxPermSize=128m -Dimpl.prefix=Carbon
-Dcom.sun.management.jmxremote -classpath %CARBON_CLASSPATH% %JAVA_OPTS%
-Djava.endorsed.dirs=%JAVA_ENDORSED% -Dcarbon.registry.root=/
-Dcarbon.home="%CARBON_HOME%" -Dwso2.server.standalone=true
-Djava.command="%JAVA_HOME%\bin\java" -Djava.opts="%JAVA_OPTS%"
-Dcarbon.xbootclasspath="%CARBON_XBOOTCLASSPATH%"
-Djava.io.tmpdir="%CARBON_HOME%\tmp"
-Dwso2.carbon.xml=%CARBON_HOME%\repository\conf\carbon.xml
-Dwso2.registry.xml="%CARBON_HOME%\repository\conf\registry.xml"
-Dwso2.user.mgt.xml="%CARBON_HOME%\repository\conf\user-mgt.xml"
-Dwso2.transports.xml="%CARBON_HOME%\repository\conf\mgt-transports.xml"
-Djava.util.logging.config.file="%CARBON_HOME%\lib\log4j.properties"
-Dcarbon.config.dir.path="%CARBON_HOME%\repository\conf"
-Dcarbon.logs.path="%CARBON_HOME%\repository\logs"
-Dcomponents.repo="%CARBON_HOME%\repository\components"
-Dcom.atomikos.icatch.file="%CARBON_HOME%\lib\transactions.properties"
-Dcom.atomikos.icatch.hide_init_file_path="true"
-Dcarbon.classpath=%CARBON_CLASSPATH% org.wso2.carbon.bootstrap.Bootstrap
%CMD%
if "%ERRORLEVEL%"=="121" goto runJava

On Sat, Apr 16, 2011 at 10:53 AM, Afkham Azeez  wrote:

> This is what I'm doing in the wso2server.sh. When I restart, I issue a
> System.exit(121) command. So the shel will spawn a new Java process once the
> current one exits. This can be done on Windows too with the ERRORLEVEL
> variable. So, we are relying on the original process which spawned the java
> process to spawn a new instance, instead of the dying java process spawning
> a new java process just before it dies. That solution is not working on
> certain Windows environments. The exit code based approach is guaranteed to
> work since we are handing back the control to the original shell that
> spawned the java process.
>
> Here is the relevant code segment in wso2server.sh
>
> START_EXIT_STATUS=121;
> status=$START_EXIT_STATUS;
>
> while [ "$status" = "$START_EXIT_STATUS" ]
> do
> sh -c "exec "$JAVACMD" \
> -Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
> -Xms256m -Xmx512m -XX:MaxPermSize=128m \
> $JAVA_OPTS \
> -Dimpl.prefix=Carbon \
> -Dcom.sun.management.jmxremote \
> -classpath "$CARBON_CLASSPATH" \
> -Djava.endorsed.dirs="$CARBON_HOME/lib/endorsed":"$JAVA_HOME/jre/lib/endorsed":"$JAVA_HOME/lib/endorsed"
> \
> -Djava.io.tmpdir="$CARBON_HOME/tmp" \
> -Dwso2.server.standalone=true \
> -Dcarbon.registry.root=/ \
> -Dcarbon.xbootclasspath="$CARBON_XBOOTCLASSPATH" \
> -Djava.command="$JAVACMD" \
> -Dcarbon.home="$CARBON_HOME" \
> -Dwso2.transports.xml="$CARBON_HOME/repository/conf/mgt-transports.xml" \
> -Djava.util.logging.config.file="$CARBON_HOME/lib/log4j.properties" \
> -Dcarbon.config.dir.path="$CARBON_HOME/repository/conf" \
> -Dcomponents.repo="$CARBON_HOME/repository/components/plugins" \
> -Dcom.atomikos.icatch.file="$CARBON_HOME/lib/transactions.properties" \
> -Dcom.atomikos.icatch.hide_init_file_path=true \
> org.wso2.carbon.bootstrap.Bootstrap $*"
>
> status=$?
>
> done
>
> On Sat, Apr 16, 2011 at 10:41 AM, Afkham Azeez  wrote:
>
>> If you do;
>>
>> $ exec ./foo.sh
>>
>> You will simply see the following line;
>> [Process completed]
>>
>> and the control does not return to the current shell.
>>
>>
>> On Sat, Apr 16, 2011 at 10:21 AM, Sanjiva Weerawarana 
>> wrote:
>>
>>> No saying "sh -c .." means you're creating a new shell and then exec'ng
>>> in there. In that case you might as well just say "java .." (without the
>>> exec at all).
>>>
>>> Doesn't having "exec java" at the end give the return code of the java
>>> command to the calling shell? That's what's spsed to happen.
>>>
>>> Sanjiva.
>>>
>>>
>>> On Sat, Apr 16, 2011 at 9:53 AM, Afkham Azeez  wrote:
>>>
 Thanks!

 sh -c "exec java ..."
 worked!

 Earlier the script only had "exec java ..."


 On Sat, Apr 16, 2011 at 7:15 AM, Sanjiva Weerawarana 
 wrote:

> Its good to use exec so that the parent shell process doesn't hang
> around. That's common practice for shell scripts which set up a bunch of
> stuff and run something else right at the end.
>
> But that should not be a problem as the process exit status should be
> that of the exec'ed command IIRC (new command is run in the same process).
>
> Here's a small test:
>
> $ cat /tmp/foo.sh
> #!/bin/sh
>
> exit 79
> $ sh -c "exec /tmp/foo.sh"
> $ echo $?
> 79
>
> Sanjiva.
>
> On Sat, Apr 16, 2011 at 4:13 AM, Afkham Azeez  wrote:
>
>> Instead of simply doing; "java ..." we do "exec java ...". Why have we
>> used exec here? I'm trying to solve the restart issue using exit codes, 
>> and
>> when exec is used, the process exit code cannot be captured.
>>
>> --
>> *Afkham Azeez*
>> Senior Soft

Re: [Carbon-dev] Why do we use exec in wso2server.sh?

[Sanjiva Weerawarana]

Ah ok now I understood what you want to do .. yep sounds good.

Only change you could do is instead of saying "sh -c 'exec java ...'" you
could simply say "java ...". Essentially you're creating a shell and
immediately running one command so might as well run that command directly.

Sanjiva.

On Sat, Apr 16, 2011 at 10:53 AM, Afkham Azeez  wrote:

> This is what I'm doing in the wso2server.sh. When I restart, I issue a
> System.exit(121) command. So the shel will spawn a new Java process once the
> current one exits. This can be done on Windows too with the ERRORLEVEL
> variable. So, we are relying on the original process which spawned the java
> process to spawn a new instance, instead of the dying java process spawning
> a new java process just before it dies. That solution is not working on
> certain Windows environments. The exit code based approach is guaranteed to
> work since we are handing back the control to the original shell that
> spawned the java process.
>
> Here is the relevant code segment in wso2server.sh
>
> START_EXIT_STATUS=121;
> status=$START_EXIT_STATUS;
>
> while [ "$status" = "$START_EXIT_STATUS" ]
> do
> sh -c "exec "$JAVACMD" \
> -Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
> -Xms256m -Xmx512m -XX:MaxPermSize=128m \
> $JAVA_OPTS \
> -Dimpl.prefix=Carbon \
> -Dcom.sun.management.jmxremote \
> -classpath "$CARBON_CLASSPATH" \
> -Djava.endorsed.dirs="$CARBON_HOME/lib/endorsed":"$JAVA_HOME/jre/lib/endorsed":"$JAVA_HOME/lib/endorsed"
> \
> -Djava.io.tmpdir="$CARBON_HOME/tmp" \
> -Dwso2.server.standalone=true \
> -Dcarbon.registry.root=/ \
> -Dcarbon.xbootclasspath="$CARBON_XBOOTCLASSPATH" \
> -Djava.command="$JAVACMD" \
> -Dcarbon.home="$CARBON_HOME" \
> -Dwso2.transports.xml="$CARBON_HOME/repository/conf/mgt-transports.xml" \
> -Djava.util.logging.config.file="$CARBON_HOME/lib/log4j.properties" \
> -Dcarbon.config.dir.path="$CARBON_HOME/repository/conf" \
> -Dcomponents.repo="$CARBON_HOME/repository/components/plugins" \
> -Dcom.atomikos.icatch.file="$CARBON_HOME/lib/transactions.properties" \
> -Dcom.atomikos.icatch.hide_init_file_path=true \
> org.wso2.carbon.bootstrap.Bootstrap $*"
>
> status=$?
>
> done
>
> On Sat, Apr 16, 2011 at 10:41 AM, Afkham Azeez  wrote:
>
>> If you do;
>>
>> $ exec ./foo.sh
>>
>> You will simply see the following line;
>> [Process completed]
>>
>> and the control does not return to the current shell.
>>
>>
>> On Sat, Apr 16, 2011 at 10:21 AM, Sanjiva Weerawarana 
>> wrote:
>>
>>> No saying "sh -c .." means you're creating a new shell and then exec'ng
>>> in there. In that case you might as well just say "java .." (without the
>>> exec at all).
>>>
>>> Doesn't having "exec java" at the end give the return code of the java
>>> command to the calling shell? That's what's spsed to happen.
>>>
>>> Sanjiva.
>>>
>>>
>>> On Sat, Apr 16, 2011 at 9:53 AM, Afkham Azeez  wrote:
>>>
 Thanks!

 sh -c "exec java ..."
 worked!

 Earlier the script only had "exec java ..."


 On Sat, Apr 16, 2011 at 7:15 AM, Sanjiva Weerawarana 
 wrote:

> Its good to use exec so that the parent shell process doesn't hang
> around. That's common practice for shell scripts which set up a bunch of
> stuff and run something else right at the end.
>
> But that should not be a problem as the process exit status should be
> that of the exec'ed command IIRC (new command is run in the same process).
>
> Here's a small test:
>
> $ cat /tmp/foo.sh
> #!/bin/sh
>
> exit 79
> $ sh -c "exec /tmp/foo.sh"
> $ echo $?
> 79
>
> Sanjiva.
>
> On Sat, Apr 16, 2011 at 4:13 AM, Afkham Azeez  wrote:
>
>> Instead of simply doing; "java ..." we do "exec java ...". Why have we
>> used exec here? I'm trying to solve the restart issue using exit codes, 
>> and
>> when exec is used, the process exit code cannot be captured.
>>
>> --
>> *Afkham Azeez*
>> Senior Software Architect & Senior Manager; WSO2, Inc.;
>> http://wso2.com,
>> *
>> *
>> *Member; Apache Software Foundation; 
>> **http://www.apache.org/*
>> *
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: 
>> **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
>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880| +1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean

[Carbon-dev] Java process restarting

[Afkham Azeez]

//System.exit(9123456);
/*StringBuilder cmd = new StringBuilder();

 
cmd.append(System.getProperty("java.home")).append(File.separator).append("bin").
append(File.separator).append("java ");
for (String jvmArg :
ManagementFactory.getRuntimeMXBean().getInputArguments()) {
cmd.append(jvmArg).append(" ");
}
cmd.append("-cp
").append(ManagementFactory.getRuntimeMXBean().getClassPath()).append(" ");
cmd.append("org.wso2.carbon.bootstrap.Bootstrap").append(" ");
String[] args = (String[])
System.getProperties().get("carbon.args");
if (args != null) {
for (String arg : args) {
cmd.append(arg).append(" ");
}
}
try {
//Runtime.getRuntime().exec(cmd.toString());
final ProcessBuilder builder = new
ProcessBuilder(cmd.toString());
builder.start();
System.out.println("Starting a new Carbon instance. Current
instance will be shutdown");
System.out.println("Halting JVM");
System.exit(0);
} catch (IOException e) {
e.printStackTrace();
}*/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev