[ANNOUNCE] WicketStuff 9.17.0 Released
WicketStuff core 9.17.0 based on Apache Wicket 9.17.0 is released and soon will be available at Maven Central! Maxim Solodovnik (8): Switching to the next development version Dependencies are updated Fixes issue #764: presense of 'getAttribute' function is being tested Dependencies are updated Dependencies are updated Dashboard: outdated widgets are dropped; examples are fixed Dependencies are updated; some javadoc errors are fixed wicketstuff-core-9.17.0 release build is successful The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 10.0.0 Released
WicketStuff core 10.0.0 based on Apache Wicket 10.0.0 is released and soon will be available at Maven Central! dependabot[bot] (50): Bump org.springframework:spring-core from 6.0.10 to 6.0.15 (#760) Bump org.springframework:spring-core from 6.0.15 to 6.0.16 (#761) Bump com.hazelcast:hazelcast in /datastores-parent/datastore-hazelcast (#763) Bump org.springframework:spring-web from 6.0.16 to 6.0.17 (#765) Bump actions/checkout from 2 to 4 (#766) Bump actions/setup-java from 2 to 4 (#768) Bump actions/cache from 2 to 4 (#770) Bump ch.qos.logback:logback-classic from 1.4.8 to 1.5.0 (#815) Bump commons-logging:commons-logging from 1.2 to 1.3.0 (#814) Bump org.apache.maven.plugins:maven-surefire-report-plugin (#813) Bump org.apache.maven.plugins:maven-project-info-reports-plugin (#812) Bump org.javassist:javassist from 3.29.2-GA to 3.30.2-GA (#811) Bump org.apache.maven.archetype:archetype-packaging from 3.1.0 to 3.2.1 (#805) Bump org.apache.felix:org.apache.felix.webconsole from 3.1.8 to 5.0.0 (#802) Bump com.datastax.cassandra:cassandra-driver-core from 3.6.0 to 3.11.5 (#801) Bump org.apache.maven.plugins:maven-clean-plugin from 3.2.0 to 3.3.2 (#799) Bump com.hazelcast:hazelcast from 5.3.5 to 5.3.6 (#798) Bump org.webjars.bower:datatables from 1.10.19 to 1.10.21 (#796) Bump org.ow2.asm:asm-util from 9.5 to 9.6 (#795) Bump scala.version from 2.13.11 to 2.13.13 (#794) Bump com.google.protobuf:protobuf-java from 3.19.6 to 3.25.3 (#787) Bump redis.clients:jedis from 4.3.1 to 5.1.1 (#786) Bump org.apache.maven.plugins:maven-jxr-plugin from 2.5 to 3.3.2 (#783) Bump org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib (#782) Bump org.apache.ignite:ignite-core from 2.14.0 to 2.16.0 (#781) Bump org.apache.maven.plugins:maven-checkstyle-plugin from 2.15 to 3.3.1 (#776) Bump spring.version from 6.0.17 to 6.1.4 (#773) Bump net.javacrumbs.json-unit:json-unit from 2.17.0 to 3.2.7 (#769) Bump org.apache.shiro:shiro-core from 1.11.0 to 1.13.0 (#759) Bump org.glassfish.main.extras:glassfish-embedded-all from 4.0 to 7.0.12 (#778) Bump org.apache.shiro:shiro-web from 1.11.0 to 1.13.0 (#758) Bump log4j.version from 2.20.0 to 2.23.0 (#797) Bump org.codehaus.mojo:findbugs-maven-plugin from 3.0.1 to 3.0.5 (#829) Bump ch.qos.logback:logback-classic from 1.5.0 to 1.5.2 (#828) Bump org.webjars.npm:tinymce from 6.8.2 to 6.8.3 (#827) Bump org.codehaus.mojo:taglist-maven-plugin from 2.4 to 3.0.0 (#826) Bump org.apache.maven.plugins:maven-archetype-plugin from 3.1.0 to 3.2.1 (#825) Bump org.apache.maven.plugins:maven-site-plugin (#824) Bump jakarta.servlet.jsp:jakarta.servlet.jsp-api from 3.1.0 to 3.1.1 (#823) Bump org.glassfish.main.extras:glassfish-embedded-all (#820) Bump com.sun.xml.bind:jaxb-core from 2.3.0.1 to 4.0.4 (#819) Bump org.mockito:mockito-core from 5.10.0 to 5.11.0 (#818) Bump org.apache.maven.plugins:maven-toolchains-plugin from 1.1 to 3.1.0 (#817) Bump shiro.version from 1.13.0 to 2.0.0 (#816) Bump slf4j.version from 2.0.7 to 2.0.12 (#779) Bump org.clojure:clojure from 1.11.1 to 1.11.2 (#830) Bump ch.qos.logback:logback-classic from 1.5.2 to 1.5.3 (#836) Bump com.sun.xml.bind:jaxb-core from 4.0.4 to 4.0.5 (#835) Bump com.fasterxml.jackson.core:jackson-databind from 2.14.3 to 2.16.2 (#833) Bump redis.clients:jedis from 5.1.1 to 5.1.2 (#832) Maxim Solodovnik (15): Switching to the next development version schemaLocation for web.xml files is updated Jetty DTD URL is updated Dependencies are updated Merge is fixed Duplicate property removed TinyMCE 3 and 4 are dropped Modules for TinyMCE 3 and 4 are dropped Dependencies are updated Fixes issue #764: presense of 'getAttribute' function is being tested Dependencies are updated Dependencies are updated Fast serializer is updated GPG plugin is updated wicketstuff-core-10.0.0 is released Johannes Renoth (1): Add TinyMCE 6 module (#762) Martin Tzvetanov Grigorov (1): Add dependabot config for updating the Java deps and Github Actions Silas Porth (1): Update/partial rewrite of editable-grid (#756) The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 9 + Jetty 12: Lots of exceptions due to modification of read-only response
Hello Martin, On Mon, 22 Jan 2024 at 23:09, Martin Simons wrote: > > Hey everyone, > > I started a gnarly migration of a really old Wicket 6 application to Wicket 9 > last week. One of the objectives was to move away from a .war-based > deployment to a Tomcat app server, and instead go with an embedded server > which runs within a Docker file. The choice here fell on Jetty 12 using the > EE8 environment. I believe you need Wicket10 for Jetty12 :) > > So far, so good. After getting all the API changes sorted out, most things > work as expected. But what puzzles me is that I get the logs flooded with > exceptions because different pieces of code try to write to the web response > at a point in the web request cycle when it has already been committed. > > For Wicket itself, this affects the COOP and COEP filters when handling HEAD > requests. > > My one code is affected (for example) when trying to set a cookie at the end > of a request cycle. > > So two questions: > > 1. I am likely missing something obvious. Does anyone see what it might be? > 2. Regarding my own code: I get that I can’t write to a response that’s > been committed, but what’s “the Wicket way” to modify a response header after > the response has been processed but before it is written? > RequestCycleListener::onEndRequest() seems to be too late. > > I found surprisingly little on this problem when googling, so I am almost > certain it’s my mistake. But after looking at it for days, I am sort of > stuck. I would greatly appreciate a few pointers. > > Thank you very much, > Martin -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.16.0 Released
WicketStuff core 9.16.0 based on Apache Wicket 9.16.0 is released and soon will be available at Maven Central! Maxim Solodovnik (5): Switching to the next development version BCprov is updated; Tests are fixed Jetty is updated Dependencies are updated wicketstuff-core-9.16.0 release build is successful The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 10.0.0-M2 Released
WicketStuff core 10.0.0-M2 based on Apache Wicket 10.0.0-M2 is released and soon will be available at Maven Central! Maxim Solodovnik (10): portlet-parent is dropped Switching to the next development version Fixes #753: wicketstuff-openlayers3-bootstrap modified to work under bootstrap 4/5 HTTPS SniHostCheck is turned off for all Start applications Build is fixed due to M2 restructure Some modules were converted to JPMS Javadoc links are updated Naming clean-up wicket-webjars and jquery-selectors are updated wicketstuff-core-10.0.0-M2 is released The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.15.0 Released
WicketStuff core 9.15.0 based on Apache Wicket 9.15.0 is released and soon will be available at Maven Central! Maxim Solodovnik (6): Switching to the next development version wicketstuff-openlayers3 fixed to work with bootstrap 3, 4, 5 Jackson is downgraded Jetty is updated Dependencies are updated wicketstuff-core-9.15.0 is released The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Quickstart Problems
On Sun, 27 Aug 2023 at 03:53, Dr. Janko Jochimsen wrote: > > Dear Maxim, > > thank you. > > I tested 9.15.0-SNAPSHOT and it works like charm (Start.java and Jetty > Version). Non errors no complains. (Http and Https). Glad it works as expected :) Thanks for the report! > > Best > > Janko > > -----Ursprüngliche Nachricht- > Von: Maxim Solodovnik > Gesendet: Samstag, 26. August 2023 09:01 > An: users@wicket.apache.org > Betreff: Re: Quickstart Problems > > On Sat, 26 Aug 2023 at 01:12, Dr. Janko Jochimsen > wrote: > > > > Hi Maxim, > > > > your response is great. > > > > I am a little bit lost with installing this quickstart (very much my fault > > as I am using maven 99% within eclipse). > > > > No problem at all :) > The code is commited and fresh SNAPSHOT should be available via maven :) So > if you have SNAPSHOTS enabled for https://repository.apache.org you can just > use it :) > > Select "9.15.0-SNAPSHOT" at this page > https://wicket.apache.org/start/quickstart.html > > Fix for 10.0 is here: https://github.com/apache/wicket/pull/605 > > > I cloned the git repro and tried to start building in the main > > directory as well as in the quickstart dir. Both worked for a while > > and downloaded but then I got a BUILD FAILURE Could not find goal > > 'create' in plugin > > org.apache.maven.plugins:maven-archetype-plugin:3.2.1 > > I know that is my problem and has probably nothing to do with wicket, > > however I am stuck somehow... > > The steps should be: > 1) git clone g...@github.com:apache/wicket.git > 2) cd wicket > 3) mvn clean install [-DskipTests] > > (you can skip tests to speed up the build :))) > > > > > Best > > > > Janko > > > > > > -Ursprüngliche Nachricht- > > Von: Maxim Solodovnik > > Gesendet: Freitag, 25. August 2023 18:40 > > Cc: users@wicket.apache.org > > Betreff: Re: Quickstart Problems > > > > Can you please try to use quickstart from this branch: > > https://github.com/apache/wicket/tree/quickstart-fix ? > > (9.15.0-SNAPSHOT so far :))) > > > > On Fri, 25 Aug 2023 at 23:34, Maxim Solodovnik wrote: > > > > > > On Fri, 25 Aug 2023 at 22:20, Dr. Janko Jochimsen > > > wrote: > > > > > > > > Hi, > > > > > > > > I am new to Wicket but have some experience with Java and Tapestry. > > > > Installing the quickstarts I have run into some problems that make me > > > > wonder how many people are starting with this platform as of 2023? > > > > > > > > First the facts: > > > > I installed the default quickstart 9.14.0 from the > > > > https://wicket.apache.org/start/quickstart.html as well as the > > > > 10.0.0.M1 directly via eclipse both into a completely fresh eclipse > > > > Version: 2023-06 (4.28.0) running under Java 17.0.8.7 from Openlogic. > > > > In both versions I have got problem 1. and 2. Problem 3. is exclusive > > > > on 10.0.0-M1 but this is due to the enforcement of Java 17 in Version > > > > 10. > > > > > > > > Now the problems: > > > > 1.) There is a simple problem with the keystore > > > > > > > > In Line 46 of the Start.java the keystore (keystore.p12) is supposed > > > > to be read. However in the path "\src\test\resources" you will find > > > > only a file keystore (without the .p12 suffix). That can not work and > > > > therefore the switch to https breaks if that file is not renamed. After > > > > renaming the keystore file it worked and I can change to https (at > > > > least in 9.14.0 under Java 11. > > > > > > > > 2.) > > > > In the path "\src\test\jetty" are four xml definition file how all > > > > get a > > > > > > > > Referenced file contains errors > > > > (http://www.eclipse.org/jetty/configure_9_0.dtd). > > > > > > > > error. > > > > > > > > I didn't managed to switch this off but it seems to be irrelevant > > > > at least for the development system > > > > > > According to > > > https://eclipse.dev/jetty/documentation/jetty-9/index.html#jetty-web > > > -x > > > ml-config > > > > > > correct URL is http://www.eclipse.org/jetty/configure_9_3.dtd > > > > > > I'll update it :) > > > > > > > > > > > > > &g
Re: Quickstart Problems
On Sat, 26 Aug 2023 at 01:12, Dr. Janko Jochimsen wrote: > > Hi Maxim, > > your response is great. > > I am a little bit lost with installing this quickstart (very much my fault as > I am using maven 99% within eclipse). > No problem at all :) The code is commited and fresh SNAPSHOT should be available via maven :) So if you have SNAPSHOTS enabled for https://repository.apache.org you can just use it :) Select "9.15.0-SNAPSHOT" at this page https://wicket.apache.org/start/quickstart.html Fix for 10.0 is here: https://github.com/apache/wicket/pull/605 > I cloned the git repro and tried to start building in the main directory as > well as in the quickstart dir. Both worked for a while and downloaded but > then I got a BUILD FAILURE Could not find goal 'create' in plugin > org.apache.maven.plugins:maven-archetype-plugin:3.2.1 > I know that is my problem and has probably nothing to do with wicket, however > I am stuck somehow... The steps should be: 1) git clone g...@github.com:apache/wicket.git 2) cd wicket 3) mvn clean install [-DskipTests] (you can skip tests to speed up the build :))) > > Best > > Janko > > > -Ursprüngliche Nachricht- > Von: Maxim Solodovnik > Gesendet: Freitag, 25. August 2023 18:40 > Cc: users@wicket.apache.org > Betreff: Re: Quickstart Problems > > Can you please try to use quickstart from this branch: > https://github.com/apache/wicket/tree/quickstart-fix ? > (9.15.0-SNAPSHOT so far :))) > > On Fri, 25 Aug 2023 at 23:34, Maxim Solodovnik wrote: > > > > On Fri, 25 Aug 2023 at 22:20, Dr. Janko Jochimsen > > wrote: > > > > > > Hi, > > > > > > I am new to Wicket but have some experience with Java and Tapestry. > > > Installing the quickstarts I have run into some problems that make me > > > wonder how many people are starting with this platform as of 2023? > > > > > > First the facts: > > > I installed the default quickstart 9.14.0 from the > > > https://wicket.apache.org/start/quickstart.html as well as the 10.0.0.M1 > > > directly via eclipse both into a completely fresh eclipse Version: > > > 2023-06 (4.28.0) running under Java 17.0.8.7 from Openlogic. In both > > > versions I have got problem 1. and 2. Problem 3. is exclusive on > > > 10.0.0-M1 but this is due to the enforcement of Java 17 in Version 10. > > > > > > Now the problems: > > > 1.) There is a simple problem with the keystore > > > > > > In Line 46 of the Start.java the keystore (keystore.p12) is supposed to > > > be read. However in the path "\src\test\resources" you will find only a > > > file keystore (without the .p12 suffix). That can not work and therefore > > > the switch to https breaks if that file is not renamed. After renaming > > > the keystore file it worked and I can change to https (at least in 9.14.0 > > > under Java 11. > > > > > > 2.) > > > In the path "\src\test\jetty" are four xml definition file how all > > > get a > > > > > > Referenced file contains errors > > > (http://www.eclipse.org/jetty/configure_9_0.dtd). > > > > > > error. > > > > > > I didn't managed to switch this off but it seems to be irrelevant at > > > least for the development system > > > > According to > > https://eclipse.dev/jetty/documentation/jetty-9/index.html#jetty-web-x > > ml-config > > > > correct URL is http://www.eclipse.org/jetty/configure_9_3.dtd > > > > I'll update it :) > > > > > > > > > > > 3.) > > > > > > It looks as if the usage of org.eclipse.jetty.util.ssl.SslContextFactory > > > is outdated and for Java 17 broken. > > > > > > a.) > > > In Line 58 of the Start.java a SslContextFactory is created by this > > > command: > > > > > > SslContextFactory sslContextFactory = new SslContextFactory(); > > > > > > This call is deprecated in Java 11 and causes an error in Java 17. It > > > should read: > > > > > > SslContextFactory sslContextFactory = new > > > SslContextFactory.Server(); > > > > > > > > > b.) > > > > > > A little bit more complicated is the problem in line 64 ff > > > > > > It states: > > > ServerConnector https = new ServerConnector(server, new > > > SslConnectionFactory( sslContextFactory, "http/1.1"), new > > > HttpConnectionFactory(https_config)); > > > > > > While this is
Re: Quickstart Problems
On Fri, 25 Aug 2023 at 22:43, Dan Haywood wrote: > > Hi Maxim, > > with causeway.apache.org (which uses wicket under the covers) we've taken > to keeping our quickstarts [1],[2] as a separate github project ... makes > it easier for us to maintain out of band, and for users to contribute > issues. Just an idea. This might be great idea (since JIRA registration is a bit complicated these days ) :) > > Thx > Dan > > [1] https://github.com/apache/causeway-app-simpleapp > [2] https://github.com/apache/causeway-app-helloworld > > > On Fri, 25 Aug 2023 at 16:39, Maxim Solodovnik wrote: > > > Sounds like we can fix something before 9.15 release :) > > > > I'll try to check it :) > > > > can you please file JIRA here: > > https://issues.apache.org/jira/projects/WICKET ? > > > > On Fri, 25 Aug 2023 at 22:20, Dr. Janko Jochimsen > > wrote: > > > > > > Hi, > > > > > > I am new to Wicket but have some experience with Java and Tapestry. > > Installing the quickstarts I have run into some problems that make me > > wonder how many people are starting with this platform as of 2023? > > > > > > First the facts: > > > I installed the default quickstart 9.14.0 from the > > https://wicket.apache.org/start/quickstart.html as well as the 10.0.0.M1 > > directly via eclipse both into a completely fresh eclipse Version: 2023-06 > > (4.28.0) running under Java 17.0.8.7 from Openlogic. In both versions I > > have got problem 1. and 2. Problem 3. is exclusive on 10.0.0-M1 but this is > > due to the enforcement of Java 17 in Version 10. > > > > > > Now the problems: > > > 1.) There is a simple problem with the keystore > > > > > > In Line 46 of the Start.java the keystore (keystore.p12) is supposed to > > be read. However in the path "\src\test\resources" you will find only a > > file keystore (without the .p12 suffix). That can not work and therefore > > the switch to https breaks if that file is not renamed. After renaming the > > keystore file it worked and I can change to https (at least in 9.14.0 under > > Java 11. > > > > > > 2.) > > > In the path "\src\test\jetty" are four xml definition file how all get a > > > > > > Referenced file contains errors ( > > http://www.eclipse.org/jetty/configure_9_0.dtd). > > > > > > error. > > > > > > I didn't managed to switch this off but it seems to be irrelevant at > > least for the development system > > > > > > > > > 3.) > > > > > > It looks as if the usage of org.eclipse.jetty.util.ssl.SslContextFactory > > is outdated and for Java 17 broken. > > > > > > a.) > > > In Line 58 of the Start.java a SslContextFactory is created by this > > command: > > > > > > SslContextFactory sslContextFactory = new SslContextFactory(); > > > > > > This call is deprecated in Java 11 and causes an error in Java 17. It > > should read: > > > > > > SslContextFactory sslContextFactory = new SslContextFactory.Server(); > > > > > > > > > b.) > > > > > > A little bit more complicated is the problem in line 64 ff > > > > > > It states: > > > ServerConnector https = new ServerConnector(server, new > > SslConnectionFactory( > > > sslContextFactory, "http/1.1"), new HttpConnectionFactory(https_config)); > > > > > > While this is legal in Java 11 but not in Java 17. With 17 you get a > > > > > > The constructor SslConnectionFactory(SslContextFactory, String) is > > undefined > > > > > > error. > > > > > > You can kind of work around it by making an explicit cast > > > > > > ServerConnector https = new ServerConnector(server, new > > SslConnectionFactory( > > > (org.eclipse.jetty.util.ssl.SslContextFactory.Server) sslContextFactory, > > "http/1.1"), new HttpConnectionFactory(https_config)); > > > > > > That works for the http side but it will break if you change to https > > with the following error. > > > > > > [qtp2009787198-27] WARN org.eclipse.jetty.server.HttpChannel - > > handleException / org.eclipse.jetty.http.BadMessageException: 400: Invalid > > SNI > > > > > > > > > I understand that a lot of the old hands work in their production > > environments and do not have any problems on this level but
Re: Quickstart Problems
did it myself: https://issues.apache.org/jira/browse/WICKET-7070 :) On Fri, 25 Aug 2023 at 22:39, Maxim Solodovnik wrote: > > Sounds like we can fix something before 9.15 release :) > > I'll try to check it :) > > can you please file JIRA here: https://issues.apache.org/jira/projects/WICKET > ? > > On Fri, 25 Aug 2023 at 22:20, Dr. Janko Jochimsen > wrote: > > > > Hi, > > > > I am new to Wicket but have some experience with Java and Tapestry. > > Installing the quickstarts I have run into some problems that make me > > wonder how many people are starting with this platform as of 2023? > > > > First the facts: > > I installed the default quickstart 9.14.0 from the > > https://wicket.apache.org/start/quickstart.html as well as the 10.0.0.M1 > > directly via eclipse both into a completely fresh eclipse Version: 2023-06 > > (4.28.0) running under Java 17.0.8.7 from Openlogic. In both versions I > > have got problem 1. and 2. Problem 3. is exclusive on 10.0.0-M1 but this is > > due to the enforcement of Java 17 in Version 10. > > > > Now the problems: > > 1.) There is a simple problem with the keystore > > > > In Line 46 of the Start.java the keystore (keystore.p12) is supposed to be > > read. However in the path "\src\test\resources" you will find only a file > > keystore (without the .p12 suffix). That can not work and therefore the > > switch to https breaks if that file is not renamed. After renaming the > > keystore file it worked and I can change to https (at least in 9.14.0 under > > Java 11. > > > > 2.) > > In the path "\src\test\jetty" are four xml definition file how all get a > > > > Referenced file contains errors > > (http://www.eclipse.org/jetty/configure_9_0.dtd). > > > > error. > > > > I didn't managed to switch this off but it seems to be irrelevant at least > > for the development system > > > > > > 3.) > > > > It looks as if the usage of org.eclipse.jetty.util.ssl.SslContextFactory is > > outdated and for Java 17 broken. > > > > a.) > > In Line 58 of the Start.java a SslContextFactory is created by this command: > > > > SslContextFactory sslContextFactory = new SslContextFactory(); > > > > This call is deprecated in Java 11 and causes an error in Java 17. It > > should read: > > > > SslContextFactory sslContextFactory = new SslContextFactory.Server(); > > > > > > b.) > > > > A little bit more complicated is the problem in line 64 ff > > > > It states: > > ServerConnector https = new ServerConnector(server, new > > SslConnectionFactory( > > sslContextFactory, "http/1.1"), new HttpConnectionFactory(https_config)); > > > > While this is legal in Java 11 but not in Java 17. With 17 you get a > > > > The constructor SslConnectionFactory(SslContextFactory, String) is undefined > > > > error. > > > > You can kind of work around it by making an explicit cast > > > > ServerConnector https = new ServerConnector(server, new > > SslConnectionFactory( > > (org.eclipse.jetty.util.ssl.SslContextFactory.Server) sslContextFactory, > > "http/1.1"), new HttpConnectionFactory(https_config)); > > > > That works for the http side but it will break if you change to https with > > the following error. > > > > [qtp2009787198-27] WARN org.eclipse.jetty.server.HttpChannel - > > handleException / org.eclipse.jetty.http.BadMessageException: 400: Invalid > > SNI > > > > > > I understand that a lot of the old hands work in their production > > environments and do not have any problems on this level but for a newcomer > > it is a bit disappointing to run into a number of problems as soon as you > > load / create a completely untouched quickstart, > > > > Thanks anyway to keep going with this interesting platform. > > > > > > Best > > > > > > Janko > > > > > > This email was scanned by Bitdefender > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > -- > Best regards, > Maxim -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Quickstart Problems
Can you please try to use quickstart from this branch: https://github.com/apache/wicket/tree/quickstart-fix ? (9.15.0-SNAPSHOT so far :))) On Fri, 25 Aug 2023 at 23:34, Maxim Solodovnik wrote: > > On Fri, 25 Aug 2023 at 22:20, Dr. Janko Jochimsen > wrote: > > > > Hi, > > > > I am new to Wicket but have some experience with Java and Tapestry. > > Installing the quickstarts I have run into some problems that make me > > wonder how many people are starting with this platform as of 2023? > > > > First the facts: > > I installed the default quickstart 9.14.0 from the > > https://wicket.apache.org/start/quickstart.html as well as the 10.0.0.M1 > > directly via eclipse both into a completely fresh eclipse Version: 2023-06 > > (4.28.0) running under Java 17.0.8.7 from Openlogic. In both versions I > > have got problem 1. and 2. Problem 3. is exclusive on 10.0.0-M1 but this is > > due to the enforcement of Java 17 in Version 10. > > > > Now the problems: > > 1.) There is a simple problem with the keystore > > > > In Line 46 of the Start.java the keystore (keystore.p12) is supposed to be > > read. However in the path "\src\test\resources" you will find only a file > > keystore (without the .p12 suffix). That can not work and therefore the > > switch to https breaks if that file is not renamed. After renaming the > > keystore file it worked and I can change to https (at least in 9.14.0 under > > Java 11. > > > > 2.) > > In the path "\src\test\jetty" are four xml definition file how all get a > > > > Referenced file contains errors > > (http://www.eclipse.org/jetty/configure_9_0.dtd). > > > > error. > > > > I didn't managed to switch this off but it seems to be irrelevant at least > > for the development system > > According to > https://eclipse.dev/jetty/documentation/jetty-9/index.html#jetty-web-xml-config > > correct URL is http://www.eclipse.org/jetty/configure_9_3.dtd > > I'll update it :) > > > > > > > 3.) > > > > It looks as if the usage of org.eclipse.jetty.util.ssl.SslContextFactory is > > outdated and for Java 17 broken. > > > > a.) > > In Line 58 of the Start.java a SslContextFactory is created by this command: > > > > SslContextFactory sslContextFactory = new SslContextFactory(); > > > > This call is deprecated in Java 11 and causes an error in Java 17. It > > should read: > > > > SslContextFactory sslContextFactory = new SslContextFactory.Server(); > > > > > > b.) > > > > A little bit more complicated is the problem in line 64 ff > > > > It states: > > ServerConnector https = new ServerConnector(server, new > > SslConnectionFactory( > > sslContextFactory, "http/1.1"), new HttpConnectionFactory(https_config)); > > > > While this is legal in Java 11 but not in Java 17. With 17 you get a > > > > The constructor SslConnectionFactory(SslContextFactory, String) is undefined > > > > error. > > > > You can kind of work around it by making an explicit cast > > > > ServerConnector https = new ServerConnector(server, new > > SslConnectionFactory( > > (org.eclipse.jetty.util.ssl.SslContextFactory.Server) sslContextFactory, > > "http/1.1"), new HttpConnectionFactory(https_config)); > > > > That works for the http side but it will break if you change to https with > > the following error. > > > > [qtp2009787198-27] WARN org.eclipse.jetty.server.HttpChannel - > > handleException / org.eclipse.jetty.http.BadMessageException: 400: Invalid > > SNI > > > > > > I understand that a lot of the old hands work in their production > > environments and do not have any problems on this level but for a newcomer > > it is a bit disappointing to run into a number of problems as soon as you > > load / create a completely untouched quickstart, > > > > Thanks anyway to keep going with this interesting platform. > > > > > > Best > > > > > > Janko > > > > > > This email was scanned by Bitdefender > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > -- > Best regards, > Maxim -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Quickstart Problems
On Fri, 25 Aug 2023 at 22:20, Dr. Janko Jochimsen wrote: > > Hi, > > I am new to Wicket but have some experience with Java and Tapestry. > Installing the quickstarts I have run into some problems that make me wonder > how many people are starting with this platform as of 2023? > > First the facts: > I installed the default quickstart 9.14.0 from the > https://wicket.apache.org/start/quickstart.html as well as the 10.0.0.M1 > directly via eclipse both into a completely fresh eclipse Version: 2023-06 > (4.28.0) running under Java 17.0.8.7 from Openlogic. In both versions I have > got problem 1. and 2. Problem 3. is exclusive on 10.0.0-M1 but this is due to > the enforcement of Java 17 in Version 10. > > Now the problems: > 1.) There is a simple problem with the keystore > > In Line 46 of the Start.java the keystore (keystore.p12) is supposed to be > read. However in the path "\src\test\resources" you will find only a file > keystore (without the .p12 suffix). That can not work and therefore the > switch to https breaks if that file is not renamed. After renaming the > keystore file it worked and I can change to https (at least in 9.14.0 under > Java 11. > > 2.) > In the path "\src\test\jetty" are four xml definition file how all get a > > Referenced file contains errors > (http://www.eclipse.org/jetty/configure_9_0.dtd). > > error. > > I didn't managed to switch this off but it seems to be irrelevant at least > for the development system According to https://eclipse.dev/jetty/documentation/jetty-9/index.html#jetty-web-xml-config correct URL is http://www.eclipse.org/jetty/configure_9_3.dtd I'll update it :) > > > 3.) > > It looks as if the usage of org.eclipse.jetty.util.ssl.SslContextFactory is > outdated and for Java 17 broken. > > a.) > In Line 58 of the Start.java a SslContextFactory is created by this command: > > SslContextFactory sslContextFactory = new SslContextFactory(); > > This call is deprecated in Java 11 and causes an error in Java 17. It should > read: > > SslContextFactory sslContextFactory = new SslContextFactory.Server(); > > > b.) > > A little bit more complicated is the problem in line 64 ff > > It states: > ServerConnector https = new ServerConnector(server, new SslConnectionFactory( > sslContextFactory, "http/1.1"), new HttpConnectionFactory(https_config)); > > While this is legal in Java 11 but not in Java 17. With 17 you get a > > The constructor SslConnectionFactory(SslContextFactory, String) is undefined > > error. > > You can kind of work around it by making an explicit cast > > ServerConnector https = new ServerConnector(server, new SslConnectionFactory( > (org.eclipse.jetty.util.ssl.SslContextFactory.Server) sslContextFactory, > "http/1.1"), new HttpConnectionFactory(https_config)); > > That works for the http side but it will break if you change to https with > the following error. > > [qtp2009787198-27] WARN org.eclipse.jetty.server.HttpChannel - > handleException / org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI > > > I understand that a lot of the old hands work in their production > environments and do not have any problems on this level but for a newcomer it > is a bit disappointing to run into a number of problems as soon as you load / > create a completely untouched quickstart, > > Thanks anyway to keep going with this interesting platform. > > > Best > > > Janko > > > This email was scanned by Bitdefender > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Quickstart Problems
On Fri, 25 Aug 2023 at 22:57, Maxim Solodovnik wrote: > > On Fri, 25 Aug 2023 at 22:20, Dr. Janko Jochimsen > wrote: > > > > Hi, > > > > I am new to Wicket but have some experience with Java and Tapestry. > > Installing the quickstarts I have run into some problems that make me > > wonder how many people are starting with this platform as of 2023? > > > > First the facts: > > I installed the default quickstart 9.14.0 from the > > https://wicket.apache.org/start/quickstart.html as well as the 10.0.0.M1 > > directly via eclipse both into a completely fresh eclipse Version: 2023-06 > > (4.28.0) running under Java 17.0.8.7 from Openlogic. In both versions I > > have got problem 1. and 2. Problem 3. is exclusive on 10.0.0-M1 but this is > > due to the enforcement of Java 17 in Version 10. > > > > Now the problems: > > 1.) There is a simple problem with the keystore > > > > In Line 46 of the Start.java the keystore (keystore.p12) is supposed to be > > read. However in the path "\src\test\resources" you will find only a file > > keystore (without the .p12 suffix). That can not work and therefore the > > switch to https breaks if that file is not renamed. After renaming the > > keystore file it worked and I can change to https (at least in 9.14.0 under > > Java 11. > > Just tried these steps: > > 1) generate project: `mvn > org.apache.maven.plugins:maven-archetype-plugin:2.4:generate > -DarchetypeGroupId=org.apache.wicket > -DarchetypeArtifactId=wicket-archetype-quickstart > -DarchetypeVersion=9.15.0-SNAPSHOT -DgroupId=org.apache.solomax > -DartifactId=test1 > -DarchetypeRepository=https://repository.apache.org/content/repositories/snapshots/ > -DinteractiveMode=false` > > 2) `cd test1` > > 3) `mvn jetty:run` > > 4) In browser open https://localhost:8443/ > > certificate is invalid (expected) > The page was displayed, no errors in console > > wicket 9.15.0-SNAPSHOT (build locally from sources) > Ubuntu 22.04 > Apache Maven 3.9.1 (2e178502fcdbffc201671fb2537d0cb4b4cc58f8) > Maven home: /opt/maven > Java version: 17.0.8, vendor: Private Build, runtime: > /usr/lib/jvm/java-17-openjdk-amd64 > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "5.15.0-79-generic", arch: "amd64", family: "unix" > > Tried with 9.14 (official) > > Same result > > What am I doing wrong? Got it :) `mvn jetty:run` works as expected :) Debugging Start.java doesn't :) I'll fix it :) > > > > > > 2.) > > In the path "\src\test\jetty" are four xml definition file how all get a > > > > Referenced file contains errors > > (http://www.eclipse.org/jetty/configure_9_0.dtd). > > > > error. > > > > I didn't managed to switch this off but it seems to be irrelevant at least > > for the development system > > > > > > 3.) > > > > It looks as if the usage of org.eclipse.jetty.util.ssl.SslContextFactory is > > outdated and for Java 17 broken. > > > > a.) > > In Line 58 of the Start.java a SslContextFactory is created by this command: > > > > SslContextFactory sslContextFactory = new SslContextFactory(); > > > > This call is deprecated in Java 11 and causes an error in Java 17. It > > should read: > > > > SslContextFactory sslContextFactory = new SslContextFactory.Server(); > > > > > > b.) > > > > A little bit more complicated is the problem in line 64 ff > > > > It states: > > ServerConnector https = new ServerConnector(server, new > > SslConnectionFactory( > > sslContextFactory, "http/1.1"), new HttpConnectionFactory(https_config)); > > > > While this is legal in Java 11 but not in Java 17. With 17 you get a > > > > The constructor SslConnectionFactory(SslContextFactory, String) is undefined > > > > error. > > > > You can kind of work around it by making an explicit cast > > > > ServerConnector https = new ServerConnector(server, new > > SslConnectionFactory( > > (org.eclipse.jetty.util.ssl.SslContextFactory.Server) sslContextFactory, > > "http/1.1"), new HttpConnectionFactory(https_config)); > > > > That works for the http side but it will break if you change to https with > > the following error. > > > > [qtp2009787198-27] WARN org.eclipse.jetty.server.HttpChannel - > > handleException / org.eclipse.jetty.http.BadMessageException: 400: Invalid > > SNI > > > > > > I understand that a lot
Re: Quickstart Problems
On Fri, 25 Aug 2023 at 22:20, Dr. Janko Jochimsen wrote: > > Hi, > > I am new to Wicket but have some experience with Java and Tapestry. > Installing the quickstarts I have run into some problems that make me wonder > how many people are starting with this platform as of 2023? > > First the facts: > I installed the default quickstart 9.14.0 from the > https://wicket.apache.org/start/quickstart.html as well as the 10.0.0.M1 > directly via eclipse both into a completely fresh eclipse Version: 2023-06 > (4.28.0) running under Java 17.0.8.7 from Openlogic. In both versions I have > got problem 1. and 2. Problem 3. is exclusive on 10.0.0-M1 but this is due to > the enforcement of Java 17 in Version 10. > > Now the problems: > 1.) There is a simple problem with the keystore > > In Line 46 of the Start.java the keystore (keystore.p12) is supposed to be > read. However in the path "\src\test\resources" you will find only a file > keystore (without the .p12 suffix). That can not work and therefore the > switch to https breaks if that file is not renamed. After renaming the > keystore file it worked and I can change to https (at least in 9.14.0 under > Java 11. Just tried these steps: 1) generate project: `mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeGroupId=org.apache.wicket -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=9.15.0-SNAPSHOT -DgroupId=org.apache.solomax -DartifactId=test1 -DarchetypeRepository=https://repository.apache.org/content/repositories/snapshots/ -DinteractiveMode=false` 2) `cd test1` 3) `mvn jetty:run` 4) In browser open https://localhost:8443/ certificate is invalid (expected) The page was displayed, no errors in console wicket 9.15.0-SNAPSHOT (build locally from sources) Ubuntu 22.04 Apache Maven 3.9.1 (2e178502fcdbffc201671fb2537d0cb4b4cc58f8) Maven home: /opt/maven Java version: 17.0.8, vendor: Private Build, runtime: /usr/lib/jvm/java-17-openjdk-amd64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.15.0-79-generic", arch: "amd64", family: "unix" Tried with 9.14 (official) Same result What am I doing wrong? > > 2.) > In the path "\src\test\jetty" are four xml definition file how all get a > > Referenced file contains errors > (http://www.eclipse.org/jetty/configure_9_0.dtd). > > error. > > I didn't managed to switch this off but it seems to be irrelevant at least > for the development system > > > 3.) > > It looks as if the usage of org.eclipse.jetty.util.ssl.SslContextFactory is > outdated and for Java 17 broken. > > a.) > In Line 58 of the Start.java a SslContextFactory is created by this command: > > SslContextFactory sslContextFactory = new SslContextFactory(); > > This call is deprecated in Java 11 and causes an error in Java 17. It should > read: > > SslContextFactory sslContextFactory = new SslContextFactory.Server(); > > > b.) > > A little bit more complicated is the problem in line 64 ff > > It states: > ServerConnector https = new ServerConnector(server, new SslConnectionFactory( > sslContextFactory, "http/1.1"), new HttpConnectionFactory(https_config)); > > While this is legal in Java 11 but not in Java 17. With 17 you get a > > The constructor SslConnectionFactory(SslContextFactory, String) is undefined > > error. > > You can kind of work around it by making an explicit cast > > ServerConnector https = new ServerConnector(server, new SslConnectionFactory( > (org.eclipse.jetty.util.ssl.SslContextFactory.Server) sslContextFactory, > "http/1.1"), new HttpConnectionFactory(https_config)); > > That works for the http side but it will break if you change to https with > the following error. > > [qtp2009787198-27] WARN org.eclipse.jetty.server.HttpChannel - > handleException / org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI > > > I understand that a lot of the old hands work in their production > environments and do not have any problems on this level but for a newcomer it > is a bit disappointing to run into a number of problems as soon as you load / > create a completely untouched quickstart, > > Thanks anyway to keep going with this interesting platform. > > > Best > > > Janko > > > This email was scanned by Bitdefender > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Quickstart Problems
Sounds like we can fix something before 9.15 release :) I'll try to check it :) can you please file JIRA here: https://issues.apache.org/jira/projects/WICKET ? On Fri, 25 Aug 2023 at 22:20, Dr. Janko Jochimsen wrote: > > Hi, > > I am new to Wicket but have some experience with Java and Tapestry. > Installing the quickstarts I have run into some problems that make me wonder > how many people are starting with this platform as of 2023? > > First the facts: > I installed the default quickstart 9.14.0 from the > https://wicket.apache.org/start/quickstart.html as well as the 10.0.0.M1 > directly via eclipse both into a completely fresh eclipse Version: 2023-06 > (4.28.0) running under Java 17.0.8.7 from Openlogic. In both versions I have > got problem 1. and 2. Problem 3. is exclusive on 10.0.0-M1 but this is due to > the enforcement of Java 17 in Version 10. > > Now the problems: > 1.) There is a simple problem with the keystore > > In Line 46 of the Start.java the keystore (keystore.p12) is supposed to be > read. However in the path "\src\test\resources" you will find only a file > keystore (without the .p12 suffix). That can not work and therefore the > switch to https breaks if that file is not renamed. After renaming the > keystore file it worked and I can change to https (at least in 9.14.0 under > Java 11. > > 2.) > In the path "\src\test\jetty" are four xml definition file how all get a > > Referenced file contains errors > (http://www.eclipse.org/jetty/configure_9_0.dtd). > > error. > > I didn't managed to switch this off but it seems to be irrelevant at least > for the development system > > > 3.) > > It looks as if the usage of org.eclipse.jetty.util.ssl.SslContextFactory is > outdated and for Java 17 broken. > > a.) > In Line 58 of the Start.java a SslContextFactory is created by this command: > > SslContextFactory sslContextFactory = new SslContextFactory(); > > This call is deprecated in Java 11 and causes an error in Java 17. It should > read: > > SslContextFactory sslContextFactory = new SslContextFactory.Server(); > > > b.) > > A little bit more complicated is the problem in line 64 ff > > It states: > ServerConnector https = new ServerConnector(server, new SslConnectionFactory( > sslContextFactory, "http/1.1"), new HttpConnectionFactory(https_config)); > > While this is legal in Java 11 but not in Java 17. With 17 you get a > > The constructor SslConnectionFactory(SslContextFactory, String) is undefined > > error. > > You can kind of work around it by making an explicit cast > > ServerConnector https = new ServerConnector(server, new SslConnectionFactory( > (org.eclipse.jetty.util.ssl.SslContextFactory.Server) sslContextFactory, > "http/1.1"), new HttpConnectionFactory(https_config)); > > That works for the http side but it will break if you change to https with > the following error. > > [qtp2009787198-27] WARN org.eclipse.jetty.server.HttpChannel - > handleException / org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI > > > I understand that a lot of the old hands work in their production > environments and do not have any problems on this level but for a newcomer it > is a bit disappointing to run into a number of problems as soon as you load / > create a completely untouched quickstart, > > Thanks anyway to keep going with this interesting platform. > > > Best > > > Janko > > > This email was scanned by Bitdefender > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 10.0.0-M1 Released
WicketStuff core 10.0.0-M1 based on Apache Wicket 10.0.0-M1 is released and soon will be available at Maven Central! Maxim Solodovnik (24): wicket-webjars is updated Fixes Issue #743: JSON.stringify is used instead of $.toJson Deprecated code is removed closure-compiler updated to test build Debugging secrets Testing environments Testing environments Testing environments Testing environments: clean-up Attempt to fix CI build Another attempt to fix CI build Deprecated code is removed Dependencies are updated Dependencies are updated; jetty:run is fixed Build should be fixed maven-deploy-plugin is updated Jetty-uber is dropped Dependencies are updated Tests are fixed Portlets should be fixed; Deprecations are cleaned-up Code clean-up Dependencies are updated SNAPSHOT dependency is removed, duplicated wicket-native-websocket-javax is removed Portlets are dropped; wicketstuff-core-10.0.0-M1 released dependabot[bot] (3): Bump spring-core from 6.0.4 to 6.0.7 (#746) Bump log4j-core (#745) Bump hazelcast in /datastores-parent/datastore-hazelcast (#751) Urs Joss (2): bump jasperreports to 6.20.3 and explicitly depend on openpdf (#749) bump jasperreports to 6.20.4 and fall back to transitive dependency on openpdf (#750) Francesco Chicchiriccò (1): Upgrading to Wicket 10, Spring 6 and related Jakarta EE specs (#741) Martin Tzvetanov Grigorov (1): Update jQuery from 3.6.0 to 3.6.4 The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff v10?
I'm back :) going to create release today :) You can track progress here https://github.com/wicketstuff/core/issues/752 On Tue, 4 Jul 2023 at 02:21, Shawn McKinney wrote: > > > > On Jul 3, 2023, at 11:26 AM, Maxim Solodovnik wrote: > > > > Hello Shawn, > > > > I'll get back from vacation in a week or so and will create a release :) > > > > Or someone might create release earlier :) > > > > Hey Maxim, > > That will be fine for me. Thanks for replying and have a nice time on your > break. > > Best > > — > Shawn > > > > from mobile (sorry for typos ;) > > > > > > On Mon, Jul 3, 2023, 18:44 Shawn McKinney wrote: > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff v10?
Hello Shawn, I'll get back from vacation in a week or so and will create a release :) Or someone might create release earlier :) from mobile (sorry for typos ;) On Mon, Jul 3, 2023, 18:44 Shawn McKinney wrote: > Hello, > > Any projections on when wicketstuff for v10.x will be available? > > Thanks! > > — > Shawn > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Plans for Wicket 10 Release
Should be fixed with this: https://github.com/apache/wicket/pull/591 :) On Tue, 30 May 2023 at 22:16, Maxim Solodovnik wrote: > > > > from mobile (sorry for typos ;) > > > On Tue, May 30, 2023, 20:05 Jeroen Steenbeeke > wrote: >> >> The current wicket-commons-fileupload 10.0.0-M1-SNAPSHOT jar in the Apache >> snapshots repo duplicates classes from commons-io, Jakarta Servlet and >> SLF4J and is triggering my Maven Enforcer's BanDuplicateClasses rule. > > > Sounds interesting > Could you share details? :) > >> >> Op za 27 mei 2023 om 21:53 schreef Martin Grigorov : >> >> > On Sat, May 27, 2023 at 8:18 PM smallufo wrote: >> > >> > > Hi >> > > Where can I get wicket-10 snapshot ? >> > > >> > >> > >> > https://github.com/apache/wicket/blob/master/archetypes/quickstart/src/main/resources/archetype-resources/pom.xml#L175-L186 >> > >> > I cannot find it in mvnrepository.com ... >> > >> > I've upgrade all subsystems from javax to jakarta , and spring 5 to spring >> > 6 >> > > But a lot of incompatibility issues are in wicket 9 >> > > Since it has no major issues , how about releasing it ASAP ? >> > > Thanks. >> > > >> > > >> > > János Cserép 於 2023年5月25日 週四 下午3:51寫道： >> > > >> > > > Just a thought... >> > > > >> > > > I've been using Wicket 10 snapshot builds in production for over a year >> > > now >> > > > with latest Spring and Jakarta libs without any major issues, so if >> > that >> > > is >> > > > an option for you, go ahead. You can mitigate risks by creating release >> > > > from a known git rev yourself if your release process does not like >> > > > SNAPSHOT dependencies. >> > > > >> > > > j >> > > > >> > > > >> > > > On Thu, 25 May 2023 at 09:15, Tony Tkacik > > > > .invalid> >> > > > wrote: >> > > > >> > > > > Hi, >> > > > > I would like to ask about your timeline / plans regarding release of >> > > > > Wicket 10? >> > > > > >> > > > > We are in process of upgrading our open-source project midPoint to >> > > latest >> > > > > Spring releases and that requires Wicket to be updated to version 10 >> > > > > in order to support Spring 6. >> > > > > >> > > > > Thanks, >> > > > > Anton Tkacik >> > > > > >> > > > >> > > >> > >> >> >> -- >> Jeroen Steenbeeke -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Plans for Wicket 10 Release
from mobile (sorry for typos ;) On Tue, May 30, 2023, 20:05 Jeroen Steenbeeke wrote: > The current wicket-commons-fileupload 10.0.0-M1-SNAPSHOT jar in the Apache > snapshots repo duplicates classes from commons-io, Jakarta Servlet and > SLF4J and is triggering my Maven Enforcer's BanDuplicateClasses rule. > Sounds interesting Could you share details? :) > Op za 27 mei 2023 om 21:53 schreef Martin Grigorov : > > > On Sat, May 27, 2023 at 8:18 PM smallufo wrote: > > > > > Hi > > > Where can I get wicket-10 snapshot ? > > > > > > > > > > https://github.com/apache/wicket/blob/master/archetypes/quickstart/src/main/resources/archetype-resources/pom.xml#L175-L186 > > > > I cannot find it in mvnrepository.com ... > > > > I've upgrade all subsystems from javax to jakarta , and spring 5 to > spring > > 6 > > > But a lot of incompatibility issues are in wicket 9 > > > Since it has no major issues , how about releasing it ASAP ? > > > Thanks. > > > > > > > > > János Cserép 於 2023年5月25日 週四 下午3:51寫道： > > > > > > > Just a thought... > > > > > > > > I've been using Wicket 10 snapshot builds in production for over a > year > > > now > > > > with latest Spring and Jakarta libs without any major issues, so if > > that > > > is > > > > an option for you, go ahead. You can mitigate risks by creating > release > > > > from a known git rev yourself if your release process does not like > > > > SNAPSHOT dependencies. > > > > > > > > j > > > > > > > > > > > > On Thu, 25 May 2023 at 09:15, Tony Tkacik > > > .invalid> > > > > wrote: > > > > > > > > > Hi, > > > > > I would like to ask about your timeline / plans regarding release > of > > > > > Wicket 10? > > > > > > > > > > We are in process of upgrading our open-source project midPoint to > > > latest > > > > > Spring releases and that requires Wicket to be updated to version > 10 > > > > > in order to support Spring 6. > > > > > > > > > > Thanks, > > > > > Anton Tkacik > > > > > > > > > > > > > > > > > -- > Jeroen Steenbeeke >
[ANNOUNCE] WicketStuff 9.14.0 Released
WicketStuff core 9.14.0 based on Apache Wicket 9.14.0 is released and soon will be available at Maven Central! Maxim Solodovnik (6): Switching to the next development version Hazelcast is updated Dependencies are updated Code clean-up Dependencies are updated wicketstuff-core-9.14.0 release Urs Joss (2): bump jasperreports to 6.20.3 and explicitly depend on openpdf (#749) bump jasperreports to 6.20.4 and fall back to transitive dependency on openpdf (#750) The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 8.15.0 Released
WicketStuff core 8.15.0 based on Apache Wicket 8.15.0 is released and soon will be available at Maven Central! Maxim Solodovnik (3): Switching to the next development version Versions are updated WicketStuff Core 8.15.0 build is successful The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.13.0 Released
WicketStuff core 9.13.0 based on Apache Wicket 9.13.0 is released and soon will be available at Maven Central! Maxim Solodovnik (16): Switching to the next development version Dependencies are updated Dependencies are updated, vulnerable testng is removed Dependencies are updated Fixes Issue #743: JSON.stringify is used instead of $.toJson Attempt to fix CI build Another attempt to fix CI build Deprecated code is removed Dependencies are updated Fixing CI build Dependencies are updated, tests are fixed More dependencies are updated; Attempt to fix CI build maven-deploy-plugin is updated Tests are fixed Dependencies are updated wicketstuff-core-9.13.0 is released Martin Tzvetanov Grigorov (1): Build only when wicket-9.x branch is modified muecke87 (1): fixes issue #737 (#738) The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 10 + Commons FileUpload
It seems Gary preparing release 2.0.0 On Mon, 3 Apr 2023 at 14:49, Francesco Chicchiriccò wrote: > > I see several recent commits on FileUpload, however: > > https://github.com/apache/commons-fileupload/commits/master > > and AFAICT Wicket 10.0.0-M1-SNAPSHOT depends on Commons FileUpload > 2.0-SNAPSHOT no? > > Last Friday all was working on Syncope side as well: > > https://github.com/apache/syncope/commit/c65cbde960768ca370a6757d423ccb2c013b4704 > > Regards. > > On 2023/04/03 07:33:57 Martin Grigorov wrote: > > Hi Francesco, > > > > There are no new commits in master since Mar 24 - > > https://github.com/apache/wicket/commits/master. > > The PR about commons-fileupload2 is not yet merged to master - > > https://github.com/apache/wicket/pull/565. > > I see no reasons in Wicket for this exception ... > > > > One possible way to break the -SNAPSHOTs at Nexus is someone (Maxim ?!) to > > `mvn deploy`-ed PR 565 from his dev machine, but I doubt it. > > > > > > On Mon, Apr 3, 2023 at 10:04 AM Francesco Chicchiriccò > > wrote: > > > > > Hi there, > > > FTR this morning I've started receiving the following exception from > > > Syncope Console 4.0.0-SNAPSHOT, based on Wicket 10.0.0-M1-SNAPSHOT: > > > > > > java.lang.ClassNotFoundException: > > > org.apache.commons.fileupload2.pub.FileSizeLimitExceededException > > > at > > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1437) > > > at > > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1245) > > > at > > > org.apache.wicket.protocol.http.servlet.ServletWebRequest.newMultipartWebRequest(ServletWebRequest.java:431) > > > at > > > org.apache.wicket.markup.html.form.Form.handleMultiPart(Form.java:1461) > > > at > > > org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:793) > > > at > > > org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:202) > > > at > > > org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:139) > > > at > > > org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:630) > > > at > > > org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:300) > > > at > > > org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:274) > > > at > > > org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:222) > > > at > > > org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:202) > > > at > > > org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:910) > > > at > > > org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:63) > > > at > > > org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:294) > > > at > > > org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:255) > > > at > > > org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:277) > > > at org.apache.wicket.protocol.ws > > > .AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:67) > > > at > > > org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:208) > > > at > > > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:307) > > > > > > Regards. > > > > > > On 2023/03/31 07:55:27 Andrea Del Bene wrote: > > > > Habemus (almost...) FileUpload 2.0! > > > > https://lists.apache.org/thread/kknw9bn2t8dzpbwojpg2hcqbgqf1qyzc > > > > Thanks again to Maxim, although I'm sorry he had to spend time working > > > > to > > > > the PR > > > > > > > > > > > > > > > > > > > > On Sat, Mar 25, 2023 at 5:02 PM Greb Lindqvist > > > > > > > wrote: > > > > > > > > > Thank you! > > > > > > > > > > On Sat, Mar 25, 2023 at 6:05 AM Maxim Solodovnik > > > > > > > > wrote: > > > > >
Re: Wicket 10 + Commons FileUpload
On Mon, 3 Apr 2023 at 14:39, Martin Grigorov wrote: > > https://repository.apache.org/content/repositories/snapshots/org/apache/wicket/wicket-util/10.0.0-M1-SNAPSHOT/wicket-util-10.0.0-M1-20230324.080605-197.pom > is the last version and it contains the dependency to commons-fileupload2 > > On Mon, Apr 3, 2023 at 10:33 AM Martin Grigorov > wrote: > > > Hi Francesco, > > > > There are no new commits in master since Mar 24 - > > https://github.com/apache/wicket/commits/master. > > The PR about commons-fileupload2 is not yet merged to master - > > https://github.com/apache/wicket/pull/565. > > I see no reasons in Wicket for this exception ... > > > > One possible way to break the -SNAPSHOTs at Nexus is someone (Maxim ?!) to > > `mvn deploy`-ed PR 565 from his dev machine, but I doubt it. It's not me :))) Another option: local `mvn install` of wicket and/or commons-fileupload2 I would clean ~/.m2/repository/...coordinates... > > > > > > On Mon, Apr 3, 2023 at 10:04 AM Francesco Chicchiriccò < > > ilgro...@apache.org> wrote: > > > >> Hi there, > >> FTR this morning I've started receiving the following exception from > >> Syncope Console 4.0.0-SNAPSHOT, based on Wicket 10.0.0-M1-SNAPSHOT: > >> > >> java.lang.ClassNotFoundException: > >> org.apache.commons.fileupload2.pub.FileSizeLimitExceededException > >> at > >> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1437) > >> at > >> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1245) > >> at > >> org.apache.wicket.protocol.http.servlet.ServletWebRequest.newMultipartWebRequest(ServletWebRequest.java:431) > >> at > >> org.apache.wicket.markup.html.form.Form.handleMultiPart(Form.java:1461) > >> at > >> org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:793) > >> at > >> org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:202) > >> at > >> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:139) > >> at > >> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:630) > >> at > >> org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:300) > >> at > >> org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:274) > >> at > >> org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:222) > >> at > >> org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:202) > >> at > >> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:910) > >> at > >> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:63) > >> at > >> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:294) > >> at > >> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:255) > >> at > >> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:277) > >> at org.apache.wicket.protocol.ws > >> .AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:67) > >> at > >> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:208) > >> at > >> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:307) > >> > >> Regards. > >> > >> On 2023/03/31 07:55:27 Andrea Del Bene wrote: > >> > Habemus (almost...) FileUpload 2.0! > >> > https://lists.apache.org/thread/kknw9bn2t8dzpbwojpg2hcqbgqf1qyzc > >> > Thanks again to Maxim, although I'm sorry he had to spend time working > >> to > >> > the PR > >> > > >> > > >> > > >> > > >> > On Sat, Mar 25, 2023 at 5:02 PM Greb Lindqvist < > >> greb.lindqv...@gmail.com> > >> > wrote: > >> > > >> > > Thank you! > >> > > > >> > > On Sat, Mar 25, 2023 at 6:05 AM Maxim Solodovnik < > >> solomax...@gmail.com> > >> > > wrote: > >> > > > >> > > > https://githu
Re: Wicket 10 + Commons FileUpload
Always better to have plan b :) from mobile (sorry for typos ;) On Fri, Mar 31, 2023, 14:57 Andrea Del Bene wrote: > Habemus (almost...) FileUpload 2.0! > https://lists.apache.org/thread/kknw9bn2t8dzpbwojpg2hcqbgqf1qyzc > Thanks again to Maxim, although I'm sorry he had to spend time working to > the PR > > > > > On Sat, Mar 25, 2023 at 5:02 PM Greb Lindqvist > wrote: > > > Thank you! > > > > On Sat, Mar 25, 2023 at 6:05 AM Maxim Solodovnik > > wrote: > > > > > https://github.com/apache/wicket/pull/565 :)) > > > > > > On Thu, 23 Mar 2023 at 19:49, Martin Grigorov > > > wrote: > > > > > > > > Hi, > > > > > > > > The plan is to copy the fileupload classes in Wicket. > > > > Do you want to help with a PR ? > > > > Just create a new Maven module, e.g. wicket-commons-fileupload, and > > copy > > > > the Jakarta related classes into org/apache/wicket/commons/fileupload > > > > package, i.e. to shade them. > > > > Then update wicket-core to make use of the new module and classes. > > > > > > > > On Thu, Mar 23, 2023 at 1:46 PM Greb Lindqvist < > > greb.lindqv...@gmail.com > > > > > > > > wrote: > > > > > > > > > Hello again, > > > > > > > > > > Like you, I've been watching > > > > > > > > > https://issues.apache.org/jira/projects/FILEUPLOAD/issues/FILEUPLOAD-309 > > > > > > > > > > If the FileUpload maintainers continue to be unresponsive, does the > > > Wicket > > > > > team have a plan? > > > > > Are you willing to wait indefinitely or might you commit to an > > > alternative? > > > > > If the latter, do you have a feel for when that might be? > > > > > > > > > > Thanks for any info. > > > > > > > > > > > > > > > > > -- > > > Best regards, > > > Maxim > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > -- > Andrea Del Bene. > Apache Wicket committer. >
Re: Wicket 10 + Commons FileUpload
https://github.com/apache/wicket/pull/565 :)) On Thu, 23 Mar 2023 at 19:49, Martin Grigorov wrote: > > Hi, > > The plan is to copy the fileupload classes in Wicket. > Do you want to help with a PR ? > Just create a new Maven module, e.g. wicket-commons-fileupload, and copy > the Jakarta related classes into org/apache/wicket/commons/fileupload > package, i.e. to shade them. > Then update wicket-core to make use of the new module and classes. > > On Thu, Mar 23, 2023 at 1:46 PM Greb Lindqvist > wrote: > > > Hello again, > > > > Like you, I've been watching > > https://issues.apache.org/jira/projects/FILEUPLOAD/issues/FILEUPLOAD-309 > > > > If the FileUpload maintainers continue to be unresponsive, does the Wicket > > team have a plan? > > Are you willing to wait indefinitely or might you commit to an alternative? > > If the latter, do you have a feel for when that might be? > > > > Thanks for any info. > > -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: FormComponent and FormComponentPanel ClassCast Issue
Maybe you can create quickstart? On Mon, 30 Jan 2023 at 08:58, Eric Hamel wrote: > > Good evening, > > Does anyone have any insight on this ? > > ———- > Eric Hamel > Senior Project Manager > Albany ITG > 528-697-4503 > > > On Jan 23, 2023, at 10:31 AM, Eric Hamel wrote: > > > > The hierarchy is DocumentSearchPanel extends BootstrapGenericPanel -> > > BodyPanel extends GenericPanel -> BootstrapForm -> FormGroup -> > > ClassificationPanel. > > > > > > ClassificationPanel is an anonymous class of DocumentSearchPanel. > > > >> On Jan 23, 2023, at 10:19 AM, Martin Grigorov wrote: > >> > >> Hi, > >> > >>> On Mon, Jan 23, 2023 at 5:09 PM Eric Hamel > >>> wrote: > >>> > >>> Good morning, > >>> > >>> We are running into intermittent issues on our WebSphere 8.5 environment. > >>> The server keeps crashing and we see no cause in our logs. With that said, > >>> admins have seen the following error in our logs and I can’t make sense > >>> out > >>> of it. > >>> > >>> 07:48:51.632 ERROR [CVIENS | 10.79.49.41 | 5uRaDK6Hu4gj0ABIXyNTo76] > >>> o.a.wicket.DefaultExceptionMapper [DefaultExceptionMapper.java:170] - > >>> Unexpected error occurred > >>> java.lang.ClassCastException: > >>> gov.osc.ouf.web.components.document.search.DocumentSearchPanel$ClassificationsPanel$1 > >>> incompatible with org.apache.wicket.markup.html.form.FormComponent > >>> at > >>> de.agilecoders.wicket.core.markup.html.bootstrap.form.FormGroup.findFormComponents(FormGroup.java:255) > >>> ~[wicket-bootstrap-core-0.9.22.jar:0.9.22] > >>> at > >>> de.agilecoders.wicket.core.markup.html.bootstrap.form.FormGroup.onInitialize(FormGroup.java:175) > >>> ~[wicket-bootstrap-core-0.9.22.jar:0.9.22] > >>> at > >>> org.apache.wicket.Component.fireInitialize(Component.java:877) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.MarkupContainer$3.component(MarkupContainer.java:967) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.MarkupContainer$3.component(MarkupContainer.java:963) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:144) > >>> ~[wicket-util-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162) > >>> ~[wicket-util-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162) > >>> ~[wicket-util-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162) > >>> ~[wicket-util-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:123) > >>> ~[wicket-util-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:192) > >>> ~[wicket-util-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:875) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.MarkupContainer.internalInitialize(MarkupContainer.java:962) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at org.apache.wicket.Page.isPageStateless(Page.java:463) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.core.request.mapper.AbstractBookmarkableMapper.getPageInfo(AbstractBookmarkableMapper.java:465) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.core.request.mapper.AbstractBookmarkableMapper.mapHandler(AbstractBookmarkableMapper.java:409) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.core.request.mapper.MountedMapper.mapHandler(MountedMapper.java:395) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.request.mapper.CompoundRequestMapper.mapHandler(CompoundRequestMapper.java:215) > >>> ~[wicket-request-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.request.cycle.RequestCycle.mapUrlFor(RequestCycle.java:429) > >>> [wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:281) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:890) > >>> ~[wicket-core-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) > >>> ~[wicket-request-6.24.0.jar:6.24.0] > >>> at > >>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261) > >>> [wicket-core-6.24.0.jar:6.24.0] > >>> at > >>>
Re: Wicket on low end hardware
You can render components, not just pages
According to the list
You can create the list of all HTML files, find correspondent Java files
and try to render them
from mobile (sorry for typos ;)
On Fri, Jan 6, 2023, 01:20 Chris Colman
wrote:
> In my case I have lots of modal forms (using Wicketstuff ModalX) that
> can be potentially opened by the user.
>
> Doing a 'pre-fetch' of each page won't 'pre-warm' the markup cache for
> all of those modal forms as the page markup has no reference to the
> modal form contents/markup as it is using ModalX's generic modal dialog
> feature so there's no need to specify which form you wish to open in the
> markup of the page that will open it.
>
> I wonder if it would be possible to develop a 'parse all markup' that
> would pick up the markup for these forms as well, not just for the pages.
>
> On 5/01/2023 12:31 am, Martin Grigorov wrote:
> > On Wed, Jan 4, 2023 at 2:48 PM wrote:
> >
> >> Hi Anna,
> >>
> >> I attempted this, and ended up with a method like this:
> >>
> >> private void preloadPages(Collection>
> >> pages) {
> >> final Supplier oldSessionStoreProvider =
> >> getSessionStoreProvider();
> >>
> >> try {
> >> setSessionStoreProvider(() -> new MockSessionStore());
> >>
> >> final RequestCycle rc = createRequestCycle(new MockWebRequest(new
> >> Url()), new MockWebResponse());
> >> ThreadContext.setRequestCycle(rc);
> >>
> >> for (Class p : pages)
> >> ComponentRenderer.renderPage(new PageProvider(p));
> >> }
> >> finally {
> >> setSessionStoreProvider(oldSessionStoreProvider);
> >> }
> >> }
> >>
> >> Which I have not been able to test on more than one page yet, because I
> >> still need to implement something to render my other pages with an
> >> AuthenticatedWebSession. My login page's first load time has been
> >> reduced to about 10% of what it was though.
> >>
> >> I call that method from app.init().
> >>
> >> I have some doubts over Martin's claim that it is possible to do this on
> >> a different thread. As you may notice, I had to change the
> >> SessionStoreProvider to make this work. If I am correct that means that
> >> as long as this method runs, all sessions will be handled by the
> >> MockSessionStore.
> >>
> >> Stan
> >>
> >>
> >>
> >>
> >> Anna Eileen Eileen schreef op 2023-01-04 01:22:
> >>
> >>> Dear Martin
> >>>
> >>> I don't know how to do "pre-touch", do you have any example?
> >>>
> >>> From: Martin Terra
> >>> Date: Tuesday, January 3, 2023 at 11:37 PM
> >>> To:s...@stantastic.nl
> >>> Cc:users@wicket.apache.org
> >>> Subject: Re: Wicket on low end hardware
> >>> Just a note, you don't need to make the startup "pre-touching" process
> >>> a
> >>> blocking one so that if a user were to interact with the app, they
> >>> could do
> >>> so while startup pretouch is doing its thing.
> >>>
> >>> And you could profile whether you want to do the pre-touch in single
> >>> thread
> >>> or multi-thraded.
> >>>
> >>> **
> >>> Martin
> >>>
> >>> ti 3. tammik. 2023 klo 16.58s...@stantastic.nl kirjoitti:
> >>>
> >>> Thanks everyone. I did not expect the amount of feedback that I got. It
> >>> is much appreciated.
> >>>
> >>> I spent most of my day profiling with VisualVM and it strengthened by
> >>> beliefs that my problems do not appear to be related to anything but
> >>> Wicket combined with our dated hardware. Please do not consider this a
> >>> criticism. I understand that not a lot of people run servlet containers
> >>> on this kind of hardware nowadays.
> >>>
> >>> My database queries all run quickly and my domain classes are hardly
> >>> even touched when the system starts. Our rather simple login page -
> >>> which is stateless and does not query the database when the form is
> >>> empty - takes 5-15 seconds to load on the first try. Subsequent
> >>> requests
> >>> take about 40-120ms (browser caching disabled). Once logged in, the
> >>> other pages do not take as long, but they do feel sluggish until they
> >>> have been requested once.
> >>>
> >>> I tried to only load the quickstart example as Martijn suggested. It
> >>> starts more quickly than our own application but all things considered,
> >>> its performance did not impress me and that application really is super
> >>> simple. The first page load of the quickstart took about 2 seconds,
> >>> after that it normalized to about 30ms per request.
> >>>
> >>> When all pages have been loaded once, things are absolutely fine. So I
> >>> am considering Martin's approach of preloading components. That still
> >>> leaves me with the considerable startup time but we will learn to live
> >>> with that. Or we might switch from Tomcat to Jetty eventually.
> > You may want to check the implementation of Wicket Native WebSocket
> module
> > [1]
> > WebSocket messages come in a TCP connection, i.e. there is no HTTP
> > session/request/response.
> > Because of that Wicket Native WebSocket stores the app name, session id,
> > page id /
Re: Wicket on low end hardware
from mobile (sorry for typos ;) On Tue, Jan 3, 2023, 00:26 wrote: > It is not a very special setup. > > All devices run a Tomcat 9 servlet container. The servlet container runs > a webservice that is being used onsite by other systems and an > administration UI which is Wicket based. Both apps use the same H2 > database, which is tiny (<1MB) and only contains configuration and small > amounts of temporary data. The data layer is based on MyBatis, and > besides that there only are a couple of our own libraries there, and > those really only contain some domain logic. The heavy lifting happens > in the other app. > > Typical boot time for the servlet container is 10 to 20 seconds, > depending on the hardware (it is about 4 seconds on my development > machine). Startup time can be decreased by using -Djava.security.egd=file:/dev/./urandom Which - isn't a lot if you ask me, but it annoys our support > staff when they have to update the devices. And they probably do this a > lot on a daily basis. > > When the first page of the day is requested it can take a good 5-15 > seconds for it to appear, even when the device has already been running > for most of the day. On my development machine it is nearly instant. > > The Wicket application's performance does not improve when it is the > only app being run on the device. > > But you and Martin are spot on. Instead of hoping for the golden lottery > ticket, it is probably better for me to just spend half a day profiling > and then ask a well researched question. So I guess I figured out what > I'll be doing tomorrow morning ;-). > > Thanks! > > Stan > > > Anna Eileen schreef op 2023-01-02 02:19: > > > Hello > > > > Would you please describe your web application components? Database ? > > What services ran on the device? > > > > From: s...@stantastic.nl > > Date: Monday, January 2, 2023 at 5:23 AM > > To: users@wicket.apache.org > > Subject: Wicket on low end hardware > > > > Hi, > > > > My use case for Wicket is a quite unconventional one. I use it as the > > framework for the web interface of an appliance that runs on low end > > hardware. The appliance doesn't have gigabytes of memory to waste or > > tens of CPU cores. It's more like Celeron powered hardware with maybe > > one or two gigabytes of RAM. > > > > I general this all works and customers are happy once the device is > > running. But I find that deployment is quite slow, and so are the first > > couple of page loads of the day. Just to be clear: I cannot really > > claim > > that my performance problems are all Wicket related. They may be, but > > they probably also are down to other underlying issues. A badly > > optimized database, or a badly configured servlet container come to > > mind... > > > > However, I was wondering if anyone has experience in using Wicket on > > low > > end hardware. I would be very interested in how to optimize for this. > > > > Thanks, > > > > Stan > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Ajax - component not rendered.
Steps to create Mini application are here:
https://wicket.apache.org/start/quickstart.html :))
On Tue, 8 Nov 2022 at 15:01, Martin Grigorov wrote:
> Hi,
>
> Please try to reproduce the problem in a mini application and share it
> with us!
>
> On Tue, Nov 8, 2022 at 9:41 AM Laurent Duparchy wrote:
>
>> Hi,
>>
>> I got rid of this javascript error, that was due to incorrect design, I
>> think.
>>
>> devicesGroup is a CheckGroup
>>
>> devicesGroup = new CheckGroup("devicesGroup", new ArrayList()) {
>> @Override
>> public boolean isVisible() {
>> super.isVisible();
>>.
>> };
>> };
>>
>>
>>
>> but it contained also what seems to be a useless CheckGroupSelector.
>>
>> // devicesGroup.add(new CheckGroupSelector("devicesGroupSelector"));
>>
>>
>> So, the javascript error is gone but the Ajax rendering is still flawed.
>>
>> When I add both feedbackpanel and devicesGroup, nothing is rendered the
>> Ajax response is as follow
>>
>>
>>
>> id5 being the feedbackpanel (which is empty in the response)
>> id7 being the devicesGroup which still contains the deleted line.
>>
>> All in all, this response does not take into account the added component
>> for repainting. I added them to the Ajax "target" but perhaps I need to add
>> them to a "parent" ?
>>
>> I recall that if I add only the feedbackpanel for Ajax rendering, it is
>> well painted.
>>
>> generated markup :
>>
>> > id="header">WakeOnLan Utility Utility to
>> start / wake up a computer > id="signOut">Sign Out
>>
>> > action="./?6-2.-wakeUpForm">> class="hidden-fields">
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Laurent Duparchy ESRF - The European Synchrotron MIS Unit 04 76 88 22 56*
>> Martin Grigorov wrote on 07/11/2022 20:57:
>>
>> Hi Laurent,
>>
>> The problem is the JavaScript error: Uncaught TypeError: b is null.
>>
>> It seems there is some bug in
>> "Wicket.CheckboxSelector.updateSelectorState(c,e)},initializeSelector:function(c,d){var
>> b=document.getElementById(c); ..."
>>
>> Due to this JS error Wicket cannot replace neither the feedback panel nor
>> any other component.
>>
>> You should focus on debugging the JavaScript. If you don't know how to do
>> it then please create a quickstart app that reproduces the problem and
>> share it with us.
>>
>>
>> On Mon, Nov 7, 2022 at 6:37 PM Laurent Duparchy
>> wrote:
>>
>>
>> If I add the entire page (which is defeating the entire "Ajax" idea I
>> think.), it works. The new list is painted
>> > target.get().add(getPage());
>>
>> If I add only the feedback panel, it is is painted.
>> > target.get().add(feedbackPanel);
>>
>> If I add both, the feedbackpanel is not painted... Go figure.
>>
>> I probably don't understand what a "target" is and I'm giving up that.
>> Sorry for being an annoyance.
>>
>>
>> *Laurent Duparchy
>> ESRF - The European Synchrotron
>> MIS Unit
>> 04 76 88 22 56*
>> Laurent Duparchy wrote on 03/11/2022 10:11:
>>
>> Yes I corrected that HTML too. (which was auto-corrected by browsers I
>>
>> think, at least by Firefox).
>>
>> I looked for errors in Firefox debugger. The console reports a warning
>>
>> then an error in a generated js :
>>
>> Warning :
>>
>> jQuery.Deferred exception: b is null updateSelectorState@
>>
>> https://xx/misapps/wakeOnLan/wicket/resource/org.apache.wicket.markup.html.form.AbstractCheckSelector/CheckSelector-ver-1CE61F040D59ED57EADC3FBB51E1E02C.js:1:392
>> attachUpdateHandlers@https://xx.esrf.fr/misapps/wakeOnLan/wicket/resource/org.apache.wicket.markup.html.form.AbstractCheckSelector/CheckSelector-ver-1CE61F040D59ED57EADC3FBB51E1E02C.js:1:598
>>
>> Error :
>>
>>
>> Uncaught TypeError: b is null
>>
>> in
>>
>>
>>
>> (function(a){if(typeof(Wicket.CheckboxSelector)==="object"){return}Wicket.CheckboxSelector={updateAllCheckboxes:function(f,e){var
>> d=e();for(var b=0;b> c=d[b];if(c.checked!==f){c.click()}}},updateSelectorState:function(e,g){var
>> f=g(),c=f.length>0;for(var
>> d=0;d> b=document.getElementById(e);b.checked=c},attachUpdateHandlers:function(c,e){var
>> d=e(),f=function(){Wicket.CheckboxSelector.updateSelectorState(c,e)};for(var
>> b=0;b> b=document.getElementById(c);Wicket.Event.add(b,"click",function(){Wicket.CheckboxSelector.updateAllCheckboxes(b.checked,d)})},findCheckboxesFunction:function(c,b){return
>> function(){var d=[];var
>> g=document.getElementById(c).getElementsByTagName("input");for(var
>> e=0;e>
>> d}},getCheckboxesFunction:function(b){return function(){var
>>
>> c=[];for(var e=0;e> d=document.getElementById(b[e]);if(d){c.push(d)}}return c)();
>>
>> *Laurent Duparchy
>> ESRF - The European Synchrotron
>> MIS Unit
>> 04 76 88 22 56*
>> Sven Meier wrote on 03/11/2022 09:38:
>>
>> That HTML doesn't look
[ANNOUNCE] WicketStuff 9.12.0 Released
WicketStuff core 9.12.0 based on Apache Wicket 9.12.0 is released and soon will be available at Maven Central! Maxim Solodovnik (7): Switching to the next development version Jetty and Spring are updated Dependencies are updated Dependencies are updated .vscode is added to .gitignore Dependencies are updated wicketstuff-core-9.12.0 is released dependabot[bot] (1): Bump protobuf-java from 3.19.3 to 3.19.6 (#733) rkurucz9 (1): [wicketstuff-input-events] 'disable_in_input' would handle the contenteditable="true" attribute (#731) The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.11.0 Released
WicketStuff core 9.11.0 based on Apache Wicket 9.11.0 is released and soon will be available at Maven Central! Maxim Solodovnik (3): Switching to the next development version Dependencies are updated and organized wicketstuff-core 9.11.0 is released The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Reg : Multiple versions of jQuery's are loaded on same page causing conflict
Can you share quick-start project? from mobile (sorry for typos ;) On Tue, May 31, 2022, 17:03 sundar saba wrote: > Hi all, > > Based on your solution my actual problem is solved. May I know from > where another version of jQuery v2.2.4 is loaded? And I know that jQuery > v3.6.0 is loaded from the "JavaScriptLibrarySettings" class by default. >
[ANNOUNCE] WicketStuff 9.10.0 Released
WicketStuff core 9.10.0 based on Apache Wicket 9.10.0 is released and soon will be available at Maven Central! Maxim Solodovnik (3): Switching to the next development version Dependencies are updated wicketstuff-core-9.10.0 is released The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.9.1 Released
WicketStuff core 9.9.1 based on Apache Wicket 9.9.1 is released and soon will be available at Maven Central! Maxim Solodovnik (5): commons-io is updated push-* modules are dropped Dependencies and plugins are updated Dependencies are updated Wicketstuff-core 9.9.1 The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.9.0 Released
WicketStuff core 9.9.0 based on Apache Wicket 9.9.0 is released and soon will be available at Maven Central! Maxim Solodovnik (3): Switching to the next development version Dependencies are updated wicketstuff core 9.9.0 is released The WicketStuff team
Re: Get session details when it expires
from mobile (sorry for typos ;) On Tue, Mar 15, 2022, 16:56 Arunachalam Sibisakkaravarthi < arunacha...@mcruncher.com> wrote: > Hi guys, > My app uses custom Session and Session Store classes that extend WebSession > and HttpSessionStore respectively. Additional details stored in the Session > class. > I couldn't get the session when it expires and the app throws the below > exception when attempting to get the current session when it expires. > > org.apache.wicket.WicketRuntimeException: There is no application attached > to current thread > Maybe the session is alive but you are using "self-constructed" threads? > Is there a way to get the session object to get the details upon > session expiration? > > > > *Thanks And RegardsSibi.ArunachalammCruncher* >
Re: module error
On Mon, 21 Feb 2022 at 10:11, Locke, Jonathan (Luo Shibo) < jonath...@telenav.com> wrote: > Hi Martin, > > I have access to my account now, but I get this when I try to push a new > branch rel/wicket-9.8.1 > > wicket: remote: Permission to apache/wicket.git denied to jonathanlocke. > unable to access 'https://github.com/apache/wicket.git/': The requested > URL returned error: 403 > > Can someone give me push access? > please try to add your github username at id.apache.org or use https://gitbox.apache.org/ <https://gitbox.apache.org/setup/> >Jon > > > From: Martin Grigorov > Sent: Sunday, February 20, 2022 5:58 PM > To: users@wicket.apache.org > Subject: Re: module error > > You are still a member of the team - > https://home.apache.org/phonebook.html?uid=jonl > > If your login was disabled your id would appear scratched at > https://home.apache.org/phonebook.html?pmc=wicket > > I guess you have forgotten your ID and/or associated email and/or password. > The quickest way to start using again your account is to contact Infra team > at JIRA. > > > Once you have access to your Apache account you should go to > https://gitbox.apache.org/setup/ to link it with your GitHub account. > > > > On Sun, Feb 20, 2022, 08:00 Locke, Jonathan (Luo Shibo) < > jonath...@telenav.com> wrote: > > > Yes, I checked. I don't. > > > > From: Maxim Solodovnik > > Sent: Saturday, February 19, 2022 8:11 PM > > To: users@wicket.apache.org > > Subject: Re: module error > > > > from mobile (sorry for typos ;) > > > > > > On Sun, Feb 20, 2022, 02:41 Locke, Jonathan (Luo Shibo) < > > jonath...@telenav.com> wrote: > > > > > I don't think I'm a committer anymore. It's been at least a decade > since > > > my last commit. > > > > > > > Commitership shouldn't be dropped due to inactivity > > > > Can you check if you have your github login at id.apache.org ? > > > > > > I'm amazed that wicket is still going strong. In two years it will be 20 > > > years of Wicket. > > > > > >Jon > > > > > > > > > From: Maxim Solodovnik > > > Sent: Saturday, February 19, 2022 5:57 AM > > > To: users@wicket.apache.org > > > Subject: Re: module error > > > > > > from mobile (sorry for typos ;) > > > > > > > > > On Sat, Feb 19, 2022, 19:20 Ernesto Reinaldo Barreiro < > > reier...@gmail.com> > > > wrote: > > > > > > > No if you are a committer :-) > > > > > > > > > > Commiter will never see 403 :) > > > > > > > > > > > On Fri, Feb 18, 2022 at 11:44 PM Maxim Solodovnik < > > solomax...@gmail.com> > > > > wrote: > > > > > > > > > On Sat, 19 Feb 2022 at 03:04, Locke, Jonathan (Luo Shibo) < > > > > > jonath...@telenav.com> wrote: > > > > > > > > > > > Hi Martin, > > > > > > > > > > > > I was able to fix the problem as you suggested by adding: > > > > > > > > > > > > uses org.apache.wicket.IInitializer; > > > > > > > > > > > > to > > > > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fmodule-info.java=E,1,WO4T_dAL8ww57jzExgL1QE2YUg9PSzf2JkCUtz233hgGolAnoaigRG7sFCy0R4-qUwC5-Hx7dj3RPzsVYEU2af8Pfa75fVWyNkUJcZk3X0YerNK-FcxQ=1 > > > in wicket-core. I created a pull request, but got > > > > an > > > > > > error trying to push it in IntelliJ: > > > > > > > > > > > > Can't create a new pull request: Push failed: remote: Permission > to > > > > > > apache/wicket.git denied to jonathanlocke. unable to access ' > > > > > > https://github.com/apache/wicket.git/': The requested URL > returned > > > > > error: > > > > > > 403 > > > > > > > > > > > > > > > > You need to fork the repo first :) > > > > > > > > > > > > > > > > > > > > > > Could we add this as a patch release to wicket 9.8.x? > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Jon > > > > > > > > > > > > From: Martin Grigorov > > > > &
Re: module error
from mobile (sorry for typos ;) On Sun, Feb 20, 2022, 02:41 Locke, Jonathan (Luo Shibo) < jonath...@telenav.com> wrote: > I don't think I'm a committer anymore. It's been at least a decade since > my last commit. > Commitership shouldn't be dropped due to inactivity Can you check if you have your github login at id.apache.org ? I'm amazed that wicket is still going strong. In two years it will be 20 > years of Wicket. > >Jon > > ________ > From: Maxim Solodovnik > Sent: Saturday, February 19, 2022 5:57 AM > To: users@wicket.apache.org > Subject: Re: module error > > from mobile (sorry for typos ;) > > > On Sat, Feb 19, 2022, 19:20 Ernesto Reinaldo Barreiro > wrote: > > > No if you are a committer :-) > > > > Commiter will never see 403 :) > > > > > On Fri, Feb 18, 2022 at 11:44 PM Maxim Solodovnik > > wrote: > > > > > On Sat, 19 Feb 2022 at 03:04, Locke, Jonathan (Luo Shibo) < > > > jonath...@telenav.com> wrote: > > > > > > > Hi Martin, > > > > > > > > I was able to fix the problem as you suggested by adding: > > > > > > > > uses org.apache.wicket.IInitializer; > > > > > > > > to > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fmodule-info.java=E,1,WO4T_dAL8ww57jzExgL1QE2YUg9PSzf2JkCUtz233hgGolAnoaigRG7sFCy0R4-qUwC5-Hx7dj3RPzsVYEU2af8Pfa75fVWyNkUJcZk3X0YerNK-FcxQ=1 > in wicket-core. I created a pull request, but got > > an > > > > error trying to push it in IntelliJ: > > > > > > > > Can't create a new pull request: Push failed: remote: Permission to > > > > apache/wicket.git denied to jonathanlocke. unable to access ' > > > > https://github.com/apache/wicket.git/': The requested URL returned > > > error: > > > > 403 > > > > > > > > > > You need to fork the repo first :) > > > > > > > > > > > > > > Could we add this as a patch release to wicket 9.8.x? > > > > > > > > Thanks, > > > > > > > > Jon > > > > > > > > From: Martin Grigorov > > > > Sent: Friday, February 18, 2022 2:55 AM > > > > To: users@wicket.apache.org > > > > Subject: Re: module error > > > > > > > > Hm. > > > > Looking at https://github.com/qos-ch/logback/commit/5186d2604b460f I > > > think > > > > we need the 'uses' only in the module where we call > > ServiceLoader.load(), > > > > i.e. in wicket-core. > > > > > > > > On Fri, Feb 18, 2022 at 11:53 AM Martin Grigorov < > mgrigo...@apache.org > > > > > > > wrote: > > > > > > > > > Hi Jon, > > > > > > > > > > According to > > > > > > > > > > > > > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.oracle.com%2fcorporate%2ffeatures%2funderstanding-java-9-modules.html=E,1,AlcuJddqQ1zhtdsihzDbje23huNpDs6zcgn19JZMXP_Y1UGGpZLts-DudDYPcu75JyHkjFHLNGJw3KmnkhBiyTndIjuRNCIVCuhKfLjxxCsCSVE,=1 > > > > > > > > > > *provides…with.* A provides…with module directive specifies that a > > > module > > > > > provides a service implementation—making the module a *service > > > provider*. > > > > > The provides part of the directive specifies an interface or > abstract > > > > > class listed in a module’s uses directive and the with part of the > > > > > directive specifies the name of the service provider class that > > > > implements > > > > > the interface or extends the abstract class. > > > > > > > > > > AFAIU it we need to add "uses org.apache.wicket.IInitializer" next > to > > > all > > > > > "provides org.apache.wicket.IInitializer with > > > x.y.z.SomeImplementation;" > > > > > > > > > > Please try it and if it fixes the issue then send a PR! > > > > > > > > > > On Thu, Feb 17, 2022 at 8:16 PM Locke, Jonathan (Luo Shibo) < > > > > > jonath...@telenav.com> wrote: > > > > > > > > > >> > > > > >> Does anyone know what this is? Thanks -- Jon > > > > >> > > > > >> Exception in thread "main" java.util.ServiceConfigurationError: > > > > >> org.apache.wicket.IInitializer:
Re: module error
from mobile (sorry for typos ;) On Sat, Feb 19, 2022, 19:20 Ernesto Reinaldo Barreiro wrote: > No if you are a committer :-) > Commiter will never see 403 :) > > On Fri, Feb 18, 2022 at 11:44 PM Maxim Solodovnik > wrote: > > > On Sat, 19 Feb 2022 at 03:04, Locke, Jonathan (Luo Shibo) < > > jonath...@telenav.com> wrote: > > > > > Hi Martin, > > > > > > I was able to fix the problem as you suggested by adding: > > > > > > uses org.apache.wicket.IInitializer; > > > > > > to module-info.java in wicket-core. I created a pull request, but got > an > > > error trying to push it in IntelliJ: > > > > > > Can't create a new pull request: Push failed: remote: Permission to > > > apache/wicket.git denied to jonathanlocke. unable to access ' > > > https://github.com/apache/wicket.git/': The requested URL returned > > error: > > > 403 > > > > > > > You need to fork the repo first :) > > > > > > > > > > Could we add this as a patch release to wicket 9.8.x? > > > > > > Thanks, > > > > > > Jon > > > > > > From: Martin Grigorov > > > Sent: Friday, February 18, 2022 2:55 AM > > > To: users@wicket.apache.org > > > Subject: Re: module error > > > > > > Hm. > > > Looking at https://github.com/qos-ch/logback/commit/5186d2604b460f I > > think > > > we need the 'uses' only in the module where we call > ServiceLoader.load(), > > > i.e. in wicket-core. > > > > > > On Fri, Feb 18, 2022 at 11:53 AM Martin Grigorov > > > > wrote: > > > > > > > Hi Jon, > > > > > > > > According to > > > > > > > > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.oracle.com%2fcorporate%2ffeatures%2funderstanding-java-9-modules.html=E,1,AlcuJddqQ1zhtdsihzDbje23huNpDs6zcgn19JZMXP_Y1UGGpZLts-DudDYPcu75JyHkjFHLNGJw3KmnkhBiyTndIjuRNCIVCuhKfLjxxCsCSVE,=1 > > > > > > > > *provides…with.* A provides…with module directive specifies that a > > module > > > > provides a service implementation—making the module a *service > > provider*. > > > > The provides part of the directive specifies an interface or abstract > > > > class listed in a module’s uses directive and the with part of the > > > > directive specifies the name of the service provider class that > > > implements > > > > the interface or extends the abstract class. > > > > > > > > AFAIU it we need to add "uses org.apache.wicket.IInitializer" next to > > all > > > > "provides org.apache.wicket.IInitializer with > > x.y.z.SomeImplementation;" > > > > > > > > Please try it and if it fixes the issue then send a PR! > > > > > > > > On Thu, Feb 17, 2022 at 8:16 PM Locke, Jonathan (Luo Shibo) < > > > > jonath...@telenav.com> wrote: > > > > > > > >> > > > >> Does anyone know what this is? Thanks -- Jon > > > >> > > > >> Exception in thread "main" java.util.ServiceConfigurationError: > > > >> org.apache.wicket.IInitializer: module org.apache.wicket.core does > not > > > >> declare `uses` > > > >> at java.base/ > > > > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fjava.util.ServiceLoader.fail=E,1,2x_TAvfY-cjOXXMq-PK1WQZp3HpRsfitQcisq2lSSdigHB1fuLg4Un_Ch3NVlsHPuGsx1r8PejxwY0JdlGRrY2C2drem7b8IxqPf8rSvijXa9Q,,=1(https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fServiceLoader.java%3a589=E,1,cis_qtCg_hnDhiLzgOVbloD3TvvURxsW_mR8jY_GLJSaBpOtuXQJUWKaJ_JrPr61_00oAuYKmsG399grMpFwMKTC0mk8-ulQZF8Om98TsswwCgflaQ,,=1) > > > >> at java.base/java.util.ServiceLoader.checkCaller( > > > > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fServiceLoader.java%3a575=E,1,9qC3hJZa-Ru3NfQ0Cu_xyUf_1TZj3k6pzwnMObpxVdF9nmaNB2Rc-7lJtCoeo-It3FF8Ycad-exairuNw8NewoRyu6p0DmFxGH3lEQdd=1 > > > ) > > > >> at java.base/java.util.ServiceLoader.( > > > > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fServiceLoader.java%3a504=E,1,cG_JOkZF6cVpHdKnhFXnJdubZajDowT1aiqJ9nZMqXb8XP1HyPF8zffkOEW6pB1tIpgfKXetT1e_Av2K_LQiQ4IawQx7L_1ecDlhhxbW-A,,=1 > > > ) > > > >> at java.base/java.util.ServiceLoader.load( > > > > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fServiceLoader.java%3a1687=E,1,ygqiqrdRgnPTbUdIwfyfaUU7N
Re: module error
On Sat, 19 Feb 2022 at 03:04, Locke, Jonathan (Luo Shibo) < jonath...@telenav.com> wrote: > Hi Martin, > > I was able to fix the problem as you suggested by adding: > > uses org.apache.wicket.IInitializer; > > to module-info.java in wicket-core. I created a pull request, but got an > error trying to push it in IntelliJ: > > Can't create a new pull request: Push failed: remote: Permission to > apache/wicket.git denied to jonathanlocke. unable to access ' > https://github.com/apache/wicket.git/': The requested URL returned error: > 403 > You need to fork the repo first :) > > Could we add this as a patch release to wicket 9.8.x? > > Thanks, > > Jon > > From: Martin Grigorov > Sent: Friday, February 18, 2022 2:55 AM > To: users@wicket.apache.org > Subject: Re: module error > > Hm. > Looking at https://github.com/qos-ch/logback/commit/5186d2604b460f I think > we need the 'uses' only in the module where we call ServiceLoader.load(), > i.e. in wicket-core. > > On Fri, Feb 18, 2022 at 11:53 AM Martin Grigorov > wrote: > > > Hi Jon, > > > > According to > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.oracle.com%2fcorporate%2ffeatures%2funderstanding-java-9-modules.html=E,1,AlcuJddqQ1zhtdsihzDbje23huNpDs6zcgn19JZMXP_Y1UGGpZLts-DudDYPcu75JyHkjFHLNGJw3KmnkhBiyTndIjuRNCIVCuhKfLjxxCsCSVE,=1 > > > > *provides…with.* A provides…with module directive specifies that a module > > provides a service implementation—making the module a *service provider*. > > The provides part of the directive specifies an interface or abstract > > class listed in a module’s uses directive and the with part of the > > directive specifies the name of the service provider class that > implements > > the interface or extends the abstract class. > > > > AFAIU it we need to add "uses org.apache.wicket.IInitializer" next to all > > "provides org.apache.wicket.IInitializer with x.y.z.SomeImplementation;" > > > > Please try it and if it fixes the issue then send a PR! > > > > On Thu, Feb 17, 2022 at 8:16 PM Locke, Jonathan (Luo Shibo) < > > jonath...@telenav.com> wrote: > > > >> > >> Does anyone know what this is? Thanks -- Jon > >> > >> Exception in thread "main" java.util.ServiceConfigurationError: > >> org.apache.wicket.IInitializer: module org.apache.wicket.core does not > >> declare `uses` > >> at java.base/ > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fjava.util.ServiceLoader.fail=E,1,2x_TAvfY-cjOXXMq-PK1WQZp3HpRsfitQcisq2lSSdigHB1fuLg4Un_Ch3NVlsHPuGsx1r8PejxwY0JdlGRrY2C2drem7b8IxqPf8rSvijXa9Q,,=1(https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fServiceLoader.java%3a589=E,1,cis_qtCg_hnDhiLzgOVbloD3TvvURxsW_mR8jY_GLJSaBpOtuXQJUWKaJ_JrPr61_00oAuYKmsG399grMpFwMKTC0mk8-ulQZF8Om98TsswwCgflaQ,,=1) > >> at java.base/java.util.ServiceLoader.checkCaller( > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fServiceLoader.java%3a575=E,1,9qC3hJZa-Ru3NfQ0Cu_xyUf_1TZj3k6pzwnMObpxVdF9nmaNB2Rc-7lJtCoeo-It3FF8Ycad-exairuNw8NewoRyu6p0DmFxGH3lEQdd=1 > ) > >> at java.base/java.util.ServiceLoader.( > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fServiceLoader.java%3a504=E,1,cG_JOkZF6cVpHdKnhFXnJdubZajDowT1aiqJ9nZMqXb8XP1HyPF8zffkOEW6pB1tIpgfKXetT1e_Av2K_LQiQ4IawQx7L_1ecDlhhxbW-A,,=1 > ) > >> at java.base/java.util.ServiceLoader.load( > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fServiceLoader.java%3a1687=E,1,ygqiqrdRgnPTbUdIwfyfaUU7NeLViUlaxe25c2cEr4ugbgFscntOvbGkTMrOa6kItGqMQ8hU1VDEzNaoKdV3-6CvBlcsrRFxlFuwjq6IqJK4Z_uzDIyI=1 > ) > >> at org.apache.wicket.core@9.6.0 > >> /org.apache.wicket.Application.initInitializers( > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fApplication.java%3a556=E,1,xO9MV3KborBvFc4BL8FxC_4uuwfGaJqvrr-QVfntZI9iuOSmldotcVrEPvDYOTDHJI2hraMPQKQ5UOmqIxeJinkgxDyfchFVTm-AleqRwae6OLPTDfo,=1 > ) > >> at org.apache.wicket.core@9.6.0 > >> /org.apache.wicket.Application.initApplication( > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fApplication.java%3a765=E,1,53VvaIOZTG7mETf35tkUcXDXfgaVHqiw29gxxq_4y_ZXHn8AGzbIbtFXR4tf6Oh_rbl7mOLXjgPBeEW3-pd7jBqEp-30i2WA26_CdN5uIVJtHsjBDJuep4DVDA,,=1 > ) > >> at org.apache.wicket.core@9.6.0 > >> /org.apache.wicket.protocol.http.WicketFilter.init( > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fWicketFilter.java%3a441=E,1,He0Z2RxpNcC-ziRHqyjYFORYOn-LK_eNOZGT9zHWjBKPv3GAhtI8TUG2W-9YOiYdW6_ArVy_6GMjKIt_0nLh3u0FHuh0H-pscUXDZj11B8s,=1 > ) > >> at org.apache.wicket.core@9.6.0 > >> /org.apache.wicket.protocol.http.WicketFilter.init( > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fWicketFilter.java%3a365=E,1,yo_2tJnAV4qbr-cq49OMx3sq4HWonvaqycQkJ_db-wYcUtt-8EyuDB-_tz0hjwH9lQgYN9mHJniiRilRX9pL2VXbKQEd6QnNcrLzbwVOzRzTSmM,=1 > ) > >> > >> > [EXTERNAL EMAIL] CAUTION: This email originated from outside of Telenav. > DO NOT CLICK links or attachments unless you recognize the sender and know > the content is safe. > -- Best regards, Maxim
[ANNOUNCE] WicketStuff 9.8.0 Released
WicketStuff core 9.8.0 based on Apache Wicket 9.8.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (11): Switching to the next development version [dashboard] proper way of RTL detection, jquery-ui is updated Merge branch 'master' of github.com:wicketstuff/core Dependencies are updated protobuf-java moved to dependencyManagement and updated Merge branch 'master' of github.com:wicketstuff/core POI is updated Merge branch 'master' of github.com:wicketstuff/core Dependencies are updated wicketstuff-jwicket-ui* are dropped wicketstuff-core-9.8.0 is released dependabot[bot] (7): Bump log4j-core (#716) Bump log4j-core from 2.16.0 to 2.17.0 (#717) Bump log4j-core (#718) Bump log4j-core from 2.17.0 to 2.17.1 (#719) Bump spring-core from 5.3.13 to 5.3.14 (#720) Bump hazelcast in /datastores-parent/datastore-hazelcast (#723) Bump xstream from 1.4.18 to 1.4.19 (#724) Martin Grigorov (1): Use Github Actions as CI (#722) Martin Tzvetanov Grigorov (1): Add Github Actions CI config The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [DISCUSSION] drop wicketstuff-jwicket-ui*
Dropped! Thanks a lot! :) On Wed, 12 Jan 2022 at 13:58, Sven Meier wrote: > +1 for dropping them > > Sven > > Am 12. Januar 2022 07:29:19 MEZ schrieb Martin Grigorov < > mgrigo...@apache.org>: > >+1 to drop them ! > > > >On Wed, Jan 12, 2022 at 8:19 AM Maxim Solodovnik > >wrote: > > > >> Hello All, > >> > >> I've just noticed: > >> > >> wicketstuff-jwicket-ui-datepicker > >> Contains `jQuery UI Datepicker 1.10.3` ( more than 160 js/css files) > >> wicketstuff-jwicket-ui-tooltip > >> Contains `jQuery UI Tooltip 1.10.3` > >> > >> wicketstuff-jwicket-ui-accordion > >> wicketstuff-jwicket-ui-dragdrop > >> wicketstuff-jwicket-ui-effects > >> wicketstuff-jwicket-ui-menu > >> wicketstuff-jwicket-ui-resize > >> wicketstuff-jwicket-ui-sort > >> Contains `jQuery UI * 1.8.6` > >> > >> these components seems to very much outdated > >> maybe we can drop them? > >> > >> > >> -- > >> Best regards, > >> Maxim > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > -- Best regards, Maxim
[ANNOUNCE] WicketStuff 8.14.0 Released
WicketStuff core 8.14.0 based on Apache Wicket 8.14.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (3): Switching to the next development version Dependencies are updated wicketstuff-core 8.14.0 is released The WicketStuff team
Re: Indicator on IndicatingAjaxButton and IndicatingAjaxLink not working
Have you tried the SpinnerButton from wicket-bootstrap?
Does it work for you?
from mobile (sorry for typos ;)
On Fri, Jan 21, 2022, 08:49 Michelle Ee Siew Phing <
michelle...@mcruncher.com> wrote:
> Sorry... missed out the wicket.bootstrap.version
>
> 5.0.5
>
> On Fri, Jan 21, 2022 at 9:35 AM Michelle Ee Siew Phing <
> michelle...@mcruncher.com> wrote:
>
>> Hi,
>>
>> Checking the examples again... the "hidden" is not removed after clicking
>> on the button, but the style="display:inline" is appended.
>> [image: Screenshot from 2022-01-21 09-04-51.png]
>>
>> I think this would pose an issue with any .css that has the following
>> [hidden] {
>>
>>1. display: none !important;
>>
>> }
>> Attached herewith the demo using the wicket quickstart
>> wicket-test-1.0-SNAPSHOT.war
>>
>>
>> In the quick start codes, I've added
>> 1. the required dependencies [pom.xml]
>>
>> de.agilecoders.wicket
>> wicket-bootstrap-core
>> ${wicket.bootstrap.version}
>>
>>
>>
>> de.agilecoders.wicket
>> wicket-bootstrap-extensions
>> ${wicket.bootstrap.version}
>>
>>
>> 2. added BootstrapSettings [WicketApplication.java]
>> BootstrapSettings settings = new BootstrapSettings();
>> Bootstrap.install(this, settings);
>>
>> 3. added necessary html elements
>> [HomePage.html]
>>
>> Test Indicating Ajax Button
>>
>>
>>
>> [HomePage.java]
>> private Form addForm()
>> {
>> Form testForm = new Form("form");
>> testForm.add(addTestButton(testForm));
>> return testForm;
>> }
>>
>> private AjaxButton addTestButton(Form form)
>> {
>> return new IndicatingAjaxButton("testButton", Model.of("Sleep for
>> a while"), form)
>> {
>> @Override
>> protected void onSubmit(AjaxRequestTarget target)
>> {
>> try {
>> Thread.sleep(3000);
>> } catch (InterruptedException e) {
>> e.printStackTrace();
>> }
>> }
>> };
>> }
>>
>> Could we get this fixed?
>>
>> /Michelle
>>
>> On Mon, Jan 17, 2022 at 3:07 PM Martin Grigorov
>> wrote:
>>
>>> Hi,
>>>
>>> Please check https://examples9x.wicket.apache.org/ajax/links.
>>> The third link demostrates usage of IndicatingAjaxLink.
>>> When clicked it adds style="display:inline" and removes "hidden".
>>> Its source code could be found at
>>>
>>> https://github.com/apache/wicket/blob/63c5fe205de1bea293e3b36ca8e0426b343ccafa/wicket-examples/src/main/java/org/apache/wicket/examples/ajax/builtin/LinksPage.java
>>> Please compare it with your app!
>>> If you are not able to find the problem then please create a mini demo
>>> application and share it with us!
>>>
>>> On Mon, Jan 17, 2022 at 6:08 AM Michelle Ee Siew Phing <
>>> michelle...@mcruncher.com> wrote:
>>>
>>> > Hi,
>>> >
>>> > I am having issues with the loading icon on the IndicatingAjaxButton
>>> and
>>> > IndicatingAjaxLink. Previously I'm on Wicket 9.0.0-M4 and it was
>>> working
>>> > fine. But after upgrading to Wicket 9.0.0-M5 (and later versions), I'm
>>> not
>>> > able to see the loading icon any longer.
>>> >
>>> > I checked further in the code that the AjaxIndicatorAppender now has
>>> the
>>> > hidden attribute instead of the style=display:none. However, when I
>>> click
>>> > the IndicatingAjaxButton, it will still append the
>>> style=display:inline as
>>> > before (but due to the hidden attribute, the icon will not show).
>>> >
>>> > Is there anything else during the upgrade that I needed for the
>>> > IndicatingAjaxButton (and link) to work?
>>> > Please advise.
>>> >
>>> > Thank you. Regards.
>>> > Michelle
>>> >
>>>
>>
Re: Indicator on IndicatingAjaxButton and IndicatingAjaxLink not working
from mobile (sorry for typos ;)
On Wed, Jan 19, 2022, 08:29 Michelle Ee Siew Phing <
michelle...@mcruncher.com> wrote:
> LaddaAjaxButton is only available in Bootstrap 3 (Wicket-Bootstrap 4.0.4),
> we're currently on Bootstrap 4 (Wicket-Bootstrap 5.0.5).
> So this option is not available to us.
>
Sorry
Did quick search on a wrong branch :(
We are on bootstrap5
And are
using
de.agilecoders.wicket.extensions.markup.html.bootstrap.spinner.SpinnerAjaxButton
If I do remember correctly it should work for bootstrap4 as well :)
> On Mon, Jan 17, 2022 at 5:39 PM Maxim Solodovnik
> wrote:
>
> > I would recommend to use
> >
> >
> https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/wicket-9.x/bootstrap-extensions/src/main/java/de/agilecoders/wicket/extensions/markup/html/bootstrap/ladda/LaddaAjaxButton.java
> > works for as
> >
> > On Mon, 17 Jan 2022 at 16:33, Michelle Ee Siew Phing
> > wrote:
> > >
> > > Hi,
> > >
> > > Thanks for the information. I have checked the differences between the
> > > provided example and my codes and found the place that is causing the
> > > problem.
> > >
> > > We are using Wicket Bootstrap 5.0.5 with Wicket 9.5.0, and found the
> > > following in bootstrap.css
> > >
> > > [hidden] {
> > > display:none !important;
> > > }
> > >
> > > This takes precedence over the display:inline.
> > >
> > > Is there a workaround?
> > > Thanks
> > >
> > >
> > >
> > > On Mon, Jan 17, 2022 at 3:07 PM Martin Grigorov
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > Please check https://examples9x.wicket.apache.org/ajax/links.
> > > > The third link demostrates usage of IndicatingAjaxLink.
> > > > When clicked it adds style="display:inline" and removes "hidden".
> > > > Its source code could be found at
> > > >
> > > >
> >
> https://github.com/apache/wicket/blob/63c5fe205de1bea293e3b36ca8e0426b343ccafa/wicket-examples/src/main/java/org/apache/wicket/examples/ajax/builtin/LinksPage.java
> > > > Please compare it with your app!
> > > > If you are not able to find the problem then please create a mini
> demo
> > > > application and share it with us!
> > > >
> > > > On Mon, Jan 17, 2022 at 6:08 AM Michelle Ee Siew Phing <
> > > > michelle...@mcruncher.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I am having issues with the loading icon on the
> IndicatingAjaxButton
> > and
> > > > > IndicatingAjaxLink. Previously I'm on Wicket 9.0.0-M4 and it was
> > working
> > > > > fine. But after upgrading to Wicket 9.0.0-M5 (and later versions),
> > I'm
> > > > not
> > > > > able to see the loading icon any longer.
> > > > >
> > > > > I checked further in the code that the AjaxIndicatorAppender now
> has
> > the
> > > > > hidden attribute instead of the style=display:none. However, when I
> > click
> > > > > the IndicatingAjaxButton, it will still append the
> > style=display:inline
> > > > as
> > > > > before (but due to the hidden attribute, the icon will not show).
> > > > >
> > > > > Is there anything else during the upgrade that I needed for the
> > > > > IndicatingAjaxButton (and link) to work?
> > > > > Please advise.
> > > > >
> > > > > Thank you. Regards.
> > > > > Michelle
> > > > >
> > > >
> >
> >
> >
> > --
> > Best regards,
> > Maxim
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
Re: Indicator on IndicatingAjaxButton and IndicatingAjaxLink not working
I would recommend to use
https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/wicket-9.x/bootstrap-extensions/src/main/java/de/agilecoders/wicket/extensions/markup/html/bootstrap/ladda/LaddaAjaxButton.java
works for as
On Mon, 17 Jan 2022 at 16:33, Michelle Ee Siew Phing
wrote:
>
> Hi,
>
> Thanks for the information. I have checked the differences between the
> provided example and my codes and found the place that is causing the
> problem.
>
> We are using Wicket Bootstrap 5.0.5 with Wicket 9.5.0, and found the
> following in bootstrap.css
>
> [hidden] {
> display:none !important;
> }
>
> This takes precedence over the display:inline.
>
> Is there a workaround?
> Thanks
>
>
>
> On Mon, Jan 17, 2022 at 3:07 PM Martin Grigorov
> wrote:
>
> > Hi,
> >
> > Please check https://examples9x.wicket.apache.org/ajax/links.
> > The third link demostrates usage of IndicatingAjaxLink.
> > When clicked it adds style="display:inline" and removes "hidden".
> > Its source code could be found at
> >
> > https://github.com/apache/wicket/blob/63c5fe205de1bea293e3b36ca8e0426b343ccafa/wicket-examples/src/main/java/org/apache/wicket/examples/ajax/builtin/LinksPage.java
> > Please compare it with your app!
> > If you are not able to find the problem then please create a mini demo
> > application and share it with us!
> >
> > On Mon, Jan 17, 2022 at 6:08 AM Michelle Ee Siew Phing <
> > michelle...@mcruncher.com> wrote:
> >
> > > Hi,
> > >
> > > I am having issues with the loading icon on the IndicatingAjaxButton and
> > > IndicatingAjaxLink. Previously I'm on Wicket 9.0.0-M4 and it was working
> > > fine. But after upgrading to Wicket 9.0.0-M5 (and later versions), I'm
> > not
> > > able to see the loading icon any longer.
> > >
> > > I checked further in the code that the AjaxIndicatorAppender now has the
> > > hidden attribute instead of the style=display:none. However, when I click
> > > the IndicatingAjaxButton, it will still append the style=display:inline
> > as
> > > before (but due to the hidden attribute, the icon will not show).
> > >
> > > Is there anything else during the upgrade that I needed for the
> > > IndicatingAjaxButton (and link) to work?
> > > Please advise.
> > >
> > > Thank you. Regards.
> > > Michelle
> > >
> >
--
Best regards,
Maxim
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
[DISCUSSION] drop wicketstuff-jwicket-ui*
Hello All, I've just noticed: wicketstuff-jwicket-ui-datepicker Contains `jQuery UI Datepicker 1.10.3` ( more than 160 js/css files) wicketstuff-jwicket-ui-tooltip Contains `jQuery UI Tooltip 1.10.3` wicketstuff-jwicket-ui-accordion wicketstuff-jwicket-ui-dragdrop wicketstuff-jwicket-ui-effects wicketstuff-jwicket-ui-menu wicketstuff-jwicket-ui-resize wicketstuff-jwicket-ui-sort Contains `jQuery UI * 1.8.6` these components seems to very much outdated maybe we can drop them? -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.7.0 Released
WicketStuff core 9.7.0 based on Apache Wicket 9.7.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (3): Switching to the next development version Dependencies are updated wicketstuff-core-9.7.0 released dependabot[bot] (2): Bump log4j-core (#714) Bump log4j-core from 2.14.1 to 2.15.0 (#715) The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.6.0 Released
WicketStuff core 9.6.0 based on Apache Wicket 9.6.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (7): Switching to the next development version Cometd version is increased javadocs are partially fixed Wicket is updated, link to broken javadoc is commented out Javadocs seems to be fixed Dependencies are updated wicketstuff-core-9.6.0 released The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket clickable image with tooltips map
Unfortunately I have no experience with "wicket-bootstrap 2*" 5.* and 6.* seems to work for us as expected Maybe you can provide a quickstart application demonstrating the problem? https://wicket.apache.org/start/quickstart.html On Sat, 6 Nov 2021 at 13:55, C.S. wrote: > Wicket version is 8.12.0 > wicket-bootstrap version is 2.0.15 > > Until now i am reluctant of trying a higher bootstrap version, since this > means a migration from Bootstrap 3.x to 4.x (flex model) and editing all my > html as well. > So i first have to develop a small test prototype with higher versions only > for TooltipBehavior. > > Thank you for your help > > Christos Stieglitz > -- Best regards, Maxim
Re: wicket clickable image with tooltips map
What version of wicket-bootstrap are you using?
Are there any errors in JS console?
from mobile (sorry for typos ;)
On Thu, Nov 4, 2021, 21:52 C.S. wrote:
> Many thanks Sven and Martin,
>
> Svens suggestion (adding an AjaxEventBehavior("load")) works like a charm.
> Exactly what i was asking.
>
> Now the next problem is with
>
> #de.agilecoders.wicket.core.markup.html.bootstrap.components.TooltipBehavior
>
>
> Allthough the resulting html is now perfect (img tag pointing to a usemap
> which is filled with areas, each containing a tooltip), no tooltip pops up.
> I have no idea what the cause may be, still debugging the Tooltip class
> and the corresponding JS.
>
> I will check Martins suggestion and give ClientSideImageMap a try.
>
> BTW: Once my code runs, i will be more than happy to contribute a code
> snippet to the wiki or to whatever document you regard more usefull.
>
> Regards
>
> Christos Stieglitz
>
Re: ContextRelativeResourceReference CSS rendering problem
Maybe you can create a quickstart?
http://wicket.apache.org/start/quickstart.html
On Thu, 21 Oct 2021 at 21:27, Greg Dunn wrote:
> Hi, thanks for your response and assistance.
>
> Disabling strict CSP did not make any difference.
>
> You are correct that the problem only happens on the first page load.
>
> In the console for that page load I do see errors below. These are all
> gone when the page is relaoded:
>
>
> Every JavaScript file I'm loading gets this error:
>
> Uncaught SyntaxError: Unexpected token '<' -
> applicationUtils-ver-3…298D978F3B42A7.js:1
>
> I see this error twice in JavaScript that is rendered into the header by
> Wicket:
>
> Uncaught ReferenceError: Wicket is not defined
>
> Wicket.Ajax.baseUrl="pages/MyPageForm?session=qN46B2h...
> Wicket.Event.add(window, "domready", function(event) {
>
> It appears to be the fist time Wicket.Ajax or Wicket.Event occurs.
>
> I also see this error which doesn't seem to be related to Wicket other
> than the fact that it disappears when I reload.
>
> Uncaught ReferenceError: $ is not defined
> at MyPageForm-ver-68914D2B0F86742C02F38FA95791B4BD.js:445
>
> This is the line:
>
> $(document).ready(function() { ... }
>
>
>
> -Original Message-
> From: Martin Grigorov
> Sent: Thursday, October 21, 2021 1:21 AM
> To: users@wicket.apache.org
> Subject: Re: ContextRelativeResourceReference CSS rendering problem
>
> CAUTION: This email originated from outside of NISC or its subsidiaries.
> Do not click links or open attachments unless you recognize the sender and
> know the content is safe.
>
>
> Hi,
>
> On Thu, Oct 21, 2021 at 1:15 AM Greg Dunn wrote:
>
> > I'm using the following code under Wicket 9 to load a CSS file
> >
> >
> >
> > private static final ContextRelativeResourceReference CSS_FILE =
> >
> > new ContextRelativeResourceReference("style/cssFile.css",
> > false);
> >
> >
> >
> > @Override
> >
> > public void renderHead(IHeaderResponse response) {
> >
> > response.render(CssHeaderItem.forReference(CSS_FILE));
> >
> > super.renderHead(response);
> >
> > }
> >
> >
> >
> > When the page loads the CSS is not rendered at all. Looking at the
> > source I see the link to the CSS file with a nonce as expected. If I
> > refresh the page in the browser then it renders with the CSS as expected.
> >
>
> "When the page loads the CSS is not rendered at all." -> this sounds like
> the is not rendered on the first load "Looking at the source I see
> the link to the CSS file with a nonce as expected." -> this sounds like the
> is rendered properly on the second load "If I refresh the page in
> the browser then it renders with the CSS as expected." -> on the third load
> it works again
>
> So, it seems it does not work only on the first load! Correct ?
>
> Are there any JavaScript errors in the browser console ?
> Try disabling temporarily CSP. Maybe the nonce is not correct on the first
> load and the browser prevents the loading.
>
>
> >
> >
> > I would appreciate any assistance in resolving this. Thanks.
> >
> >
>
--
Best regards,
Maxim
Re: About jQuery 2.2.4 vulnerability
On Wed, 20 Oct 2021 at 17:21, Shengche Hsiao
wrote:
> Dear Martin
>
> After I applied the code, the website showed exceptions below
>
>
> ERROR [org.apache.wicket.DefaultExceptionMapper] (default task-2521)
> Unexpected error occurred: org.apache.wicket.WicketRuntimeException: An
> error occurred while generating an Url for handler
> 'ResourceReferenceRequestHandler{resourceReference=scope:
> org.apache.wicket.resource.JQueryResourceReference; name:
> jquery/jquery-2.2.4.js; locale: null; style: null; variation: null,
> pageParameters=}'
>
>
>
> Caused by:
> org.apache.wicket.request.resource.PackageResource$PackageResourceBlockedException:
> Access denied to (static) package resource
> org/apache/wicket/resource/jquery/jquery-2.2.4.js. See IPackageResourceGuard
>
>
It seems you are still using 2.2.4
Please ensure it is switched via
`getJavaScriptLibrarySettings().setJQueryReference`
>
>
> From: Martin Grigorov
> Date: Wednesday, October 20, 2021 at 14:34
> To: users@wicket.apache.org
> Subject: Re: About jQuery 2.2.4 vulnerability
> You could use SecurePackageResourceGuard to forbid access to a resource.
> In YourApplication#init():
>
> SecurePackageResourceGuard guard = (SecurePackageResourceGuard)
> getResourceSettings().getPackageResourceGuard();
> guard.addPattern("-**/jquery-2*.js");
>
> On Wed, Oct 20, 2021 at 9:25 AM Shengche Hsiao
> wrote:
>
> > Dear Martin
> >
> > I actually configured with jQuery version 3 on Application, and on
> browser
> > console showed jquery version with 3.6.0. But the scanner still find this
> > url [
> >
> https://mysite/wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-2.2.4-v-6233386130326534.js
> ]<
> https://mysite/wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-2.2.4-v-6233386130326534.js%5d
> >
> > appears. I know this resource is generated automatically by Wicket 8.13.0
> > (our project), and I don’t want this url resource be retrieved by
> scanner.
> > How to do that?
> >
> >
> > From: Martin Grigorov
> > Date: Wednesday, October 20, 2021 at 14:17
> > To: users@wicket.apache.org
> > Subject: Re: About jQuery 2.2.4 vulnerability
> > Hi,
> >
> > On Wed, Oct 20, 2021 at 5:46 AM Shengche Hsiao
> > wrote:
> >
> > > Dear All
> > >
> > > Recently, our website made a vulnerability scanning. The report shows
> > >
> >
> [/wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-2.2.4-v-
> > > 6233386130326534.js] as a vulnerability library. How do I disallow
> output
> > > this jquery version to avoid scan?
> > >
> >
> > I don't understand your question. Please re-phrase if the following does
> > not help you!
> >
> > You can upgrade jQuery by adding such code to YourApplication#init():
> >
> > getJavaScriptLibrarySettings().setJQueryReference(new
> > JavaScriptResourceReference(MyClass.class, "jquery-x.y.z.js"));
> > you could
> > use org.apache.wicket.resource.JQueryResourceReference#INSTANCE_3, for
> > example
> >
> >
> > >
> > > Thanks
> > >
> >
>
--
Best regards,
Maxim
[ANNOUNCE] WicketStuff 9.5.0 Released
WicketStuff core 9.5.0 based on Apache Wicket 9.5.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (5): Switching to the next development version Dependencies are updated Select2 and friends are updated Dependencies are updated wicketstuff 9.5.0 is released Sven Meier (2): 709 removed browser detection Merge pull request #710 from wicketstuff/dependabot/maven/com.thoughtworks.xstream-xstream-1.4.18 dependabot[bot] (1): Bump xstream from 1.4.17 to 1.4.18 The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: login captcha issue
You can set-up NoVersionMapper https://stackoverflow.com/questions/8602489/delete-version-number-in-url from mobile (sorry for typos ;) On Sat, Jul 31, 2021, 22:39 vahid ghasemi wrote: > Hello > I have a login form with a captcha. > I tested my form with Burp suite (penetration test tool). > in Burp I can send header requests a lot of time for brood force(just > change password). > this problem is because of the number at end of my > URL(localhost:8080/login?1). > so with this way attackers can bypass captcha. > how can i fix this problem. >
[ANNOUNCE] WicketStuff 8.13.0 Released
WicketStuff core 8.13.0 based on Apache Wicket 8.13.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (4): Switching to the next development version Dependencies are updated Dependencies are updated 8.13.0 release The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.4.0 Released
WicketStuff core 9.4.0 based on Apache Wicket 9.4.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (4): Switching to the next development version jython version is extracted to variable Dependencies are updated wicketstuff-core-9.4.0 released Sven Meier (3): issue 707 disable async page storing issue #707 use specific key for InSessionPageStore issue #707 metaDataKey should be static dependabot[bot] (1): Bump xstream from 1.4.16 to 1.4.17 (#706) The WicketStuff team
Re: pass error in submit method
Maybe it would be better to perform checks during validation ? from mobile (sorry for typos ;) On Tue, Jun 29, 2021, 22:33 vahid ghasemi wrote: > Hello > How can I pass an error in an onSubmit method? > I have some errors that can detect in the onSubmit method. > I throw exceptions at end of the onSubmit method. > In the catch block, I call the error method, but after that, I expect to > don't go into the afterOnSubmit method, but he will go and I am getting > the wrong response. >
Re: reset form
you have to add the fields to the target
On Tue, 29 Jun 2021 at 15:22, vahid ghasemi
wrote:
> First, thanks for the speed of your support.
>
>1 AjaxButton reset = new AjaxButton("reset") {
>
>2 @Override
>
>3public void onSubmit(AjaxRequestTarget target) {
>
>4 name = nationalCode = email = phone = password =
> confirmPassword = "";
>
>5 target.add(form);
>
>6 }
>
>7 };
>8 reset.setDefaultFormProcessing(false);
>
> #setDefaultFormProcessing is working and breakpoint goes in line 4. but
> after running code my inputs are still filled with values that have been
> inside.
>
> Sven Meier <s...@meiers.net> در تاریخ سهشنبه ۲۹ ژوئن ۲۰۲۱ ساعت
> ۱۲:۲۶ نوشت:
>
> > Hi,
> >
> > you have to call #setDefaultFormProcessing(false).
> >
> > Have fun
> > Sven
> >
> >
> > On 29.06.21 09:46, vahid ghasemi wrote:
> > > Hello guys.
> > > I have a form that has two buttons (Submit, Reset) and my form is
> > > CompoundPropertiesModel.
> > > The type of these buttons are AjaxButtons.
> > > but Reset only works when the form is valid, otherwise it goes into the
> > > onError method.
> > > The type of reset button tag is "reset" and also the submit button is
> > > "submit".
> > > Before submitting the form (and without the wicket ajax button for
> reset
> > > button) the reset button is working. But after submitting when I click
> on
> > > the reset button (still without the wicket ajax button) my inputs don't
> > go
> > > empty.
> > > So i think my problem was for CompoundPropertiesModel and i should set
> > > empty fields of class and i need to add a wicket button to reset button
> > > that reset inputs.
> > > But the reset buttons it's not working because he thinks it is a submit
> > > button.
> > > So my questions are:
> > > 1- How can i add some button link reset button for working when form is
> > not
> > > valid.
> > > 2- What is the best way to reset the form with a button?
> > > 3- why the reset button (just with type="reset") is not working after
> > > submitting form?
> > >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
--
Best regards,
Maxim
[ANNOUNCE] WicketStuff 7.18.0 Released
WicketStuff core 7.18.0 based on Apache Wicket 7.18.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (4): Switching to the next development version Xstream is updated Xstream jdk7 wicketstuff 7.18.0 released The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 8.12.0 Released
WicketStuff core 8.12.0 based on Apache Wicket 8.12.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (3): Switching to the next development version, bcprov is updated Dependencies are updated, build is fixed WicketStuff Core 8.12.0 Martin Grigorov (1): Fixes #704 - Round the scroll properties The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.3.0 Released
WicketStuff core 9.3.0 based on Apache Wicket 9.3.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (4): Switching to the next development version Bcprov is updated, typo in version is fixed Dependencies are updated, build is fixed Wicketstuff 9.3.0 is released dependabot[bot] (3): Bump groovy from 3.0.6 to 3.0.7 (#701) Bump xstream from 1.4.14 to 1.4.15 (#703) Bump xstream from 1.4.15 to 1.4.16 (#705) Martin Grigorov (1): Fixes #704 - Round the scroll properties Martin Tzvetanov Grigorov (1): Update Scala to 2.13.5 Sven Meier (1): fix NewPage for #702 The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Error 502 for examples8x
Have checked wrong VM :(( everything seems to work now (VM was rebooted) On Tue, 19 Jan 2021 at 12:00, Maxim Solodovnik wrote: > weird enough :( > docker processes are up > Apache is OK > > will try to check the logs ... > > > On Tue, 19 Jan 2021 at 03:44, Leonardo D'Alimonte > wrote: > >> I think error 502 - Proxy error happened again for Wicket 8 examples URL.. >> >> On Fri, Dec 25, 2020 at 9:16 AM Maxim Solodovnik >> wrote: >> >> > Just have checked: works for me :) >> > >> > On Wed, 23 Dec 2020 at 20:30, Francois Meillet < >> francois.meil...@gmail.com >> > > >> > wrote: >> > >> > > There is a 502 for https://examples8x.wicket.apache.org/index.html < >> > > https://examples8x.wicket.apache.org/index.html> >> > > >> > > >> > > François >> > > >> > > >> > > >> > > >> > >> > -- >> > Best regards, >> > Maxim >> > >> >> >> -- >> Leonardo >> > > > -- > Best regards, > Maxim > -- Best regards, Maxim
Re: Error 502 for examples8x
weird enough :( docker processes are up Apache is OK will try to check the logs ... On Tue, 19 Jan 2021 at 03:44, Leonardo D'Alimonte wrote: > I think error 502 - Proxy error happened again for Wicket 8 examples URL.. > > On Fri, Dec 25, 2020 at 9:16 AM Maxim Solodovnik > wrote: > > > Just have checked: works for me :) > > > > On Wed, 23 Dec 2020 at 20:30, Francois Meillet < > francois.meil...@gmail.com > > > > > wrote: > > > > > There is a 502 for https://examples8x.wicket.apache.org/index.html < > > > https://examples8x.wicket.apache.org/index.html> > > > > > > > > > François > > > > > > > > > > > > > > > > -- > > Best regards, > > Maxim > > > > > -- > Leonardo > -- Best regards, Maxim
Re: Error 502 for examples8x
Just have checked: works for me :) On Wed, 23 Dec 2020 at 20:30, Francois Meillet wrote: > There is a 502 for https://examples8x.wicket.apache.org/index.html < > https://examples8x.wicket.apache.org/index.html> > > > François > > > > -- Best regards, Maxim
[ANNOUNCE] WicketStuff 8.11.0 Released
WicketStuff core 8.11.0 based on Apache Wicket 8.11.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (4): Switching to the next development version Xstream is updated Dependencies and plugins are updated wicketstuff-core-8.11.0 is released The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.2.0 Released
WicketStuff core 9.2.0 based on Apache Wicket 9.2.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (5): Switching to the next development version Xstream is updated Versions are fixed Dependencies and plugins are updated Wicketstuff 9.2.0 is released The WicketStuff team
Re: Prevent script-injection attacks from user's input
You can completely disable inline scripts using strict CSP
And of cause this is you who output the script entered to the page :)
If it is done via Label just remove 'setEscapeModelStrings(false)'
If you need to accept and display HTML input, you can 'sanitize' form value
from mobile (sorry for typos ;)
On Tue, Oct 27, 2020, 07:34 Arunachalam Sibisakkaravarthi <
arunacha...@mcruncher.com> wrote:
> Hi guys,
> JS script alert is displayed when user input alert('xss
> attacks') and submit the form. How to handle this? Basically I
> want to prevent Cross-Site-Scripting from user inputs.
> Is it possible to do this globally since our Wicket Webapp is big?
> I found the below post which is discussed in 2010.
> Preventing-user-input-script-injection-attacks
> <
> http://apache-wicket.1842946.n4.nabble.com/Preventing-user-input-script-injection-attacks-td3059119.html
> >
>
>
>
> *Thanks And RegardsSibi.ArunachalammCruncher*
>
Re: Apache Wicket - Enforcing POST on Ajax calls
+1
On Mon, 19 Oct 2020 at 17:28, Martin Grigorov wrote:
> Hi Eric,
>
> You can implement it yourself:
>
> In #onUpdate(AjaxRequestTarget) start with:
>
> AjaxRequestAttributes attrs = getAttributes();
> String desiredMethod = attrs.getMethod().toString();
> String actualMethod = ((HttpServletRequest)
> RequestCycle.get().getRequest().getContainerRequest()).getMethod();
> if (!desiredMethod.equalsIgnoreCase(actualMethod)) {}
>
> @devs: What do you think about adding the above to
> AjaxFormComponentUpdatingBehavior#onEvent() ?
> We can add #onMethodMismatch() to AjaxFormComponentUpdatingBehavior that is
> similar to one in Form. If it returns ABORT then we will execute the code
> above. If it returns CONTINUE (the default) then no need to calculate the
> AjaxRequestAttributes
>
>
> On Sun, Oct 18, 2020 at 11:40 PM Sven Meier wrote:
>
> > Hi,
> >
> > with AjaxFormComponentUpdatingBehavior only a single component is
> > processed and not the complete Form.
> > So method mismatches are not checked.
> >
> > Have fun
> > Sven
> >
> >
> > On 17.10.20 14:34, Eric Hamel wrote:
> > > Looking at our implementation, we are using an
> > AjaxFormComponentUpdatingBehavior to trigger our data save.
> > >
> > > Even though we do a have parent form the onSubmit is never called.
> > >
> > > Is there an alternative to the onMethodMismatch ?
> > >
> > > —
> > > Eric Hamel
> > > Senior Project Manager
> > > Albany Information Technology Group
> > > C. 518-698-4503
> > >
> > >> On Oct 16, 2020, at 4:32 PM, Martin Grigorov
> > wrote:
> > >>
> > >> On Fri, Oct 16, 2020, 23:27 Eric Hamel
> wrote:
> > >>
> > >>> I apologize in advance for my vague question. Our Wicket 8 based
> > >>> application was submitted to pen testing from our EISO. While I
> > understand
> > >>> the finding, I'm not 100% sure I understand the problem nor do I know
> > how
> > >>> to address it.
> > >>>
> > >>> In one of our complex forms that uses Ajax Calls to automatically
> > update
> > >>> the DB when the fields lose focus, the tester made the following
> > remark:
> > >>>
> > >>> Applications accepts GET requests for coded POST Ajax calls –
> > parameters
> > >>> can be passed in URL
> > >>>
> > >>> It appears that through his "fuzzer", even though our requests are
> > marked
> > >>> as POST, it still processes GET requests. Is there a way to enforce
> > POST ?
> > >>> Is there any way to mitigate this issue globally from a configuration
> > >>> standpoint ?
> > >>>
> > >>
> > >> See Form#onMethodMismatch()
> > >>
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > For additional commands, e-mail: users-h...@wicket.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
--
Best regards,
Maxim
Re: [ANNOUNCE] WicketStuff 9.1.0 Released
You are right Martin :( This time "Reply All" was a bad idea :( On Mon, 12 Oct 2020 at 17:53, Martin Grigorov wrote: > > Ernesto, Maxim, > > Please do not use announce@ for such discussions! > You can just create an issue at > https://github.com/sebfz1/wicket-jquery-ui/issues/new > > On Mon, Oct 12, 2020 at 1:47 PM Maxim Solodovnik > wrote: > > > Are you using `9.x` branch? > > > > On Mon, 12 Oct 2020 at 17:26, Ernesto Reinaldo Barreiro > > wrote: > > > > > > Or has source code moved to somewhere else? > > > > > > On Mon, Oct 12, 2020 at 1:20 PM Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> wrote: > > > > > > > I see > > > > > > > > https://github.com/sebfz1/wicket-jquery-ui > > > > > > > > Doesn't compile against wicket 9.1.0. I will fix and create PR > > > > > > > > > > > > On Mon, Oct 12, 2020 at 12:20 PM Ernesto Reinaldo Barreiro < > > > > reier...@gmail.com> wrote: > > > > > > > >> Many thanks. Can > > > >> > > > >> https://github.com/sebfz1/wicket-jquery-ui > > > >> > > > >> Be released too? > > > >> > > > >> > > > >> On Mon, Oct 12, 2020 at 8:56 AM Maxim Solodovnik > > > >> wrote: > > > >> > > > >>> WicketStuff core 9.1.0 based on Apache Wicket 9.1.0 is released > > > >>> and soon will be available at Maven Central! > > > >>> > > > >>> The changelog is: > > > >>> > > > >>> Maxim Solodovnik (7): > > > >>> Switching to the next development version > > > >>> Fixes issue #699: firstDayOfWeek should be displayed as > > expected > > > >>> wicketstuff-datetime-yui: tests are fixed > > > >>> Typos and formatting are fixed, some dependencies are updated > > > >>> Wicket is switched back to SNAPSHOT > > > >>> Release preparation: dependencies are updated > > > >>> wicketstuff-core-9.1.0 release > > > >>> > > > >>> Andrea Del Bene (2): > > > >>> Applied scope test to xml dependencies > > > >>> Try new mvn parameters to avoid "peer not authenticated" error > > > >>> > > > >>> Erik Geletti (1): > > > >>> Bootstrap version 3 (#698) > > > >>> > > > >>> The WicketStuff team > > > >>> > > > >>> - > > > >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > >>> For additional commands, e-mail: users-h...@wicket.apache.org > > > >>> > > > >>> > > > >> > > > >> -- > > > >> Regards - Ernesto Reinaldo Barreiro > > > >> > > > > > > > > > > > > -- > > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > > > > > -- > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > -- > > Best regards, > > Maxim > > -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [ANNOUNCE] WicketStuff 9.1.0 Released
Are you using `9.x` branch? On Mon, 12 Oct 2020 at 17:26, Ernesto Reinaldo Barreiro wrote: > > Or has source code moved to somewhere else? > > On Mon, Oct 12, 2020 at 1:20 PM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > I see > > > > https://github.com/sebfz1/wicket-jquery-ui > > > > Doesn't compile against wicket 9.1.0. I will fix and create PR > > > > > > On Mon, Oct 12, 2020 at 12:20 PM Ernesto Reinaldo Barreiro < > > reier...@gmail.com> wrote: > > > >> Many thanks. Can > >> > >> https://github.com/sebfz1/wicket-jquery-ui > >> > >> Be released too? > >> > >> > >> On Mon, Oct 12, 2020 at 8:56 AM Maxim Solodovnik > >> wrote: > >> > >>> WicketStuff core 9.1.0 based on Apache Wicket 9.1.0 is released > >>> and soon will be available at Maven Central! > >>> > >>> The changelog is: > >>> > >>> Maxim Solodovnik (7): > >>> Switching to the next development version > >>> Fixes issue #699: firstDayOfWeek should be displayed as expected > >>> wicketstuff-datetime-yui: tests are fixed > >>> Typos and formatting are fixed, some dependencies are updated > >>> Wicket is switched back to SNAPSHOT > >>> Release preparation: dependencies are updated > >>> wicketstuff-core-9.1.0 release > >>> > >>> Andrea Del Bene (2): > >>> Applied scope test to xml dependencies > >>> Try new mvn parameters to avoid "peer not authenticated" error > >>> > >>> Erik Geletti (1): > >>> Bootstrap version 3 (#698) > >>> > >>> The WicketStuff team > >>> > >>> - > >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >>> For additional commands, e-mail: users-h...@wicket.apache.org > >>> > >>> > >> > >> -- > >> Regards - Ernesto Reinaldo Barreiro > >> > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > Regards - Ernesto Reinaldo Barreiro -- Best regards, Maxim - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 9.1.0 Released
WicketStuff core 9.1.0 based on Apache Wicket 9.1.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (7): Switching to the next development version Fixes issue #699: firstDayOfWeek should be displayed as expected wicketstuff-datetime-yui: tests are fixed Typos and formatting are fixed, some dependencies are updated Wicket is switched back to SNAPSHOT Release preparation: dependencies are updated wicketstuff-core-9.1.0 release Andrea Del Bene (2): Applied scope test to xml dependencies Try new mvn parameters to avoid "peer not authenticated" error Erik Geletti (1): Bootstrap version 3 (#698) The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] WicketStuff 8.10.0 Released
WicketStuff core 8.10.0 based on Apache Wicket 8.10.0 is released and soon will be available at Maven Central! The changelog is: Andrea Del Bene (1): Applied scope test to xml dependencies Maxim Solodovnik (3): Switching to the next development version Release preparation: dependencies are updated wicketstuff-core-8.10.0 release The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Page locked for a long time
Thanks a lot Bas! miss this call everything start to work as expected :) sorry for the noise On Fri, 24 Jul 2020 at 12:05, Bas Gooren wrote: > Hi Maxim, > > You need to call parseFileParts() on the request yourself before accessing > files and post parameters, or there are no parts and post parameters. > > Am on mobile so cannot quickly find java doc for 8 or 9 but api is the > same: > > > https://ci.apache.org/projects/wicket/apidocs/org/apache/wicket/protocol/http/servlet/MultipartServletWebRequest.html#parseFileParts() > > // Bas > > Verstuurd vanaf mijn iPhone > > Op 24 jul. 2020 om 05:49 heeft Maxim Solodovnik het > volgende geschreven: > > Hello Martin, All, > > finally I have started to implement this functionality and faced weird > issue: no post parameters are retrievable :(( > I was able to reproduce this using quickstart > https://github.com/solomax/upload-resource > Can you please take a look at it? > > On Mon, 6 Jul 2020 at 14:33, Thomas Heigl wrote: > > We've been using Martin's solution with JQueryFileUpload for years and it > > works great. > > > Best, > > > Thomas > > > On Mon, Jul 6, 2020 at 8:59 AM Maxim Solodovnik > > wrote: > > > Thanks a million :)) > > > On Mon, 6 Jul 2020 at 13:43, Martin Grigorov > > wrote: > > > On Sun, Jul 5, 2020 at 9:16 PM Sven Meier wrote: > > > Hi Maxim, > > > you'll have to upload these files to a resource separately. > > > I'm not aware of a reusable solution for that. > > > > Here is a blog article on this topic: > > http://wicketinaction.com/2012/11/uploading-files-to-wicket-iresource/ > > and > > its demo app: > > https://github.com/martin-g/blogs/tree/master/file-upload > > > > > Have fun > > Sven > > > > On 05.07.20 17:20, Maxim Solodovnik wrote: > > Hello All, > > > our app allows huge file uploads > > I have noticed the page is locked while incoming input stream is > > being > > copied > > (might take more than an hour) > > > at java.base@11.0.7/java.io > > .InputStream.read(InputStream.java:205) > > at org.apache.commons.fileupload.util.Streams.copy(Streams.java:98) > > at org.apache.commons.fileupload.util.Streams.copy(Streams.java:68) > > at > > > > > > > org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:346) > > at > > > > > > > org.apache.wicket.protocol.http.servlet.MultipartServletWebRequestImpl.parseFileParts(MultipartServletWebRequestImpl.java:196) > > at > > > org.apache.wicket.markup.html.form.Form.handleMultiPart(Form.java:1470) > > > Are there any options to prevent page lock? > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > -- > > Best regards, > > Maxim > > > > > > -- > Best regards, > Maxim > -- Best regards, Maxim
Re: Page locked for a long time
Hello Martin, All, finally I have started to implement this functionality and faced weird issue: no post parameters are retrievable :(( I was able to reproduce this using quickstart https://github.com/solomax/upload-resource Can you please take a look at it? On Mon, 6 Jul 2020 at 14:33, Thomas Heigl wrote: > We've been using Martin's solution with JQueryFileUpload for years and it > works great. > > Best, > > Thomas > > On Mon, Jul 6, 2020 at 8:59 AM Maxim Solodovnik > wrote: > > > Thanks a million :)) > > > > On Mon, 6 Jul 2020 at 13:43, Martin Grigorov > wrote: > > > > > On Sun, Jul 5, 2020 at 9:16 PM Sven Meier wrote: > > > > > > > Hi Maxim, > > > > > > > > you'll have to upload these files to a resource separately. > > > > > > > > I'm not aware of a reusable solution for that. > > > > > > > > > > Here is a blog article on this topic: > > > http://wicketinaction.com/2012/11/uploading-files-to-wicket-iresource/ > > and > > > its demo app: > https://github.com/martin-g/blogs/tree/master/file-upload > > > > > > > > > > > > > > Have fun > > > > Sven > > > > > > > > > > > > On 05.07.20 17:20, Maxim Solodovnik wrote: > > > > > Hello All, > > > > > > > > > > our app allows huge file uploads > > > > > I have noticed the page is locked while incoming input stream is > > being > > > > > copied > > > > > (might take more than an hour) > > > > > > > > > > at java.base@11.0.7/java.io > .InputStream.read(InputStream.java:205) > > > > > at org.apache.commons.fileupload.util.Streams.copy(Streams.java:98) > > > > > at org.apache.commons.fileupload.util.Streams.copy(Streams.java:68) > > > > > at > > > > > > > > > > > > > > > org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:346) > > > > > at > > > > > > > > > > > > > > > org.apache.wicket.protocol.http.servlet.MultipartServletWebRequestImpl.parseFileParts(MultipartServletWebRequestImpl.java:196) > > > > > at > > > > > org.apache.wicket.markup.html.form.Form.handleMultiPart(Form.java:1470) > > > > > > > > > > Are there any options to prevent page lock? > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > > > > > > > -- > > Best regards, > > Maxim > > > -- Best regards, Maxim
[ANNOUNCE] WicketStuff 7.17.0 Released
WicketStuff core 7.17.0 based on Apache Wicket 7.17.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (4): Switching to the next development version Fixed issue #690: commons-io is updated Dependencies are updated (partially) wicketstuff-core 7.17.0 is released The WicketStuff team
[ANNOUNCE] WicketStuff 8.9.0 Released
WicketStuff core 8.9.0 based on Apache Wicket 8.9.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (4): Switching to the next development version Release preparation: dependencies are updated Possibly fixes #694: alternative way to resolve class wicketstuff-8.9.0 is released The WicketStuff team
[ANNOUNCE] WicketStuff 9.0.0 Released
WicketStuff core 9.0.0 based on Apache Wicket 9.0.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (6): Switching to the next development version Merge branch 'master' of github.com:wicketstuff/core Tests should be fixed Release preparation: dependencies are updated Possibly fixes #694: alternative way to resolve class Wicketstuff 9.0.0 is released dependabot[bot] (3): Bump ignite-core in /datastores-parent/datastore-ignite (#692) Bump log4j.version from 2.13.1 to 2.13.3 (#695) Bump log4j-core (#696) The WicketStuff team
Re: Page locked for a long time
Thanks a million :)) On Mon, 6 Jul 2020 at 13:43, Martin Grigorov wrote: > On Sun, Jul 5, 2020 at 9:16 PM Sven Meier wrote: > > > Hi Maxim, > > > > you'll have to upload these files to a resource separately. > > > > I'm not aware of a reusable solution for that. > > > > Here is a blog article on this topic: > http://wicketinaction.com/2012/11/uploading-files-to-wicket-iresource/ and > its demo app: https://github.com/martin-g/blogs/tree/master/file-upload > > > > > > Have fun > > Sven > > > > > > On 05.07.20 17:20, Maxim Solodovnik wrote: > > > Hello All, > > > > > > our app allows huge file uploads > > > I have noticed the page is locked while incoming input stream is being > > > copied > > > (might take more than an hour) > > > > > > at java.base@11.0.7/java.io.InputStream.read(InputStream.java:205) > > > at org.apache.commons.fileupload.util.Streams.copy(Streams.java:98) > > > at org.apache.commons.fileupload.util.Streams.copy(Streams.java:68) > > > at > > > > > > org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:346) > > > at > > > > > > org.apache.wicket.protocol.http.servlet.MultipartServletWebRequestImpl.parseFileParts(MultipartServletWebRequestImpl.java:196) > > > at > > org.apache.wicket.markup.html.form.Form.handleMultiPart(Form.java:1470) > > > > > > Are there any options to prevent page lock? > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > -- Best regards, Maxim
Page locked for a long time
Hello All, our app allows huge file uploads I have noticed the page is locked while incoming input stream is being copied (might take more than an hour) at java.base@11.0.7/java.io.InputStream.read(InputStream.java:205) at org.apache.commons.fileupload.util.Streams.copy(Streams.java:98) at org.apache.commons.fileupload.util.Streams.copy(Streams.java:68) at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:346) at org.apache.wicket.protocol.http.servlet.MultipartServletWebRequestImpl.parseFileParts(MultipartServletWebRequestImpl.java:196) at org.apache.wicket.markup.html.form.Form.handleMultiPart(Form.java:1470) Are there any options to prevent page lock? -- Best regards, Maxim
Re: WebSocket onClose/onError/onAbort is not being called
Thanks Martin! https://issues.apache.org/jira/browse/WICKET-6782 will create PR in a moment :) On Wed, 6 May 2020 at 00:22, Martin Grigorov wrote: > Hi Maxim, > > On Fri, May 1, 2020 at 2:22 PM Maxim Solodovnik > wrote: > > > On Fri, 1 May 2020 at 18:15, Martin Grigorov > wrote: > > > > > Hi Maxim, > > > > > > On Fri, May 1, 2020 at 1:31 PM Maxim Solodovnik > > > wrote: > > > > > > > Hello Martin, > > > > > > > > WicketEndpoint#onError is being called > > > > "*ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100 > > > > [EventExec-e2-t9] - An error occurred in web socket connection with > id > > : > > > > 10" > > > > > > > > The problem WebSocketBehavior#onError is not being called > > > > So my application doesn't get notified the connection has been closed > > > > > > > > > > > > > Then it must be somewhere in Wicket. > > > Check that [2] is called. > > > > > > > Yes it is called > > > > > > > Then [3], then [4]. From here on it is Wicket Event propagation [5]. It > > > > > > > [3] and [4] are not called > > As you can see from the log branch at > > > > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L299 > > is in effect: > > > > At > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L223 > we > check > whether the connection is still opened or it is a ClosedMessage. > ClosedMessage is broadcasted exactly for this reason: > > https://github.com/apache/wicket/commit/ffa34c6bfbd2ccd8340e23ff1601edd3e0e941d6 > We should simplify this condition to allow ErrorMessage too. Maybe even > AbortedMessage. > For the erroneous kind of messages we can even remove the connection from > the registry at the bottom of this method. > Please play with it and suggest a change! > > Martin > > > > DEBUG 05-01 16:10:21.741 o.a.w.p.w.a.AbstractWebSocketProcessor:299 > > [EventExec-e2-t9] - Either there is no > > > > > connection(org.apache.wicket.protocol.ws.javax.JavaxWebSocketConnection@43539f89 > > ) > > or it is closed. > > > > > > > > > > > won't find your behavior if it is not enabled or any of if its > component > > > hierarchy is disabled/invisible. > > > > > > > > > 2. > > > > > > > > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L202 > > > 3. > > > > > > > > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L272 > > > 4. * > > > > > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/WebSocketMessageBroadcastHandler.java#L69 > > > < > > > > > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/WebSocketMessageBroadcastHandler.java#L69 > > > >* > > > 5. > > > > > > > > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/WebSocketBehavior.java#L86 > > > > > > > > > > :( > > > > > > > > On Fri, 1 May 2020 at 17:12, Martin Grigorov > > > wrote: > > > > > > > > > Hi Maxim, > > > > > > > > > > If WicketEndpoint#onError() [1] is not called then probably there > is > > a > > > > bug > > > > > in Tomcat. > > > > > I suggest you to post this question at Tomcat's users@. > > > > > > > > > > 1. > > > > > >
Re: WebSocket onClose/onError/onAbort is not being called
Here are some more details on this issue In our code I'm using IWebSocketConnection.sendMessage(String) method The call is wrapped with try/catch to correctly handle any exception [1] The problem is hard to reproduce due to IOException should happen exactly at time of sendMessage do it's job (in original report author hammer the page with F5 until error will occur) As a result my try/catch doesn't play, I got "zombie" IWebSocketConnection in IWebSocketConnectionRegistry and incorrect application state due to I'm expecting to get disconnect from onClose/onError/onAbort of my WebSocketBehavior I see no other option than create periodic task to check for "zombies" in IWebSocketConnectionRegistry and restore application state Are there any other options? [1] https://github.com/apache/openmeetings/blob/master/openmeetings-core/src/main/java/org/apache/openmeetings/core/util/WebSocketHelper.java#L76 On Fri, 1 May 2020 at 18:21, Maxim Solodovnik wrote: > > On Fri, 1 May 2020 at 18:15, Martin Grigorov wrote: > >> Hi Maxim, >> >> On Fri, May 1, 2020 at 1:31 PM Maxim Solodovnik >> wrote: >> >> > Hello Martin, >> > >> > WicketEndpoint#onError is being called >> > "*ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100 >> > [EventExec-e2-t9] - An error occurred in web socket connection with id : >> > 10" >> > >> > The problem WebSocketBehavior#onError is not being called >> > So my application doesn't get notified the connection has been closed >> >> > >> >> Then it must be somewhere in Wicket. >> Check that [2] is called. >> > > Yes it is called > > >> Then [3], then [4]. From here on it is Wicket Event propagation [5]. It >> > > [3] and [4] are not called > As you can see from the log branch at > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L299 > is in effect: > > DEBUG 05-01 16:10:21.741 o.a.w.p.w.a.AbstractWebSocketProcessor:299 > [EventExec-e2-t9] - Either there is no > connection(org.apache.wicket.protocol.ws.javax.JavaxWebSocketConnection@43539f89) > or it is closed. > > > > >> won't find your behavior if it is not enabled or any of if its component >> hierarchy is disabled/invisible. >> >> >> 2. >> >> https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L202 >> 3. >> >> https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L272 >> 4. * >> https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/WebSocketMessageBroadcastHandler.java#L69 >> < >> https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/WebSocketMessageBroadcastHandler.java#L69 >> >* >> 5. >> >> https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/WebSocketBehavior.java#L86 >> >> >> > :( >> > >> > On Fri, 1 May 2020 at 17:12, Martin Grigorov >> wrote: >> > >> > > Hi Maxim, >> > > >> > > If WicketEndpoint#onError() [1] is not called then probably there is a >> > bug >> > > in Tomcat. >> > > I suggest you to post this question at Tomcat's users@. >> > > >> > > 1. >> > > >> > > >> > >> https://github.com/apache/wicket/blob/master/wicket-native-websocket/wicket-native-websocket-javax/src/main/java/org/apache/wicket/protocol/ws/javax/WicketEndpoint.java#L92 >> > > >> > > >> > > On Fri, May 1, 2020 at 12:21 PM Maxim Solodovnik < >> solomax...@gmail.com> >> > > wrote: >> > > >> > > > Hello, >> > > > >> > > > I'm having weird situation: WebSocket connection is closed on page >> > > reload, >> > > > but none of my onClose/onError/onAbort handlers are being called >> > > > I have change
Re: WebSocket onClose/onError/onAbort is not being called
On Fri, 1 May 2020 at 18:15, Martin Grigorov wrote: > Hi Maxim, > > On Fri, May 1, 2020 at 1:31 PM Maxim Solodovnik > wrote: > > > Hello Martin, > > > > WicketEndpoint#onError is being called > > "*ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100 > > [EventExec-e2-t9] - An error occurred in web socket connection with id : > > 10" > > > > The problem WebSocketBehavior#onError is not being called > > So my application doesn't get notified the connection has been closed > > > > > Then it must be somewhere in Wicket. > Check that [2] is called. > Yes it is called > Then [3], then [4]. From here on it is Wicket Event propagation [5]. It > [3] and [4] are not called As you can see from the log branch at https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L299 is in effect: DEBUG 05-01 16:10:21.741 o.a.w.p.w.a.AbstractWebSocketProcessor:299 [EventExec-e2-t9] - Either there is no connection(org.apache.wicket.protocol.ws.javax.JavaxWebSocketConnection@43539f89) or it is closed. > won't find your behavior if it is not enabled or any of if its component > hierarchy is disabled/invisible. > > > 2. > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L202 > 3. > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L272 > 4. * > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/WebSocketMessageBroadcastHandler.java#L69 > < > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/WebSocketMessageBroadcastHandler.java#L69 > >* > 5. > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/WebSocketBehavior.java#L86 > > > > :( > > > > On Fri, 1 May 2020 at 17:12, Martin Grigorov > wrote: > > > > > Hi Maxim, > > > > > > If WicketEndpoint#onError() [1] is not called then probably there is a > > bug > > > in Tomcat. > > > I suggest you to post this question at Tomcat's users@. > > > > > > 1. > > > > > > > > > https://github.com/apache/wicket/blob/master/wicket-native-websocket/wicket-native-websocket-javax/src/main/java/org/apache/wicket/protocol/ws/javax/WicketEndpoint.java#L92 > > > > > > > > > On Fri, May 1, 2020 at 12:21 PM Maxim Solodovnik > > > > wrote: > > > > > > > Hello, > > > > > > > > I'm having weird situation: WebSocket connection is closed on page > > > reload, > > > > but none of my onClose/onError/onAbort handlers are being called > > > > I have changed wicket version to latest SNAPSHOT and got some debug > > logs: > > > > > > > > *ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100 > > > > [EventExec-e2-t9] - An error occurred in web socket connection with > id > > > > : 10 > > > > java.io.IOException: java.io.IOException: Broken pipe > > > > at > > > > > > > > > > org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:315) > > > > at > > > > > > > > > > org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:258) > > > > at > > > > > > > > > > org.apache.tomcat.websocket.WsSession.sendCloseMessage(WsSession.java:612) > > > > at > > > > org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:497) > > > > at > > > > org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:459) > > > > at > > > > > > > > > > org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:313) > > > > at > > > > > > > > > > org.apach
Re: WebSocket onClose/onError/onAbort is not being called
Hello Martin, WicketEndpoint#onError is being called "*ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100 [EventExec-e2-t9] - An error occurred in web socket connection with id : 10" The problem WebSocketBehavior#onError is not being called So my application doesn't get notified the connection has been closed :( On Fri, 1 May 2020 at 17:12, Martin Grigorov wrote: > Hi Maxim, > > If WicketEndpoint#onError() [1] is not called then probably there is a bug > in Tomcat. > I suggest you to post this question at Tomcat's users@. > > 1. > > https://github.com/apache/wicket/blob/master/wicket-native-websocket/wicket-native-websocket-javax/src/main/java/org/apache/wicket/protocol/ws/javax/WicketEndpoint.java#L92 > > > On Fri, May 1, 2020 at 12:21 PM Maxim Solodovnik > wrote: > > > Hello, > > > > I'm having weird situation: WebSocket connection is closed on page > reload, > > but none of my onClose/onError/onAbort handlers are being called > > I have changed wicket version to latest SNAPSHOT and got some debug logs: > > > > *ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100 > > [EventExec-e2-t9] - An error occurred in web socket connection with id > > : 10 > > java.io.IOException: java.io.IOException: Broken pipe > > at > > > org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:315) > > at > > > org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:258) > > at > > > org.apache.tomcat.websocket.WsSession.sendCloseMessage(WsSession.java:612) > > at > > org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:497) > > at > > org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:459) > > at > > > org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:313) > > at > > > org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:250) > > at > > > org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:191) > > at > > > org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37) > > at org.apache.wicket.protocol.ws > > > .javax.JavaxWebSocketConnection.sendMessage(JavaxWebSocketConnection.java:81) > > at > > > org.apache.openmeetings.core.util.WebSocketHelper.lambda$sendClient$1(WebSocketHelper.java:75) > > at > > > org.apache.openmeetings.core.util.WebSocketHelper.lambda$sendClient$2(WebSocketHelper.java:94) > > at org.apache.wicket.protocol.ws > > .WebSocketSettings$SameThreadExecutor.run(WebSocketSettings.java:393) > > at > > > org.apache.openmeetings.core.util.WebSocketHelper.sendClient(WebSocketHelper.java:94) > > at > > > org.apache.openmeetings.core.util.WebSocketHelper.sendClient(WebSocketHelper.java:73) > > at > > > org.apache.openmeetings.core.remote.KurentoHandler.sendClient(KurentoHandler.java:209) > > at > > > org.apache.openmeetings.core.remote.KStream.lambda$createEndpoint$5(KStream.java:224) > > at > > > org.kurento.client.internal.client.RemoteObjectInvocationHandler.propagateEventTo(RemoteObjectInvocationHandler.java:281) > > at > > > org.kurento.client.internal.client.RemoteObjectInvocationHandler$1.onEvent(RemoteObjectInvocationHandler.java:208) > > at > > > org.kurento.client.internal.client.RemoteObject.fireEvent(RemoteObject.java:345) > > at > > > org.kurento.client.internal.client.RomClientObjectManager.processEvent(RomClientObjectManager.java:58) > > at > > > org.kurento.client.internal.transport.jsonrpc.RomClientJsonRpcClient.processEvent(RomClientJsonRpcClient.java:206) > > at > > > org.kurento.client.internal.transport.jsonrpc.RomClientJsonRpcClient.access$000(RomClientJsonRpcClient.java:74) > > at > > > org.kurento.client.internal.transport.jsonrpc.RomClientJsonRpcClient$1.handleRequest(RomClientJsonRpcClient.java:182) > > at > > > org.kurento.jsonrpc.internal.JsonRpcHandlerManager.handleRequest(JsonRpcHandlerManager.java:142) > > at > > > org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket$15.run(AbstractJsonRpcClientWebSocket.java:577) > > at > > > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > > at > > java.base/java.ut
WebSocket onClose/onError/onAbort is not being called
Hello, I'm having weird situation: WebSocket connection is closed on page reload, but none of my onClose/onError/onAbort handlers are being called I have changed wicket version to latest SNAPSHOT and got some debug logs: *ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100 [EventExec-e2-t9] - An error occurred in web socket connection with id : 10 java.io.IOException: java.io.IOException: Broken pipe at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:315) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:258) at org.apache.tomcat.websocket.WsSession.sendCloseMessage(WsSession.java:612) at org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:497) at org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:459) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:313) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:250) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:191) at org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37) at org.apache.wicket.protocol.ws.javax.JavaxWebSocketConnection.sendMessage(JavaxWebSocketConnection.java:81) at org.apache.openmeetings.core.util.WebSocketHelper.lambda$sendClient$1(WebSocketHelper.java:75) at org.apache.openmeetings.core.util.WebSocketHelper.lambda$sendClient$2(WebSocketHelper.java:94) at org.apache.wicket.protocol.ws.WebSocketSettings$SameThreadExecutor.run(WebSocketSettings.java:393) at org.apache.openmeetings.core.util.WebSocketHelper.sendClient(WebSocketHelper.java:94) at org.apache.openmeetings.core.util.WebSocketHelper.sendClient(WebSocketHelper.java:73) at org.apache.openmeetings.core.remote.KurentoHandler.sendClient(KurentoHandler.java:209) at org.apache.openmeetings.core.remote.KStream.lambda$createEndpoint$5(KStream.java:224) at org.kurento.client.internal.client.RemoteObjectInvocationHandler.propagateEventTo(RemoteObjectInvocationHandler.java:281) at org.kurento.client.internal.client.RemoteObjectInvocationHandler$1.onEvent(RemoteObjectInvocationHandler.java:208) at org.kurento.client.internal.client.RemoteObject.fireEvent(RemoteObject.java:345) at org.kurento.client.internal.client.RomClientObjectManager.processEvent(RomClientObjectManager.java:58) at org.kurento.client.internal.transport.jsonrpc.RomClientJsonRpcClient.processEvent(RomClientJsonRpcClient.java:206) at org.kurento.client.internal.transport.jsonrpc.RomClientJsonRpcClient.access$000(RomClientJsonRpcClient.java:74) at org.kurento.client.internal.transport.jsonrpc.RomClientJsonRpcClient$1.handleRequest(RomClientJsonRpcClient.java:182) at org.kurento.jsonrpc.internal.JsonRpcHandlerManager.handleRequest(JsonRpcHandlerManager.java:142) at org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket$15.run(AbstractJsonRpcClientWebSocket.java:577) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.io.IOException: Broken pipe at java.base/sun.nio.ch.FileDispatcherImpl.write0(Native Method) at java.base/sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47) at java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:113) at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:79) at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:50) at java.base/sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:466) at org.apache.tomcat.util.net.SecureNioChannel.flush(SecureNioChannel.java:145) at org.apache.tomcat.util.net.SecureNioChannel.write(SecureNioChannel.java:851) at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper$NioOperationState.run(NioEndpoint.java:1491) at org.apache.tomcat.util.net.SocketWrapperBase$OperationState.start(SocketWrapperBase.java:1015) at org.apache.tomcat.util.net.SocketWrapperBase.vectoredOperation(SocketWrapperBase.java:1426) at org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBase.java:1352) at org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBase.java:1323) at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:90) at
[ANNOUNCE] WicketStuff 8.8.0 Released
WicketStuff core 8.8.0 based on Apache Wicket 8.8.0 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (3): Switching to the next development version Dependencies and plugins are updated wicketstuff 8.8.0 is released The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Upgrade to Wicket 9: troubles with WicketTester and MockPageStore
On Fri, 10 Apr 2020 at 15:06, Francesco Chicchiriccò wrote: > On 2020/04/10 06:59:06, Sven Meier wrote: > > Hi Francesco, > > > > there was a slight difference in the mock setup, which should now be as > > in Wicket 8: > > > > https://issues.apache.org/jira/browse/WICKET-6766 > > > > Many thanks for testing with Wicket 9! > > Great spot Sven! > > Which is the SNAPSHOT version to try such a change? When the related > artifact will be available? > this is M6-SNAPSHOT M5 was just released ... > > Regards. > > > On 09.04.20 16:42, Francesco Chicchiriccò wrote: > > > On 2020/04/09 12:04:00, Sven Meier wrote: > > >> Hi Francesco, > > >> > > >> I'll have to check what has changed here. > > >> > > >> I wouldn't expect any problems with MockPageStore, but perhaps it > > >> changed slightly. > > >> > > >> Can you write a testcase that runs in Wicket 8 but fails in 9? > > > Not sure if I am able, but I'll try. > > > Meanwhile, should you get an enlightenment, please report. > > > > > > Regards. > > > > > >> On 09.04.20 12:20, Francesco Chicchiriccò wrote: > > >>> Hi all, > > >>> at Syncope we have been upgrading our Console and Enduser web > applications from Wicket 8 to 9.0.0-M5, in our master branch. > > >>> > > >>> The process have been quite smooth effectively, with a single > noticeable exception: in our tests we largely use WicketTester; we have > verified, however, that Pages in the MockPageStore are incrementing their > numericId during tests execution, even though they are still looked up by > their initial numericId. > > >>> > > >>> We are using this workaround: > > >>> > > >>> > https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/AbstractConsoleITCase.java#L107-L125 > > >>> > > >>> which is serving its purpose for the moment; please note that this > was not needed with Wicket 8. > > >>> > > >>> Are we missing something or the one above is effectively a bug? > > >>> > > >>> Thanks for your support. > > >>> Regards. > > >>> > > >>> - > > >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > >>> For additional commands, e-mail: users-h...@wicket.apache.org > > >>> > > >> - > > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > >> For additional commands, e-mail: users-h...@wicket.apache.org > > >> > > >> > > > - > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Best regards, Maxim
Re: Equivalent for PerSessionPageStore in Wicket 9
Released :) On Wed, 8 Apr 2020 at 15:41, Maxim Solodovnik wrote: > > OK > > Will start new release process in couple of hours > Please stop me if you will find any blocker :) > > On Wed, 8 Apr 2020 at 14:36, Thomas Heigl wrote: >> >> Hi Maxim, >> >> It works for me now! >> >> Thomas >> >> On Wed, Apr 8, 2020 at 9:17 AM Maxim Solodovnik >> wrote: >> >> > Thanks a million! >> > >> > On Wed, 8 Apr 2020 at 14:10, Thomas Heigl wrote: >> > > >> > > Hi Maxim, >> > > >> > > I'm testing against the snapshot now. Will get back to you shortly. >> > > >> > > Thomas >> > > >> > > On Wed, Apr 8, 2020 at 2:53 AM Maxim Solodovnik >> > > wrote: >> > > >> > > > Hello All, >> > > > >> > > > M5 seems to be broken (deploy has failed more than 10 times during my >> > > > build attempts) >> > > > I have to start another release >> > > > Could you please tell when can I start? >> > > > >> > > > On Wed, 8 Apr 2020 at 07:01, Maxim Solodovnik >> > > > wrote: >> > > > > >> > > > > Hello Thomas, >> > > > > >> > > > > Please test M6-SNAPSHOT (so I don't have to release M5.2 : >> > > > > >> > > > > On Wed, 8 Apr 2020 at 02:39, Thomas Heigl >> > wrote: >> > > > > > >> > > > > > Hi Maxim, >> > > > > > >> > > > > > That would be great. I want to do some more extensive testing and >> > then >> > > > > > deploy M5 into production. ;) >> > > > > > >> > > > > > Thomas >> > > > > > >> > > > > > On Tue, Apr 7, 2020 at 7:50 PM Maxim Solodovnik < >> > solomax...@gmail.com> >> > > > > > wrote: >> > > > > > >> > > > > > > I can pack another release >> > > > > > > later this week ... >> > > > > > > >> > > > > > > On Wed, 8 Apr 2020 at 00:48, Thomas Heigl >> > > > wrote: >> > > > > > > > >> > > > > > > > Thanks Sven! >> > > > > > > > >> > > > > > > > Did your changes make it into the release? Or did they just >> > miss >> > > > it? >> > > > > > > > >> > > > > > > > Thomas >> > > > > > > > >> > > > > > > > On Tue, Apr 7, 2020 at 7:43 PM Sven Meier >> > wrote: >> > > > > > > > >> > > > > > > > > Hi Thomas, >> > > > > > > > > >> > > > > > > > > yes, you're right: >> > > > > > > > > >> > > > > > > > > wicketstuff data stores missed some adjustments to the latest >> > > > updates >> > > > > > > in >> > > > > > > > > wicket-core. >> > > > > > > > > >> > > > > > > > > And SessionQuotaManagingDataStore$DelegatedPage must be >> > > > serializable of >> > > > > > > > > course. >> > > > > > > > > >> > > > > > > > > I've pushed changes to wicketstuff master. >> > > > > > > > > >> > > > > > > > > Thanks >> > > > > > > > > Sven >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > On 07.04.20 14:14, Thomas Heigl wrote: >> > > > > > > > > > And one more thing. There is now a warning logged just >> > before >> > > > > > > > > serialization: >> > > > > > > > > > >> > > > > > > > > > WARN o.a.w.pageStore.AsynchronousPageStore: Delegated >> > page >> > > > store >> > > > > > > > > >> 'org.apache.wicket.pageStore.SerializingPageStore' can >> > not be >> > > > > > > > > asynchronous >> > >
[ANNOUNCE] WicketStuff 9.0.0-M5.1 Released
WicketStuff core 9.0.0-M5.1 based on Apache Wicket 9.0.0-M5 is released and soon will be available at Maven Central! Unfortunately WicketStuff core 9.0.0-M5 is broken, please use this release instead The changelog is: Maxim Solodovnik (12): Switching to the next development version Inline styles are removed Merge branch 'master' of github.com:wicketstuff/core Tests should be fixed wicket-datetime tests are fixed Minor changes in CSS style ID and spacing Merge branch 'master' of github.com:wicketstuff/core Tests should be fixed Dependencies and plugins are updated Select2 is updated, CSP disabled for some examples Some CSP improvements WicketStuff 9.0.0-M5.1 is released Sven Meier (2): DelegatedPage is stored in session SessionQuotaManagingDataStore can be asynchronous Andrea Del Bene (1): Update readme.md renoth (1): #688 Select2 Settings should honor default (#689) The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Equivalent for PerSessionPageStore in Wicket 9
OK Will start new release process in couple of hours Please stop me if you will find any blocker :) On Wed, 8 Apr 2020 at 14:36, Thomas Heigl wrote: > Hi Maxim, > > It works for me now! > > Thomas > > On Wed, Apr 8, 2020 at 9:17 AM Maxim Solodovnik > wrote: > > > Thanks a million! > > > > On Wed, 8 Apr 2020 at 14:10, Thomas Heigl wrote: > > > > > > Hi Maxim, > > > > > > I'm testing against the snapshot now. Will get back to you shortly. > > > > > > Thomas > > > > > > On Wed, Apr 8, 2020 at 2:53 AM Maxim Solodovnik > > > wrote: > > > > > > > Hello All, > > > > > > > > M5 seems to be broken (deploy has failed more than 10 times during my > > > > build attempts) > > > > I have to start another release > > > > Could you please tell when can I start? > > > > > > > > On Wed, 8 Apr 2020 at 07:01, Maxim Solodovnik > > > > wrote: > > > > > > > > > > Hello Thomas, > > > > > > > > > > Please test M6-SNAPSHOT (so I don't have to release M5.2 : > > > > > > > > > > On Wed, 8 Apr 2020 at 02:39, Thomas Heigl > > wrote: > > > > > > > > > > > > Hi Maxim, > > > > > > > > > > > > That would be great. I want to do some more extensive testing and > > then > > > > > > deploy M5 into production. ;) > > > > > > > > > > > > Thomas > > > > > > > > > > > > On Tue, Apr 7, 2020 at 7:50 PM Maxim Solodovnik < > > solomax...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > I can pack another release > > > > > > > later this week ... > > > > > > > > > > > > > > On Wed, 8 Apr 2020 at 00:48, Thomas Heigl > > > > > wrote: > > > > > > > > > > > > > > > > Thanks Sven! > > > > > > > > > > > > > > > > Did your changes make it into the release? Or did they just > > miss > > > > it? > > > > > > > > > > > > > > > > Thomas > > > > > > > > > > > > > > > > On Tue, Apr 7, 2020 at 7:43 PM Sven Meier > > wrote: > > > > > > > > > > > > > > > > > Hi Thomas, > > > > > > > > > > > > > > > > > > yes, you're right: > > > > > > > > > > > > > > > > > > wicketstuff data stores missed some adjustments to the > latest > > > > updates > > > > > > > in > > > > > > > > > wicket-core. > > > > > > > > > > > > > > > > > > And SessionQuotaManagingDataStore$DelegatedPage must be > > > > serializable of > > > > > > > > > course. > > > > > > > > > > > > > > > > > > I've pushed changes to wicketstuff master. > > > > > > > > > > > > > > > > > > Thanks > > > > > > > > > Sven > > > > > > > > > > > > > > > > > > > > > > > > > > > On 07.04.20 14:14, Thomas Heigl wrote: > > > > > > > > > > And one more thing. There is now a warning logged just > > before > > > > > > > > > serialization: > > > > > > > > > > > > > > > > > > > > WARN o.a.w.pageStore.AsynchronousPageStore: Delegated > > page > > > > store > > > > > > > > > >> 'org.apache.wicket.pageStore.SerializingPageStore' can > > not be > > > > > > > > > asynchronous > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Apr 7, 2020 at 2:09 PM Thomas Heigl < > > > > tho...@umschalt.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > >> The cause is the following MetaData entry in the > session: > > > > > > > &
Re: Equivalent for PerSessionPageStore in Wicket 9
Thanks a million!
On Wed, 8 Apr 2020 at 14:10, Thomas Heigl wrote:
>
> Hi Maxim,
>
> I'm testing against the snapshot now. Will get back to you shortly.
>
> Thomas
>
> On Wed, Apr 8, 2020 at 2:53 AM Maxim Solodovnik
> wrote:
>
> > Hello All,
> >
> > M5 seems to be broken (deploy has failed more than 10 times during my
> > build attempts)
> > I have to start another release
> > Could you please tell when can I start?
> >
> > On Wed, 8 Apr 2020 at 07:01, Maxim Solodovnik
> > wrote:
> > >
> > > Hello Thomas,
> > >
> > > Please test M6-SNAPSHOT (so I don't have to release M5.2 :
> > >
> > > On Wed, 8 Apr 2020 at 02:39, Thomas Heigl wrote:
> > > >
> > > > Hi Maxim,
> > > >
> > > > That would be great. I want to do some more extensive testing and then
> > > > deploy M5 into production. ;)
> > > >
> > > > Thomas
> > > >
> > > > On Tue, Apr 7, 2020 at 7:50 PM Maxim Solodovnik
> > > > wrote:
> > > >
> > > > > I can pack another release
> > > > > later this week ...
> > > > >
> > > > > On Wed, 8 Apr 2020 at 00:48, Thomas Heigl
> > wrote:
> > > > > >
> > > > > > Thanks Sven!
> > > > > >
> > > > > > Did your changes make it into the release? Or did they just miss
> > it?
> > > > > >
> > > > > > Thomas
> > > > > >
> > > > > > On Tue, Apr 7, 2020 at 7:43 PM Sven Meier wrote:
> > > > > >
> > > > > > > Hi Thomas,
> > > > > > >
> > > > > > > yes, you're right:
> > > > > > >
> > > > > > > wicketstuff data stores missed some adjustments to the latest
> > updates
> > > > > in
> > > > > > > wicket-core.
> > > > > > >
> > > > > > > And SessionQuotaManagingDataStore$DelegatedPage must be
> > serializable of
> > > > > > > course.
> > > > > > >
> > > > > > > I've pushed changes to wicketstuff master.
> > > > > > >
> > > > > > > Thanks
> > > > > > > Sven
> > > > > > >
> > > > > > >
> > > > > > > On 07.04.20 14:14, Thomas Heigl wrote:
> > > > > > > > And one more thing. There is now a warning logged just before
> > > > > > > serialization:
> > > > > > > >
> > > > > > > > WARN o.a.w.pageStore.AsynchronousPageStore: Delegated page
> > store
> > > > > > > >> 'org.apache.wicket.pageStore.SerializingPageStore' can not be
> > > > > > > asynchronous
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, Apr 7, 2020 at 2:09 PM Thomas Heigl <
> > tho...@umschalt.com>
> > > > > wrote:
> > > > > > > >
> > > > > > > >> The cause is the following MetaData entry in the session:
> > > > > > > >>
> > > > > > > >> class
> > > > > > > >>>
> > > > > > >
> > > > >
> > org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$1=org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$SizeLimitedData@4090594a
> > > > > > > >>
> > > > > > > >> On Tue, Apr 7, 2020 at 1:59 PM Thomas Heigl <
> > tho...@umschalt.com>
> > > > > > > wrote:
> > > > > > > >>
> > > > > > > >>> Hi Sven,
> > > > > > > >>>
> > > > > > > >>> I just found time to give this a try with Wicket 9.0.0-M5.
> > There
> > > > > seem
> > > > > > > to
> > > > > > > >>> be issues with serialization now.
> > > > > > > >>>
> > > > > > > >>> My new config:
> > > > > > > >>>
> > > > > > > >>> protected IPageStore newCachingStore(IPageStore pageStore) {
> > > > > > > >>>> return new CachingPageStore(pageStore, new
> > > > > > > InMemoryPage
Re: Equivalent for PerSessionPageStore in Wicket 9
Hello All,
M5 seems to be broken (deploy has failed more than 10 times during my
build attempts)
I have to start another release
Could you please tell when can I start?
On Wed, 8 Apr 2020 at 07:01, Maxim Solodovnik wrote:
>
> Hello Thomas,
>
> Please test M6-SNAPSHOT (so I don't have to release M5.2 :
>
> On Wed, 8 Apr 2020 at 02:39, Thomas Heigl wrote:
> >
> > Hi Maxim,
> >
> > That would be great. I want to do some more extensive testing and then
> > deploy M5 into production. ;)
> >
> > Thomas
> >
> > On Tue, Apr 7, 2020 at 7:50 PM Maxim Solodovnik
> > wrote:
> >
> > > I can pack another release
> > > later this week ...
> > >
> > > On Wed, 8 Apr 2020 at 00:48, Thomas Heigl wrote:
> > > >
> > > > Thanks Sven!
> > > >
> > > > Did your changes make it into the release? Or did they just miss it?
> > > >
> > > > Thomas
> > > >
> > > > On Tue, Apr 7, 2020 at 7:43 PM Sven Meier wrote:
> > > >
> > > > > Hi Thomas,
> > > > >
> > > > > yes, you're right:
> > > > >
> > > > > wicketstuff data stores missed some adjustments to the latest updates
> > > in
> > > > > wicket-core.
> > > > >
> > > > > And SessionQuotaManagingDataStore$DelegatedPage must be serializable
> > > > > of
> > > > > course.
> > > > >
> > > > > I've pushed changes to wicketstuff master.
> > > > >
> > > > > Thanks
> > > > > Sven
> > > > >
> > > > >
> > > > > On 07.04.20 14:14, Thomas Heigl wrote:
> > > > > > And one more thing. There is now a warning logged just before
> > > > > serialization:
> > > > > >
> > > > > > WARN o.a.w.pageStore.AsynchronousPageStore: Delegated page store
> > > > > >> 'org.apache.wicket.pageStore.SerializingPageStore' can not be
> > > > > asynchronous
> > > > > >
> > > > > >
> > > > > > On Tue, Apr 7, 2020 at 2:09 PM Thomas Heigl
> > > wrote:
> > > > > >
> > > > > >> The cause is the following MetaData entry in the session:
> > > > > >>
> > > > > >> class
> > > > > >>>
> > > > >
> > > org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$1=org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$SizeLimitedData@4090594a
> > > > > >>
> > > > > >> On Tue, Apr 7, 2020 at 1:59 PM Thomas Heigl
> > > > > wrote:
> > > > > >>
> > > > > >>> Hi Sven,
> > > > > >>>
> > > > > >>> I just found time to give this a try with Wicket 9.0.0-M5. There
> > > seem
> > > > > to
> > > > > >>> be issues with serialization now.
> > > > > >>>
> > > > > >>> My new config:
> > > > > >>>
> > > > > >>> protected IPageStore newCachingStore(IPageStore pageStore) {
> > > > > >>>> return new CachingPageStore(pageStore, new
> > > > > InMemoryPageStore(getName(),
> > > > > >>>> MAX_PAGES_CACHED_PER_SESSION));
> > > > > >>>> }
> > > > > >>>> protected IPageStore newPersistentStore() {
> > > > > >>>> final RedissonRedisCache redisCache = new
> > > > > >>>> RedissonRedisCache(redissonClient);
> > > > > >>>> final RedisDataStore redisDataStore = new
> > > RedisDataStore(getName(),
> > > > > >>>> redisCache, new RedisSettings());
> > > > > >>>> return new SessionQuotaManagingDataStore(redisDataStore,
> > > > > >>>> DATA_STORE_MAX_BYTES_PER_SESSION);
> > > > > >>>> }
> > > > > >>>
> > > > > >>> This exception is logged after requests:
> > > > > >>>
> > > > > >>> org.springframework.data.redis.serializer.SerializationException:
> > > > > Cannot
> > > > > >>>> serialize; nested exception is
> > > > > >>>>
> > > > >
> > > org.spring
Re: Equivalent for PerSessionPageStore in Wicket 9
Hello Thomas,
Please test M6-SNAPSHOT (so I don't have to release M5.2 :
On Wed, 8 Apr 2020 at 02:39, Thomas Heigl wrote:
>
> Hi Maxim,
>
> That would be great. I want to do some more extensive testing and then
> deploy M5 into production. ;)
>
> Thomas
>
> On Tue, Apr 7, 2020 at 7:50 PM Maxim Solodovnik
> wrote:
>
> > I can pack another release
> > later this week ...
> >
> > On Wed, 8 Apr 2020 at 00:48, Thomas Heigl wrote:
> > >
> > > Thanks Sven!
> > >
> > > Did your changes make it into the release? Or did they just miss it?
> > >
> > > Thomas
> > >
> > > On Tue, Apr 7, 2020 at 7:43 PM Sven Meier wrote:
> > >
> > > > Hi Thomas,
> > > >
> > > > yes, you're right:
> > > >
> > > > wicketstuff data stores missed some adjustments to the latest updates
> > in
> > > > wicket-core.
> > > >
> > > > And SessionQuotaManagingDataStore$DelegatedPage must be serializable of
> > > > course.
> > > >
> > > > I've pushed changes to wicketstuff master.
> > > >
> > > > Thanks
> > > > Sven
> > > >
> > > >
> > > > On 07.04.20 14:14, Thomas Heigl wrote:
> > > > > And one more thing. There is now a warning logged just before
> > > > serialization:
> > > > >
> > > > > WARN o.a.w.pageStore.AsynchronousPageStore: Delegated page store
> > > > >> 'org.apache.wicket.pageStore.SerializingPageStore' can not be
> > > > asynchronous
> > > > >
> > > > >
> > > > > On Tue, Apr 7, 2020 at 2:09 PM Thomas Heigl
> > wrote:
> > > > >
> > > > >> The cause is the following MetaData entry in the session:
> > > > >>
> > > > >> class
> > > > >>>
> > > >
> > org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$1=org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$SizeLimitedData@4090594a
> > > > >>
> > > > >> On Tue, Apr 7, 2020 at 1:59 PM Thomas Heigl
> > > > wrote:
> > > > >>
> > > > >>> Hi Sven,
> > > > >>>
> > > > >>> I just found time to give this a try with Wicket 9.0.0-M5. There
> > seem
> > > > to
> > > > >>> be issues with serialization now.
> > > > >>>
> > > > >>> My new config:
> > > > >>>
> > > > >>> protected IPageStore newCachingStore(IPageStore pageStore) {
> > > > >>>> return new CachingPageStore(pageStore, new
> > > > InMemoryPageStore(getName(),
> > > > >>>> MAX_PAGES_CACHED_PER_SESSION));
> > > > >>>> }
> > > > >>>> protected IPageStore newPersistentStore() {
> > > > >>>> final RedissonRedisCache redisCache = new
> > > > >>>> RedissonRedisCache(redissonClient);
> > > > >>>> final RedisDataStore redisDataStore = new
> > RedisDataStore(getName(),
> > > > >>>> redisCache, new RedisSettings());
> > > > >>>> return new SessionQuotaManagingDataStore(redisDataStore,
> > > > >>>> DATA_STORE_MAX_BYTES_PER_SESSION);
> > > > >>>> }
> > > > >>>
> > > > >>> This exception is logged after requests:
> > > > >>>
> > > > >>> org.springframework.data.redis.serializer.SerializationException:
> > > > Cannot
> > > > >>>> serialize; nested exception is
> > > > >>>>
> > > >
> > org.springframework.core.serializer.support.SerializationFailedException:
> > > > >>>> Failed to serialize object using DefaultSerializer; nested
> > exception
> > > > is
> > > > >>>> java.io.NotSerializableException:
> > > > >>>>
> > > >
> > org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$DelegatedPage
> > > > >>>> at
> > > > >>>>
> > > >
> > org.springframework.data.redis.serializer.JdkSerializationRedisSerializer.serialize(JdkSerializationRedisSerializer.java:96)
> > > > >>>> at
> > > > >>>>
Re: Equivalent for PerSessionPageStore in Wicket 9
I can pack another release
later this week ...
On Wed, 8 Apr 2020 at 00:48, Thomas Heigl wrote:
>
> Thanks Sven!
>
> Did your changes make it into the release? Or did they just miss it?
>
> Thomas
>
> On Tue, Apr 7, 2020 at 7:43 PM Sven Meier wrote:
>
> > Hi Thomas,
> >
> > yes, you're right:
> >
> > wicketstuff data stores missed some adjustments to the latest updates in
> > wicket-core.
> >
> > And SessionQuotaManagingDataStore$DelegatedPage must be serializable of
> > course.
> >
> > I've pushed changes to wicketstuff master.
> >
> > Thanks
> > Sven
> >
> >
> > On 07.04.20 14:14, Thomas Heigl wrote:
> > > And one more thing. There is now a warning logged just before
> > serialization:
> > >
> > > WARN o.a.w.pageStore.AsynchronousPageStore: Delegated page store
> > >> 'org.apache.wicket.pageStore.SerializingPageStore' can not be
> > asynchronous
> > >
> > >
> > > On Tue, Apr 7, 2020 at 2:09 PM Thomas Heigl wrote:
> > >
> > >> The cause is the following MetaData entry in the session:
> > >>
> > >> class
> > >>>
> > org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$1=org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$SizeLimitedData@4090594a
> > >>
> > >> On Tue, Apr 7, 2020 at 1:59 PM Thomas Heigl
> > wrote:
> > >>
> > >>> Hi Sven,
> > >>>
> > >>> I just found time to give this a try with Wicket 9.0.0-M5. There seem
> > to
> > >>> be issues with serialization now.
> > >>>
> > >>> My new config:
> > >>>
> > >>> protected IPageStore newCachingStore(IPageStore pageStore) {
> > return new CachingPageStore(pageStore, new
> > InMemoryPageStore(getName(),
> > MAX_PAGES_CACHED_PER_SESSION));
> > }
> > protected IPageStore newPersistentStore() {
> > final RedissonRedisCache redisCache = new
> > RedissonRedisCache(redissonClient);
> > final RedisDataStore redisDataStore = new RedisDataStore(getName(),
> > redisCache, new RedisSettings());
> > return new SessionQuotaManagingDataStore(redisDataStore,
> > DATA_STORE_MAX_BYTES_PER_SESSION);
> > }
> > >>>
> > >>> This exception is logged after requests:
> > >>>
> > >>> org.springframework.data.redis.serializer.SerializationException:
> > Cannot
> > serialize; nested exception is
> >
> > org.springframework.core.serializer.support.SerializationFailedException:
> > Failed to serialize object using DefaultSerializer; nested exception
> > is
> > java.io.NotSerializableException:
> >
> > org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$DelegatedPage
> > at
> >
> > org.springframework.data.redis.serializer.JdkSerializationRedisSerializer.serialize(JdkSerializationRedisSerializer.java:96)
> > at
> >
> > org.springframework.data.redis.core.AbstractOperations.rawHashValue(AbstractOperations.java:185)
> > at
> >
> > org.springframework.data.redis.core.DefaultHashOperations.putAll(DefaultHashOperations.java:147)
> > at
> >
> > org.springframework.data.redis.core.DefaultBoundHashOperations.putAll(DefaultBoundHashOperations.java:147)
> > at
> >
> > org.springframework.session.data.redis.RedisIndexedSessionRepository$RedisSession.saveDelta(RedisIndexedSessionRepository.java:795)
> > at
> >
> > org.springframework.session.data.redis.RedisIndexedSessionRepository$RedisSession.save(RedisIndexedSessionRepository.java:783)
> > at
> >
> > org.springframework.session.data.redis.RedisIndexedSessionRepository$RedisSession.access$000(RedisIndexedSessionRepository.java:670)
> > at
> >
> > org.springframework.session.data.redis.RedisIndexedSessionRepository.save(RedisIndexedSessionRepository.java:398)
> > at
> >
> > org.springframework.session.data.redis.RedisIndexedSessionRepository.save(RedisIndexedSessionRepository.java:249)
> > at
> >
> > com.myproject.session.InstrumentedFindByIndexNameSessionRepository.save(InstrumentedFindByIndexNameSessionRepository.java:29)
> > at
> > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> > Method)
> > at
> >
> > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > at
> >
> > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> > at
> >
> > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
> > at
> >
> > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
> > at
> >
> > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> > at
> >
> > org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:88)
> > at
> >
> >
[ANNOUNCE] WicketStuff 9.0.0-M5 Released
WicketStuff core 9.0.0-M5 based on Apache Wicket 9.0.0-M5 is released and soon will be available at Maven Central! The changelog is: Maxim Solodovnik (12): Switching to the next development version Inline styles are removed Merge branch 'master' of github.com:wicketstuff/core Tests should be fixed wicket-datetime tests are fixed Minor changes in CSS style ID and spacing Merge branch 'master' of github.com:wicketstuff/core Tests should be fixed Dependencies and plugins are updated Select2 is updated, CSP disabled for some examples Some CSP improvements wicketstuff-core-9.0.0-M5 is released Andrea Del Bene (1): Update readme.md renoth (1): #688 Select2 Settings should honor default (#689) The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wizard vs WicketTester
This is WebSocketAwareCsrfPreventionRequestCycleListener who is unhappy :( Thanks for the hint :)) On Sat, 4 Apr 2020 at 20:07, Maxim Solodovnik wrote: > As usual everything works in test :( > Going to check what is the difference > > Shall I commit basic test to master? > > On Sat, 4 Apr 2020 at 17:32, Sven Meier wrote: > >> Hi Maxim, >> >> > lastRendered page === 'null' after submit >> > Maybe I'm doing something wrong? >> >> it seems so. Check the log output and/or provide a testcase please. >> >> Have fun >> Sven >> >> >> On 04.04.20 07:35, Maxim Solodovnik wrote: >> > Hello All, >> > >> > I'm trying to to test Wizard with WicketTester >> > Wizard is the component with "splitted" form which is partially >> submitted >> > multiple times >> > FormTester allows only single submit >> > >> > it's not a problem to create second FormTester BUT lastRendered page === >> > 'null' after submit :( >> > >> > Maybe I'm doing something wrong? >> > >> > BTW there is no tests for Wizard in Wicket code base, only WizardModel >> is >> > tested >> > >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > -- > Best regards, > Maxim > -- Best regards, Maxim
Re: Wizard vs WicketTester
As usual everything works in test :( Going to check what is the difference Shall I commit basic test to master? On Sat, 4 Apr 2020 at 17:32, Sven Meier wrote: > Hi Maxim, > > > lastRendered page === 'null' after submit > > Maybe I'm doing something wrong? > > it seems so. Check the log output and/or provide a testcase please. > > Have fun > Sven > > > On 04.04.20 07:35, Maxim Solodovnik wrote: > > Hello All, > > > > I'm trying to to test Wizard with WicketTester > > Wizard is the component with "splitted" form which is partially submitted > > multiple times > > FormTester allows only single submit > > > > it's not a problem to create second FormTester BUT lastRendered page === > > 'null' after submit :( > > > > Maybe I'm doing something wrong? > > > > BTW there is no tests for Wizard in Wicket code base, only WizardModel is > > tested > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Best regards, Maxim
Re: best way to get wysiwyg with wicket
Jquery-ui WYSIWYG editor do clean-up of html on server Custom js before submit is possible (the simpliest way is to store result of such function in hidden field onchange) On Sat, Apr 4, 2020, 16:00 Korbinian Bachl wrote: > Hello Maxim, > > thank you for the list. However, beside that tinymce3 + 4 are quite > outdated isn't there anything non html-wysiwyg existing so far? > My problem is that, after we use tinymce in another part of the project we > made the experience that letting non-tech people write HTML (even in > WYSIWYG) mode just doesnt work. They end up copy n pasting from all over > the web and inserting things they neither see nor understand - thats why we > need some simplification like markdown (e.g.: https://ui.toast.com/) or > even pure block-based editors (https://editorjs.io/)... > > I've stumbled over toast UI (https://ui.toast.com/), but I'm not sure if > wicket would be able to execute some kind of JS function > (editor.getMarkdown()) on before sending the form and catching it into a > model...? > > Best, > > KB > > - Ursprüngliche Mail - > > Von: "Maxim Solodovnik" > > An: "users" > > Gesendet: Samstag, 4. April 2020 03:02:07 > > Betreff: Re: best way to get wysiwyg with wicket > > > Here are couple examples > > > http://www.7thweb.net/wicket-jquery-ui/plugins/wysiwyg/WysiwygEditorPage?1 > > https://github.com/wicketstuff/core/tree/master/tinymce3-parent > > https://github.com/wicketstuff/core/tree/master/tinymce4-parent > > > > > > On Sat, 4 Apr 2020 at 01:24, Korbinian Bachl > > wrote: > > > >> Hi, > >> > >> I need to be able to let complete novices edit and write nicely > formatted > >> texts in an backend thats powered by wicket (required e.g.: H1-H4, > normal > >> text, bold text, images - only simple stuff mostly). > >> In the past I used the ckeditor but that outputs html and Im not sure > that > >> cluttering font sizes and stuff like that into anything that needs > later be > >> to transformed to be used on either desktop or mobile in the year 2020 > is > >> still as sufficent as it was 10 years ago. So I stumbled over markdown > that > >> might be a way to avoid this, but not sure If I missed somthing better? > >> > >> Beside, has any of you an idea where to look at to put this together > with > >> wicket, especially as I need to be able to have them insert images from > >> some gallery picker that gets its image-resources from some kind of > >> dataprovider. > >> > >> Any idea or solution is greatly appreciated. I know this is not pure > >> wicket related stuff but I hope its still ok to ask here. > >> > >> Best, > >> > >> KB > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > > > -- > > Best regards, > > Maxim > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
