I solved my problem the obvious way: stuck everything in the same classloader
as Jetty (no WEB-INF/lib or WEB-INF/classes). Not pretty, but it works.
> On Aug 28, 2015, at 10:21 AM, Don Ferguson wrote:
>
> Hi Martin,
>
> I'm already doing that (I encountered your earlier post which got me thi
Hi Martin,
I'm already doing that (I encountered your earlier post which got me this
far). This means that WebServerEndpointConfig must be in Jetty's
classpath, along with its dependencies. I'm ending up with the bulk of
wicket in Jetty's classpath (and duplicated in WEB-INF/lib) which leads to
Hi,
You can use :
ServerContainer serverContainer =
WebSocketServerContainerInitializer.configureContext(bb);
serverContainer.addEndpoint(new WicketServerEndpointConfig());
bb is: WebAppContext bb = new WebAppContext();
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigor
I have an app built on Wicket 7.0,0 and Jetty 9.2.6 to which I am attempting to
add WebSockets (wicket-native-websocket-javax). The app functions properly
when running from the IDE, however I have not been able to get web sockets to
work when running from an executable WAR file. The main issue
