← Revision 21 as of 2008-08-15 23:09:51
Size: 7272
Comment:
|
← Revision 22 as of 2008-08-16 00:02:52 →
Size: 9428
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 108: | Line 108: |
In the ''samplebundle'' directory, you may see some new | In the ''samplebundle'' directory, you may see some new files you are not familier with. |
Line 110: | Line 110: |
* Source Code - In Maven projects, source code is managed in two |
* Source Code - In Maven projects, source code is managed in two directories. * ''src/main'' - Main source code directory you are going to write your own plugin code. * ''src/test'' - For unit/integration test cases * Resource Files - If you need to include some resource files (image icons, etc.) you can put them under ''src/resources''. * MANIFEST.MF - Metadata for OSGi bundle. The most important part is the section '''''Export-Package''''' and '''''Import-Package''''' which describes what packages are exported/imported. * osgi.bnd - This is the setting file for [http://felix.apache.org/site/maven-bundle-plugin-bnd.html maven-bundle-plugin]. Instead of editing ''MANIFEST-MF'' directly, we are going to use the plugin to generate manifest file (metadata for OSGi bundle). For now, I'm not going into the detail about how to edit this file. * pom.xml - Setting file for Maven. |
Line 113: | Line 119: |
To run your plugin with Cytoscape 3 core distribution, you need to add all of its bundles to plugin pom.xml file. 1. Assume you have already checked out Cytoscape 3 and run it by '''''pax:provision''''' goal 1. Open '''''CYTOSCAPE3_ROOT/runner/deploy-pom.xml''''' where CYTOSCAPE3_ROOT is the root directory of Cytoscape 3 project 1. Copy entire '''''dependencies''''' section from the xml file 1. Open plugin root pom.xml file and paste the dependency |
|
Line 114: | Line 125: |
=== Part 4: Edit Template Code === |
attachment:pluginProject8.png === Part 4: Run Template Project with Cytoscape === 1. Create new Maven Run target. Base directory is your plugin root (see the screenshot below) attachment:pluginProject9.png 1. Apply and Run. You can see Cytoscape 3 and your new plugin is running together. attachment:pluginProject10.png attachment:pluginProject11.png attachment:pluginProject12.png 1. Quit Cytoscape === Part 5: Edit Template Code === Now you are ready to write your own code. Let's add a very simple code to the template. 1. Open '''''samplebundle > src/main/java > org.cytoscape.sample.internal > ExampleActivator.java''''' 1. Edit the following method and save it |
Line 133: | Line 165: |
=== Part 4: Run Plugin === |
1. Right-click the root dir of the project (in this example, it is ''c3plugin'') and execute '''''Run As > Maven install''''' 1. === Part 6: Debug your Plugin === |
How to Build an OSGi-Based Cytoscape 3 Plugin on Eclipse
Status
Under construction. Need to add section how to use maven archetype for Cytoscape 3: KeiichiroOno DateTime()
Introduction
This tutorial is a step-by-step instruction for creating Cytoscape 3 plugin based on OSGi framework. By following this tutorial, you can create a new plugin for Cytoscape 3.
Background
In an OSGi system, everything is a plugin. This means, Cytoscape 3 running on OSGi framework is a collection of plugins called bundle and developing a plugin for Cytoscape 3 is equivalent to developing OSGi bundles.
The main difference between Cytoscape 2.x plugin and 3.x plugin is that you do not have to implement CytoscapePlugin interface in Cytoscape 3. Instead, you need to build your plugin jar file with metadata for OSGi. However, this process will be handled by Eclipse and other tools and you do not have to create metadata manually.
Requirements
To understand each steps in this document, it is better to understand following before building your plugin:
- Basic Java
- How to build Java project on Eclipse
- OSGi Bundle
- Note: OSGi Bundle = regular jar file + metadata text file.
- OSGi-Dependent API
BundleActivator
Tools
The following tools should be installed on your machine before starting this tutorial:
[http://www.eclipse.org/ Eclipse 3.3/3.4]
[http://maven.apache.org/ Maven] 2.0.9 or later
[http://www.ops4j.org/projects/pax/construct/ Pax-Construct 1.3]
[http://java.sun.com/javase/downloads/index_jdk5.jsp Java SE 5/6]
Eclipse Plugins
[http://m2eclipse.codehaus.org/ m2Eclipse] - Maven integration for Eclipse
[http://subclipse.tigris.org/ Subclipse] - [http://subversion.tigris.org/ Subversion] client for Eclipse
[http://springide.org/blog/ Spring IDE] (Optional)
Goal of This Tutorial
There are lots of ways to organize your plugin project directory, but in this tutorial, for simplicity, we will use the following directory structure:
- Plugin Project Root - The root directory of your plugin project.
- Plugin Bundle Directory - This is the actual directory to store plugin code.
wrappers - Wrapping existing library files as OSGi bundles if they are not available as OSGi bundles
Other directories will be generated automatically. Your workspace will look like the following:
- attachment:pluginProjectTree.png
In the example above, samplePluginA is the name of plugin project and plugin1 is the name of plugin bundle.
Prerequisite
Since this project depends on Cytoscape 3 core, you need to know how to build and run Cytoscape 3 on Eclipse. Please read [:Cytoscape 3.0/Eclipse/CoreDevelopment:this tutorial] first.
Procedure
Part 1: Create New Plugin Project
- Start Eclipse. For simplicity, I recommend to use fresh and empty workspace without any other projects.
Select Run > Run Configurations...
Right click Maven Build and create new configuration
Press Variables... and select workspace_loc as the destination directory for the new plugin project. However, the location is up to you. You can select any directory. attachment:pluginProject1.png
Press Select... and select pax:create-project as the goal
Press Add and set artifactId and groupId. Usually, groupId is based on your organization's URL. This is because once you publish your plugin in the Maven repository, the string groupId+artifactId must be unique to locate your project attachment:pluginProject2.png
Press Apply and Run.
- At this point, there is no new project in your workspace. This is normal since the process above only creates Maven project, not an Eclipse project.
Open File > Import window and select Maven Projects attachment:pluginProject3.png
- Set parameters attachment:pluginProject4.png
Part 2: Create Plugin Bundle
Next, you need to create an actual OSGi bundle of your plugin. You can create multiple bundles for a plugin, but in this tutorial, your plugin consists of one bundle.
Select Run > Run Configurations...
Right click Maven Build and create new configuration
Browse Workspace and select your project root directory
Goal should be pax:create-bundle
Add two parameters for the new plugin. Package will be the root package name of this bundle, and bundleName will be the name of your new plugin. Also, add junit parameter to automatically generate test case template. The value should be the version of JUnit you want to use. attachment:pluginProject5.png
Press Apply and Run
Next, you need to add OSGi project nature to your workspace. Select Run > Run Configurations...
Right click Maven Build and create new configuration
Browse Workspace and select your project root directory
Goal should be pax:eclipse attachment:pluginProject6.png
Press Apply and Run
- Import the generated bundle into your workspace. It is same as part 1. Now your workspace looks like the following: attachment:pluginProject7.png
The samplebundle folder is the actual project you are going to write your plugin.
OSGi Project Directory Structure
In the samplebundle directory, you may see some new files you are not familier with.
- Source Code - In Maven projects, source code is managed in two directories.
src/main - Main source code directory you are going to write your own plugin code.
src/test - For unit/integration test cases
Resource Files - If you need to include some resource files (image icons, etc.) you can put them under src/resources.
MANIFEST.MF - Metadata for OSGi bundle. The most important part is the section Export-Package and Import-Package which describes what packages are exported/imported.
osgi.bnd - This is the setting file for [http://felix.apache.org/site/maven-bundle-plugin-bnd.html maven-bundle-plugin]. Instead of editing MANIFEST-MF directly, we are going to use the plugin to generate manifest file (metadata for OSGi bundle). For now, I'm not going into the detail about how to edit this file.
- pom.xml - Setting file for Maven.
Part 3: Add Cytoscape Application Dependency
To run your plugin with Cytoscape 3 core distribution, you need to add all of its bundles to plugin pom.xml file.
Assume you have already checked out Cytoscape 3 and run it by pax:provision goal
Open CYTOSCAPE3_ROOT/runner/deploy-pom.xml where CYTOSCAPE3_ROOT is the root directory of Cytoscape 3 project
Copy entire dependencies section from the xml file
- Open plugin root pom.xml file and paste the dependency attachment:pluginProject8.png
Part 4: Run Template Project with Cytoscape
- Create new Maven Run target. Base directory is your plugin root (see the screenshot below) attachment:pluginProject9.png
- Apply and Run. You can see Cytoscape 3 and your new plugin is running together. attachment:pluginProject10.png attachment:pluginProject11.png attachment:pluginProject12.png
- Quit Cytoscape
Part 5: Edit Template Code
Now you are ready to write your own code. Let's add a very simple code to the template.
Open samplebundle > src/main/java > org.cytoscape.sample.internal > ExampleActivator.java
- Edit the following method and save it
1 public void start(BundleContext bc) throws Exception {
2 System.out.println("STARTING org.cytoscape.sample");
3
4 Dictionary props = new Properties();
5 // add specific service properties here...
6
7 System.out.println("REGISTER org.cytoscape.sample.ExampleService");
8
9 // Register our example service implementation in the OSGi service
10 // registry
11 bc.registerService(ExampleService.class.getName(),
12 new ExampleServiceImpl(), props);
13
14 JOptionPane.showMessageDialog(null, "Hello Cytoscape 3!",
15 "Plugin Initialized", JOptionPane.INFORMATION_MESSAGE);
16 }
17
Right-click the root dir of the project (in this example, it is c3plugin) and execute Run As > Maven install
Part 6: Debug your Plugin
Use Spring Dynamic Modules for Your Plugin
If you want to use OSGi service mechanism, using Spring Framework is a good alternative to use OSGi-dependent API directly. In this section, you will learn how to create Spring-Powered bundles for your plugins.
Install Spring IDE
There is an Eclipse plugin for editing Spring configuration files. You can use this for your Spring-OSGi Cytoscape plugin project.
Note: although this program is called Spring IDE, it is not an independent application. It is just a regular Eclipse plugin.
You can follow this instruction to install it:
http://springide.org/project/wiki/SpringideInstall
Create Spring-Powered Bundle
=== Setup Spring-DM
(Under construction!)