WSO2 Carbon Studio Release Notes

WSO2 Carbon Studio 1.0.12 Release Notes

29th June 2011

WSO2 Carbon Studio is a fully functioned tooling environment which facilitate you to develop, test and deploy 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.

You can download this distribution from http://wso2.org/downloads/carbon-studio and give it a try.

New Features

  • General
    • Usability Improvements
    • Several bug fixes
  • Application Server Tools
    • Generate WSDL
    • Generate Apache Axis2 Client
    • Generate Apache Axis2 Archive (AAR)
    • Generate Apache Axis2 Java Skeleton

Fixed Issues

  • [TOOLS-642] - Carbon Studio -> Samples -> DataService Number Validator sample not working
  • [TOOLS-690] - Copy the pointed artifact archive to target folder before executing maven plugin
  • [TOOLS-691] - Cannot Create Data Service from wizard without selecting CApp Project
  • [TOOLS-692] - Carbon Studio shipped samples does not include the maven pom file
  • [TOOLS-693] - Registry plugin does not connect to a remote server
  • [TOOLS-695] - Selected CApp project does not get selected in new registry connection dialog
  • [TOOLS-696] - Why use a different name when exporting a CApp in to a CAR?
  • [TOOLS-698] - Sample Stock Quote Proxy Service does not get deployed on ESB by default
  • [TOOLS-699] - Create two catagories as "Services" and "Service" when creating a axis2 artifact and a data service artifact
  • [TOOLS-701] - Non of the samples are having correct server roles defined
  • [TOOLS-702] - All samples should have Apache License header
  • [TOOLS-703] - Data Service Number Validator Sample not working
  • [TOOLS-704] - No need to have src/main/java in Data Service Sample
  • [TOOLS-705] - EmployeeDataService cannot run by default since it's using MySQL, switch to H2
  • [TOOLS-706] - Acme Gadget Sample contains src/main/java structure
  • [TOOLS-708] - No need to have src/main/java in Helloworld workflow Sample
  • [TOOLS-709] - Cannot add Java Library artifacts to CApp project
  • [TOOLS-710] - Bpel Sample in CS does not support Maven project structure
  • [TOOLS-711] - Cannot import local entries from syanpse.xml of file system/registry
  • [TOOLS-716] - "Next>" button is enabled by default in New Proxy Service creation wizard
  • [TOOLS-723] - Array index out of bound error when removing a 3rd party library added in the new library artifact creation wizard
  • [TOOLS-726] - Registry plugin - 'Add users' should be 'Add User'
  • [TOOLS-728] - Don't we have a standard error format for displaying messages?
  • [TOOLS-732] - Error when creating an Axis2 artifact by pointing to a Dynamic web project in the workspace.
  • [TOOLS-737] - When deleting multiple registry resources (after selecting multiple resources) only the last resource selected gets deleted in the Registry Browser
  • [TOOLS-744] - Cannot deploy CApp to Carbon remote server
  • [TOOLS-745] - Resources whose parent is the project cannot be checked-in to registry

Key Features

  • Application Server Tools
    • Create and Edit Apache Axis2 Web Service
    • Generate WSDL
    • Generate Apache Axis2 Client
    • Generate Apache Axis2 Archive (AAR)
    • Generate Apache Axis2 Java Skeleton
    • Web Applications
    • JAX-WS services
    • Create Axis2 RPC Message Receivers classes
  • Enterprise Service Bus Tools
    • Sequences
    • Endpoints
    • Proxy Services
    • Local Entries
    • Create custom mediators
    • Registry Referencing
    • Create sequences and endpoints as registry resources
    • JBoss Smooks tools integration
  • Governance Registry Tools
    • Create and deploy registry resources
    • Create, edit, debug and deploy registry handlers, filters and registry aspects
    • Manage your remote registry instance
    • Creating registry resources through templates
    • 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)
  • 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
    • Allow creating the library artifact as a fragment bundle
    • Adding WSO2 related libraries when developing applications
  • Carbon Studio contribution features
    • 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
  • Apache Maven Support
    • Carbon Archive
    • Sequence
    • Proxy Services
    • Endpoints
    • Local Entries
    • Registry Resources
    • Registry Handlers
    • Registry Filters
    • ESB Custom Mediators
    • 3rd Party Libraries
    • Apache Axis2 Service
    • JAX-WS Services
    • Web Applications
    • Data Services
    • Data Service Validators
    • BPEL Artifact
    • Synapse Configurations
    • Gadget Artifact
    • Carbon UI Bundle
  • 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 Problems

Issues can be reported using the public JIRA available at https://wso2.org/jira/browse/TOOLS

Contact us

WSO2 Tools developers can be contacted via the mailing lists:

For Users: tools-user@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

Support

We 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