com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.

Introducing Developer Studio

WSO2 Developer Studio is a complete tooling platform where you can easily develop, deploy, test and debug your SOA applications. Developer Studio works in the popular open-source integrated development environment (IDE) Eclipse. By integrating with the award-winning WSO2 Carbon platform, Developer Studio enables you to create, deploy, and manage a variety of artifacts.

Developer Studio allows you to package your artifacts into a Composite Application aRchive (CAR) and deploy it to WSO2 products such as the Application Server, Enterprise Service Bus (ESB), and Business Process Server (BPS).

Each artifact you create has a server role assigned to it, which controls where it is deployed. For example, AXIS 2 services will be deployed to the Application Server only and not to the BPS, whereas a BPEL artifact will be deployed to the BPS only.

Developer Studio has the support for all phases of the application life cycle. During the Development phase, you create different kinds of artifact projects according to your requirement, including web applications, data services, and ESB artifacts such as proxy services. Because Developer Studio is an Eclipse plugin, you have all the capabilities of a Java IDE such as content assist, rich editors and views, and so on. Developer Studio also allows you to define a project representing a complete Composite Application (C-App) spanning multiple products and features. It immensely simplifies the creation of artifacts with graphical editors and management of the links and dependencies between these services.

After you develop the SOA application, Developer Studio makes it easy to deploy and test the application with just a couple of clicks. You can add multiple servers to your Eclipse environment, including local and remote servers, and you can connect to StratosLive. As you test the application, Developer Studio makes it just as easy to remove the application from the server, modify the application, and redeploy it. You can even enable hot deployment on a server so that the application is automatically redeployed whenever you make a change at the artifact level. You can also start servers in debug mode and debug your applications as you deploy them, which is very useful during development, and you can start servers with the OSGi console enabled, allowing you to see the state of the Carbon platform bundles during runtime.

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.