Is the (JSR-356) WebSocket client in trunk meant to be usable in a standalone
app? I have a Maven app that depends on tomcat-websocket and
tomcat-websocket-api that gives the below exception.
java.lang.NoClassDefFoundError: org/apache/tomcat/util/codec/binary/Base64
at
On 30/04/2013 22:20, Rossen Stoyanchev wrote:
Is the (JSR-356) WebSocket client in trunk meant to be usable in a standalone
app?
Yes.
I have a Maven app that depends on tomcat-websocket and tomcat-websocket-api
that gives the below exception.
java.lang.NoClassDefFoundError:
On 30/04/2013 22:29, Mark Thomas wrote:
On 30/04/2013 22:20, Rossen Stoyanchev wrote:
Is the (JSR-356) WebSocket client in trunk meant to be usable in a
standalone app?
Yes.
I have a Maven app that depends on tomcat-websocket and tomcat-websocket-api
that gives the below exception.
- Original Message -
From: Mark Thomas ma...@apache.org
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, April 30, 2013 5:35:55 PM
Subject: Re: Standalone use of WebSocket client
The Maven snapshot probably isn't recent enough.
Yep. That is it. Let me know if you
On 30/04/2013 22:45, Rossen Stoyanchev wrote:
- Original Message -
From: Mark Thomas ma...@apache.org
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, April 30, 2013 5:35:55 PM
Subject: Re: Standalone use of WebSocket client
The Maven snapshot probably isn't recent