[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] Jetty-9.1.2 - websocket : OSGi packaging issue
|
Jan,
As a workaround, I will embed jsr-356 impl into the webapp, until the availability of the fix.
Thanks,
Yves
-----Message d'origine-----
De : jetty-users-bounces@xxxxxxxxxxx [mailto:jetty-users-bounces@xxxxxxxxxxx] De la part de Jan Bartel
Envoyé : vendredi 21 février 2014 01:23
À : JETTY user mailing list
Objet : Re: [jetty-users] Jetty-9.1.2 - websocket : OSGi packaging issue
Hi Yves,
AFAIK the javax.websocket implementation is optional, so you can run with the jetty websocket impl only. Having said that, if you want to use the javax.websocket impl, have you tried putting those jars inside a bundle webapp you want to deploy (that's the way we've run it with our osgi unit tests)? Again, having said that, it should be feasible to run the javax.websocket impl with those jars in the osgi environment, so I've raised:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=428699
Jan
On 21 February 2014 02:31, MILLON, YVES (YVES) <yves.millon@xxxxxxxxxxxxxxxxxx> wrote:
> Unfortunately the bundle " javax-websocket-client-impl-9.1.2.v20140210.jar"
> exports nothing, while bundle "
> javax-websocket-server-impl-9.1.2.v20140210.jar" imports packages "
> org.eclipse.jetty.websocket.jsr356.*":
>
>
>
> Import-Package: javax.servlet;version="[3.0,4.0)",javax.servlet.annota
>
> tion;version="[3.0,4.0)",javax.servlet.http;version="[3.0,4.0)",javax
>
> .websocket;version="[1.0,2)",javax.websocket.server;version="[1.0,2)"
>
> ,org.eclipse.jetty.server;version="[9.0,10.0)",org.eclipse.jetty.serv
>
> er.handler;version="[9.0,10.0)",org.eclipse.jetty.servlet;version="[9
>
> .0,10.0)",org.eclipse.jetty.util;version="[9.0,10.0)",org.eclipse.jet
>
> ty.util.log;version="[9.0,10.0)",org.eclipse.jetty.util.thread;versio
>
> n="[9.0,10.0)",org.eclipse.jetty.websocket.api;version="[9.0,10.0)",o
>
> rg.eclipse.jetty.websocket.api.extensions;version="[9.0,10.0)",org.ec
>
> lipse.jetty.websocket.api.util;version="[9.0,10.0)",org.eclipse.jetty
>
> .websocket.common;version="[9.0,10.0)",org.eclipse.jetty.websocket.co
>
> mmon.events;version="[9.0,10.0)",org.eclipse.jetty.websocket.common.e
>
> vents.annotated;version="[9.0,10.0)",org.eclipse.jetty.websocket.jsr3
>
> 56;version="[9.0,10.0)",org.eclipse.jetty.websocket.jsr356.annotation
>
> s;version="[9.0,10.0)",org.eclipse.jetty.websocket.jsr356.client;vers
>
> ion="[9.0,10.0)",org.eclipse.jetty.websocket.jsr356.endpoints;version
>
> ="[9.0,10.0)",org.eclipse.jetty.websocket.jsr356.metadata;version="[9
>
> .0,10.0)",org.eclipse.jetty.websocket.server;version="[9.0,10.0)",org
>
> .eclipse.jetty.websocket.server.pathmap;version="[9.0,10.0)",org.ecli
>
> pse.jetty.websocket.servlet;version="[9.0,10.0)"
>
>
>
> It is why there are OSGi unresolved constraint at runtime.
>
>
>
> Regards,
>
> Yves
>
>
>
>
>
>
>
> De : jetty-users-bounces@xxxxxxxxxxx
> [mailto:jetty-users-bounces@xxxxxxxxxxx] De la part de Joakim Erdfelt
> Envoyé : jeudi 20 février 2014 15:08 À : JETTY user mailing list Objet
> : Re: [jetty-users] Jetty-9.1.2 - websocket : OSGi packaging issue
>
>
>
> The missing requirement: org.eclipse.jetty.websocket.jsr356
>
> would be provided by:
>
> javax-websocket-client-impl-9.1.2.v20140210.jar &
>
> javax-websocket-server-impl-9.1.2.v20140210.jar
>
>
>
> In maven terms:
>
>
>
> <dependency>
>
> <groupId>org.eclipse.jetty.websocket</groupId>
>
> <artifactId>javax-websocket-client-impl</artifactId>
>
> <version>9.1.2.v20140210</version>
>
> </dependency>
>
>
>
> <dependency>
>
> <groupId>org.eclipse.jetty.websocket</groupId>
>
> <artifactId>javax-websocket-server-impl</artifactId>
>
> <version>9.1.2.v20140210</version>
>
> </dependency>
>
>
>
>
> --
>
> Joakim Erdfelt <joakim@xxxxxxxxxxx>
>
> webtide.com - intalio.com/jetty
>
> Expert advice, services and support from from the Jetty & CometD
> experts
>
> eclipse.org/jetty - cometd.org
>
>
>
> On Thu, Feb 20, 2014 at 2:25 AM, MILLON, YVES (YVES)
> <yves.millon@xxxxxxxxxxxxxxxxxx> wrote:
>
> Hi,
>
>
>
> I am currently trying to deploy jetty-9.1.2 on top of Felix.
>
> When I start the OSGi framework, I get this error:
>
>
>
> ERROR: Bundle org.eclipse.jetty.websocket.javax.websocket.server [2]
> Error starting
> file:/mnt/hgfs/Documents/felix-framework-4.2.1/bundle/javax-websocket-
> server-impl-9.1.2.v20140210.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.eclipse.jetty.websocket.javax.websocket.server [2]: Unable to
> resolve
> 2.0: missing requirement [2.0] osgi.wiring.package;
> (&(osgi.wiring.package=org.eclipse.jetty.websocket.jsr356)(version>=9.
> 0.0)(!(version>=10.0.0))))
>
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.eclipse.jetty.websocket.javax.websocket.server [2]: Unable to
> resolve
> 2.0: missing requirement [2.0] osgi.wiring.package;
> (&(osgi.wiring.package=org.eclipse.jetty.websocket.jsr356)(version>=9.
> 0.0)(!(version>=10.0.0)))
>
> at
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3974
> )
>
> at
> org.apache.felix.framework.Felix.startBundle(Felix.java:2037)
>
> at
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1291)
>
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartL
> evelImpl.java:304)
>
> at java.lang.Thread.run(Thread.java:722)
>
>
>
> The list of deployed bundles is:
>
> ID|State |Level|Name
>
> 0|Active | 0|System Bundle (4.2.1)
>
> 1|Active | 1|Jetty :: Websocket :: javax.websocket :: Client
> Implementation (9.1.2.v20140210)
>
> 2|Installed | 1|Jetty :: Websocket :: javax.websocket.server ::
> Server Implementation (9.1.2.v20140210)
>
> 3|Active | 1|WebSocket server API (1.0.0)
>
> 4|Active | 1|Jetty :: Asynchronous HTTP Client (9.1.2.v20140210)
>
> 5|Active | 1|Jetty :: Continuation (9.1.2.v20140210)
>
> 6|Active | 1|Jetty :: Deployers (9.1.2.v20140210)
>
> 7|Active | 1|Jetty :: Http Utility (9.1.2.v20140210)
>
> 8|Active | 1|Jetty :: IO Utility (9.1.2.v20140210)
>
> 9|Active | 1|Jetty :: JMX Management (9.1.2.v20140210)
>
> 10|Active | 1|Jetty :: Proxy (9.1.2.v20140210)
>
> 11|Active | 1|Jetty :: Rewrite Handler (9.1.2.v20140210)
>
> 12|Active | 1|Jetty Servlet Schemas (3.1.0.M0)
>
> 13|Active | 1|Jetty :: Security (9.1.2.v20140210)
>
> 14|Active | 1|Jetty :: Server Core (9.1.2.v20140210)
>
> 15|Active | 1|Jetty :: Servlet Handling (9.1.2.v20140210)
>
> 16|Active | 1|Jetty :: Utility Servlets and Filters
> (9.1.2.v20140210)
>
> 17|Active | 1|Jetty :: Utilities (9.1.2.v20140210)
>
> 18|Active | 1|Jetty :: Webapp Application Support
> (9.1.2.v20140210)
>
> 19|Active | 1|Jetty :: XML utilities (9.1.2.v20140210)
>
> 20|Active | 1|Apache Felix Bundle Repository (1.6.6)
>
> 21|Active | 1|Apache Felix Gogo Command (0.12.0)
>
> 22|Active | 1|Apache Felix Gogo Runtime (0.10.0)
>
> 23|Active | 1|Apache Felix Gogo Shell (0.10.0)
>
> 24|Active | 1|Java Servlet API (3.1.0)
>
> 25|Active | 1|Jetty :: Websocket :: API (9.1.2.v20140210)
>
> 26|Active | 1|Jetty :: Websocket :: Client (9.1.2.v20140210)
>
> 27|Active | 1|Jetty :: Websocket :: Common (9.1.2.v20140210)
>
> 28|Active | 1|Jetty :: Websocket :: Server (9.1.2.v20140210)
>
> 29|Active | 1|Jetty :: Websocket :: Servlet Interface
> (9.1.2.v20140210)
>
>
>
> Is there really a packaging issue or did I miss something?
>
>
>
> Thanks,
>
> Yves
>
>
>
>
>
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
>
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
--
Jan Bartel <janb@xxxxxxxxxxx>
www.webtide.com
'Expert Jetty/CometD developer,production,operations advice'
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users
