[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jetty-users] Re: NPE in WebSocketServlet
- From: Sven Jacobs <sven.jacobs@xxxxxx>
- Date: Tue, 2 Mar 2010 21:51:34 +0100
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=aMz9EYCKD22fpErj39mSaUXOgmXbPMsfLqcI/58g5ZAoWawHDo2+CqJw97tZdUjMsq 6qI51bMYK2IR1YzShJGzEYd+Tbv+AHh+Oy43nsszmG9RRCLU39hJbaQHRi9NAuSk45Ki ClpnuOFYIq4JIiuQlVyElh4sn3IRYLQDZ77ts=
2010/3/2 Greg Wilkins <gregw@xxxxxxxxxxx>
Jetty is meant to hide most of it's implementation classes from
the webapp. ÂWebSocket is an exception to that "rule".
I'll have to check if the jetty-maven-plugin has been updated
to handle that.
thanks for the feedback.
I was already wondering how this will work when other servlet containers implement WebSockets. WebSockets will need to go into a future servlet standard, right?
By the way, when I also set org.eclipse.jetty.jetty-server to "provided" then Jetty won't even find basic classes like HttpConnection when run with "mvn jetty:run". This can't be right?