On Thu, Jun 3, 2021 at 2:27 PM Martin Grigorov <[email protected]> wrote:
> > > On Wed, Jun 2, 2021 at 4:12 PM Maxim Solodovnik <[email protected]> > wrote: > >> I've started this work for our project >> seems to be doable >> >> Maybe you can share what are the benefits? >> > > As I said I don't have any practical experience with JPMS, but I hoped to > learn something new for Wicket 10 :-) > One more thing to learn for me: Replace Reflection APIs usage in PropertyResolver & Co. with MethodHandles. People say that MethodHandles are both faster and less memory intensive than Reflection APIs. > >> >> On Wed, 2 Jun 2021 at 15:15, Martin Tzvetanov Grigorov < >> [email protected]> >> wrote: >> >> > >> > >> > On 2021/04/02 11:58:02, Martin Grigorov <[email protected]> wrote: >> > > Hi, >> > > >> > > Now since we have 9.3.0 released is it time to start thinking/working >> on >> > > Wicket 10 ? >> > > >> > > Here are few ideas what to break :-) >> > > >> > > 1) Move to Servlet 5.x, i.e. jakarta.servlet.** >> > > 2) Use @Inject + @Named instead of @SpringBean. If everything is >> covered >> > > by @Inject we may deprecate @SpringBean in 9.x >> > > 3) Depending on the release date we may even bump Java to 17 (it is >> going >> > > to be released this September and it is going to be LTS). I expect >> Wicket >> > > 10.0.0 to be released in 1-2 years from now, so by this time Java 17 >> > should >> > > be mainstream! :-) I know that this is too brave. Most projects still >> use >> > > Java 8 for some reason. >> > >> > One more idea: add proper support for JPMS (Java 9+ modules) in Wicket. >> > I still don't have any experience with this, so I am not sure how much >> > work this is and what problems we may face with it. >> > >> > > >> > > Regards, >> > > Martin >> > > >> > >> >> >> -- >> Best regards, >> Maxim >> >
