More enterprises are deploying their composite applications and Web services both in the data center and in the cloud. However, too often this requires multiple tools to support different deployment scenarios, adding complexity and redundancy to IT projects. By contrast, the WSO2 Developer Studio integrated development environment (IDE) uniquely enables developers to write an application once and then deploy it on servers, in the cloud, or in a hybrid environment. Today, WSO2 builds on these capabilities with the availability of WSO2 Developer Studio 3.0 and 3.1.

The Eclipse-based WSO2 Developer Studio 3.0 IDE adds significant new functionality to streamline application development and integration using the WSO2 Enterprise Service Bus (WSO2 ESB). These include a WSO2 ESB Graphical Flow composition tool, WSO2 ESB REST API support, and WSO2 ESB Task support. The latest release of WSO2’s IDE also adds improvements to the Registry Resource Editor, and it has enhanced performance over previous versions of WSO2 Developer Studio. With version 3.1, WSO2’s IDE adds support for Juno SR2, the newest release of Eclipse, as well as JAX-RS-based REST code generation using the Web Application Description Language (WADL).

Using WSO2’s IDE to Deploy on Servers and in the Cloud
Version 3.0 builds on WSO2 Developer Studio 2.0, which provides the tools for creating service-oriented architecture (SOA) applications, RESTful services, and composite applications based on the cloud-enabled WSO2 Carbon platform. With WSO2’s IDE, developers can create a Carbon Application (C-App) that includes services running on multiple WSO2 servers—for example WSO2 ESB, WSO2 Governance Registry, and WSO2 Application Server. After it is tested, the C-App then can be deployed into production on servers or in the cloud using a WSO2 Carbon Archive (CAR).

“Using WSO2 Developer Studio to deploy Carbon Archives has become a popular approach among our Global 1000 customers, who are implementing their applications and services across a range of on-premises and cloud deployment models,” said Samisa Abeysinghe, WSO2 vice president of engineering. “With version 3.0, WSO2 Developer Studio enhances the developer experience by adding popular functions of WSO2 ESB into our IDE, facilitating the movement of artifacts across different deployments, and speeding performance.”

New Capabilities Support Development with WSO2 ESB
WSO2 Developer Studio 3.0 adds a number of capabilities that enable developers to take advantage of popular WSO2 ESB functions within the IDE.

The new WSO2 ESB Graphical Flow composition tool allows developers to easily visualize the path of a message from the client to the backend simply by clicking on components of WSO2 ESB and moving them around the canvas. This provides a clear view into whether a message is going through the appropriate mediators and completing the appropriate tasks.

New WSO2 ESB REST API support means that, for the first time, developers deploying ESB artifacts in WSO2 Developer Studio can package REST services automatically within the CAR, rather than having to develop the REST services directly in WSO2 ESB.

New WSO2 ESB Task support lets developers use WSO2 Developer Studio to set up recurring tasks that run, for example, once every hour or day and then package it up in a CAR. There is no longer a need to use the WSO2 ESB management console to set up this functionality.

Nested Architecture Support
WSO2 Developer Studio 3.0 enhances support for a nested architecture with Eclipse. This addresses one of the top architectural issues in Eclipse by enabling developers to create Eclipse projects within another project to provide flexible project structures. Using WSO2’s IDE, users can maintain the same view of how the projects are organized in the file system from Eclipse, as well as the normal flat project structure view supported by Eclipse, irrespective of the project structure in the file system. WSO2 Developer Studio achieves this by creating filters that work with Eclipse, which WSO2 will be contributing back to the Eclipse project.

Registry Resource Editor Enhanced for Easier Migration
The enhanced Registry Resource Editor in WSO2 Developer Studio 3.0 addresses growing customer demand to migrate artifacts across multiple environments. The latest version adds support for media types to simplify the migration process. As a result, developers can see the end points in the system represented by the proper media types, as well as more easily filter out irrelevant media types, in order to complete a clean migration.

WSO2 Developer Studio 3.1
Version 3.1 builds on WSO2 Developer Studio 3.0 by adding two significant capabilities. This release of WSO2’s IDE supports Juno SR2, the latest release of Eclipse, addressing developers’ interest in migrating from the earlier Helios SR2 version of Eclipse. Additionally, WSO2 Developer Studio 3.1 supports popular JAX-RS based REST Web services based on WADL.

On-demand Webinars for WSO2 Developer Studio
Developers who want to learn more can view a series of on-demand webinars, which examine how to use WSO2 Developer Studio to optimize enterprise application development, deployment, testing and debugging; deploy to multiple environments; and rapidly create mediation flows. The three webinars are:
• Introducing WSO2 Developer Studio – Tools for SOA Developers:
• Composite Enterprise Application Development with the WSO2 Developer Studio:
• Improving User Experience with WSO2 Developer Studio Graphical Flow Composition Tool for the WSO2 ESB:

Availability and Support
The latest release of WSO2 Developer Studio is available today both as a standalone Eclipse-based product and as a set of Eclipse plug-ins. Like all WSO2 SOA middleware products, it is a fully open source solution that does not carry any licensing fees. It is released under the Apache License 2.0 and Eclipse Public License. WSO2 offers a range of service and support options for WSO2 Developer Studio, including development support.