Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » Statement of direction: OSGi Subsystems spec support
Statement of direction: OSGi Subsystems spec support [message #930423] Tue, 02 October 2012 05:53 Go to next message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
See the Future tab of the wiki for the future direction of Subsystems support. After you've read the rationale, please feel free to comment here.

[Updated on: Tue, 02 October 2012 05:56]

Report message to a moderator

Re: Statement of direction: OSGi Subsystems spec support [message #933798 is a reply to message #930423] Fri, 05 October 2012 06:56 Go to previous messageGo to next message
GianMaria Romanato is currently offline GianMaria Romanato
Messages: 59
Registered: July 2009
Member
Hi,

one of the reasons I like Virgo is that it is lightweight and modular.
When I read support for Java EE API, I am a bit scared that Virgo could become a download of hundreds of megabytes and that the start-up time of the server may increase because of the EJB container and so on (usually EBJ support implies JMS support for Message Driven beans).

Could you elaborate a bit about how you plan to support all those APIs?

Thanks
GianMaria.




Re: Statement of direction: OSGi Subsystems spec support [message #933815 is a reply to message #933798] Fri, 05 October 2012 07:17 Go to previous messageGo to next message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
Some of the other committers know the details of the support for Java EE applications that is going into Virgo 3.6.0, but let me sketch the high-level picture. The important thing to note from a bloat point of view is that this support is only being packaged in the Virgo Nano Web deliverable. Virgo Nano itself will not change much and will be as minimal as ever. Virgo Kernel, Virgo Server for Apache Tomcat, and Virgo Jetty Server are not affected - those deliverables are aimed at thorough-going OSGi applications, with Virgo's custom support for plans, PARS, and scoping to help deal with large numbers of bundles. If this is a bit confusing, please refer to the feature summary matrix for Virgo 3.5.

Virgo Nano Web is being extended in a modular way too to add in components to support various EE technologies such as EJB, but I'll ask someone else to provide a bit more detail on that front.

Oh and I should point out that the EE application support isn't anything to do with OSGi Subsystems support, or lack thereof.

[Updated on: Fri, 05 October 2012 07:18]

Report message to a moderator

Re: Statement of direction: OSGi Subsystems spec support [message #933922 is a reply to message #933815] Fri, 05 October 2012 09:13 Go to previous messageGo to next message
Borislav Kapukaranov is currently offline Borislav Kapukaranov
Messages: 80
Registered: September 2010
Member
Hi,

In addition to what Glyn said I can exmplain a bit more about the EE add-on. I'm saying add-on because it will be a p2 feature hosted on Virgo's p2 repository.
We still haven't decided whether to ship Virgo Nano Web with that add-on preinstalled or not. In any case the add-on can come and go with a few shell commands. So it will be quite modular and if you don't want it you can just uninstall it.

Also this won't provide support for all the APIs included in the JavaEE 6 Full profile, but only for its Web Profile subset. Which means: EJB 3.1 Lite, JPA, CDI, JTA, all the Web APIs(JSP, JSTL, JSF, Servlets, etc.) and a few more.

In terms of footprint and size everything remains quite lean, not as lean as a pure Virgo Nano Web but still good.
The current working version is about 34Mb in size and starts in about 5-7 seconds which is actually leaner than most other OSGi-based servers with similar EE API support.
It is also comparable to the other Virgo Web server offerings.

Best Regards
Bobby
Re: Statement of direction: OSGi Subsystems spec support [message #933976 is a reply to message #933922] Fri, 05 October 2012 10:21 Go to previous messageGo to next message
GianMaria Romanato is currently offline GianMaria Romanato
Messages: 59
Registered: July 2009
Member
Hi Glyn and Borislav,

thank you very much for the insights into Virgo 3.6.
I know p2, and your comments made clear that I will be able to avoid the J2EE stack if I don't need it.

At this point, I am looking forward for the new admin console.
The current console (3.5) is useful for problem determination (for example I sometimes used it to review the wiring), but apart from that I almost never use it, because I am deploying all resources via file system. Will the new console offer new screens to perform administrative tasks or is still mostly focused on inspecting the status of the deployed OSGi bundles?

thanks
GianMaria.




Re: Statement of direction: OSGi Subsystems spec support [message #936732 is a reply to message #933976] Mon, 08 October 2012 05:20 Go to previous message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
The new web admin console replaces the existing web admin console, but adds four functions: supports the Virgo kernel in addition to Virgo Server for Apache Tomcat and Virgo Jetty Server; allows repository browsing and deploying the browsed artefacts; allows bulk deployment of multiple artefacts at once; dumps can now be created and deleted,
Previous Topic:Virgo + ConditionalPermissionAdmin question
Next Topic:Maven repository for Virgo artifacts?
Goto Forum:
  


Current Time: Wed Aug 20 22:31:41 EDT 2014

Powered by FUDForum. Page generated in 0.02264 seconds