Re: thanks for wonderful work with Wicket 8.
Hi, > Already done: > https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-9.x > I use it for my Wicket trainings application. > > Haha... It is difficult to beat you in speed :-) > There is something similar here: > > https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-8.x/bootstrap-less > For Bootstrap 4.x we have it for Sass/Scss: > > https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-8.x-bootstrap-4.x/bootstrap-sass > Hum... I didn't know about this. My implementation seems to bet simpler: just an Interface to make LESS for compiler plugable + Resource + ResourceReference (for package served resources). No need for a cache. But for our use case it works well. -- Regards - Ernesto Reinaldo Barreiro
Re: thanks for wonderful work with Wicket 8.
Hi Ernesto, On Thu, Apr 11, 2019 at 11:58 AM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi Andrea, > > > > PS: we are voting for the first milestone of Wicket 9 to be released. If > > you have the chance to play with it we are looking forward for your > > feedback :-) > > > :-( Unfortunately My customer has a very tight schedule for delivering the > application I just migrated. Even jumping to Wicket 8.x was something we > had to consider very carefully. All I can offer is if I start some side > personal project, which sometimes I do, try to use Wicket 9.x. Or help > migrating some of the satellite projects, like Wicket bootstrap, to wish I > have contributed from time to time, to Wicket 9.x. > Already done: https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-9.x I use it for my Wicket trainings application. > > Also our project have some home made components and wrappers around > JavaScript libraries that I might try to convince my customer to "open > source". E.g. I have rolled out a LESS resource class that on the spot > compiles LESS into CSS, if you modify your less this class will discard > cached less and recompiles it, when I created this component I was looking > around and found nothing similar. Or a wicket wrapper for > There is something similar here: https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-8.x/bootstrap-less For Bootstrap 4.x we have it for Sass/Scss: https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-8.x-bootstrap-4.x/bootstrap-sass > http://bootstrap-notify.remabledesigns.com/. And some other Wicket things > that might benefit community. But this decisions do not depend on me, > -- > Regards - Ernesto Reinaldo Barreiro >
Re: thanks for wonderful work with Wicket 8.
Hi Andrea, > PS: we are voting for the first milestone of Wicket 9 to be released. If > you have the chance to play with it we are looking forward for your > feedback :-) :-( Unfortunately My customer has a very tight schedule for delivering the application I just migrated. Even jumping to Wicket 8.x was something we had to consider very carefully. All I can offer is if I start some side personal project, which sometimes I do, try to use Wicket 9.x. Or help migrating some of the satellite projects, like Wicket bootstrap, to wish I have contributed from time to time, to Wicket 9.x. Also our project have some home made components and wrappers around JavaScript libraries that I might try to convince my customer to "open source". E.g. I have rolled out a LESS resource class that on the spot compiles LESS into CSS, if you modify your less this class will discard cached less and recompiles it, when I created this component I was looking around and found nothing similar. Or a wicket wrapper for http://bootstrap-notify.remabledesigns.com/. And some other Wicket things that might benefit community. But this decisions do not depend on me, -- Regards - Ernesto Reinaldo Barreiro
Re: thanks for wonderful work with Wicket 8.
It's been a pleasure using Wicket all these years. Thanks again! On Thu, Apr 11, 2019 at 11:22 AM Martin Grigorov wrote: > I am glad to read this small success story, Ernesto! > > I want to thank you for using Wicket all these years, for all the bug > reports and the suggested features! > > On Thu, Apr 11, 2019 at 11:13 AM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Hi, > > > > I would like to thanks Wicket's development team for wonderful work done > > with wicket 8.x! > > > > Yesterday mid morning I started to migrate the application of a customer > of > > mine to Wicket 8.4 (form WIcket 7.9). By the end of the day I had fixed > > almost all compile errors (most of them due to the removal of Form on > > onSubmit and onError (on AJAX submitting components) and our derived > > codebase depending on that) and fixed all warnings (most of them because > of > > depreciation of AbstractReadOnlyModel). Today, early in the morning, > > application was already compiling! Then I ran Wicket based tests... Most > of > > them were failing :-( Our fault: one component (some home backed wrapper > > around bootstrap modal) was missing calling super.onConfig()). Fixed that > > line and all tests passed! I run the application and started to do some > > manual testing (some of our features are very complex and use lots of > > advanced low level Wicket JavaScript and even WebSockets). Again > everything > > seems to work flawlessly. Wow! > > > > Many thanks again to Wicket team! > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
Re: thanks for wonderful work with Wicket 8.
Thanks to you Ernesto for your support and kind words! I'm happy that the hard work done with Wicket 8 is paying off. PS: we are voting for the first milestone of Wicket 9 to be released. If you have the chance to play with it we are looking forward for your feedback :-) On Thu, Apr 11, 2019 at 10:22 AM Martin Grigorov wrote: > I am glad to read this small success story, Ernesto! > > I want to thank you for using Wicket all these years, for all the bug > reports and the suggested features! > > On Thu, Apr 11, 2019 at 11:13 AM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Hi, > > > > I would like to thanks Wicket's development team for wonderful work done > > with wicket 8.x! > > > > Yesterday mid morning I started to migrate the application of a customer > of > > mine to Wicket 8.4 (form WIcket 7.9). By the end of the day I had fixed > > almost all compile errors (most of them due to the removal of Form on > > onSubmit and onError (on AJAX submitting components) and our derived > > codebase depending on that) and fixed all warnings (most of them because > of > > depreciation of AbstractReadOnlyModel). Today, early in the morning, > > application was already compiling! Then I ran Wicket based tests... Most > of > > them were failing :-( Our fault: one component (some home backed wrapper > > around bootstrap modal) was missing calling super.onConfig()). Fixed that > > line and all tests passed! I run the application and started to do some > > manual testing (some of our features are very complex and use lots of > > advanced low level Wicket JavaScript and even WebSockets). Again > everything > > seems to work flawlessly. Wow! > > > > Many thanks again to Wicket team! > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Andrea Del Bene. Apache Wicket committer.
Re: Integrate Wicket with Keycloak
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
Re: thanks for wonderful work with Wicket 8.
I am glad to read this small success story, Ernesto! I want to thank you for using Wicket all these years, for all the bug reports and the suggested features! On Thu, Apr 11, 2019 at 11:13 AM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi, > > I would like to thanks Wicket's development team for wonderful work done > with wicket 8.x! > > Yesterday mid morning I started to migrate the application of a customer of > mine to Wicket 8.4 (form WIcket 7.9). By the end of the day I had fixed > almost all compile errors (most of them due to the removal of Form on > onSubmit and onError (on AJAX submitting components) and our derived > codebase depending on that) and fixed all warnings (most of them because of > depreciation of AbstractReadOnlyModel). Today, early in the morning, > application was already compiling! Then I ran Wicket based tests... Most of > them were failing :-( Our fault: one component (some home backed wrapper > around bootstrap modal) was missing calling super.onConfig()). Fixed that > line and all tests passed! I run the application and started to do some > manual testing (some of our features are very complex and use lots of > advanced low level Wicket JavaScript and even WebSockets). Again everything > seems to work flawlessly. Wow! > > Many thanks again to Wicket team! > > -- > Regards - Ernesto Reinaldo Barreiro >
thanks for wonderful work with Wicket 8.
Hi, I would like to thanks Wicket's development team for wonderful work done with wicket 8.x! Yesterday mid morning I started to migrate the application of a customer of mine to Wicket 8.4 (form WIcket 7.9). By the end of the day I had fixed almost all compile errors (most of them due to the removal of Form on onSubmit and onError (on AJAX submitting components) and our derived codebase depending on that) and fixed all warnings (most of them because of depreciation of AbstractReadOnlyModel). Today, early in the morning, application was already compiling! Then I ran Wicket based tests... Most of them were failing :-( Our fault: one component (some home backed wrapper around bootstrap modal) was missing calling super.onConfig()). Fixed that line and all tests passed! I run the application and started to do some manual testing (some of our features are very complex and use lots of advanced low level Wicket JavaScript and even WebSockets). Again everything seems to work flawlessly. Wow! Many thanks again to Wicket team! -- Regards - Ernesto Reinaldo Barreiro
