CSP: inline JS in Choices and Selection of Palette
>
> ** Task
>
> * [WICKET-7064] - commons-fileupload2 dependency should be added back
> * [WICKET-7069] - assertTrue(equals()) in tests should be replaced
> with assertEquals
> * [WICKET-7073] - Update JQuery to 3.7.1
>
>
--
Jeroen Steenbeeke
pting Wicket 9, introducing
servlet 4.0 would mean I cannot upgrade until Jetty stabilizes.
- Jeroen
Op vr 10 jan. 2020 om 14:29 schreef Martijn Dashorst <
martijn.dasho...@gmail.com>:
> On Fri, Jan 10, 2020 at 2:09 PM Jeroen Steenbeeke
> wrote:
> >
> > Jetty is
gt; > >
> > > > Hi all,
> > > >
> > > > While building our application against Wicket 9, I noticed Wicket
> > > > still uses the Java EE 8 APIs. I would like to change these to the
> > > > Jakarta versions. The APIs themselves are completely identical, it is
> > > > just the maven coordinate that changes. They do however come with a
> > > > better license (Eclipse). What do you think?
> > > >
> > > > Best regards,
> > > > Emond
> > > >
> >
> >
> >
> > --
> > Become a Wicket expert, learn from the best: http://wicketinaction.com
>
--
Jeroen Steenbeeke
fault port
>
> --
> WBR
> Maxim aka solomax
>
--
Jeroen Steenbeeke
A better approach, in my opinion, when dealing with optionals, is to use
ifPresent:
RequestCycle.get().find(AjaxRequestTarget.class).ifPresent(target -> {
// The logic you want to apply to your AjaxRequestTarget
});
2016-08-05 8:14 GMT+02:00 Jeroen Steenbeeke :
> get() is supposed to th
t after...
>
> Could someone confirm?
>
> Thanks in advance,
> Sebastien.
>
--
Jeroen Steenbeeke
True, but my point was that for someone on the user end (the one
running the webapp, not the developers), the speed alone should be a
very compelling reason to switch to 1.6.
And let's not forget that nobody is suggesting moving current Wicket
versions to Java 1.6. For those poor souls who are stuck developing
for Java 1.5 there is still Wicket 1.4, or even 1.3 for that matter.
The increase in speed alone is reason enough to switch to 1.6 in my opinion.
