/me likes !!! Once it is buildable with javac:
*) Since it doesn't need changes in any of the current Wicket classes I think it could be added to WicketStuff 7.x and battle tested until Wicket 8.0.0 is out. *) What is the purpose of WriteOnlyModel? My concern is that Wicket will fail every time such model is used in a component when this component is being rendered. *) I think you have to name some of the methods #map and #flatMap, and add "Monad" somewhere in the javadoc. Just to make it more fancy :-) Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Oct 6, 2015 at 11:15 AM, Martijn Dashorst < [email protected]> wrote: > I've created a Lambdas class that compiles just fine in ECJ but fails > using javac. > > https://gist.github.com/dashorst/da876be2f01770e862a5 > > The benefit of this way is that we don't perpetuate SerializableFoo > (Foo==[Function, Consumer, Predicate, Supplier, ...]) but instead > require that the passed in stuff is in fact serializable. > > This way companies that have their own SerializableFunction et al, kan > pass those references into our Lambda models. > > Unfortunately this is currently way beyond the capabilities of javac. > > Check out the code above (the signature is quite hard to read, but in > use it is awesome, just use Eclipse 4.5.1) > > Martijn > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com >
