Thursday, June 14, 2012

Apache Axis2 integration with Eclipse

Article written by Harshana Eranga Martin on Axis2 Tools support in Developer Studio is now available at [1] and [2].


If you have any comments or questions, please feel free to send them to the Author or the WSO2 User mailing list.

Friday, May 11, 2012

Await for WSO2 Developer Studio 2.0.0 !!!

WSO2 Developer Studio 2.0.0 release is round the corner. We have release the beta backs recently. You can download all the binaries and documentation from here and give it a try.  There you can find two binary distributions as "with dependencies" and "without dependencies". If you download "with dependencies" pack, you can go for an offline installation. Inside "dev-studio-installed-eclipse-dist", you can find WSO2 Developer Studio installed Eclipse distribution which you do not have to install anything. You can just start Eclipse and you have Developer Studio installed.

Following are some of new features introduced with WSO2 Developer Studio 2.0.0

  • More flexible way of artifact creation
  • Can create artifact projects at any location of the workspace. i.e users can define there own folder structure and create projects
  • Each artifact project is a maven project
  • Creation of deployable units for each and every artifact project
  • Carbon application project will act like the distribution for artifact projects
  • Content assist support for data services descriptor files and synapse configurations
  • Carbon offset support
  • JAX-RS support
  • Carbon 4.0.0 based server support
  • Improved Data Services design view
  • Multi module maven support
  • Developer studio dashboard
  • New editors for registry handler information, carbon application project pom editing, registry resource editor
  • Improved wizard pages
  • Tech preview of ESB flow tool

Following are some of the screenshots. Do a try and give us your feedback.

Thursday, April 19, 2012

WSO2 Carbon Studio -> WSO2 Developer Studio

Recently we have renamed WSO2 Carbon Studio as WSO2 Developer Studio due to several reasons. Major reason behind this is, since the tooling platform provides tools for both on premise servers as well to Stratos.

Name Developer Studio gives more breadth meaning compare to Carbon Studio. On the other hand, WSO2 tooling platform is for developers, who build SOA applications on top of WSO2 middle-ware product stack.

Considering all these facts, we felt that the WSO2 Developer Studio is more appealing name for our tooling platform.