On Tue, Apr 12, 2011 at 8:50 AM, Saminda Wijeratne <samin...@wso2.com>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) > <http://www.apache.org/licenses/LICENSE-2.0.html>. > 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 > > When developing extensions (handlers, filters, aspects, custom mediators etc) to WSO2 Servers, there are 3rd party and WSO2 related libraries we need to add to the classpath. Most commonly used libraries has already been listed for users to add to the classpath. > > - Other usability improvements > - ESB tools > - Ability to specify references of ESB artifacts from a filtered > list of resources in the workspace > > When creating a synapse configuration, you can point already created ESB artifacts in the workspace. > > - Ability to create registry resource references on the fly for ESB > artifacts > > When creating ESB artifacts, you can make it as a registry resource. This is the same functionality as dynamic endpoints and sequences in WSO2 ESB Server. > > - JBoss Smooks tools integration > > JBoss Smooks editor has integrated in order to provide more user-friendly editor to do data mapping and testing the mapping on the fly. With this integration, users can covert XML -> XML, CSV-> CSV, EDI -> XML, CSV -> XML with the help of graphical interface that has been provided. Created Smooks configurations can be used in Smooks mediator. > > - 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<http://wso2.org/project/carbon-studio/1.0.5/docs/cstudio-features.html> > page. Project Resources > > 1. *Home page :* WSO2 Carbon Studio<http://wso2.org/library/carbon-studio> > 2. *JIRA-Issue Tracker :* WSO2 Carbon Studio - JIRA > Issues<https://wso2.org/jira/browse/tools> > > 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 <http://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 <http://wso2.org/> 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 and Regards, Chathuri
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
