| <html><head> |
| <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> |
| <title>Virgo Tools Guide</title><link rel="stylesheet" href="css/stylesheet.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><!--Begin Google Analytics code--><script type="text/javascript"> |
| var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www."); |
| document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E")); |
| </script><script type="text/javascript"> |
| var pageTracker = _gat._getTracker("UA-2728886-3"); |
| pageTracker._setDomainName("none"); |
| pageTracker._setAllowLinker(true); |
| pageTracker._trackPageview(); |
| </script><!--End Google Analytics code--></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="d0e1"></a>Virgo Tools Guide</h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Ramnivas</span> <span class="surname">Laddad</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Colin</span> <span class="surname">Yates</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Sam</span> <span class="surname">Brannen</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Rob</span> <span class="surname">Harrop</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Christian</span> <span class="surname">Dupuis</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Andy</span> <span class="surname">Wilkinson</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Glyn</span> <span class="surname">Normington</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Steve</span> <span class="surname">Powell</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Christopher</span> <span class="surname">Frost</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Miles</span> <span class="surname">Parker</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Leo</span> <span class="surname">Dos Santos</span></h3></div><div class="author"><h3 class="author"><span class="firstname">GianMaria</span> <span class="surname">Romanato</span></h3></div></div></div><div><div class="mediaobject" align="right"><img src="images/virgo-logo-small.png" align="right"></div></div><div><span class="productname">Virgo<br></span></div><div><p class="releaseinfo">3.7.0.BUILD-20161031211612</p></div></div><div><div><div class="legalnotice"><a name="d0e77"></a><p>Copyright © 2012 VMware Inc.</p><p>Copyright © 2016 GianMaria Romanato</p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#introduction">1. Tooling</a></span></dt><dt><span class="chapter"><a href="#What.27s_New">2. What's New</a></span></dt><dd><dl><dt><span class="section"><a href="#1.5.0_Release">2.1. 1.5.0 Release</a></span></dt><dt><span class="section"><a href="#1.0.0_Release">2.2. 1.0.0 Release</a></span></dt><dt><span class="section"><a href="#1.0.0_M4">2.3. 1.0.0 M4</a></span></dt></dl></dd><dt><span class="chapter"><a href="#running">3. Running a Virgo Runtime Environment</a></span></dt><dt><span class="chapter"><a href="#server-perspective-views">4. Server Perspective and Views</a></span></dt><dd><dl><dt><span class="section"><a href="#server-perspective">4.1. Virgo Perspective</a></span></dt><dt><span class="section"><a href="#views">4.2. Views</a></span></dt><dt><span class="section"><a href="#views-projects">4.3. Virgo Server Projects</a></span></dt></dl></dd><dt><span class="chapter"><a href="#server-editor">5. Server Editor</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e455">5.1. Overview Page</a></span></dt><dt><span class="section"><a href="#d0e511">5.2. Repository Page</a></span></dt><dt><span class="section"><a href="#d0e526">5.3. Bundle Overview Page</a></span></dt><dt><span class="section"><a href="#d0e539">5.4. Bundle Dependency Graph Page</a></span></dt><dt><span class="section"><a href="#d0e552">5.5. Server Console Page</a></span></dt></dl></dd><dt><span class="chapter"><a href="#developing">6. Developing OSGi Bundles</a></span></dt><dd><dl><dt><span class="section"><a href="#tooling-developing-resolving-bundle-dependencies">6.1. Resolving Bundle Dependencies</a></span></dt><dt><span class="section"><a href="#tooling-developing-editing-manifest-mf">6.2. Editing the Manifest</a></span></dt></dl></dd><dt><span class="chapter"><a href="#developing_with_PDE">7. Developing OSGi Bundles using Plug-in Development Environment |
| (PDE) |
| </a></span></dt><dd><dl><dt><span class="section"><a href="#pde_dependencies">7.1. Resolving Bundle Dependencies</a></span></dt><dt><span class="section"><a href="#runtime-wizard">7.2. Server Runtime Wizard</a></span></dt><dt><span class="section"><a href="#pde-projects">7.3. PDE Bundle projects</a></span></dt><dt><span class="section"><a href="#resource-publishing">7.4. Publishing</a></span></dt><dt><span class="section"><a href="#pde-migration-actions">7.5. Migration actions</a></span></dt></dl></dd><dt><span class="chapter"><a href="#plans">8. Developing Plans</a></span></dt><dd><dl><dt><span class="section"><a href="#planBenefits">8.1. Benefit of using Plan files</a></span></dt><dt><span class="section"><a href="#planPublishing">8.2. Discovery of Plan files in the workspace</a></span></dt></dl></dd><dt><span class="chapter"><a href="#pars">9. Developing PARs</a></span></dt><dt><span class="chapter"><a href="#deploying">10. Deploying Applications</a></span></dt><dt><span class="chapter"><a href="#d0e1053">11. Installation and Release Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#Features">11.1. Features</a></span></dt><dt><span class="section"><a href="#Installation">11.2. Installation</a></span></dt><dt><span class="section"><a href="#Known_Issues">11.3. Known Issues</a></span></dt><dt><span class="section"><a href="#Maven_plugin">11.4. Maven plugin</a></span></dt><dt><span class="section"><a href="#Importing_Virgo_Projects_into_Eclipse">11.5. Importing Virgo Projects into Eclipse</a></span></dt><dt><span class="section"><a href="#FAQ">11.6. FAQ</a></span></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="introduction"></a>1. Tooling</h2></div></div></div><p>Virgo Tools support the Virgo runtime with tools for managing servers, server runtimes, and bundles. The IDE |
| tools build on top of the Eclipse Web Tools Project (WTP) and collaborate with other Eclipse technologies such as the |
| Eclipse Libra project. |
| </p><p>Among other things, the Virgo Tools support the creation of new OSGi bundle and PAR projects within Eclipse, and |
| the conversion of existing projects into OSGi bundle projects. Projects can then be deployed and debugged on a running |
| Virgo Runtime from within Eclipse. |
| </p><p>Besides its OSGi bundle projects, starting from version 1.5 Virgo Tools support usage of Plug-in Development |
| Environment (Eclipse PDE) for developing projects that can be deployed and debugged on a running Virgo Runtime from within Eclipse. |
| </p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="What.27s_New"></a>2. What's New</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="1.5.0_Release"></a>2.1 1.5.0 Release</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="UI_15"></a>UI</h3></div></div></div><p>Starting from version 1.5 it is possible to develop for the Virgo Runtime |
| using the Eclipse Plug-in Development Environment (PDE). See the Tooling Guide for more information on this new feature. |
| </p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="Wizards"></a>Wizards</h4></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="Server_Runtime_Wizard"></a>Server Runtime Wizard</h5></div></div></div><p>The Server Runtime Wizard can now optionally assist the user in setting up a PDE Target Platform definition whose content reflects the |
| Virgo Runtime repository configuration. |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="PDE_Project_Wizard"></a>PDE Project Wizard</h5></div></div></div><p>A new project wizard allows creating PDE Plug-in projects that are also Virgo Runtime projects and can be deployed on a Virgo Server |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="Plan_Project_Wizard"></a>Plan Project Wizard</h5></div></div></div><p>A new project wizard allows creating Plan projects in the workspace. Plan projects permit to deploy a plan to the Virgo Runtime within Eclipse |
| and can be seen as a possibly more convenient alternative to adding individual bundles to the Virgo Runtime and defining their activation order |
| via the Server Editor. |
| </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="Server_Editor"></a>Server Editor</h4></div></div></div><p>The Server Editor has been improved to:</p><div class="itemizedlist"><ul type="disc"><li><p>provide proper support for PDE Target Platform definitions</p></li><li><p>allow multi-selection in the 'Artefact Deployment Order' section.</p></li></ul></div></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="1.0.0_Release"></a>2.2 1.0.0 Release</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="UI"></a>UI</h3></div></div></div><p>We've added more views and other tools for working with Virgo Runtime instances. See the expanded Tooling |
| Guide for more information on these new features. |
| </p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="Views"></a>Views</h4></div></div></div><p>In addition to the new Repository View, we've added:</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="Properties_View"></a>Properties View</h5></div></div></div><p>The properties view allows you to directly access all of those Virgo Runtime properties that are buried away |
| in one file or another. |
| </p><p> |
| </p><div class="mediaobject"><img src="images/views-properties-list.png"></div><p> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="Logs_View"></a>Logs View</h5></div></div></div><p>The logs view gives you direct access to all of the relevant Virgo logs, no matter where they are located. |
| </p><p> |
| </p><div class="mediaobject"><img src="images/views-properties-list.png"></div><p> |
| </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="Virgo_Server_Projects"></a>Virgo Server Projects</h4></div></div></div><p>To support those new features, Virgo Tooling now maintains a project for each configured Runtime. Because |
| these are Eclipse projects you can use all of the powerful Eclipse IDE tools to explore artifacts installed on the |
| servers. (You shouldn't try to modify these projects directly though.) For example, you can use the JDT Type |
| Hierarchy and Open Type tools. |
| </p><p> |
| </p><div class="mediaobject"><img src="images/views-open-type-dialog.png"></div><p> |
| </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Quality"></a>Quality</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>We've addressed a number of significant bugs for the final release.</p></li><li><p>Clarified UI.</p></li><li><p>Improved documentation.</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="1.0.0_M4"></a>2.3 1.0.0 M4</h2></div></div></div><p>We've made extensive changes throughout Virgo, focusing on quality and migration, but with a few new features |
| as well. |
| </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Improved_Server_Support"></a>Improved Server Support</h3></div></div></div><p>Virgo now supports almost all versions and types of Virgo installs, including older versions of Virgo and |
| Tomcat, Jetty and Kernel installations. Best of all, you can now define servers using a single Server Runtime and |
| the tooling will automatically discover the appropriate server configurations. You can even change server |
| installations and versions for server runtimes without having to maintain any server setttings. |
| </p><p> |
| </p><div class="mediaobject"><img src="images/whats-new-M4-server.png"></div><p> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="UI_2"></a>UI</h3></div></div></div><p>We've provided a number of new features aimed at improving the user experience. We've been giving more |
| transparency and leverage into what's actually happening on the server. Right now, interactions with the server |
| involve frequent shifts back and forth between the Eclipse IDE, the native file system and the command line. Our |
| ultimate goal is to have tools powerful and complete enough that you can work with the server without ever having |
| to move out of Eclipse. |
| </p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="Virgo_Perspective"></a>Virgo Perspective</h4></div></div></div><p>You can now get your own perspective on Virgo. We've organized it to support runtime exploration but it |
| should be usable for general development as well. Please give us feedback on the overall setup; we'll incorporate |
| the feedback in future releases. |
| </p><p> |
| </p><div class="mediaobject"><img src="images/whats-new-M4-perspective.png"></div><p> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="Views_2"></a>Views</h4></div></div></div><p>When we talked to current users of the Spring Source / Virgo tools, one of the things we discovered is that |
| there were a lot of features that they wanted to have us implement that actually already existed, but in many |
| cases were buried somewhere -- in many cases on a page in the server editor. So we're providing some of the |
| information and tools that are provided in the WTP-based Server Editor as stand-alone views and enriching it. The |
| idea is provide better insight into what's happening on the server side. Some of these features involve |
| significant changes to how server resources are treated and we'd appreciate your feedback on how well they work |
| for your usage scenarios. We'll use these changes as a basis for further enhancements. |
| </p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="Outline_View"></a>Outline View</h5></div></div></div><p>As a first take at helping users find what they're looking for, we provided an outline view that gives quick |
| access to server artifacts. |
| </p><p> |
| </p><div class="mediaobject"><img src="images/whats-new-M4-outline-view.png"></div><p> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="Artifacts_View"></a>Artifacts View</h5></div></div></div><p>A new view supports transparent access to runtime artifacts. Currently, you can view bundle jars and |
| libraries, but we'd like to support plans, pars, properties and other artifact types as well. But the real news |
| is what we've built behind this -- Virgo runtimes are now exposed as Eclipse projects, giving you full access to |
| the contents of jars, including classes. You can even use JDT tools like the Type view on Server side jar |
| contents. |
| </p><p> |
| </p><div class="mediaobject"><img src="images/whats-new-M4-artifacts-view.png"></div><p> |
| </p><p>All of the new views are supported through the Eclipse Common Navigator Framework (CNF), which means that |
| the views are highly configurable, and we've provided buttons to allow you to easily toggle on and off artifact |
| types and present the artifacts in a tree or list view so that you can see all installed jars in one place. |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="Servers_View"></a>Servers View</h5></div></div></div><p>And because the views are all supported through CNF, you can easily customize them. For example, currently |
| you can access all of the bundle information from the server view -- but we'll probably disable that by default |
| in the release. In any case, you can set it up anyway you want by adding or removing the content provider. Again |
| please let us know if you think of a way that we can improve the user experience for you. |
| </p><p> |
| </p><div class="mediaobject"><img src="images/whats-new-M4-servers-view.png"></div><p> |
| </p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Documentation_and_Help"></a>Documentation and Help</h3></div></div></div><p>The complete virgo documentation set -- including the Tooling, Programmer and User's Guide as well as the Wiki |
| pages -- is now included as Eclipse Help. |
| </p><p> |
| </p><div class="mediaobject"><img src="images/whats-new-M4-help.png"></div><p> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Installation_Process"></a>Installation Process</h3></div></div></div><p>Virgo Tools can now be installed from a single update site location.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Quality_2"></a>Quality</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Extensive bug fixes and re-factorings.</p></li><li><p>All Remaining Spring Dependencies have been removed.</p></li><li><p>Updated to meet Eclipse branding, packaging build and testing standards.</p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="running"></a>3. Running a Virgo Runtime Environment</h2></div></div></div><p>After installing the Tools from the update site outlined in the previous section, you will be able to configure |
| an instance of the Virgo Runtime inside Eclipse. |
| </p><p> |
| To do so bring up the WTP Servers view (i.e., |
| <span class="guimenu">Window</span> → <span class="guisubmenu">Show View</span> → <span class="guimenuitem">Other</span> → <span class="guimenuitem">Server</span> → <span class="guimenuitem">Servers</span> |
| ). You can now right-click in the view and select " |
| <span class="guimenu">New</span> → <span class="guimenuitem">Server</span> |
| ". This will bring up a "New Server" dialog. Select Virgo Runtime in the "@runtime.category@" category |
| and click " |
| <span class="guibutton">Next</span> |
| ". |
| </p><p> |
| <img src="images/tooling-new-server.png"> |
| </p><p>Within the "New Server Wizard" point to the installation directory of the Virgo Runtime and |
| finish the wizard. (The tools will automatically detect the type of server install, so you can point to a |
| Virgo Server for Apache Tomcat, Virgo Jetty Server, Virgo Kernel or any other supported |
| Virgo Runtime.) |
| </p><p> |
| <img src="images/tooling-new-server-2.png"> |
| </p><p>After finishing the wizard you should see a Virgo Runtime for the relevant server type in the |
| Servers view. |
| </p><p>To start, stop, and debug the created Virgo Runtime instance use the toolbar or the context menu |
| actions of the Servers view. |
| </p><p> |
| <img src="images/tooling-start-server.png"> |
| </p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="server-perspective-views"></a>4. Server Perspective and Views</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="server-perspective"></a>4.1 Virgo Perspective</h2></div></div></div><p> |
| The Virgo perspective provides an environment customized to support configuring and running Virgo Runtime Environment |
| instances, including views for working with Virgo Runtimes. To switch to the Virgo Perspective from |
| your current perspective, select |
| <span class="guimenu">Window</span> → <span class="guisubmenu">Show Perspective</span> → <span class="guimenuitem">Other...</span> |
| And select "Virgo". |
| </p><p> |
| <img src="images/virgo-perspective.png"> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="views"></a>4.2 Views</h2></div></div></div><p> |
| You can explore the contents of installed servers using the Virgo Server Views. These views are designed to help you |
| get to resources on the server without having to switch to the native file system, and integrate those resources with |
| other Eclipse IDE tools. (You can also use the Virgo views from within other perspectives, of course. Select |
| <span class="guimenu">Window</span> → <span class="guisubmenu">Show View</span> → <span class="guimenuitem">Other...</span> |
| and then open the "Virgo" folder to display them.) |
| </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="views-respository"></a>Repository View</h3></div></div></div><p>The Virgo Repository view allows you to work directly with the contents of installed bundles and libraries on |
| Virgo Runtime instances. |
| </p><p> |
| <img src="images/views-repository.png"> |
| </p><p>To view resources, select a repository in the Servers View. You can customize what and how they are displayed |
| using the view toolbar buttons. |
| </p><p>You can select multiple respositories as well, allowing you to easily navigate and compare resources on |
| multiple servers. You can double-click on items, open them, and even explore class hierchies and other Eclipse |
| features by right clicking on the repository resources. |
| </p><p> |
| <span class="emphasis"><em>Hint:</em></span> |
| In the example below we have selected the Flat Layout and can see that javax.ejb library is present in one |
| Virgo Runtime, but not the other. |
| </p><p> |
| <img src="images/views-repository-example.png"> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="views-properties"></a>Properties View</h3></div></div></div><p>The Virgo Properties view allows you to inspect the properties of Virgo Runtime instances. Rather then digging |
| through files on the server instance to find the parameters you need to adjust, simply select the server(s) you want |
| to find parameters for, and a list of properties files will be displayed in the editor. To open a file in the |
| appropriate Eclipse editor, just double-click on it. Or open a tree node and double-click on a specific property and |
| the property value will be highlighted for editing. |
| </p><p> |
| <img src="images/views-properties-tree.png"> |
| </p><p> |
| <span class="emphasis"><em>Hint:</em></span> |
| Not sure where a given property is even located? You can easily see all properties within a given |
| Virgo Runtime |
| across all properties files, sorted by name. Click the "List" button in the view |
| toolbar. You can even see properties across runtime instances by selecting multiple servers in the Server View. |
| </p><p> |
| <img src="images/views-properties-list.png"> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="views-logs"></a>Logs View</h3></div></div></div><p>The Virgo Logs view supports easy access to runtime log files. As with the other views, just select the |
| Virgo Runtime instance(s) you are interested in. Then double-click to open the relevant log file. |
| </p><p> |
| <img src="images/views-logs.png"> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="views-console"></a>Console View</h3></div></div></div><p>The Console view is the same view that is used in the Java and other perspectives. It displays the console |
| activity for the last server instance you launched, assuming that you haven't launched another console hosted |
| process in the mean-time. (This view is not connected to the Server View -- if you want to examine consoles for |
| differnt running servers, click the "Down Triangle" icon in the view toolbar and select the appropriate console.) |
| </p><p> |
| <img src="images/views-logs.png"> |
| </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="views-projects"></a>4.3 Virgo Server Projects</h2></div></div></div><p>To support all of the view features, projects are created within your workspace. These are managed automatically |
| and shouldn't be modified, deleted or renamed. But you can explore these artifacts directly from the project and |
| package explorers and with other Eclipse tools. |
| </p><p> |
| <span class="emphasis"><em>Hint:</em></span> |
| For example, you can find out what classes are available on Virgo Servers using the Type and Resource search |
| dialogs. Just select |
| <span class="guimenu">Navigate</span> |
| and enter a search pattern. |
| </p><p> |
| <img src="images/views-open-type-dialog.png"> |
| </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="server-editor"></a>5. Server Editor</h2></div></div></div><p>After successful configuration of an instance of the Virgo Runtime Environment in Eclipse you can use the server |
| editor to configure and explore many different aspects of the Virgo Runtime instance. To open a server editor double-click |
| a Virgo Runtime instance in the Servers view. |
| </p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e455"></a>5.1 Overview Page</h2></div></div></div><p>The server overview page is the first page of the editor. Please note that opening of the Editor may take a few |
| seconds as the contents of the local repository needs to be indexed before opening. |
| </p><p> |
| <img src="images/editor-overview-page.png"> |
| </p><p> |
| The overview page contains several sections. Some of them are inherited by the Web Tools Platform while other |
| are contributed specifically by the Virgo Tools. |
| </p><div class="itemizedlist"><ul type="disc"><li>The <span class="emphasis"><em>Target Platform</em></span> section has been introduced in release 1.5 and provides shortcuts |
| for editing or reloading the PDE Target Platform associated to the current Virgo Runtime Environment. |
| </li><li>The <span class="emphasis"><em>Redeploy Behavior</em></span> section allows the user to specify files that should be copied |
| into the server without redeploying the bundle. This is typically used to speed up publishing operations for static files. |
| </li><li>The <span class="emphasis"><em>Publishing</em></span> section allows the user to select when changed resources should be published |
| to the running server. |
| </li><li>The <span class="emphasis"><em>Timeouts</em></span> section allows the user to configure the server startup and shutdown timeout. |
| </li><li>The <span class="emphasis"><em>Deployer Control</em></span> section allows the user to configure the parameters of the JMX communication |
| between the Virgo Tools and the Virgo Runtime Environment. |
| </li><li>The <span class="emphasis"><em>Artefact Deployment Order</em></span> section allows the user to configure the activation order of the artefacts |
| deployed into the Virgo Runtime Environment. Multi-selection is supported. |
| </li><li>The <span class="emphasis"><em>Server Startup Configuration</em></span> section allows the user to configure statup parameters of |
| the Virgo Runtime Environment. The <span class="emphasis"><em>-clean</em></span> options if checked forces the cleaning of the Virgo Runtime Environment |
| temporary folders at every startup. |
| </li></ul></div><p> |
| </p><p> |
| See the |
| <span class="emphasis"><em>Web Tools Platform Guide</em></span> |
| for more information on the other configuration sections. |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e511"></a>5.2 Repository Page</h2></div></div></div><p>The Repository Browser allows you to see what bundles and libraries are available on the @product.instance and |
| to very easily install bundles and libraries from the remote Enterprise Bundle Repository. To view resources |
| installed on the Server select the "Repository" tab in the server editor. |
| </p><p> |
| <img src="images/editor-repository-page.png"> |
| </p><p>The left section of the Repository Browser allows the user to run searches against the SpringSource Enterprise Bundle Repository and displays |
| matching results. The search can take parts of bundle symbolic names, class or package names and allows wildcards |
| such as ‘?’ and ‘*’. By selecting the checkbox left to a matching bundle and/or library and |
| clicking the "Download" button it is very easy to install new bundles in the Virgo Runtime. For your |
| convenience JARs containing the bundle source code can be automatically downloaded as well. |
| </p><p>Clicking the "Download" button will trigger an Eclipse background job that will download the selected repository |
| artifacts and -- if desired -- the source JARs one after another. |
| </p><p>The section on the right displays the bundles and libraries that exist on the server. Bundles with available |
| sources are visually marked. You can very easily download missing source JARs by using the "Install Sources" button. |
| Note that these bundles may or may not be actually "installed" on the Virgo Runtime in the sense that |
| they are known to it -- they may simply exist in the respective directories. |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e526"></a>5.3 Bundle Overview Page</h2></div></div></div><p>To view and control resources actually installed on the Server select the "Bundle Overview" tab in the server |
| editor. |
| </p><p> |
| <img src="images/editor-bundle-overview-page.png"> |
| </p><p>Here you can start, stop, refresh and update bundles, as well as view detailed information about the bundle. |
| Note that information about running bundles cannot be displayed unless the server is actually running. You can |
| refresh the list of bundles by selecting the refresh button in the upper-right-hand corner of the "Bundle Status" |
| section. |
| </p><p>Click the "Show dependency graph for bundle" link to bring up the Bundle Dependency Graph page focused on the |
| selected bundle. See the next section. |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e539"></a>5.4 Bundle Dependency Graph Page</h2></div></div></div><p>The "Bundle Dependency Graph" tab takes you to a page where you can visualize the complex relationships between |
| bundles. |
| </p><p> |
| <img src="images/editor-graph-page.png"> |
| </p><p>You can view package or services relationships by selecting the relevant radio button in the "Configuration" |
| section. The "Incoming" and "Outgoing" controls define how many levels of dependencies are shown. For example, if you |
| select a value of 2 for Incoming, the graph will who items that the selected bundle(s) are dependent on as well as |
| the bundles that those bundles are then dependent on. |
| </p><p>Use the search text area in the editor header to select the source bundles for the graph. Wild cards are |
| supported. Click the refresh button to update the bundle graph. |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e552"></a>5.5 Server Console Page</h2></div></div></div><p>The "Server Console" tab takes you to an interactive console for exploring and managing the state of a running |
| server. (This console is different from the "Console View", which displays the log output of running server |
| instances.) Enter text in the "Command" text area and click the "Execute" button or press RETURN to execute the |
| command. |
| </p><p> |
| <img src="images/editor-console-page.png"> |
| </p><p> |
| For a list of available commands and how to use them, see the |
| <span class="emphasis"><em>Virgo Shell Command Reference</em></span> |
| sub-section of the |
| <span class="emphasis"><em>Equinox Console</em></span> |
| section in the Virgo |
| <span class="emphasis"><em>User Guide</em></span> |
| </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="developing"></a>6. Developing OSGi Bundles</h2></div></div></div><p>The Tools provide functionality that makes developing OSGi bundles, especially the editing of MANIFEST.MF files, |
| easier. |
| </p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tooling-developing-resolving-bundle-dependencies"></a>6.1 Resolving Bundle Dependencies</h2></div></div></div><p> |
| While working with OSGi bundles, one of the most interesting and challenging aspects is defining the package, bundle, |
| and library imports in the manifest and then keeping this in sync with your compile classpath either in Ant and Maven |
| or Eclipse. In most cases you would typically be required to manually set up the Eclipse classpath. Ultimately, the |
| Eclipse compile classpath is still different from the bundle runtime classpath, as normally an entire JAR file is |
| being made available on the Eclipse classpath but not necessarily at runtime due to the explicit visibility rules |
| defined in |
| <code class="code">Import-Package</code> |
| headers. |
| </p><p> |
| The Tools address this problem by providing an Eclipse classpath container that uses an |
| Virgo Runtime Environment-specific dependency resolution mechanism. This classpath container makes resolved |
| dependencies available on the project’s classpath but allows only access to those package that are imported |
| explicitly (e.g., via |
| <code class="code">Import-Package</code> |
| ) or implicitly by using |
| <code class="code">Import-Library</code> |
| or |
| <code class="code">Import-Bundle</code> |
| . |
| </p><p> To use the automatic dependency resolution, an OSGi bundle or PAR project needs to be targeted to a configured |
| Virgo Runtime Environment instance. This can be done from the project’s preferences by selecting the runtime on |
| the "Targeted Runtimes" preference page. </p><p> |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"> |
| In most scenarios it is sufficient to target the PAR project to a runtime. The nested bundles will then |
| automatically inherit this setting. |
| </td></tr></table></div><p> |
| </p><p> |
| <img src="images/tooling-classpath.png"> |
| </p><p> After targeting the project or PAR you will see a "Bundle Dependencies" classpath container in your Java |
| project. It is now safe to remove any manually configured classpath entries. </p><p> The classpath container will automatically attach Java source code to the classpath entries by looking for |
| source JARs next to the binary JARs in the Virgo Runtime Environment’s repository. You can also manually override |
| the source code attachment by using the properties dialog on a single JAR entry. This manual attachment will always |
| override the convention-based attachment. </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tooling-developing-editing-manifest-mf"></a>6.2 Editing the Manifest</h2></div></div></div><p> |
| The Tools provide a Bundle Manifest Editor that assists the developer to create and edit MANIFEST.MF files. The |
| editor understands the Virgo Runtime Environment specific headers like |
| <code class="code">Import-Library</code> |
| and |
| <code class="code">Import-Bundle</code> |
| and provides content assist features while editing source code. Furthermore a Eclipse Form-based UI is also |
| available. |
| </p><p> To open the Bundle Manifest Editor right click a MANIFEST.MF file and select "Bundle Manifest Editor" from the |
| "Open With" menu. </p><p> |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"> |
| Please note that the Virgo Runtime Environment specific manifest headers appear in green color to distinguish them |
| from those headers defined in the OSGi specification. This also makes navigating much easier. |
| </td></tr></table></div><p> |
| </p><p> |
| <img src="images/tooling-manifest-source-editor.png"> |
| </p><p> The content assist proposals in the source tab as well as in the UI-based tabs are resolved from the bundle and |
| library repository of an installed and configured Virgo Runtime Environment. Therefore it is important to target the |
| project or PAR to a specific Virgo Runtime instance to indicate to the tooling which bundle repository |
| to use. </p><p> |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"> |
| If a OSGi bundle project is not targeted to a Virgo Runtime instance, either directory or indirectly |
| via a PAR project’s targetting, the manifest editor will not be able to provide content assist for importing |
| packages, bundles, and libraries. |
| </td></tr></table></div><p> |
| </p><p> |
| <img src="images/tooling-manifest-form-ui-editor.png"> |
| </p><p> The Dependencies tab of the Bundle Manifest Editor enables the user to easily download and install bundles and |
| libraries from the SpringSource Enterprise Bundle Repository by using the "Download..." buttons next to the "Import Bundle" and "Import Library" |
| sections. </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="developing_with_PDE"></a>7. Developing OSGi Bundles using Plug-in Development Environment |
| (PDE) |
| </h2></div></div></div> |
| This chapter assumes that the user is already familiar with the Plug-in Development Environment (PDE). Should this not be the case |
| it is recommended to read first the PDE documentation or one of the many tutorials available online. |
| <div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pde_dependencies"></a>7.1 Resolving Bundle Dependencies</h2></div></div></div><p> |
| Starting from release 1.5.0 the Tools support developing OSGi |
| Bundles using the widely popular Eclipse Plug-in Development |
| Environment (PDE). |
| </p><p> |
| While working with OSGi bundles, one of the most important |
| aspects is defining the required dependencies in the MANIFEST.MF file. |
| When used in conjunction with the PDE, the Virgo Tools address this problem |
| by leveraging on the PDE tooling and in particular on the PDE Target Platform Definition. |
| A Target Platform Definition defines the bundles which your workspace will be built against. |
| </p><p> |
| At runtime however, a PDE Target Platform won't be available and |
| dependency resolution will always occur against the bundle |
| repositories configured for the Virgo Runtime Environment. The Tools |
| try to bridge runtime and development by providing a Server |
| wizard that creates a new PDE Target Platform Definition that |
| matches the Server repository configuration, |
| as defined in |
| <code class="code">org.eclipse.virgo.repository.properties</code> |
| . |
| </p><p> |
| The Virgo Runtime Environment supports watched, external and remote |
| repositories. Watched and external repositories correspond to |
| file system folders, while a remote repository is a remote Virgo |
| instance that can serve its repository content to other Virgo instances |
| for the purpose of dependency resolution. The PDE Target Platform allows its content |
| to be specified only as file system folders or P2 Update sites. As such, when the Tools create a |
| PDE Target Platform Definition from the runtime repository configuration only watched and |
| external repositories are considered. |
| </p><p> |
| Developers should properly setup a local Virgo Runtime Environment so that its bundle repositories |
| contain their application dependencies. Then they should use the Tools to setup a PDE Target Platform |
| so that their workspace projects are built and resolved against the same bundles that will be available |
| at runtime. |
| </p><p> |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"> |
| Note that when using the Tools together with PDE to develop for |
| Virgo it's not possible to use the MANIFEST.MF headers |
| <code class="code">Import-Bundle</code> |
| (not part of the standard OSGi specification but supported by |
| Virgo) |
| and <code class="code">Require-Bundle</code> |
| (part of the standard OSGi specification but not supported by Virgo). |
| Developers will have to declare all of their external dependencies |
| using the |
| <code class="code">Import-Package</code> |
| header only. |
| </td></tr></table></div><p> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="runtime-wizard"></a>7.2 Server Runtime Wizard</h2></div></div></div><p> |
| After installing the Virgo Tools in Eclipse it is possible |
| to create a new Server. |
| A Server can be created from the global <span class="emphasis"><em>New</em></span> dialog, by selecting the |
| <span class="emphasis"><em>Virgo Runtime</em></span> item within the <span class="emphasis"><em>EclipseRT</em></span> category. |
| Alternatively, users can right click over the <span class="emphasis"><em>Servers</em></span> view (easily accessible from |
| the <span class="emphasis"><em>Virgo</em></span> perspective or via <span class="emphasis"><em>New -> Show View -> Other</em></span>) and select <span class="emphasis"><em>New</em></span> to |
| open the same wizard. |
| </p><p> |
| <img src="images/new_server_wiz_1.png"> |
| </p><p> |
| In both cases the Server wizard will appear and will ask the user |
| to select a valid Virgo installation from the local file system. |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"> |
| The first time a Server is created in a new workspace the wizard |
| will create both a Server instance and a Server Runtime. |
| The former corresponds to the Server where the bundles in the workspace will be deployed, |
| the latter corresponds to the runtime definition of which the former will be an instance. |
| </td></tr></table></div><p> |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"> |
| While it's in theory possible to create multiple runtimes and different Server instances |
| associated to them within a single workspace, only one PDE target platform can be active in a workspace at a time. |
| As such when working with the Virgo Tools and PDE it is recommended to use one dedicated Eclipse workspace |
| for one Server runtime and one PDE Target Platform.</td></tr></table></div><p> |
| </p><p> |
| <img src="images/new_server_wiz_2.png"> |
| </p><p> |
| To manage bundle dependencies with PDE make sure to select the check-box in the next page of the wizard: |
| </p><p> |
| <img src="images/new_server_wiz_3.png"> |
| </p><p> |
| The wizard will then parse the <code class="code">org.eclipse.virgo.repository.properties</code> file and show to the |
| user the folders that will be used for setting up the PDE Target Platform definition. |
| In this page it's possible to include additional folders before pressing <span class="emphasis"><em>Finish</em></span>. |
| The folders visible in the picture above are the default content of an unchanged <code class="code">org.eclipse.virgo.repository.properties</code> file plus the server <span class="emphasis"><em>plugins</em></span> folder |
| contained in the server home directory. In reality the <span class="emphasis"><em>plugins</em></span> folder is not a bundle repository and is not listed in the <code class="code">org.eclipse.virgo.repository.properties</code> file. |
| It contains some core components of the Virgo Runtime Environment and gets included in the Target Platform definition |
| because at runtime the contained bundles are made available to the deployed applications for dependencies resolution. |
| </p><p> |
| Additional folders can be added (or removed if already present in the <code class="code">org.eclipse.virgo.repository.properties</code> file). When the <span class="emphasis"><em>Finish</em></span> button |
| is pressed the wizard will create a PDE Target Platform definition and will offer to modify <code class="code">org.eclipse.virgo.repository.properties</code> to reflect any change applied by the user. |
| The newly created Target Platform will be named after the Server runtime (usually "Virgo Runtime" if not changed by the user in the previous wizard page). |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"> |
| Note that while it's safe to include additional folders, users should not remove the default folders unless they really know what they are doing. |
| </td></tr></table></div><p> |
| </p><p> |
| It is possible to double check the content of the newly created PDE Target Platform via the Target Platform preferences page in the |
| Preferences dialog (<span class="emphasis"><em>Window -> Preferences</em></span>): |
| </p><p><img src="images/virgo_target_platform.png"></p><p> |
| The target platform name must match the Server runtime name ("Virgo Runtime" in this example) for the Virgo Tools to be able to correlate |
| the two. |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top">When a PDE Target platform exists for a Virgo Server instance and is named like the corresponding Virgo Runtime, the Server icon |
| is decorated in the <span class="emphasis"><em>Servers</em></span> view with a tiny plug-in icon in the top-left, as depicted below.</td></tr></table></div><p> |
| </p><p><img src="images/servers_and_editor.png"></p><p> |
| As visible in the above picture, the <span class="emphasis"><em>Server editor</em></span>, which is easily accessible by double-clicking over the Virgo Runtime Environment |
| in the <span class="emphasis"><em>Server</em></span> view, provides an new section titled <span class="emphasis"><em>Target Platform</em></span> which allows reloading the |
| content of the Target Platform definition associated to the current server (useful for example when new bundles are added to the repository) |
| and allows editing the content of the current Target Platform definition by recalling the same UI of the last page of the server creation wizard. |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pde-projects"></a>7.3 PDE Bundle projects</h2></div></div></div><p> |
| Now that the Virgo Runtime Environment has been properly setup in the Eclipse workspace, including the corresponding PDE Target Platform definition, |
| it's finally possible to create new projects. |
| </p><p>The Virgo Tools require PDE Plug-in projects to be augmented with some additional features to be usable. As such, in order to create |
| a new project it is necessary to use the dedicated wizard named <span class="emphasis"><em>PDE Bundle project</em></span> located within the <span class="emphasis"><em>Virgo</em></span> |
| category: |
| </p><p><img src="images/pde_bundle_wiz.png"></p><p> |
| The above wizard is the standard PDE <span class="emphasis"><em>Plug-in project</em></span> wizard with some choices disabled or defaulted. |
| In addition to the usual pages it includes an extra page where the user can optionally specify a Web context root. |
| If a context root is specified the new project will be a Web Application bundle (WAB). If the context root is not specified |
| the new project will be a regular OSGi bundle. |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"> |
| The icon of Plug-in projects created for Virgo using the above wizard will be decorated with a tiny <span class="emphasis"><em>EclipseRT globe</em></span> in the top left. |
| </td></tr></table></div><p> |
| </p><p><img src="images/new_pde_bundle.png"></p><p> |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"> |
| Once a <span class="emphasis"><em>PDE Bundle project</em></span> has been created as explained above, the developer can use the standard <span class="emphasis"><em>PDE Plug-in Editor</em></span> |
| and related tooling to work with the newly created project. Please refer to the official PDE documentation for further details.</td></tr></table></div><p> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="resource-publishing"></a>7.4 Publishing</h2></div></div></div><p> |
| The Virgo Server Editor includes a section to select when publishing to the server runtime should take place. |
| The section offers three options: |
| </p><table class="simplelist" border="0" summary="Simple list"><tr><td>immediate publish on resource change</td></tr><tr><td>publish after build</td></tr><tr><td>never publish automatically</td></tr></table><p> |
| Immediate publish means that a change to a file in a bundle project deployed on the Virgo Runtime Environment will be automatically published, triggering in most cases a |
| re-deploy of the bundle project, as soon as the file is saved. |
| Publish after build means that a change to one or more files will be automatically published, triggering in most cases a re-deploy, when the containing project |
| is built, either because workspace auto-build is enabled or because the user requested a workspace or project build. |
| Never publish automatically means that publishing will take place only on user request, via the "Publish" action on the Servers view. |
| </p><p> |
| While automatic publishing reduces the learning curve for beginners, it may also imply longer waits on large workspaces with many bundle projects deployed to a server, because |
| the re-deploy of a project also implies the re-deploy of all dependent projects. |
| On large workspaces it's recommend to turn off auto-publish and to manually publish bundles as needed. In fact, when the server is running in debug mode, |
| if a source file is changed without altering the external "signature" of a class the Java Virtual Machine will be able to push the new byte-code to the server without requiring |
| a re-deploy of the containing bundle and dependencies. In such case the developer can simply save and build and the Java Virtual Machine will perform the hot-code replace. |
| When the source code change affects the "signature" of a class (such as a change in the signature of a method, a change in inheritance, the addition/removal of new properties of methods) |
| the Java Virtual Machine won't be able to perform the hot-code replace and in such case the user can manually invoke the publish action to trigger a re-deploy of the involved bundle. |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pde-migration-actions"></a>7.5 Migration actions</h2></div></div></div><p> |
| Before the Virgo Tools provided support for PDE, some developers where using an unofficial Eclipse plug-in called |
| <a class="ulink" href="http://github.com/giamma/PDE2Virgo" target="_top">PDE2Virgo</a>. |
| The Virgo Tools provide a migration action for migrating PDE2Virgo projects into <span class="emphasis"><em>PDE bundle projects</em></span>. |
| The migration action is accessible via <span class="emphasis"><em>Virgo</em></span> context menu and is labeled <span class="emphasis"><em>Migrate PDE2Virgo project</em></span>. |
| The action is visible when the selection contains only <span class="emphasis"><em>PDE2Virgo</em></span> projects and supports multiple selection. |
| </p><p> |
| A migration action is also provided for PDE users who want to migrate PDE <span class="emphasis"><em>Plug-in</em></span> projects to <span class="emphasis"><em>PDE bundle projects</em></span> to be |
| able to run their projects on a Virgo test environment integrated in Eclipse. |
| The migration action is accessible via <span class="emphasis"><em>Virgo</em></span> context menu and is labeled <span class="emphasis"><em>Migrate Plug-in project</em></span>. |
| The action is visible when the selection contains only <span class="emphasis"><em>Plug-in</em></span> projects and supports multiple selection. |
| </p><p><img src="images/migrate_plugin.png"></p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="plans"></a>8. Developing Plans</h2></div></div></div><p>In Virgo, applications consisting of multiple bundles can be declared using one or more Plans. |
| </p><p> |
| To create a Plan project, right-click in the |
| <span class="emphasis"><em>Package Explorer</em></span> |
| and select |
| <span class="guimenu">New</span> → <span class="guimenuitem">Project…</span> |
| . In the dialog that opens select |
| <span class="guimenu">Virgo</span> → <span class="guimenuitem">Plan Project</span> |
| and press |
| <span class="emphasis"><em>Next</em></span> |
| : |
| </p><div class="mediaobject" align="center"><img src="images/new-plan-project.png" align="middle"></div><p> |
| </p><p> |
| In the New Plan Project dialog, enter a suitable name for the project, set the location to a suitable directory, and press |
| <span class="emphasis"><em>Next</em></span> |
| </p><p> |
| In the next wizard page, you can optionally specify a Plan name to also have a Plan file created for you by the wizard. |
| </p><p> |
| When creating additional Plan files, make sure you place them within the source folder. |
| You can now add Plan files to the Virgo Runtime in Eclipse via the usual add/remove dialog or by means of drag and drop. |
| </p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="planBenefits"></a>8.1 Benefit of using Plan files</h2></div></div></div><p> |
| Plan projects and plan files can be used as an alternative to adding individual bundles to the test environment integrated in Eclipse. |
| The main benefits of using Plan files are: |
| </p><div class="itemizedlist"><ul type="disc"><li><p> |
| Plan files can be more easily shared with coworkers and/or committed to a source code repository |
| </p></li><li><p> |
| It may be more convenient to re-order the content of a Plan file using the Eclipse text editor than editing artefact ordering in the Server Editor |
| </p></li><li><p> |
| Plan files can be composed of other plan files |
| </p></li><li><p> |
| Items in Plan files will be picked either from the workspace or from the configured bundle repositories |
| </p></li><li><p> |
| Using Plan files in the test environment is more representative of the production deployment |
| </p></li></ul></div><p> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="planPublishing"></a>8.2 Discovery of Plan files in the workspace</h2></div></div></div><p> |
| The Virgo Tools create Plan projects as special types of Java projects with an additional Virgo-specific nature. |
| Plan files must be created within the source folder(s) of Plan projects. |
| </p><p> |
| When a Plan file refers to another Plan file, the Virgo Tools will look for the referred Plan file in the same project |
| of the top-level Plan and in all the Plan projects that are directly or indirectly reachable via the project's <span class="emphasis"><em>Java |
| Build Path</em></span>. |
| If more than one Plan with the same name is found in the project's <span class="emphasis"><em>Java Build Path</em></span>, the Virgo Tooling will |
| pick the first found when following the <span class="emphasis"><em>Java Build Path</em></span> defined class-path order. |
| Note that the Plan is identified by the value of the <span class="emphasis"><em>name</em></span> attribute of the <span class="emphasis"><em>plan</em></span> element |
| inside the Plan XML document and not the by the file name. |
| </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pars"></a>9. Developing PARs</h2></div></div></div><p>In Virgo, applications consisting of multiple bundles can be packaged as a PAR. |
| </p><p> |
| To create a PAR, right-click in the |
| <span class="emphasis"><em>Package Explorer</em></span> |
| and select |
| <span class="guimenu">New</span> → <span class="guimenuitem">Project…</span> |
| . In the dialog that opens select |
| <span class="guimenu">EclipseRT</span> → <span class="guimenuitem">PAR Project</span> |
| and press |
| <span class="emphasis"><em>Next</em></span> |
| . |
| </p><p> |
| In the New PAR Project dialog, ensure the |
| <span class="emphasis"><em>Use default location</em></span> |
| option is unchecked, enter a suitable name for the project, set the location to a suitable directory, and press |
| <span class="emphasis"><em>Next</em></span> |
| . For example, the Greenpages sample PAR project would look like this: |
| </p><div class="mediaobject" align="center"><img src="images/create-par-project.png" align="middle"></div><p> |
| </p><p> |
| In the next dialog, some of the PAR properties are pre-populated. Set the Application Name and the Version as |
| appropriate, then ensure that the |
| <span class="emphasis"><em>Target Runtime</em></span> |
| is set to |
| <span class="emphasis"><em>Virgo Web Server (Runtime) ...</em></span> |
| and press |
| <span class="emphasis"><em>Next</em></span> |
| . For example: |
| </p><div class="mediaobject" align="center"><img src="images/par-content.png" align="middle"></div><p> |
| </p><p> |
| In the next dialog, select the bundles so that they are contained in the PAR and press |
| <span class="emphasis"><em>Finish</em></span> |
| . For example: |
| </p><div class="mediaobject" align="center"><img src="images/bundle-references.png" align="middle"></div><p> |
| </p><p>The PAR project is then created. |
| </p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="deploying"></a>10. Deploying Applications</h2></div></div></div><p>Currently the Tools support direct deployment of WTP Dynamic Web Projects, OSGi bundle projects, |
| PDE Bundle projects, PAR projects and Plan files (contained in Plan projects) to the |
| Virgo Runtime from directly within Eclipse. |
| </p><p>To deploy an application to the Virgo Runtime Environment just bring up the context menu on the configured |
| Virgo Runtime runtime in the Servers view and choose "Add or Remove Projects...". In the dialog, select |
| the desired project and add it to the list of "Configured projects". |
| </p><p> |
| <img src="images/tooling-deployed-application.png"> |
| </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"><p> Deploying and undeploying an application from the Virgo Runtime certainly works while the |
| Virgo Runtime Environment is running, but you can also add or remove projects if the Virgo Runtime is not |
| running. </p></td></tr></table></div><p>Once an application is deployed on the Virgo Runtime Environment the tooling support will automatically pick up any |
| change to source files -- for example, Java and XML context files -- and refresh the deployed application on the |
| Virgo Runtime. |
| </p><p>The wait time between a change and the actual refresh can be configured in the configuration editor of the |
| runtime. To bring up that editor, double-click on the configured Virgo Runtime Environment instance in the Servers view. |
| </p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d0e1053"></a>11. Installation and Release Notes</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Features"></a>11.1 Features</h2></div></div></div><p>The Virgo Tooling/IDE concept concerns the whole Virgo tooling (that was available inside SpringSource Tool Suite) being put in a separate project. The tooling supports the following: </p><div class="itemizedlist"><ul type="disc"><li><p>Bundle projects </p></li><li><p>Par projects </p></li><li><p>Plan files/projects </p></li><li><p>Web Bundles </p></li><li><p>New from release 1.5.0: PDE Plug-in projects (created via a dedicated Wizard)</p></li><li><p>Deployment to a Virgo Server in the server view.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Installation"></a>11.2 Installation</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Install_Eclipse"></a>Install Eclipse</h3></div></div></div><p>If you're not installing into an existing Eclipse, you'll need one. </p><p>Eclipse for Java EE developers is recommended.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Install_Virgo"></a>Install Virgo</h3></div></div></div><div class="orderedlist"><ol type="1"><li><p>Select |
| <span class="italic">Help>Install New Software..</span> |
| </p></li><li><p>Enter one of the Virgo update sites below.</p></li><li><p>Select "Virgo Tools" feature and click install.</p></li></ol></div><p><span style="color:#FF0000"><b>Note:</b> Select <i>only</i> Virgo Tooling. This is a composite site, and the other features are <i>not</i> designed to work within the Eclipse IDE.</span></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Update_Sites"></a>Update Sites</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Milestone: <code> |
| <a class="ulink" href="http://download.eclipse.org/virgo/milestone/tooling&lt;/code&gt" target="_top">http://download.eclipse.org/virgo/milestone/tooling&lt;/code&gt</a>; (Recommended) |
| </span></dt><dd></dd><dt><span class="term">Snapshot: <code> |
| <a class="ulink" href="http://download.eclipse.org/virgo/snapshot/tooling&lt;/code&gt" target="_top">http://download.eclipse.org/virgo/snapshot/tooling&lt;/code&gt</a>; (Bleeding Edge) |
| </span></dt><dd></dd></dl></div><p>Many users will also want to install the M2E release at: <code> |
| <a class="ulink" href="http://download.eclipse.org/technology/m2e/releases&lt;/code&gt" target="_top">http://download.eclipse.org/technology/m2e/releases&lt;/code&gt</a>;. (You'll need this to run the greenpages examples.) |
| </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Known_Issues"></a>11.3 Known Issues</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Manifest generation does not seem to be working properly. |
| <a class="ulink" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=379233" target="_top">https://bugs.eclipse.org/bugs/show_bug.cgi?id=379233</a> |
| </p></li><li><p>Other significant bugs still exist. Please see these release train bugs for a current list, and please report any other issues you discover:</p><div class="itemizedlist"><ul type="circle"><li><p>368783: Server management UI bug train |
| <a class="ulink" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=368783" target="_top">https://bugs.eclipse.org/bugs/show_bug.cgi?id=368783</a> |
| </p></li><li><p>368785: Server runtime support bug train |
| <a class="ulink" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=368785" target="_top">https://bugs.eclipse.org/bugs/show_bug.cgi?id=368785</a> |
| </p></li><li><p>368782: Plugin packaging issues bug train |
| <a class="ulink" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=368782" target="_top">https://bugs.eclipse.org/bugs/show_bug.cgi?id=368782</a> |
| </p></li><li><p>You can see all open bugs |
| <a class="ulink" href="https://bugs.eclipse.org/bugs/buglist.cgi?list_id=1289794;query_format=advanced;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;component=tooling;product=Virgo" target="_top">here</a>. |
| </p></li></ul></div></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Maven_plugin"></a>11.4 Maven plugin</h2></div></div></div><p>To support the development of OSGi bundles for Eclipse Virgo with Maven a Maven plugin is available. This plugin is able to start/stop a local Eclipse Virgo instance. Moreover it is possible to deploy/undeploy/refresh bundles via Maven. </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Build"></a>Build</h3></div></div></div><p>In order to use the plugin one has to download the source code from |
| <a class="ulink" href="https://github.com/frieder/virgo-maven-plugin" target="_top">Github</a>&nbsp;and build the binary manually. This can be easily done by executing the following Maven command in the root folder of the plugin where the pom.xml file is located. |
| < pre>mvn clean install</pre> |
| Moreover to generate the documentation just execute the following Maven command (or take the one provided in the repository on Github). |
| < pre>mvn clean&nbsp;plugin:xdoc javadoc:javadoc jxr:jxr site |
| < /pre> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Goals"></a>Goals</h3></div></div></div><p>The plugin provides a set of Maven goals that allow different actions. </p><table><tr> |
| <td rowspan="1" colspan="1"> |
| <span class="bold"><strong>Goal</strong></span> |
| </td> |
| <td rowspan="1" colspan="1"> |
| <span class="bold"><strong>Description</strong></span> |
| </td> |
| </tr><tr> |
| <td rowspan="1" colspan="1"><code>virgo:start</code> </td> |
| <td rowspan="1" colspan="1">Starts a Virgo instance by executing the provided startup script. <br> </td> |
| </tr><tr> |
| <td rowspan="1" colspan="1"><code>virgo:shutdown</code> </td> |
| <td rowspan="1" colspan="1">Stops a running Virgo instance.</td> |
| </tr><tr> |
| <td rowspan="1" colspan="1"><code>virgo:immediateShutdown</code> </td> |
| <td rowspan="1" colspan="1">Stops a running Virgo instance immediately.</td> |
| </tr><tr> |
| <td rowspan="1" colspan="1"><code>virgo:deploy</code> </td> |
| <td rowspan="1" colspan="1">Deploys an OSGi bundle to a running Virgo instance.</td> |
| </tr><tr> |
| <td rowspan="1" colspan="1"><code>virgo:undeploy</code> </td> |
| <td rowspan="1" colspan="1">Undeploys an OSGi bundle from a running Virgo instance.</td> |
| </tr><tr> |
| <td rowspan="1" colspan="1"><code>virgo:refresh</code> </td> |
| <td rowspan="1" colspan="1">Refreshs an already installed module on a running Virgo instance.</td> |
| </tr><tr> |
| <td rowspan="1" colspan="1"><code>virgo:bundleRefresh</code> </td> |
| <td rowspan="1" colspan="1">Refreshs an already installed OSGi bundle on a running Virgo instance.</td> |
| </tr></table></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="Simple_example_POM"></a>Simple example POM</h3></div></div></div><p>Once the plugin has been build and installed in the local Maven repository it can be used within a Maven project. Following is a simple example of a pom file that uses the Maven plugin.&nbsp; |
| < pre>&lt;project xmlns=" |
| <a class="ulink" href="http://maven.apache.org/POM/4.0.0&quot" target="_top">http://maven.apache.org/POM/4.0.0&quot</a>; xmlns:xsi=" |
| <a class="ulink" href="http://www.w3.org/2001/XMLSchema-instance&quot" target="_top">http://www.w3.org/2001/XMLSchema-instance&quot</a>; |
| xsi:schemaLocation=" |
| <a class="ulink" href="http://maven.apache.org/POM/4.0.0" target="_top">http://maven.apache.org/POM/4.0.0</a> |
| <a class="ulink" href="http://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&amp;gt" target="_top">http://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&amp;gt</a>; |
| &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt; |
| &lt;groupId&gt;org.example.osgi&lt;/groupId&gt; |
| &lt;artifactId&gt;test-bundle&lt;/artifactId&gt; |
| &lt;version&gt;0.0.1-SNAPSHOT&lt;/version&gt; |
| &lt;packaging&gt;bundle&lt;/packaging&gt; |
| &lt;name&gt;OSGi Test Bundle&lt;/name&gt; |
| &lt;properties&gt; |
| &lt;project.build.sourceEncoding&gt;UTF-8&lt;/project.build.sourceEncoding&gt; |
| &lt;/properties&gt; |
| &lt;build&gt; |
| &lt;plugins&gt; |
| &lt;plugin&gt; |
| &lt;groupId&gt;org.apache.felix&lt;/groupId&gt; |
| &lt;artifactId&gt;maven-bundle-plugin&lt;/artifactId&gt; |
| &lt;version&gt;2.3.6&lt;/version&gt; |
| &lt;extensions&gt;true&lt;/extensions&gt; |
| &lt;configuration&gt; |
| &lt;instructions&gt; |
| &lt;Bundle-SymbolicName&gt;${project.groupId}.${project.artifactId}&lt;/Bundle-SymbolicName&gt; |
| &lt;Bundle-Name&gt;${project.name}&lt;/Bundle-Name&gt; |
| &lt;Bundle-Version&gt;${project.version}&lt;/Bundle-Version&gt; |
| &lt;/instructions&gt; |
| &lt;/configuration&gt; |
| &lt;/plugin&gt; |
| &lt;plugin&gt; |
| &lt;groupId&gt;net.flybyte.virgo&lt;/groupId&gt; |
| &lt;artifactId&gt;virgo-maven-plugin&lt;/artifactId&gt; |
| &lt;version&gt;1.0.0&lt;/version&gt; |
| &lt;configuration&gt; |
| &lt;virgoRoot&gt;C:/Java/virgo-tomcat-server-3.0.2.RELEASE&lt;/virgoRoot&gt; |
| &lt;/configuration&gt; |
| &lt;/plugin&gt; |
| &lt;/plugins&gt; |
| &lt;/build&gt; |
| & lt;/project&gt; |
| < /pre> |
| More examples can be found in the documentation. Following are some exemplary Maven commands. |
| < pre>mvn virgo:start &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;-- will start a Virgo instance |
| mvn clean package virgo:deploy &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;-- will create an artifact and deploy it to Virgo</pre> |
| </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Importing_Virgo_Projects_into_Eclipse"></a>11.5 Importing Virgo Projects into Eclipse</h2></div></div></div><p>See |
| <a class="ulink" href="http://wiki.eclipse.org/Virgo/Committers#Eclipse_Setup" target="_top">Eclipse Setup</a> under the Committers tab. |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="FAQ"></a>11.6 FAQ</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> |
| <span class="bold"><strong>How do I turn on (or turn off) automatic Manifest generation? (Bundlor)</strong></span> |
| </p></li></ul></div><p>Bundlor is not used by default, you must create you own template file and then turn on incremental manifest generation. Right-click your Virgo project, select the Virgo subcategory from the context menu and select Enable (or Disable) Incremental Generation of MANIFEST.MF File. You can also modify this setting from the Overview page of the Bundle Manifest Editor, under the Bundle Actions section.</p><div class="itemizedlist"><ul type="disc"><li><p> |
| <span class="bold"><strong>Sometimes I'd like to automatically update my Manifest without having to turn on the automatic Manifest setting. How can I do this?</strong></span> |
| </p></li></ul></div><p>Right-click your Virgo project, select the Virgo subcategory from the context menu and select Run Generation of MANIFEST.MF File. This command has a keybinding that you may customize through Eclipse's Keys preferences. You can also perform an automatic update of the Manifest from the Overview page of the Bundle Manifest Editor, under the Bundle Actions section.</p><div class="itemizedlist"><ul type="disc"><li><p> |
| <span class="bold"><strong>Automatic Manifest generation doesn't appear to picking up changes to my source files.</strong></span> |
| </p></li></ul></div><p>Sometimes Manifest generation may behave differently depending on whether the tools are configured to scan source folders or to scan output folders. To modify this setting right-click your Virgo project, select properties and select the Virgo -> Manifest Generation subcategory. If Manifest generation isn't working correctly for you, uncheck the "Scan output folders instead of source folders to generate MANIFEST.MF" setting and re-run the Manifest generation. If your Manifest is not being properly generated under either setting, please file a bug.</p><p> |
| <a class="ulink" href="/wiki/image:virgo-manifest-generation.png" target="_top">image:virgo-manifest-generation.png</a> |
| </p><div class="itemizedlist"><ul type="disc"><li><p> |
| <span class="bold"><strong>My Virgo project is validating its dependencies against the wrong Virgo runtime! How do I manage server runtimes for my Virgo projects?</strong></span> |
| </p></li></ul></div><p>If you've deployed your Virgo projects to multiple Virgo runtimes the tools will associate the project with each runtime, but will only validate against one runtime. In order to manage which Virgo runtime your bundle dependencies are validated against, right-click on the project, select Properties and select the Targeted Runtimes category. From this dialog you can give priority to a particular Virgo runtime.</p><p> |
| <a class="ulink" href="/wiki/image:virgo-targeted-runtimes.png" target="_top">image:virgo-targeted-runtimes.png</a> |
| </p><div class="itemizedlist"><ul type="disc"><li><p> |
| <span class="bold"><strong>How do I create a Web Application Bundle?</strong></span> |
| </p></li></ul></div><p>To create a web application bundle choose to create a normal bundle project, but on the Bundle Content panel select the additional property entitled "Web Application Bundle". On the Bundle Properties panel enter a suitable context path for the application as the Web-ContextPath.</p><div class="itemizedlist"><ul type="disc"><li><p> |
| <span class="bold"><strong>How do I export a Web Application Bundle (WAB)? Export -> Bundle Project produces an incorrect product.</strong></span> |
| </p></li></ul></div><p>To export a WAB invoke Export -> Web -> WAR File</p><div class="itemizedlist"><ul type="disc"><li><p> |
| <span class="bold"><strong>Virgo Jetty Server (VJS) does not startup correctly and I see a 503 error when I go to |
| <a class="ulink" href="http://localhost:8080/admin" target="_top">http://localhost:8080/admin</a> |
| </strong></span> |
| </p></li></ul></div><p>This can happen after starting VJS clean because VJS is looking for a directory at $KERNEL_HOME/work/tmp but no tmp directory exists. A workaround is to start VJS from the command line without the -clean command, which will create the tmp directory. VJS can then be used from the tools. This bug and workaround are documented at |
| <a class="ulink" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=384288" target="_top">https://bugs.eclipse.org/bugs/show_bug.cgi?id=384288</a> |
| </p><div class="itemizedlist"><ul type="disc"><li><p> |
| <span class="bold"><strong>Can I get a deeper look into the state of the server from the Virgo Tools?</strong></span> |
| </p></li></ul></div><p>Yes! If you double-click a Virgo server runtime in the Servers view, you'll open up the server editor, with several pages of information. The Repository, Bundle Overview, Bundle Dependency Graph, and Server Console pages all give valuable insight into the state of the server. The Virgo perspective also provides several views into the Virgo Repository, Virgo Properties and Virgo Logs. See the Virgo Tooling Guide for more information.</p><div class="itemizedlist"><ul type="disc"><li><p> |
| <span class="bold"><strong>I want to install Virgo Tools. Should I install all of this neat looking stuff under Virgo Add-ons?</strong></span> |
| </p></li></ul></div><p>We really don't recommend doing so (see |
| <a class="link" href="#Install_Virgo" title="Install Virgo">Install_Virgo</a>). Select only Virgo Tooling and Eclipse will take care of installing anything the tooling relies on. |
| </p><p> |
| <a class="ulink" href="/wiki/Category:Virgo" target="_top">Category:Virgo</a> |
| <a class="ulink" href="/wiki/Category:EclipseRT" target="_top">Category:EclipseRT</a></rev></revisions></page></pages></query></api> |
| </p></div></div></div><!--Begin LoopFuse code--><script src="http://loopfuse.net/webrecorder/js/listen.js" type="text/javascript"></script><script type="text/javascript"> |
| _lf_cid = "LF_48be82fa"; |
| _lf_remora(); |
| </script><!--End LoopFuse code--></body></html> |
