Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] What do we exactly dislike in Servlet?

Well technically JAXRS is always slower than servlet - in particular when implemented on top of servlet as required by the spec - until you make it 1-1 (a method called directly handling the input/output streams) where it is just about proposing different programming model but iso in terms of perf.

I think that servlet by itself is not bad and not that fat but dropping the xml requirement can be a big thing (enhancing initializers to have @Priority and other small details like that is sufficient).

Dropping some inter-dependencies like jaspic, jaas etc can be neat but think most vendors did their homework to enable it so not sure how much it would bring at spec level.

The other big thing I would hope can be to enable to embed the container from an application instead of deploying into the container (servlet-se API, a bit similar to EJBContainer or SeContainer of CDI. JAXRS and JAXWS had such features, not sure why servlet can't and it would help in all the microservices we write these days).

So to summarize:

1. Same API as today (compat is key)
2. Embeddable (SE "profile")
3. XML free (initializers enhancements + probably no xml in the "light" spec jar)

Romain Manni-Bucau
@rmannibucau |  Blog | Old BlogGithub | LinkedIn | Book

Le mer. 13 juil. 2022 à 12:40, arjan tijms <arjan.tijms@xxxxxxxxx> a écrit :

On Wednesday, July 13, 2022, Stuart Douglas <sdouglas@xxxxxxxxxx> wrote:

On Wed, 13 Jul 2022 at 16:27, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:

On Wed, 13 Jul 2022 at 05:57, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
One argument I heard is that Servlets are much, much slower than Jakarta REST. But I'm not quite sure why a Java class that implements jakarta.servlet.Servlet should be slower in any way than a Java class with the @Path annotation.

TBH I don't know if the horse has bolted with this one, as most interested parties already have their own low level APIs. 

Isn’t standardising similar but incompatible existing APIs from multiple vendors one of the things that Jakarta EE stands for?

Kind regards,
Arjan Tijms


At the very least, I'd like Servlet 7 to look at splitting the servlet spec into the pure API concerns and the application framework concerns (eg war packaging, annotations, descriptors etc.).   Perhaps the core API will not be to everybody's taste or meet every need, but it might be simpler and fast enough such that it's standard nature provides something good enough for many non servlet usages.

I think all of these 'HTTP core implementations' mentioned in the other emails are fully async, and even if we stripped all the packaging etc from Servlet it will never meet that requirement in its current form.



servlet-dev mailing list
To unsubscribe from this list, visit
jakartaee-platform-dev mailing list
To unsubscribe from this list, visit

Back to the top