I've prepared a branch 'jakarta-api' with the migration to Jakarta,
Servlet 4 and Jetty 10.0.0-alpha1. Most of the examples work fine,
however I get an NPE on the websocket upgrade:
Caused by: java.lang.NullPointerException
at
On Fri, Jan 10, 2020 at 4:03 PM Emond Papegaaij
wrote:
> I tend to agree with Martijn here. The Jakarta APIs are the future. It
> is unfortunate that the last stable version of Jetty is 4 years old
> now and they have not been able to produce a new version in the past 2
> years. Maybe us moving
I tend to agree with Martijn here. The Jakarta APIs are the future. It
is unfortunate that the last stable version of Jetty is 4 years old
now and they have not been able to produce a new version in the past 2
years. Maybe us moving to servlet 4 will give them a bit more
incentive to pick op the
Most of my Wicket applications (i.e. the ones I don't get paid to write)
run on Jetty 9.4, Java 11 and Wicket 8.
Jetty 10 is, as indicated on the site I linked, still in alpha and marked
as unstable, and has no official Docker image yet.
Right now there is nothing blocking me from adopting
On Fri, Jan 10, 2020 at 3:29 PM Martijn Dashorst
wrote:
> On Fri, Jan 10, 2020 at 2:09 PM Jeroen Steenbeeke
> wrote:
> >
> > Jetty is still on 3.1:
> >
> >
> https://www.eclipse.org/jetty/documentation/current/what-jetty-version.html
>
> Well, Emond was talking about the major
On Fri, Jan 10, 2020 at 2:09 PM Jeroen Steenbeeke
wrote:
>
> Jetty is still on 3.1:
>
> https://www.eclipse.org/jetty/documentation/current/what-jetty-version.html
Well, Emond was talking about the major application/servlet containers :-D...
As we are targeting Java 11 with Wicket 9, perhaps
Jetty is still on 3.1:
https://www.eclipse.org/jetty/documentation/current/what-jetty-version.html
Op vr 10 jan. 2020 om 14:05 schreef Emond Papegaaij <
emond.papega...@gmail.com>:
> It turns out Wicket 9 is still on servlet 3.1, which is pre-Jakarta.
> Any objections against raising this to
It turns out Wicket 9 is still on servlet 3.1, which is pre-Jakarta.
Any objections against raising this to 4.0? AFAIK all major
application/servlet containers have versions with support for 4.0.
Best regards,
Emond
On Fri, Jan 10, 2020 at 1:04 PM Martijn Dashorst
wrote:
>
> Just the maven
Just the maven coordinates.
As for expected problems: probably folks have to update their poms to
use the jakarta variants, but mostly they shouldn't bite if they use
the provided scope.
For benefits:
- the Jakarta group-id is the future, all servers will move to that
maven coordinate
- the
Hi Emond,
If it is just about different Maven coordinates then it is OK.
For the change javax.servlet -> jakarta.servlet it is too soon.
On Fri, Jan 10, 2020 at 12:40 PM Emond Papegaaij
wrote:
> Hi all,
>
> While building our application against Wicket 9, I noticed Wicket
> still uses the Java
I'm tempted to say "yes, let's move to Jakarta", but I'm not sure about the
consequences. Could it be a problem with web servers (Jetty, Tomcat)? Do
they have a minimum version required to work with Jakarta?
On Fri, Jan 10, 2020 at 11:40 AM Emond Papegaaij
wrote:
> Hi all,
>
> While building
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
12 matches
Mail list logo
