Eclipse Community Forums: Virgo » HttpService workaround

Help

Home

Home » Eclipse Projects » Virgo » HttpService workaround (Enablind httpservice in a Virgo Distribution.)

Show: Today's Messages :: Show Polls :: Message Navigator

HttpService workaround [message #660052]

Wed, 16 March 2011 13:13

Carlos Salinas
Messages: 32
Registered: March 2011
Location: Avd. de la Argentina 132,...

Member

HI COMMUNITY,

As i found more than one asking for a HTTPSERVICE in a Virgo Distribution. I would like to share our workaround.

Our reason is, beacuse we are developing a Web Modular Platform using Vaadin as the UI Framework. In a OSGi environment, vaadin main class(in our bundle) is launched by a vaadin library servlet, through a bridge bundle using httpservice. This bridge bundle is a official add-on propose by Vaadin Community for this kind of environment.

Well our solution was to start using Virgo Jetty Server, because there is no httpservice implementation for tomcat (Gemini Web -> Virgo web Server) and also we deployed in Pax Web version 0.8.0. This Last choice was as result that org.eclipse.equinox.http.jetty bundle is only implemented for jetty 5 or 6. Pax Web is for 7.x (The same version packacked in the Virgo Distribution)

We deployed the following bundles in the $SERVER_HOME/repository/usr and edit the initialArtifacts header in org.eclipse.virgo.kernel.userregion.properties file in $SERVER_HOME/config to enable the service in the userregion when the server starts:
pax-web-api.jar
pax-web-jetty.jar
pax-web-runtime.jar
pax-web-spi.jar

If there is any doubt id be glad to help.

Report message to a moderator

Re: HttpService workaround [message #660064 is a reply to message #660052]

Wed, 16 March 2011 13:44

Chris Frost
Messages: 222
Registered: January 2010
Location: Southampton, England

Senior Member

Hi,

There are various options depending on how much support you need. The Jetty distribution doesn't provide a HttpService, it's there to provide an alternative implementation of the OSGi Web Application Container Spec and is by no means as stable or tested as the Tomcat based one as we only recently added the Jetty option.

There is a HttpService for Jetty 7 that can be deployed on top of the Jetty WAB support, you can find it here if you want to play with it. http://repo1.maven.org/maven2/org/eclipse/jetty/osgi/jetty-h ttpservice/ It runs on top of the Jetty 7 Web Application Container.

If you only require a basic HttpService then their is one that comes with Equinox and is very simple to deploy on top of the Virgo Kernel distribution, simply add the servlet api bundle to the usr repository and drop org.eclispe.equinox.http in the pickup directory. This can of course be configured to start with the 'initialArtifacts' property as well. This has the benefit of being much more much more minimal.

Chris.

------------------------------------------------
Chris Frost, Twitter @cgfrost
Springsource, a divison of VMware.

Report message to a moderator

Re: HttpService workaround [message #660071 is a reply to message #660064]

Wed, 16 March 2011 14:00

Carlos Salinas
Messages: 32
Registered: March 2011
Location: Avd. de la Argentina 132,...

Member

Hi Chris,

Thanks for ur answer. I didnt find the implementation for jetty 7 in the equinox server side bundles pages.

Am i right or there is an httpservice implementation for tomcat?

I wouldnt like to start from the Virgo Kernel, because i would lose the webconsole, springframework and spring DM configured.

By the way, i posted two bugs about Virgo Jetty Server about the needness of adapter in the Virgo Tooling an a failure starting either from the shell or Eclipse IDE.

Report message to a moderator

Re: HttpService workaround [message #660167 is a reply to message #660071]

Thu, 17 March 2011 04:17

Glyn Normington
Messages: 1186
Registered: July 2009

Senior Member

Thindtrack Developer wrote on Wed, 16 March 2011 18:00

I wouldnt like to start from the Virgo Kernel, because i would lose the webconsole, springframework and spring DM configured.

For the record, Virgo Kernel provides the Spring framework and Spring DM in the same way that Virgo Tomcat/Jetty Servers do. But you would indeed lose the web admin console (although the kernel provides a vsh subcommand in the Equinox console which gives the most basic admin capabilities).

Report message to a moderator

Re: HttpService workaround [message #660173 is a reply to message #660167]

Thu, 17 March 2011 04:49

Carlos Salinas
Messages: 32
Registered: March 2011
Location: Avd. de la Argentina 132,...

Member

Thanks Glyn for your information. Yes I am using the vsh console.

Is there any httpservice implementation for Tomcat?
I found one for the JonAS server, but i dont know to integrate it in Virgo.

Report message to a moderator

Re: HttpService workaround [message #660187 is a reply to message #660173]

Thu, 17 March 2011 05:44

Glyn Normington
Messages: 1186
Registered: July 2009

Senior Member

Neither Tomcat nor Virgo Tomcat Server (the new name for Virgo Web Server to distinguish it from Virgo Jetty Server) provide a HTTP Service.

The options appear to be using Virgo Jetty Server or deploying the Equinox HTTP Service on Virgo Kernel.

Report message to a moderator

Re: HttpService workaround [message #660201 is a reply to message #660187]

Thu, 17 March 2011 06:37

Chris Frost
Messages: 222
Registered: January 2010
Location: Southampton, England

Senior Member

The Virgo Jetty Server doesn't provide a HttpService either but you can get one with Jetty 7. It is available from Maven Central at the link I provided. The Equinox Bundles are still providing a HttpService based on Jetty 6, I don't know when/if they will provide the Jetty 7 one.

------------------------------------------------
Chris Frost, Twitter @cgfrost
Springsource, a divison of VMware.

Report message to a moderator

Previous Topic:	Split packages in single scope
Next Topic:	Milestone 3.0.0.M03 available

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Jun 19 13:18:58 EDT 2013