alexander.landsnes.k...@visma.com wrote:
I forked Wicket to my github repo and took a look at it. Compiling
wicket-native-websocket-javax with Java 6 and Wicket 6.19.0-SNAPSHOT
was
no
problem at all, my problem popped up when I tried to get the embedded
jetty
server to run the test case
Hi,
JSR356 API jar is built with Java 7. This is the main reason why this
module is not part of Wicket 6.x.
If this single method is the only problem to use
wicket-native-websocket-javax:7.0.0-M4 with Wicket 6.18.0 then please
create a ticket in JIRA and we will make it public for 6.20.0.
I
Reading the documentation I was under the impression that
wicket-native-websocket-javax could be used along with Wicket 6.X, however that
seems to not be the case.
In the constructor of
org.apache.wicket.protocol.ws.api.AbstractWebSocketProcessor
line 120 (7.0.0-M4) it accesses WicketFilter
.
Naming conventions are the spice of policies. Milestones are viewed as
dangerously buggy and unstable, and hence unfit for the hallowed halls of
shippable code. I may try to sneak it in nonetheless, since I do need websocket
support and the stable release is weeks away.
Alex
-Original
it in nonetheless, since I do need
websocket support and the stable release is weeks away.
Alex
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: 27 January 2015 10:30
To: users@wicket.apache.org
Subject: Re: JSR356 Websocket with Wicket 6.18
Hi,
JSR356 API jar
Hi Wicket Group Members.
Anyone have this, I can't seem to get websocket to connect Wicket7.0.0m4, I
suspect my problem is something with dependencies with jetty 9.3+?
The behavior is injected properly, however in the Javascript console in the
client I have the following.
Firefox can't
.
Anyone have this, I can't seem to get websocket to connect Wicket7.0.0m4, I
suspect my problem is something with dependencies with jetty 9.3+?
The behavior is injected properly, however in the Javascript console in the
client I have the following.
Firefox can't establish a connection
Neither of those break, at the WebSocket parts.
It's embedded jetty 9.3
server = new Server(Simple.getPort());
WebAppContext bb = new WebAppContext();
bb.setServer(server);
bb.setContextPath(/);
bb.setWar(src/main/webapp);
// START JMX SERVER
The problem is that with your code Jetty won't scan
for javax.websocket.server.ServerApplicationConfig's in the classpath.
So org.apache.wicket.protocol.ws.javax.WicketServerApplicationConfig is not
used at all.
Here is a trick that I've just did to make my websocket demo work in
embedded Jetty
.
Here is a trick that I've just did to make my websocket demo work in
embedded Jetty:
Create a class :
package org.apache.wicket.protocol.ws.javax;
public class MyEndpointConfig extends WicketServerEndpointConfig
{
}
You need to do that because WicketServerEndpointConfig has package private
is a trick that I've just did to make my websocket demo work in
embedded Jetty:
Create a class :
package org.apache.wicket.protocol.ws.javax;
public class MyEndpointConfig extends WicketServerEndpointConfig
{
}
You need to do that because WicketServerEndpointConfig has package
org.apache.wicket.protocol.ws.javax.WicketServerApplicationConfig is
not used at all.
Here is a trick that I've just did to make my websocket demo work in
embedded Jetty:
Create a class :
package org.apache.wicket.protocol.ws.javax;
public class MyEndpointConfig extends WicketServerEndpointConfig
{
}
You need
Hi,
I think it should work.
What kind of problems do you face ?
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Fri, Oct 3, 2014 at 4:55 PM, Maxim Solodovnik solomax...@gmail.com
wrote:
Hello All,
I wonder is it possible to send IWebSocketPushMessage from
To be fair I haven't tried :(
I thought I will have no session/application bound to current thread
exceptions :(
I'll test and let you know
On 7 October 2014 15:21, Martin Grigorov mgrigo...@apache.org wrote:
Hi,
I think it should work.
What kind of problems do you face ?
Martin Grigorov
You use request and session scoped Spring beans in WebSocket request
because such requests are not processed by Servlet filters and Spring has
no chance to set its proxy objects as request/session attributes.
But in Spring bean code you can do:
Application app = Application..get(myFilterName
Thanks a lot for the tip Martin!
will give it a try and write back :)
On 7 October 2014 16:39, Martin Grigorov mgrigo...@apache.org wrote:
You use request and session scoped Spring beans in WebSocket request
because such requests are not processed by Servlet filters and Spring has
no chance
Hello All,
I wonder is it possible to send IWebSocketPushMessage from Spring bean? (I
can access Spring beans from wicket pages, now I need backward
compatibility)
Thanks in advance for your help!
--
WBR
Maxim aka solomax
Hello Wickets,
I am doing some extensive testing with the native-websocket implementation in
preparation for wicket-7 conversion of my apps. The websocket part is going to
be used for an internal messaging system which sends/broadcasts system
notifications to the logedin users. This all
Hi,
See https://issues.apache.org/jira/browse/WICKET-5453
Martin Grigorov
Wicket Training and Consulting
On Fri, May 30, 2014 at 4:18 PM, Jan Moxter jan.mox...@innobix.com wrote:
Hello Wickets,
I am doing some extensive testing with the native-websocket implementation
in preparation
Thanks for the indication,
best list ever!
Jan
- Original Message -
From: Martin Grigorov mgrigo...@apache.org
To: users@wicket.apache.org, Jan Moxter jan.mox...@innobix.com
Sent: Friday, May 30, 2014 9:27:51 AM
Subject: Re: WebSocket with InitParameter
Hi,
See https
Hi Martin,
thanks for the input. Using the wicket-native-websocket-javax 7.0.0-M1 in
conjunction with the 6.15.0 modules and configuring my embeded jetty correctly
( :-) ) I got it to work.
jan
- Original Message -
From: Martin Grigorov mgrigo...@apache.org
To: users
...
Martin Grigorov
Wicket Training and Consulting
On Fri, May 23, 2014 at 9:06 PM, Jan Moxter jan.mox...@innobix.com wrote:
Hi Martin,
thanks for the input. Using the wicket-native-websocket-javax 7.0.0-M1 in
conjunction with the 6.15.0 modules and configuring my embeded jetty
correctly
Hallo,
right now if you download a jetty server in the version 9 you get the stable
version 9.1.5.v20140505. The API for the websocket implementation did change
between 9.0 and 9.1. so that the wicket-native-websocket-jetty9 module does not
work any more.
- are you planning to update
Hi,
Jetty 9.1 implements JSR356 and the recommended way is to use
wicket-native-websocket-javax module.
On May 23, 2014 4:38 AM, Jan Moxter jan.mox...@innobix.com wrote:
Hallo,
right now if you download a jetty server in the version 9 you get the
stable version 9.1.5.v20140505. The API
On Fri, Mar 7, 2014 at 8:12 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
On Fri, Mar 7, 2014 at 2:50 AM, Henrik Østerlund Gram
henrik.g...@gmail.com wrote:
I just tried it out by building 7.x, copying over just the
wicket-native-websocket-javax
artifact, modded the pom to depend
applies to version 6.x) instructs you to just include the
wicket-native-websocket-javax dependency, but that doesn't work as that
artifact does not seem to exist for the latest 6.x branch and I was also
unable to find it in the git repo.
Now I do see it in the master branch for 7.x, and I'm wondering
Hi,
The main reason to not backport it to wicket-6.x is that JSR356
(websocket-api.jar) is built with Java 7.
And Wicket 6.x is being build with Java 6 ...
One option is to wait for Wicket 7.0.0.M1 (we talk about it for a month
now, so I hope it will be released soon!).
Another option is to port
I just tried it out by building 7.x, copying over just the
wicket-native-websocket-javax
artifact, modded the pom to depend on the 6.14 parent, and it pretty much
worked as expected (using jdk7 + wildfly 8)
WebSocketBehavior seems to be missing code to handle WebSocketPushPayload,
both in 6.x
Hi,
On Fri, Mar 7, 2014 at 2:50 AM, Henrik Østerlund Gram henrik.g...@gmail.com
wrote:
I just tried it out by building 7.x, copying over just the
wicket-native-websocket-javax
artifact, modded the pom to depend on the 6.14 parent, and it pretty much
worked as expected (using jdk7 + wildfly
Is there a 6.X branch I can use which contains native javax websockets?
My git kung fu is letting me down. (Still only a white belt)
Thanks
Peter.
from others then I can port the module to
wicket-6.x branch.
But why do you prefer the -javax impl ?
The Wicket Native WebSocket APIs for Jetty and Tomcat are the same, the
only difference is the WicketFilter impl you should use.
Martin Grigorov
Wicket Training and Consulting
On Wed, Dec 18
Hi Martin,
Tomcat 7.0.47 back ported javax websockets from 8.
Which means wicket-native-websocket-tomcat no longer works
(well I couldn't get it working but I didn't try too hard)
Wicket 7 sounds lovely.
Many thanks
Peter.
On 18 December 2013 11:23, Martin Grigorov mgrigo...@apache.org
wicket-native-websocket-tomcat no longer works
(well I couldn't get it working but I didn't try too hard)
Wicket 7 sounds lovely.
Many thanks
Peter.
On 18 December 2013 11:23, Martin Grigorov mgrigo...@apache.org wrote:
Hi,
https://twitter.com/mtgrigorov/status/364323832490110976
Hello,
I do my first steps using Apache Wicket and would like to test the WebSocket
feature. However, I fail to get anything compiled and deployed. Wicket by
itself seems to work (i,e. message in Index.html is replaced
successfully). I am using Jetty 9.0.0M3 and Wicket 6.6.0. Here are my
Hi,
Jetty 9.x APIs are not stable yet. wicket-native-websocket-jetty9 uses M0
and needs upgrade to the later 9.x milestone.
You can either play with wicket-native-websocket-jetty (Jetty 7/8) or try
to upgrade to the new Jetty 9.x APIs in wicket-native-websocket-jetty9 and
contribute your work
Hi Folks,
iam using Wicket 6.2.0 with Wicket-Atmosphere 0.4 and everything works
great, but Iam not able to debug the websocket-transfer in Chrome
Debug-Tools like its explained and working here :
http://blog.kaazing.com/2012/05/09/inspecting-websocket-traffic-with-chrome-developer-tools
Are you sure web socket connection was established? Maybe your connection
is long-polling.
N
On Nov 29, 2012 7:36 AM, MattyDE ufer.mar...@gmail.com wrote:
Hi Folks,
iam using Wicket 6.2.0 with Wicket-Atmosphere 0.4 and everything works
great, but Iam not able to debug the websocket-transfer
How should i test this? I did no special configuration and testing it with
the latest google chrome, which supports WebSockets.
I think the atmosphere implementation tests on clientside which type of
transfer is possible (WebSocket, SSE, Long-Polling etc.)
--
View this message in context
Atmosphere checks both the client and the server capabilities to decide
which transport to use.
Some web servers do not support WebSocket.
On Thu, Nov 29, 2012 at 2:18 PM, MattyDE ufer.mar...@gmail.com wrote:
How should i test this? I did no special configuration and testing
-cant-debug-the-websocket-tp4654322p4654329.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h
tests on clientside which type of
transfer is possible (WebSocket, SSE, Long-Polling etc.)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/What-is-Atmosphere-doing-wrong-so-i-cant-debug-the-websocket-tp4654322p4654327.html
Sent from the Users forum mailing list
this resource
reference necessary?
Wicket filters duplicate header contributions. This way both of them
declare that they depend on wicket-websocket-jquery.js but only one
contribution is actually done.
Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com
Hi,
You should ask this question in Tomcat's users@ mailing list.
I'm not sure what mod_jk does with the web socket connection.
On Tue, Sep 18, 2012 at 3:37 AM, sfwicket li...@bgb.net wrote:
I have realized my WebSocket connection was closing briefly after opening
because I have Apache httpd
http://tomcat.10.n6.nabble.com/Tomcat7-WebSocket-mod-jk-td4986848.html
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-6-WebSocket-Apache-mod-jk-tp4652073p4652128.html
Sent from the Users forum mailing list archive at Nabble.com
Thanks for sharing!
On Wed, Sep 19, 2012 at 12:39 AM, sfwicket li...@bgb.net wrote:
http://tomcat.10.n6.nabble.com/Tomcat7-WebSocket-mod-jk-td4986848.html
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-6-WebSocket-Apache-mod-jk-tp4652073p4652128.html
Is there a working Wicket 6.0.0 Websocket example written in Java? The
only demo provided here on the wiki page is written in Scala.
https://cwiki.apache.org/WICKET/wicket-native-websockets.html
The other demo I found has outdated dependencies on Wicket
6.0-SNAPSHOT and wicket-native
Hi,
http://wicketinaction.com/2012/07/wicket-6-native-websockets/
This is the Java example.
What is the problem with compiling it ?
On Mon, Sep 17, 2012 at 11:13 PM, sfwicket li...@bgb.net wrote:
Is there a working Wicket 6.0.0 Websocket example written in Java? The only
demo provided here
will not resolve this dependency:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-native-websocket-tomcat/artifactId
version0.1-SNAPSHOT/version
/dependency
but I found version 0.2 or 0.3
-websocket-tomcat/artifactId
version0.1-SNAPSHOT/version
/dependency
but I found version 0.2 or 0.3-SNAPSHOT do resolve. similarly for the
wicket-native-websocket-jetty artifact.
Quoting Martin Grigorov mgrigo...@apache.org:
Hi,
http
got it - thanks!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-6-Websocket-Example-tp4652059p4652064.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e
Good!
I've updated the code of the demo apps in my repository.
On Mon, Sep 17, 2012 at 11:57 PM, sfwicket li...@bgb.net wrote:
got it - thanks!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-6-Websocket-Example-tp4652059p4652064.html
Sent from
:
http://apache-wicket.1842946.n4.nabble.com/Wicket-6-Websocket-Example-tp4652059p4652067.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
I have realized my WebSocket connection was closing briefly after opening
because I have Apache httpd on port 80 with mod_jk running in front of my
Tomcat instance on port 8080. When I connect directly on 8080 to Tomcat the
Wicket WebSocket demo app works.
What is the recommended configuration
Hi Pierre,
Take a look at
https://github.com/martin-g/wicket-native-websocket-example/blob/master/src/main/resources/org/apache/wicket/websocket/jetty/example/client.js
There is Wicket.WebSocket object which basically wraps native
window.WebSocket just to be able to intercept the calls and send
Great! Thanks a lot!
Regards,
Pierre
On Wed, Jun 20, 2012 at 2:31 PM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi Pierre,
Take a look at
https://github.com/martin-g/wicket-native-websocket-example/blob/master/src/main/resources/org/apache/wicket/websocket/jetty/example/client.js
wicket plus atmosphere framework might also be a possibility. one tutorial here:
http://jfarcand.wordpress.com/2010/10/07/writing-websocket-application-using-apache-wicket/
On Sun, Nov 21, 2010 at 5:05 PM, kamiseq kami...@gmail.com wrote:
ok, thanks, I will try that
pozdrawiam
Paweł Kamiński
On Mon, Nov 22, 2010 at 4:38 PM, heapifyman heapify...@gmail.com wrote:
wicket plus atmosphere framework might also be a possibility. one tutorial
here:
http://jfarcand.wordpress.com/2010/10/07/writing-websocket-application-using-apache-wicket/
A way more Wicket-ish version at
https
thanks, I run into the first page but I was curious if I can do this
depending only on wicket. but I will give it a try again
pozdrawiam
Paweł Kamiński
kami...@gmail.com
pkaminski@gmail.com
__
101 - 158 of 158 matches
Mail list logo
