The main advantages of ByteBuddy are: - actively developed - Mockito 2 moved to it - Hibernate 5.x is moving to it ( https://twitter.com/vlad_mihalcea/status/798971296910483456) - Spring considers it (they actually already use it for the tests: https://twitter.com/ankinson/status/799363435775586308) - support for Java 9 (we will need it at some point) - support for Android (I guess no one will ever run Wicket inside Android, but who knows)
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Sun, Nov 20, 2016 at 7:08 PM, Sven Meier <s...@meiers.net> wrote: > Replace CGLIB with ByteBuddy because it has better support for Java 8 and 9 >> > > What are the advantages? Seems Spring hasn't decided on this yet: > > https://jira.spring.io/browse/SPR-8190 > > Regards > Sven > > > > On 20.11.2016 00:47, Martin Grigorov wrote: > >> Replace CGLIB with ByteBuddy because it has better support for Java 8 and >> 9 >> ? >> CGLIB could stay as fallback (via system property) until 9.0.0. >> >> Martin Grigorov >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Fri, Nov 18, 2016 at 12:49 PM, Andrea Del Bene <an.delb...@gmail.com> >> wrote: >> >> yah, I think it's better >>> >>> >>> >>> On 14/11/2016 19:54, Martin Grigorov wrote: >>> >>> +1 >>>> >>>> Maybe rename #forResource() to #of() ? >>>> >>>> Martin Grigorov >>>> Wicket Training and Consulting >>>> https://twitter.com/mtgrigorov >>>> >>>> On Fri, Nov 11, 2016 at 5:00 PM, Andrea Del Bene <an.delb...@gmail.com> >>>> wrote: >>>> >>>> I'm wondering if there is room for an improvement for ResourceReference, >>>> >>>>> introducing lambda support also for this component. Actually it's >>>>> something >>>>> that can be done after the release of 8.0.0, but I'd like to collect >>>>> your >>>>> feedback anyway. The idea is to provide factory methods to build a >>>>> ResourceReference using lambdas and avoiding anonymous classes to >>>>> implement >>>>> getResource(). >>>>> The following snippet should better explain what I mean: >>>>> >>>>> https://gist.github.com/bitstorm/03cfe9905a3f86a7160ab49f0ce23f13 >>>>> >>>>> Andrea. >>>>> >>>>> On 31/10/2016 14:41, Martin Grigorov wrote: >>>>> >>>>> Hi, >>>>> >>>>>> What other improvements do we need in 8.x/master before promoting it >>>>>> to >>>>>> 8.0.0 final ? >>>>>> >>>>>> At https://cwiki.apache.org/confluence/display/WICKET/Ideas+ >>>>>> for+Wicket+8.0 >>>>>> we still have: >>>>>> >>>>>> - new DateTime APIs for wicket-datetime *WICKET-6105 >>>>>> <https://issues.apache.org/jira/browse/WICKET-6105>* - I'll give this >>>>>> one >>>>>> more try but the problem is that I don't believe this is the proper >>>>>> way >>>>>> and >>>>>> this demotivates me. >>>>>> If someone else wants to give it a try - please assign it to yourself! >>>>>> >>>>>> - Better SEO for stateful pages - the only way I see this is by using >>>>>> ServiceWorker to add the pageId as a request header to all requests >>>>>> (normal >>>>>> & Ajax) >>>>>> >>>>>> >>>>>> Recently I wondered whether Redux.js could be in use for Wicket. >>>>>> I don't have much experience with it, but both React and AngularJs >>>>>> communities use it to manage the state for their components. >>>>>> There are some Java impls, even a standard is coming: >>>>>> https://github.com/jvm-redux/jvm-redux-api >>>>>> >>>>>> What else ? >>>>>> >>>>>> Martin Grigorov >>>>>> Wicket Training and Consulting >>>>>> https://twitter.com/mtgrigorov >>>>>> >>>>>> >>>>>> >>>>>> >
