Wicke website makeover time?

Hi fellow wicketeers! We all know that Wicket has to be the most awesome and productive Java UI framework around but I am worried when I point new clients to the Wicket website because it's look and feel is possibly a little dated or '2007ish style'. I feel like the look and feel of the Wicket

[ANNOUNCE] WicketStuff 6.18.0 is released

Hi, WicketStuff core 6.18.0 based on Apache Wicket 6.18.0 is released and soon will be available in Maven Central. The changelog since 6.17.0 is: Martin Tzvetanov Grigorov (14): Build against Wicket 6.18.0-SNAPSHOT [travis] Try to build and deploy wicket-6.x with Travis [travis

[ANNOUNCE] WicketStuff 7.0.0-M4 is released

Hi, WicketStuff core 7.0.0-M4 based on Apache Wicket 7.0.0-M4 is released and soon will be available in Maven Central. The changelog since 7.0.0-M3 is: Martin Tzvetanov Grigorov (28): Upgrade Spring to 4.0.7 Try to deploy snapshots to Sonatype after successful build Add notific

Re: Web sockets - version confusion

On Tue, Nov 11, 2014 at 8:48 PM, Niranjan Rao wrote: > Another naive question. POM file for wicket-native-websocket-javax > version 7.0.0.-M4 (https://repo1.maven.org/maven2/org/apache/wicket/ > wicket-native-websocket-javax/7.0.0-M4/wicket-native- > websocket-javax-7.0.0-M4.pom) includes jetty

Re: Web sockets - version confusion

Hi, On Tue, Nov 11, 2014 at 8:16 PM, Niranjan Rao wrote: > Martin, > > Thanks for the reply. If I understand you correctly I need to do following > so that I have JSR 356 compliant code which in theory will be independent > of container. > > 1. Use 7.0* version for wicket-native-websocket-javax

Re: Web sockets - version confusion

Another naive question. POM file for wicket-native-websocket-javax version 7.0.0.-M4 (https://repo1.maven.org/maven2/org/apache/wicket/wicket-native-websocket-javax/7.0.0-M4/wicket-native-websocket-javax-7.0.0-M4.pom) includes jetty dependencies. If I am using some other container such as tom

Re: Web sockets - version confusion

Martin, Thanks for the reply. If I understand you correctly I need to do following so that I have JSR 356 compliant code which in theory will be independent of container. 1. Use 7.0* version for wicket-native-websocket-javax 2. Use maven exclusions so that wicket 7 code is not included. This

Re: Could not clear select2Choice component model value.

Hello Martin, I know you are busy man ..., but, were you able to take a look at this issue? :) On 22 October 2014 11:23, Maxim Solodovnik wrote: > It seems like script generated in renderInitializationScript should be > added to AjaxRequestTarget on every Ajax update ... > > On 21 October 2014

Re: [ANNOUNCE] Apache Wicket 6.18.0 Released

I used bcc in order to prevent bad reply-to-all behaviors... Martijn On Tue, Nov 11, 2014 at 1:50 PM, Martin Grigorov wrote: > MarkMail has received for all MLs. So it was fine. > Use To/CC instead of BCC. It's open source product :-) > > Martin Grigorov > Wicket Training and Consulting > https:

Re: [ANNOUNCE] Apache Wicket 6.18.0 Released

MarkMail has received for all MLs. So it was fine. Use To/CC instead of BCC. It's open source product :-) Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Nov 11, 2014 at 2:48 PM, Martin Grigorov wrote: > I've received 6.18.0 from announce@ and 7.0.0-M4 from

Re: [ANNOUNCE] Apache Wicket 6.18.0 Released

I've received 6.18.0 from announce@ and 7.0.0-M4 from users@. I thought that you just forgot to add all recipients... Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Nov 11, 2014 at 2:24 PM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > this was bc

Re: [ANNOUNCE] Apache Wicket 7.0.0-M4 Released

it was bcc-d to annou...@wicket.apache.org didn't it get through? Martijn On Tue, Nov 11, 2014 at 8:59 AM, Martin Grigorov wrote: > -- Forwarded message -- > From: Martijn Dashorst > Date: Tue, Nov 11, 2014 at 12:18 AM > Subject: [ANNOUNCE] Apache Wicket 7.0.0-M4 Released > To:

Re: [ANNOUNCE] Apache Wicket 6.18.0 Released

this was bcc-d to users@, dev@ and annou...@wicket.apache.org. Didn't it get through? Martijn On Tue, Nov 11, 2014 at 8:59 AM, Martin Grigorov wrote: > -- Forwarded message -- > From: Martijn Dashorst > Date: Tue, Nov 11, 2014 at 12:17 AM > Subject: [ANNOUNCE] Apache Wicket 6.18

Re: javax WebSockets configuration

Cool! On Tue, Nov 11, 2014 at 12:47 PM, Maxim Solodovnik wrote: > works as expected after adding tomcat-embed-websocket > < > http://mvnrepository.com/artifact/org.apache.tomcat.embed/tomcat-embed-websocket > > > jar > file > Will stay on tomcat specific version for now > > Thanks! > > On 11 Nov

Re: javax WebSockets configuration

works as expected after adding tomcat-embed-websocket jar file Will stay on tomcat specific version for now Thanks! On 11 November 2014 16:40, Maxim Solodovnik wrote: > 5080 is standard port for our application a

Re: javax WebSockets configuration

5080 is standard port for our application and work as expected with tomcat connector org.apache.wicket.protocol.ws.javax.WicketEndpoint#onOpen() is not being called :( maybe tomcat embed jar list used: ecj-4.4.jar tomcat-embed-core.jar tomcat-embed-jasper.jar tomcat-embed-logging-juli.jar tomcat-

Re: javax WebSockets configuration

Hi Maxim, On Tue, Nov 11, 2014 at 11:54 AM, Maxim Solodovnik wrote: > Hello, > > I just tried to switch to "javax" websockets (from "tomcat" websockets) > was was done: > 1) wicket version was changed to 7.0.0-M4 > good > 2) filter changed > to org.apache.wicket.protocol.ws.javax.JavaxWebSoc

javax WebSockets configuration

Hello, I just tried to switch to "javax" websockets (from "tomcat" websockets) was was done: 1) wicket version was changed to 7.0.0-M4 2) filter changed to org.apache.wicket.protocol.ws.javax.JavaxWebSocketFilter 3) these 2 dependencies added to pom org.apache.wicket wicket-native-websocket-core

Fwd: [ANNOUNCE] Apache Wicket 6.18.0 Released

-- Forwarded message -- From: Martijn Dashorst Date: Tue, Nov 11, 2014 at 12:17 AM Subject: [ANNOUNCE] Apache Wicket 6.18.0 Released To: annou...@apache.org The Apache Wicket PMC is proud to announce Apache Wicket 6.18.0! This release marks another minor release of Wicket 6. Sta