Eclipse Community Forums: Virgo » Virgo, Jetty 8 and WebSockets

Help

Home

Home » Eclipse Projects » Virgo » Virgo, Jetty 8 and WebSockets

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

Virgo, Jetty 8 and WebSockets [message #792012]

Mon, 06 February 2012 09:05

Joel Lucuik
Messages: 3
Registered: July 2009

Junior Member

Hi,

Any early releases of virgo with Jetty 8?

Our bundle uses WebSockets which needs Jetty 8.

I am currently attempting merging Jetty 8 manually into Virgo because a co-worker suggested Virgo and Jetty are very loosely coupled, and a move from 7.4 to 8 shouldn't be too hard.

Suggestions?

Schedule on the upgrade to Jetty 8?

Thanks.
Joel

Report message to a moderator

Re: Virgo, Jetty 8 and WebSockets [message #792041 is a reply to message #792012]

Mon, 06 February 2012 09:42

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

Senior Member

Hi,

Jetty 8 will be a part of the Virgo 3.5 release which is scheduled for the Eclipse release train in June. The actual work required for this is actually happening very soon so you can have a play with snapshot builds. I expect the work required to upgrade to Jetty (8.1 actually) to be very straight forward, simply replace the jars using new ones from Maven central and then update the Jetty Web Plan file to point at the new versions, look in repository/ext for the plan file. That should be it but I will be able to tell you more once I've done the actual work here.

FYI, we will be upgrading the 3.0.x line to Jetty 7.6 as well.

Chris.

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

Report message to a moderator

Re: Virgo, Jetty 8 and WebSockets [message #792068 is a reply to message #792041]

Mon, 06 February 2012 10:17

Eduardo Frazão
Messages: 83
Registered: January 2012

Member

Cool. It will be great if Tomcat supports WebSocket as well.
The major problem I belive, is the incomplet specification of this protocol. What a shame. Sad

Report message to a moderator

Re: Virgo, Jetty 8 and WebSockets [message #792261 is a reply to message #792041]

Mon, 06 February 2012 15:12

Joel Lucuik
Messages: 3
Registered: July 2009

Junior Member

Ok i tried that...must be missing something small. It's close.
I see references to 7.4.2.v20110526 in poms, but nowhere else I can find.

* Changed:

<artifact type="bundle" name="org.eclipse.jetty.osgi.boot" version="[7.3, 8)"/>
to
<artifact type="bundle" name="org.eclipse.jetty.osgi.boot" version="[7.3, 8.1)"/>

* copied Jetty 8.1.0 Jars verbatim in .. similar to jetty-ajp-8.1.0.v20120127.jar.

Exception:

[2012-02-06 14:35:52.375] system-artifacts <ME0003I> Dump 'servicea
ility\dump\2012-02-06-14-35-999' generated
[2012-02-06 14:35:52.379] system-artifacts <DE0002E> Installation o
plan 'org.eclipse.virgo.jetty.web' version '3.0.0' failed. java.lang.IllegalAr
umentException: Supplied file 'C:\virgo-jetty-server-3.5.0.M02Original\reposito
y\ext\jetty-osgi-boot-7.4.2.v20110526.jar' must exist
at org.eclipse.virgo.util.common.Assert.isTrue(Assert.java:43)
at org.eclipse.virgo.util.io.ZipUtils.unzipTo(ZipUtils.java:62)
at org.eclipse.virgo.util.io.JarUtils.unpackTo(JarUtils.java:41)
at org.eclipse.virgo.kernel.install.artifact.internal.StandardArtifactS
orage.synchronize(StandardArtifactStorage.java:86)
at org.eclipse.virgo.kernel.install.artifact.internal.StandardArtifactS
orage.synchronize(StandardArtifactStorage.java:59)
at org.eclipse.virgo.kernel.install.artifact.internal.StandardArtifactS
orage.<init>(StandardArtifactStorage.java:54)
at org.eclipse.virgo.kernel.install.artifact.internal.StandardArtifactS
orageFactory.create(StandardArtifactStorageFactory.java:54)
at org.eclipse.virgo.kernel.install.artifact.internal.StandardInstallAr
ifactGraphInclosure.createInstallGraph(StandardInstallArtifactGraphInclosure.ja
a:110)
at org.eclipse.virgo.kernel.deployer.core.internal.PlanResolver.createI
stallArtifactGraph(PlanResolver.java:112)
at org.eclipse.virgo.kernel.deployer.core.internal.PlanResolver.operate
PlanResolver.java:70)
at org.eclipse.virgo.kernel.deployer.core.internal.PlanResolver.access$
(PlanResolver.java:62)
at org.eclipse.virgo.kernel.deployer.core.internal.PlanResolver$1.visit
PlanResolver.java:56)
at org.eclipse.virgo.util.common.ThreadSafeGraphNode.visitInternal(Thre
dSafeGraphNode.java:193)
at org.eclipse.virgo.util.common.ThreadSafeGraphNode.visit(ThreadSafeGr
phNode.java:184)
at org.eclipse.virgo.kernel.deployer.core.internal.PlanResolver.transfo
m(PlanResolver.java:53)
at org.eclipse.virgo.kernel.install.pipeline.stage.transform.internal.T
ansformationStage.doProcessGraph(TransformationStage.java:54)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStag
.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.
oProcessGraph(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipel
ne.doProcessGraph(CompensatingPipeline.java:73)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStag
.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.
oProcessGraph(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStag
.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplication
eployer.driveInstallPipeline(PipelinedApplicationDeployer.java:286)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplication
eployer.doInstall(PipelinedApplicationDeployer.java:165)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplication
eployer.install(PipelinedApplicationDeployer.java:137)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplication
eployer.deploy(PipelinedApplicationDeployer.java:204)
at org.eclipse.virgo.kernel.userregion.internal.InitialArtifactDeployer
ArtifactDeployingRunnable.deployArtifacts(InitialArtifactDeployer.java:156)
at org.eclipse.virgo.kernel.userregion.internal.InitialArtifactDeployer
ArtifactDeployingRunnable.run(InitialArtifactDeployer.java:146)
at java.lang.Thread.run(Thread.java:662)

[2012-02-06 14:35:52.405] system-artifacts <DE0003E> Install failed
for plan 'org.eclipse.virgo.jetty.web' version '3.0.0'.

Report message to a moderator

Re: Virgo, Jetty 8 and WebSockets [message #792281 is a reply to message #792068]

Mon, 06 February 2012 15:45

Violeta Georgieva
Messages: 173
Registered: October 2010

Senior Member

Quote:

Cool. It will be great if Tomcat supports WebSocket as well.

There is already a work in this direction - https://issues.apache.org/bugzilla/show_bug.cgi?id=51181

Once it is available in some Tomcat 7.0.x version, Virgo Tomcat Server can adapt it.

Report message to a moderator

Previous Topic:	Running Virgo with the security manager
Next Topic:	Virgo and STS 2.7.2

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri May 24 13:48:03 EDT 2013