[ANNOUNCE] WicketStuff 7.13.0 Released
WicketStuff core 7.13.0 based on Apache Wicket 7.13.0 is released and soon will be available at Maven Central! The changelog since 7.12.0 is: Dennis Hoersch (1): Allow to customize selectize.js settings (#656) Lucas Fernandes (1): Add language support Portuguese-BR (#659) Maxim Solodovnik (3): Fixes #654: NPE due to transient fiels is null after component was deserialized Wicket version is switched to next SNAPSHOT wicketstuff-core-7.13.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] Apache Wicket 9.0.0-M1 released
The Apache Wicket PMC is proud to announce Apache Wicket 9.0.0-M1! Apache Wicket is an open source Java component oriented web application framework that powers thousands of web applications and web sites for governments, stores, universities, cities, banks, email providers, and more. You can find more about Apache Wicket at https://wicket.apache.org This release marks the first milestone of the major release of Wicket 9. Since Wicket 9 is still in development, backward api compatibility between milestone release is not guaranteed. We will continue to use semantic versioning when we will made Wicket 9 final and maintain api compatibility between minor versions of Wicket 9. New and noteworthy -- * Java 11 support The new milestone requires Java 11 as minimum version. * JUnit 5 support Wicket 9 has been migrated from JUnit 4 to 5. Module junit-vintage-engine is provided as test dependency to make old tests work without migrating all the code to JUnit 5. * Test with newer Java versions Wicket 9 branch is also tested with Java 12 and 13 as part of OpenJDK Quality Outreach project lead by Oracle OpenJDK team. For more informations see the following link: http://apache-wicket.1842946.n4.nabble.com/Fwd-Testing-Apache-Wicket-with-JDK-Early-Access-builds-td4681441.html * Rework page and data storage The internal mechanism used to store page instances has been reworked and refactored to be simpler and easier to use. Using this release -- With Apache Maven update your dependency to (and don't forget to update any other dependencies on Wicket projects to the same version): org.apache.wicket wicket-core 9.0.0-M1 Or download and build the distribution yourself, or use our convenience binary package you can find here: * Download: http://wicket.apache.org/start/wicket-9.x.html#manually Upgrading from earlier versions --- If you upgrade from 9.y.z this release is a drop in replacement. If you come from a version prior to 9.0.0, please read our Wicket 9 migration guide found at * http://s.apache.org/wicket9migrate Have fun! — The Wicket team The signatures for the source release artefacts: Signature for apache-wicket-9.0.0-M1.zip: -BEGIN PGP SIGNATURE- iQIzBAABCgAdFiEE0a6YZHC1pJw+aieyh48B+qjTVuEFAlyuOSEACgkQh48B+qjT VuFLNA/+NZ13eStA3Gi09RXn0/mUPfQ/On8vOL2ypveLOu3isCOTHddWBowWPaeX GAa3ycFseLalszzoYAC0hoSTnh3LF0O3RYqEgAI4GX1hdRzpnOVksb0Bkj27s+N/ lDiPCvdm1gxPVGoSWz8rvn6Y9v9t+1Y/WwjduCxB6NvmaDTXwnn2nnTQjNwNz/kX vBr7BnDkHcUjpYW5q2ZHdo2ZBOZS81tABe2JI86CeHYJVjzjy5GuDjZqa7ixGeMj DzaZ0RaxSEAlTjbJ5DtC5bVrRaDrLPwWCn4ynZVjmIDOmuUacgnNYIiVIlo5MIhY l5896eUdu4bImP1RdiYCDN0o0UGD9jOycJO9QvDzYUTiK+m2d2C7n4Cgbvo6JKrX fjYpRY95Xi8ST13yGaJl+3yUWXQSJvtOdneibcbkN20Pp7K9UGcGbY+efwNLejqe d4VO2reNsFapD6mBgremaIQK9C3jeuAJmzq1rM0tSkbrt1zHmGBU5R+Kc9dWFZRY QRKbuuTya/XW03si2uBzh+rxC+7Mpyi7SUE3LEOilACt0lPz0lJJu/oUzZiMM2VN UKG4VdxAkzZ2Ja1FDSOPJ6zw9lN3mPvWj9l4T7/cXQpELIVQSo17Foq16JdrCB6H BnYdUkVTJ4cWxNmlyDU6AhSQkKVUbps23XjfXD2E0uD84dbj1eo= =ArhK -END PGP SIGNATURE- Signature for apache-wicket-9.0.0-M1.tar.gz: -BEGIN PGP SIGNATURE- iQIzBAABCgAdFiEE0a6YZHC1pJw+aieyh48B+qjTVuEFAlyuOSEACgkQh48B+qjT VuGEdQ//aLP1iPvV8LftKphL2fEoxNASi8a4yJ6n1llQgJm692uLo9VPL1tALXDJ r7glipgHu5NYGy5zXV6gZMb6Gr0V2ydW9mS37V1BWWSw2X6D1tgYbzZMmYlhfZcQ 9O5hWVFQ8qAD345E7Tjw+nRdr4lFSKxgQDsohZiSDtYc1duFQ31fxt7v8xMpJT4b Nu2AJkzB7L0LjQT3graovZuNkjp/5wWcTZ8gRN3A+VlF/Cp6KmWfWWXYNJLRXZZV YRlWA5CF6DLu9VQJqOWS4FxcJirJroawatn9rNUs48j/ExJhooyno36JTy4BiBA4 i9h5bJaxYmMECpO0Y5WaNm9TOEMmrb4VHwx/DDvG/WXEAtY1Nt+C0A65l23KHRuD cjd0tHEBzDo052m34duQwtVcuOnxxyfg6kue1plRdOF9zyW1484RCUhsit370IT2 m84ek1kbQnUzxICQYm2J/3ak056wQ08rYmWkki2rw2uTvXz3YvrQo+jPg2Avybct yE+wVCTbRqvfcmn5hcOTdcth50BV273iwczMealbdulnfp7PoDi8Z00AJ6kICQMz 48y6Y5VSz94xLxb6a99xkGfnqwos78xh4iV2DG3+778oAfewYgo9d2NTVfsX4xox D+eLF92tdmEQbIN3e6r6KGv4YamL+DypvAcbsPEDL1e1MrHA8mQ= =lIwn -END PGP SIGNATURE- CHANGELOG for 9.0.0-M1: ** Bug * [WICKET-5552] - Events to close pop-up on Modal Window are not propagated * [WICKET-6568] - Wicket fails / does not encode request header values in AjaxCalls * [WICKET-6570] - Unable to read cookies containing '.' characters in names when using CookieUtils * [WICKET-6574] - JQueryResourceReference#get() (still) return V1 * [WICKET-6584] - Import Junit Package as optional * [WICKET-6586] - Broken JavaScript due to fix charsetName in JavaScriptPackageResource * [WICKET-6588] - Under Tomcat (ver. >= 8.5) BaseWebSocketBehavior can't find session id cookie * [WICKET-6599] - ResponseIOException should never escape from WicketFilter * [WICKET-6602] - AuthenticatedWebApplication login Workflow broken with replaceSession * [WICKET-6603] - WicketTester.destro
Re: AJAX error on chrome with latest 8.4 release
Maybe non-minimized stacktrace can gave some more info? On Tue, 16 Apr 2019 at 22:35, Ernesto Reinaldo Barreiro wrote: > > Hi, > > Bumping jQuery version to 3.4.0 provides same results (no minimized). > > On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik > wrote: > > > non minified jquery and/or wicket.mode=DEVELOPMENT > > May be it will shed some light on this issue ... > > > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < > > reier...@gmail.com> > > wrote: > > > > > Hi, > > > > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik > > > wrote: > > > > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > > > > > > > Do you mean jquery non minified jQuery? > > > > > > -- > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > -- > > WBR > > Maxim aka solomax > > > > > -- > Regards - Ernesto Reinaldo Barreiro -- WBR Maxim aka solomax - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: AJAX error on chrome with latest 8.4 release
Hi, Bumping jQuery version to 3.4.0 provides same results (no minimized). On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik wrote: > non minified jquery and/or wicket.mode=DEVELOPMENT > May be it will shed some light on this issue ... > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi, > > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik > > wrote: > > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > > > > Do you mean jquery non minified jQuery? > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > WBR > Maxim aka solomax > -- Regards - Ernesto Reinaldo Barreiro
[ANNOUNCE] WicketStuff 8.4.0 Released
WicketStuff core 8.4.0 based on Apache Wicket 8.4.0 is released and soon will be available at Maven Central! The changelog since 8.3.0 is: Dennis Hoersch (1): Allow to customize selectize.js settings (#656) Lucas Fernandes (1): Add language support Portuguese-BR (#659) Martin Tzvetanov Grigorov (2): Fixes #655 - Do not try to render the model objects when AbstractSelect2Choice component is in stateless mode [datatables] Fixes #660 - Add support for filtering to the Infinite Scroll demo page Maxim Solodovnik (7): Switching to the next development version Fixes #654: NPE due to transient fiels is null after component was deserialized String.format is replaced with '+' Dependencies are updated with safe versions Merge branch 'wicket-8.x' of github.com:wicketstuff/core into wicket-8.x Initial attempt to fix cometd (tests are 'semi-working') wicketstuff-core 8.4.0 is released Thanos Apostolou (1): Ajax redirect keeps ResponseState (#652) The WicketStuff team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: AJAX error on chrome with latest 8.4 release
Wicket is on development mode already. I'm serving "my own" minified version of jquery. I will play with that next and try to "reorder my code" to see if I can spot what is different. On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik wrote: > non minified jquery and/or wicket.mode=DEVELOPMENT > May be it will shed some light on this issue ... > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi, > > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik > > wrote: > > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > > > > Do you mean jquery non minified jQuery? > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > WBR > Maxim aka solomax > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
non minified jquery and/or wicket.mode=DEVELOPMENT May be it will shed some light on this issue ... On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro wrote: > Hi, > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik > wrote: > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > Do you mean jquery non minified jQuery? > > -- > Regards - Ernesto Reinaldo Barreiro > -- WBR Maxim aka solomax
Re: AJAX error on chrome with latest 8.4 release
Hi, On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik wrote: > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > Do you mean jquery non minified jQuery? -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Is it reproducible with non-minified (i.e. DEVELOPMENT) version? On Tue, 16 Apr 2019 at 20:34, Ernesto Reinaldo Barreiro wrote: > Hi Maxim, > > Thanks for feedback. > > wicket-jquery-ui based Wizard works for me as expected (just have tested > > Chrome latest at Ubuntu 18.10) > > > > We are using or own home grown implementation of a wizard on top of a > custom wrapper around bootstrap modal (I was the person creating those > components, so I know them well). We have many similar wizards in > application. I was expecting this wizard to be the same :-( I have already > tested some of the other wizards and they still work. Funny thing is we are > not doing anything particularly different here.. Or so I believe :-) > > > > > > On Tue, 16 Apr 2019 at 18:33, Ernesto Reinaldo Barreiro < > > reier...@gmail.com> > > wrote: > > > > > Hi, > > > > > > I'm experiencing following error > > > > > > POST > > > > > > > > > http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button > > > net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 > > > send @ jquery-3.2.1.min-ver-1555412805000.js:4 > > > ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 > > > doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 > > > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 > > > e @ jquery-3.2.1.min-ver-1555412805000.js:2 > > > schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 > > > schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 > > > ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 > > > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 > > > dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 > > > q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 > > > > > > On latest Chrome on Mac. This does not happens with latest FF (So, I > > assume > > > this is a wicket bug). Is this a known issue? Our application is very > > > complicated and I'm not sure I will be able to create a quickstart. > > > > > > -- > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > -- > > WBR > > Maxim aka solomax > > > > > -- > Regards - Ernesto Reinaldo Barreiro > -- WBR Maxim aka solomax
Re: AJAX error on chrome with latest 8.4 release
Hi Maxim, Thanks for feedback. wicket-jquery-ui based Wizard works for me as expected (just have tested > Chrome latest at Ubuntu 18.10) > We are using or own home grown implementation of a wizard on top of a custom wrapper around bootstrap modal (I was the person creating those components, so I know them well). We have many similar wizards in application. I was expecting this wizard to be the same :-( I have already tested some of the other wizards and they still work. Funny thing is we are not doing anything particularly different here.. Or so I believe :-) > > On Tue, 16 Apr 2019 at 18:33, Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi, > > > > I'm experiencing following error > > > > POST > > > > > http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button > > net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 > > send @ jquery-3.2.1.min-ver-1555412805000.js:4 > > ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 > > doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 > > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 > > e @ jquery-3.2.1.min-ver-1555412805000.js:2 > > schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 > > schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 > > ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 > > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 > > dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 > > q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 > > > > On latest Chrome on Mac. This does not happens with latest FF (So, I > assume > > this is a wicket bug). Is this a known issue? Our application is very > > complicated and I'm not sure I will be able to create a quickstart. > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > WBR > Maxim aka solomax > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Hello Ernesto, wicket-jquery-ui based Wizard works for me as expected (just have tested Chrome latest at Ubuntu 18.10) On Tue, 16 Apr 2019 at 18:33, Ernesto Reinaldo Barreiro wrote: > Hi, > > I'm experiencing following error > > POST > > http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button > net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 > send @ jquery-3.2.1.min-ver-1555412805000.js:4 > ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 > doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 > e @ jquery-3.2.1.min-ver-1555412805000.js:2 > schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 > schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 > ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 > dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 > q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 > > On latest Chrome on Mac. This does not happens with latest FF (So, I assume > this is a wicket bug). Is this a known issue? Our application is very > complicated and I'm not sure I will be able to create a quickstart. > > -- > Regards - Ernesto Reinaldo Barreiro > -- WBR Maxim aka solomax
Re: AJAX error on chrome with latest 8.4 release
Hi Martin, Many thanks for your answer. > > https://stackoverflow.com/questions/22608564/neterr-incomplete-chunked-encoding-in-chrome-only > suggests > that it might be a local problem. Some people said that disabling the > antivirus software helped them, others had no disk space, ... > > Yes I have read that post but I have no antivirus running... I will check around to see what I can spot. > If you are able to reproduce it with wicket-examples or any other way then > please open an issue at JIRA! > Ok. I will try first to see what might be "wrong" with my computer + ask other team members to try failing code locally in order to check if it is just my computer. -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Hi Ernesto, No, it is not known. https://stackoverflow.com/questions/22608564/neterr-incomplete-chunked-encoding-in-chrome-only suggests that it might be a local problem. Some people said that disabling the antivirus software helped them, others had no disk space, ... If you are able to reproduce it with wicket-examples or any other way then please open an issue at JIRA! On Tue, Apr 16, 2019 at 2:33 PM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi, > > I'm experiencing following error > > POST > > http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button > net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 > send @ jquery-3.2.1.min-ver-1555412805000.js:4 > ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 > doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 > e @ jquery-3.2.1.min-ver-1555412805000.js:2 > schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 > schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 > ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 > dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 > q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 > > On latest Chrome on Mac. This does not happens with latest FF (So, I assume > this is a wicket bug). Is this a known issue? Our application is very > complicated and I'm not sure I will be able to create a quickstart. > > -- > Regards - Ernesto Reinaldo Barreiro >
AJAX error on chrome with latest 8.4 release
Hi, I'm experiencing following error POST http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 send @ jquery-3.2.1.min-ver-1555412805000.js:4 ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 e @ jquery-3.2.1.min-ver-1555412805000.js:2 schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 On latest Chrome on Mac. This does not happens with latest FF (So, I assume this is a wicket bug). Is this a known issue? Our application is very complicated and I'm not sure I will be able to create a quickstart. -- Regards - Ernesto Reinaldo Barreiro
Re: Integrate Wicket with Keycloak
Thank you for sharing your knowledge, Jeroen! On Tue, Apr 16, 2019 at 12:32 PM Jeroen Steenbeeke < j.steenbeeke...@gmail.com> wrote: > Hello David, > > Excellent idea! I went ahead and did just that: > https://tech.jeroensteenbeeke.nl/2019/04/16/using-keycloak-with-wicket.html > > Hope it's helpful. > > Regards, > > Jeroen > > Op ma 15 apr. 2019 om 19:53 schreef David Beer : > > > Hi Jeroen > > > > This sounds good, I once tried to setup a link between Wicket and > Keycloak, > > would be good if you had a blog post, or posted this on the wicket site, > > along with code examples on github. Just a thought. > > > > Thanks > > > > David > > > > On Thu, 11 Apr 2019 at 09:23, Jeroen Steenbeeke < > j.steenbeeke...@gmail.com > > > > > wrote: > > > > > I've recently created an application that has a Wicket frontend (and > > Spring > > > backend) authenticated by Keycloak. It's a relatively simple > integration > > > really, all pages require a valid Keycloak session, so it uses the > > default > > > Keycloak servlet filter adapter: > > > > > > > > > > > > https://search.maven.org/artifact/org.keycloak/keycloak-servlet-filter-adapter/5.0.0/jar > > > > > > In my setup I've mapped the Keycloak filter to all URLs (before the > > Wicket > > > filter). Using this filter is simply a matter of adding it to your > > web.xml > > > and making sure you have a keycloak.json file in your WEB-INF folder. > > > > > > In Wicket, you can then get the Keycloak context from the RequestCycle: > > > > > > ServletWebRequest request = (ServletWebRequest) > > > RequestCycle.get().getRequest(); > > > HttpServletRequest containerRequest = request.getContainerRequest(); > > > KeycloakSecurityContext securityContext = (KeycloakSecurityContext) > > > containerRequest.getAttribute(KeycloakSecurityContext.class.getName()); > > > > > > Hope this helps. > > > > > > Sincerely, > > > > > > Jeroen > > > > > > > > > Op wo 10 apr. 2019 om 16:43 schreef Calin Pavel >: > > > > > > > Hi everybody, > > > > > > > > Did anybody integrated Wicket with Keycloak? > > > > Do you have any sample how this could be done - to restrict access to > > > > pages, to authenticate user > > > > > > > > > > > > Thank you, > > > > Calin Pavel > > > > > > > > - > > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > > > > -- > > > Jeroen Steenbeeke > > > > > > > > -- > Jeroen Steenbeeke >
Re: Integrate Wicket with Keycloak
Hello David, Excellent idea! I went ahead and did just that: https://tech.jeroensteenbeeke.nl/2019/04/16/using-keycloak-with-wicket.html Hope it's helpful. Regards, Jeroen Op ma 15 apr. 2019 om 19:53 schreef David Beer : > Hi Jeroen > > This sounds good, I once tried to setup a link between Wicket and Keycloak, > would be good if you had a blog post, or posted this on the wicket site, > along with code examples on github. Just a thought. > > Thanks > > David > > On Thu, 11 Apr 2019 at 09:23, Jeroen Steenbeeke > > wrote: > > > I've recently created an application that has a Wicket frontend (and > Spring > > backend) authenticated by Keycloak. It's a relatively simple integration > > really, all pages require a valid Keycloak session, so it uses the > default > > Keycloak servlet filter adapter: > > > > > > > https://search.maven.org/artifact/org.keycloak/keycloak-servlet-filter-adapter/5.0.0/jar > > > > In my setup I've mapped the Keycloak filter to all URLs (before the > Wicket > > filter). Using this filter is simply a matter of adding it to your > web.xml > > and making sure you have a keycloak.json file in your WEB-INF folder. > > > > In Wicket, you can then get the Keycloak context from the RequestCycle: > > > > ServletWebRequest request = (ServletWebRequest) > > RequestCycle.get().getRequest(); > > HttpServletRequest containerRequest = request.getContainerRequest(); > > KeycloakSecurityContext securityContext = (KeycloakSecurityContext) > > containerRequest.getAttribute(KeycloakSecurityContext.class.getName()); > > > > Hope this helps. > > > > Sincerely, > > > > Jeroen > > > > > > Op wo 10 apr. 2019 om 16:43 schreef Calin Pavel : > > > > > Hi everybody, > > > > > > Did anybody integrated Wicket with Keycloak? > > > Do you have any sample how this could be done - to restrict access to > > > pages, to authenticate user > > > > > > > > > Thank you, > > > Calin Pavel > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > -- > > Jeroen Steenbeeke > > > -- Jeroen Steenbeeke
Re: Wicket collapsable panel
Hi, There are several ways to do this. E.g 1- Use javascript at client side and just hide nent of panel (bound to the link that toggles the panel) 2- Use wicket AJAX and content.steVisible(false|true) where content is the panel containing you "box" content. This logic attached to the AJAX link closing/opening box. On Mon, Apr 15, 2019 at 10:28 PM Sibgha Nazir wrote: > Hi, > > I am looking for a way to create a panel that opens and closes from one > side of the container. I havent been lucky enough to find a related thing > on internet. > > Can anybody hint me? > > Thanks. > -- Regards - Ernesto Reinaldo Barreiro
