About WSO2 Carbon
WSO2 Carbon is the award-winning, component-based, service oriented platform for the enterprise-grade WSO2 middleware products stack. It is 100% open source and delivered under Apache License 2.0. The WSO2 Carbon platform is lean, high-performant and consists of a collection of OSGi bundles. Â
The WSO2 Carbon core platform hosts a rich set of middleware components encompassing capabilities such as security, clustering, logging, statistics, management and more. These are basic features required by all WSO2 products, which are developed on top of the base platform.
All WSO2 products are a collection of Carbon components. They have been developed simply by plugging various Carbon components which provide different features. The WSO2 Carbon Component Manager provides capability to extend the Carbon base platform by selecting the components which address your unique requirements and installing them with point-and-click simplicity. Therefore, by provisioning this innovative base platform, you can develop your own, lean middleware product which has remarkable flexibility to change as business requirements change.
Known Issues
For a list of known issues in WSO2 Carbon 4.0, refer to the following link in the WSO2 Oxygen Tank:
- WSO2 Carbon 4.0 - Issues
Community Resources
WSO2 is willing to provide you guidance for technical issues or questions regarding the WSO2 Carbon product. You can communicate with the WSO2 Carbon developers and users directly through the following mailing lists:
- Carbon Developer List : dev@wso2.com
- Users List : user@wso2.com
- Carbon Architecture List : architecture@wso2.org
- For details on subscriptions, refer to http://wso2.org/mail
WSO2 encourages you to report issues and enhancement requests for WSO2 Carbon using the publicJIRA available at https://wso2.org/jira/browse/CARBON. You can also track their resolutions and comment on the progress.
Questions regarding WSO2 Carbon can also be raised through http://stackoverflow.com. Ensure that you tag the question with appropriate keywords such as WSO2 and Carbon so that our team can easily find your questions and provide answers.
For tutorials, articles, Webinars and similar resources on WSO2 Carbon, visit the WSO2 Oxygen Tank and search under the Resources menu.
Support Options
WSO2 also offers a variety of development and production support programs, ranging from Web-based support during normal business hours, to premium 24x7 phone support. WSO2 is committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that support leverages the open development methodology and is provided by the very same engineers who build the products. For additional support information please refer to http://wso2.com/support.
Get Involved
WSO2 invites you to contribute by checking out the source from SVN using the following commands. Instructions on Subversion can be found at http://svnbook.red-bean.com.
Anonymous access:
$ svn checkout http://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0 wso2carbon
Developer access:
Committers must checkout the Subversion repository via HTTPS.
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0 wso2carbon
Execute the following command to commit your changes (SVN will prompt you for password).
$ svn commit --username your-username -m "A message"
Access through a Firewall
If you are behind a corporate firewall which is blocking http access to the Subversion repository, you can try the developer connection:
$ svn checkout https://svn.wso2.org/repos/wso2/trunk/carbon carbon
Access through a Proxy
The Subversion client can be configured to access through a proxy.
- "~/.subversion" directory for Linux/Unix
- "%APPDATA%\Subversion" hidden directory for Windows. (Try "echo %APPDATA%")
2) There are comments in the file explaining what to do. If you don't have this file, get the latest Subversion client and run any command. It will create the configuration directory and template files.
Example : Edit the 'servers' file and add something similar to the following:
[global] http-proxy-host = your.proxy.name http-proxy-port = 3128