Dana,
On 4/11/21 05:18, dana whitelow wrote:
Hi,I ran the migration tool against the sample.war
./migrate.sh sample.war webapp.war
Performing migration from source
[/home/dana/servers/jakartaee-migration-0.2.0/bin/sample.war] to destination
[/home/dana/servers/jakartaee-migration-0.2.0/bin/webapp.war] with Jakarta EE
specification profile [TOMCAT]
Migration starting for archive [sample.war] using streaming
Migration finished for archive [sample.war]
Migration completed successfully in [66] milliseconds
The migrated webapp.war did work in tomcat apache-tomcat-10.0.5
BUT the web.xml header remained unchanged
<web-app xmlns="http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";
version="2.4">
should be <web-app xmlns="https://jakarta.ee/xml/ns/jakartaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee
https://jakarta.ee/xml/ns/jakartaee/web-app_5_0.xsd";
version="5.0">
It is not appropriate to migrate the web.xml file. The 2.4 version is
still valid and should be left alone. If you want to upgrade your
application, you should do it manually. This migration process is meant
to do the minimal required.
You say your error is "connection refused" but you provided almost no
other information. Connection refused when trying to contact your
application? Or is there an outgoing connection which is failing?
What do the logs say on startup?
-chris
-----Original Message-----
From: Усманов Азат Анварович <usma...@ieml.ru>
To: Tomcat Users List <users@tomcat.apache.org>; dana whitelow
<danawhite...@aol.com>
Sent: Sat, 10 Apr 2021 20:59
Subject: RE: version change failure
Dana, Please see the migration -guide (https://tomcat.apache.org/migration-10.html)
here is a quote from it "
Apache Tomcat 10 supports the Jakarta Servlet 5.0, Jakarta Server Pages 3.0, Jakarta
Expression Language 4.0, JakartaWebSocket 2.0 and Jakarta Authentication 2.0
specifications<https://cwiki.apache.org/confluence/display/TOMCAT/Specifications>.
There is a significant breaking change between Tomcat 9.0.x and Tomcat 10.0.x. The Java
package used by the specification APIs has changed from javax... to jakarta.... It will be
necessary to recompile web applications against the new APIs. Alternatively, users can
convert an existing WAR file from Java EE 8 to Jakarta EE 9 using the Apache Tomcat
migration tool for Jakarta
EE<https://tomcat.apache.org/download-migration.cgi>."
С уважением,
Азат Усманов
Отдел разработки программного обеспечения
Казанский инновационный университет имени В.Г.Тимирясова
________________________________
От: dana whitelow <danawhite...@aol.com.INVALID>
Отправлено: 10 апреля 2021 г. 22:08
Кому: users@tomcat.apache.org <users@tomcat.apache.org>
Тема: version change failure
Hi ,
I changed tomcat version
from
<version>8.5.38</version>
to
<version>10.0.5</version>
The setup was running without web.xml and it was picking up index.jsp
automatically
but with the new version there is a connection refused error.
what has changed ?
Thanks
danawhite...@aol.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
