Jon,
On 3/16/23 15:19, jonmcalexan...@wellsfargo.com.INVALID wrote:
-----Original Message-----
From: jonmcalexan...@wellsfargo.com.INVALID
<jonmcalexan...@wellsfargo.com.INVALID>
Sent: Thursday, March 16, 2023 1:54 PM
To: users@tomcat.apache.org
Subject: RE: Quick Question with Tomcat 10.1x
-----Original Message-----
From: Torsten Krah <krah...@gmail.com>
Sent: Thursday, March 16, 2023 1:40 PM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Quick Question with Tomcat 10.1x
<jonmcalexan...@wellsfargo.com.invalid> schrieb am Do., 16. März 2023,
19:32:
<SNIP>
Please read
https://urldefense.com/v3/__https://tomcat.apache.org/whichversion.htm
l
__;!!F9svGWnIaVPGSwU!sqrCJdsIe3_3iYLirxu4vrA4Xj8DffbYlvj5JdwcXcILyGX
yLmBtRF78uePA8eNGJa8ahRawR8Fvw5jflikZzHI$ - you have used the
wrong
servlet API version in your war file for tomcat 10.1 .
Thank you so very much. This is exactly what I was looking for.
FWIW, I'm not any type of developer, just slapped something together for
my testing purposes. I'll see if I can figure out how to update my war file.
Thank you,
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Another silly add on to this,
Is it possible to reference multiple servlet specs? Or can you only reference 1?
Torsten's reply was technically correct but not entirely helpful.
Tomcat 10.1 implements the jakarta.servlet APIs but it has a feature
would allows you to deploy a javax.servlet-based application onto it
through one of two techniques:
1. Use the tomcat-migration-tool [1] to convert your application WAR (or
exploded WAR-directory) into a jakarta.servlet-compliant application.
2. Use the legacyAppBase option[1] on your <Host> ans just drop your
javax.servlet-compliant application into there in either WAR or
expanded-WAR format.
Again, not a developer, so silly question I know.
This is not a silly question /at all/. It's quite complicated and I
think the Tomcat team did a great job building a migration path for
developers and admins who want to migrate from one major version of
these APIs to another completely 100% incompatible version in a way that
is nearly painless.
Note that you should encourage your development team to begin looking at
migrating the original source from javax.servlet -> jakarta.servlet for
a "complete" migration. It's probably not a great idea to just keep
running the same old application without any changes forever and ever
even if the servlet container allows you to do so :)
Hope that helps,
-chris
[1] https://tomcat.apache.org/download-migration.cgi
[2] https://tomcat.apache.org/tomcat-10.1-doc/config/host.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
