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

Creating a Gadget

This page describes how to create a gadget for use with the Gadget Server.

To create a Gadget, open WSO2 Developer Studio Dashboard and select Gadget from Gadget Server category.

There are three ways to create a gadget.

  1. New Gadget
  2. Import Gadget from File System
  3. Import Dashboard Archive

With the New Gadget option, you will get a simple gadget.xml with the specified name. Give necessary information as Project Name, Gadget XML and click Finish.

New Server Runtime 

Once you click Finish, you will see a new project has been created in the workspace and it will contain the Gadget XML with the specified name and a file called gadget-conf.xml which includes metadata for Gadget deployment.

New Server Runtime 

With the Import Gadget Resources from File System option, you can browse a location where you have Gadget configuration files, images and other related resources.

New Server Runtime 

Once you click Finish, you will see that the new project has been created with the given name with imported resources in the workspace.

With the third option, you can browse a Dashboard Archive [DAR] file, and create a new Gadget Project.

New Server Runtime 

Once you click Finish, you will see that the DAR file, you have specified has been extracted and new project has been created in the workspace.

New Server Runtime 

As you did for all the other projects, you can export the created Gadget in to a deployable artifact by right click on the project and select Export Project as Deployable Archive. With this it will create you a Dashboard Archive [DAR] file, which is a bundle that you can deploy in to any WSO2 Gadget Server. At the same time, you can group it with a Carbon Application Project and create the Carbon Application Archive [CAR] and deploy in to the WSO2 Gadget Server.

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