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

Creating Carbon Projects

This page describes how to create Carbon projects. It includes the following sections:

Java Library Project

With Java Library Project, you can refer a jar file or a project in your workspace and make it a bundle which will be available in to bundle classpath during the runtime. To create a Java Library Project, open WSO2 Developer Studio Dashboard and select Java Library Project from Carbon category.

New Server Runtime

Give a name to the project and click Next.

New Server Runtime

There are two ways to create a Java Library Artifact.

  1. From File System
  2. From Workspace

New Server Runtime

With the File Systemoption, you can point to a jar file of the file system which you may use in the when creating your SOA application.

New Server Runtime

With the second option, it will list all the available projects in the workspace and you can select the project you want to create a Java Library dependency.

New Server Runtime

You can add multiple jars and projects for a single Java Library Project. Once you add needed jars and projects, click Finish.

New Server Runtime

Now you will see Library Project has been created in the workspace. You can create a bundle out of that project by exporting it in to a deployable archive. To do that right click on the project and select Export Project as Deployable Archive.

New Server Runtime

You can do the same thing by grouping the created Library Project in to a Carbon Application Project and make a Carbon Application Archive out of it.

Carbon UI Bundle Project

To create a Carbon UI Bundle Project, open WSO2 Developer Studio Dashboard and select Carbon UI Bundle Project from Carbon category.

New Server Runtime

You can create a Carbon UI Bundle Project in two different ways.

  • Create New Carbon UI Bundle
  • Import Carbon UI Bundle From Workspace

New Server Runtime

With New Carbon UI Bundle option, you will create a new bundle project from the scratch. In the wizard page, you will see an entry called Deploy Path with entries to enter other necessary information. Deploy Path is the path where you specify all your resources like jsp files, html files etc. Give the necessary information and click Finish.

New Server Runtime

Now you will see new Carbon UI Bundle Project has been created in the workspace.

New Server Runtime

You will see a folder structure has been created according to the Deploy Path you have specified.

New Server Runtime

With Import Carbon UI Bundle From Workspace option, you can refer already defined Carbon UI Bundle Components in the workspace. With WSO2 Developer Studio you can create Carbon UI Bundle Component as well. This will be a stand-alone Eclipse Plugin Project with customizations relevant to make it a Carbon UI Bundle. This option is available under File -> New -> Other -> Carbon -> Carbon UI Component.

New Server Runtime

This also includes the same data as you entered when creating a Carbon UI Bundle Project. Give necessary information and click Finish.

New Server Runtime 


New Server Runtime

Now you will see a new project has been created in the workspace. These projects will be available when you select the Import Carbon UI Bundle From Workspace option when creating a Carbon UI Bundle Project.

New Server Runtime 

You can add your jsps/js/html files under the folder structure created according to the Deploy Path you have specified.

As you did for all the other projects, you can export the created Carbon UI Bundle Project 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 bundle which you can deploy in to any Carbon Server. At the same time, you can group it with a Carbon Application Project and create the Carbon Application Archive as well.

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