Virgo (software)
In this article, we will explore and analyze in depth Virgo (software), a figure/topic/emotion/theme that has captured the attention and curiosity of people of all ages and backgrounds. Virgo (software) is a phenomenon/trend/aspect that has generated great interest and debate in contemporary society, and it is important to understand its impact and relevance in today's world. Throughout these pages, we will examine different aspects and perspectives of Virgo (software), from its origin and evolution to its influence in various areas of daily life. With the help of experts and testimonies, we will try to shed light on this fascinating/fascinating/controversial topic, with the aim of providing a more complete and enriching vision of Virgo (software).
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
&sq=Virgo_(software)&lang=en&file=File:Question_book-new.svg){kind=small}
| Virgo | |
|---|---|
| Original author | SpringSource |
| Developer | Eclipse Foundation |
| Stable release | 3.7.4[1]
/ August 8, 2020 |
| Written in | Java |
| Operating system | Cross-platform |
| Type | Application server |
| License | EPL-1.0 |
| Website | www |
Virgo is an open source, OSGi-based, Java application server. Virgo supports the deployment of OSGi bundles and unmodified Java web applications as well as OSGi-influenced Shared Libraries WARs and Shared Services WARs.[2]
Virgo is based on the Equinox OSGi implementation, part of the Eclipse project. A few different distributions of Virgo exist:[3] Virgo Nano, Virgo Kernel, Virgo Server for Apache Tomcat (embedding the Apache Tomcat servlet container) and Virgo Jetty Server (embedding the Eclipse Jetty servlet container). Virgo Server for Apache Tomcat is the primary distribution for OSGi development.
Virgo uses Spring Framework which is embedded and made available as a run-time dependency to deployed applications. Virgo is licensed using the Eclipse Public License.
Virgo was originally developed as SpringSource dm Server by SpringSource and is currently maintained by the Eclipse Foundation.[4][5] SpringSource is now a division of VMware.
History
The SpringSource dm Server was originally announced as the SpringSource Application Platform on April 30, 2008.[6] Version 1.0 of the SpringSource dm Server was released September 30, 2008.[7] Version 2.0 was released January 12, 2010.[8]
SpringSource donated dm Server to Eclipse as the Virgo project later in 2010.[9]
In 2013 SpringSource contributions to Eclipse Virgo came to an end and the team members got reallocated to different projects.[10] In absence of a lead, the Virgo project was about to be archived[11] until Florian Waibel stepped in as the new project lead.[12]
IDE Tools
Eclipse Virgo is supported by a set of Eclipse plug-ins called Virgo Tools[13] which allow using the Eclipse IDE for the development and testing of OSGi applications against an embedded Virgo test environment. The tools support hot deploy of individual bundles and allow deployment of plan files.[14]
Feature summary
- Web admin console - deploy and manage artifacts, examine diagnostic dumps, and explore bundle wiring, either in a live system or offline following a resolution failure
- Gogo shell - manage Virgo and deployed artifacts using a command line shell accessed via ssh or telnet
- Plans - define the artifacts that compose an application, optionally making the application atomic to tie the artifact lifecycles together, and scoped to isolate the application from other applications
- Provisioning - automatically supply the dependencies of an application including bundles, plans, plan archives (PARs), and configurations, from both local and remote repositories
- Web container - supports vanilla WAR files, with all their dependencies in WEB-INF/lib, and Web Application Bundles, that import their dependencies via OSGi manifest metadata, via the reference implementation of the OSGi Web Container specification, based on embedded Apache Tomcat and configured using the standard Tomcat server.xml
- User region - isolates the kernel from user-installed applications and enables administrators to focus on application artifacts and their dependencies without seeing those of the kernel as well
- Spring – Virgo 3.6.2 packages Spring 3.1.x, Virgo 3.7 packages Spring 4.2.x
- Hot deployment - deploy artifacts to Virgo by copying them into the pickup directory, either in archive or exploded form, as an alternative to deploying via the admin console or shell
- Logging - via embedded LogBack with a rich set of appenders available out of the box
- JMX management, accessed via the admin console, the shell, the Virgo IDE tooling, or directly via a JMX client such as JConsole
References
- ^ Eclipse Virgo projects.eclipse.org
- ^ Virgo Programmer Guide, section 3.1
- ^ Virgo Deliverables
- ^ SpringSource dm Server product page
- ^ Eclipse Virgo home page
- ^ Introducing the SpringSource Application Platform
- ^ SpringSource dm Server 1.0.0 reaches GA
- ^ dm Server 2.0.0 released
- ^ Eclipse Virgo Released
- ^ Mailing list message about lead step down
- ^ Forum post about project archival
- ^ InfoQ interview with Florian Waibel
- ^ Virgo Tools Wiki page
- ^ Virgo Tools documentation