it appears i never get a WebSocketPayload in onEvent. i checked in
WebSocketBehavior.renderHead and it's getting in there and rendering JS to
set up the web socket, but it never gets to onConnect.
add(new WebSocketBehavior() {
private static final long serialVersionUID =
5630063441999050198L;
@Override
protected void onConnect(final ConnectedMessage message) {
View.this.webSocketConnection = new WebSocketConnection(
message); <<<<<<<------ never gets here
logger.log(new Information("Connected " + View.this.
webSocketConnection));
}
});
ideas?
<!-- Wicket Version -->
<wicket.version>7.4.0</wicket.version>
<!-- Jetty Version -->
<jetty.version>9.2.2.v20140723</jetty.version>
<!-- Servlet Version -->
<servlet.api.version>3.1.0</servlet.api.version>
<!-- Jersey Version -->
<jersey.version>2.23.2</jersey.version>
On Thu, Oct 6, 2016 at 9:28 AM, Jonathan Locke <jonathan.lo...@gmail.com>
wrote:
> well this part is solved now. i believe the issue was that jersey wanted
> an older jetty and web sockets wanted a newer one. regardless, i'm done
> upgrading to wicket 7 and there are no longer linkage problems. the issue
> now is that my web socket connection never happens :) i will re-read the
> docs you sent. thanks!
>
> jon
>
>
> On Wed, Oct 5, 2016 at 8:35 PM, Martin Grigorov <martin.grigo...@gmail.com
> > wrote:
>
>> What exactly is the problem?
>> Which impl of Wicket WebSockets do you use?
>>
>> On Oct 5, 2016 9:56 PM, "Jonathan Locke" <jonathan.lo...@gmail.com>
>> wrote:
>>
>> > trying to find a set of maven dependencies that work for servlet api +
>> > wicket 6.24.0 + jetty 9 + wicket web sockets + jersey
>> >
>> > does anyone know the magic combination of version numbers?
>> >
>> > jon
>> >
>>
>
>
