8 as indicated in the subject.

The test.war app supplies all the jetty classes in the WEB-INF/lib folder.
I'm trying to avoid this, since the server already have them.


On Mon, Feb 18, 2013 at 11:43 AM, Joakim Erdfelt <[email protected]> wrote:

> Which version of Jetty?
>
> And note that the test webapp (that ships with the distribution) has a
> websocket chat example that works with the existing classloader
> configuration.
>
> --
> Joakim Erdfelt <[email protected]>
> webtide.com <http://www.webtide.com/>
> Developer advice, services and support
> from the Jetty & CometD experts
> eclipse.org/jetty - cometd.org
>
>
> On Mon, Feb 18, 2013 at 10:31 AM, Nils Kilden-Pedersen 
> <[email protected]>wrote:
>
>> According to the wiki[1], the web sockets classes are part of the default
>> system classes. Yet for as long as I can remember, trying to use the web
>> sockets classes, leads to this exception:
>>
>> java.lang.NoClassDefFoundError:
>> org/eclipse/jetty/websocket/WebSocketServlet
>>
>> Is this a long-standing bug, or is the documentation incorrect?
>>
>> I know how to work around this, and have obviously done so for a long
>> time, but I thought I'd ask, because it yet again came up.
>>
>> [1]:
>> http://wiki.eclipse.org/Jetty/Reference/Jetty_Classloading#Setting_System_Classes
>>
>> _______________________________________________
>> jetty-users mailing list
>> [email protected]
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>
>>
>
> _______________________________________________
> jetty-users mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to