One of the most powerful features of Wicket, component events, let’s you build complex yet decoupled structures.
Are you deploying different versions of your software to multiple clients with test, staging, and production environments? Are clients picky about features they want to release to each environment? Let’s create a dashboard to keep track of all of this.
In case you aren’t using it yet, Apache Wicket is a java-based, stateful, component-based web development framework. Let’s look at why you might want to use it.
- KB I hated Wicket when I started my first job in 2014. But that was due to newbie ignorance, and I quickly came to appreciate its simplicity. One Java file, one very very slim HTML file, and that's it. I...
- Dan Haywood Nice to hear you've discovered us. Would love to see you on our slack channel, perhaps you could share your use case?
- E.F.L Also, there exists Apache Isis, which automates the UI creation. It is awesome.
- Olivier Dutrieux Hello @RomanSery, Thx for all your series, very interresting 🙂 Just a mistake on this page : String msg = ((CriticalUpdate)event.getPayload()); is not correct but rather CriticalUpdate msg =...
- René Aravena Hi Roman, I followed your advice and it worked, I had to extend several classes, because in principle, although visually showed the month in Spanish, did not accept dates beyond the 12th day of each...