Re: version change failure
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 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 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: Усманов Азат Анварович To: Tomcat Users List ; dana whitelow 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 Отправлено: 10 апреля 2021 г. 22:08 Кому: users@tomcat.apache.org Тема: version change failure Hi , I changed tomcat version from 8.5.38 to 10.0.5 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
Re: version change failure [OT]
Dana,
On 4/10/21 16:34, dana whitelow wrote:
Thanks. I used the migration tool.
The problem is still there.
I believe this simple *.nix shell script can do a better job
grep -RiIl 'javax' | xargs sed -i 's/javax/jakarta/g'
That will migrate lots of APIs which haven't moved to Jakarta. It's not
javax.everything. It's only javax.some-things. And this should only
affect package imports or fully-qualified class names. If the text
"javax" appears in some comment somewhere, you don't want to replace it
with "jakarta", do you?
Quick grep explanation:
-R - recursive search
-i - case-insensitive
Why insensitive? 'javax' should be case-sensitive.
-I - skip binary files (you want text, right?)
Note that the migration tool will re-write binaries.
-chris
-Original Message-
From: Усманов Азат Анварович
To: Tomcat Users List ; dana whitelow
Sent: Sat, 10 Apr 2021 20:59
Subject: RE: version change failure
#yiv8603607814 P {margin-top:0;margin-bottom:0;}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.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."
С уважением,Азат Усманов
Отдел разработки программного обеспечения
Казанский инновационный университет имени В.Г.Тимирясова
От: dana whitelow
Отправлено: 10 апреля 2021 г. 22:08
Кому: users@tomcat.apache.org
Тема: version change failure Hi ,
I changed tomcat version
from
8.5.38
to
10.0.5
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
Re: version change failure
Think you can copy/test your war by using folder webapps-javaee rather than webapps, then migrate jakarta.* later. "Integration of the Apache Tomcat Migration Tool for Jakarta EE via the webapps-javaee directory" On 11/04/2021 10: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 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 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"> Is it possible to get hold of sample application or archetype showing the handling of a non-static file like jsp or servlet preferably .xhtml welcome file in jakartee even without the use of web.xml for the welcome file because it is meant to be optional in jakartaee? danawhite...@aol.com -Original Message- From: Усманов Азат Анварович To: Tomcat Users List ; dana whitelow 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 Отправлено: 10 апреля 2021 г. 22:08 Кому: users@tomcat.apache.org Тема: version change failure Hi , I changed tomcat version from 8.5.38 to 10.0.5 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
Re: version change failure
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 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 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"> Is it possible to get hold of sample application or archetype showing the handling of a non-static file like jsp or servlet preferably .xhtml welcome file in jakartee even without the use of web.xml for the welcome file because it is meant to be optional in jakartaee? danawhite...@aol.com -Original Message- From: Усманов Азат Анварович To: Tomcat Users List ; dana whitelow 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 Отправлено: 10 апреля 2021 г. 22:08 Кому: users@tomcat.apache.org Тема: version change failure Hi , I changed tomcat version from 8.5.38 to 10.0.5 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
Re: version change failure
Thanks. I used the migration tool.
The problem is still there.
I believe this simple *.nix shell script can do a better job
grep -RiIl 'javax' | xargs sed -i 's/javax/jakarta/g'
Quick grep explanation:
-R - recursive search
-i - case-insensitive
-I - skip binary files (you want text, right?)
-l - print a simple list as output. Needed for the other commands
danawhite...@aol.com
-Original Message-
From: Усманов Азат Анварович
To: Tomcat Users List ; dana whitelow
Sent: Sat, 10 Apr 2021 20:59
Subject: RE: version change failure
#yiv8603607814 P {margin-top:0;margin-bottom:0;}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.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."
С уважением,Азат Усманов
Отдел разработки программного обеспечения
Казанский инновационный университет имени В.Г.Тимирясова
От: dana whitelow
Отправлено: 10 апреля 2021 г. 22:08
Кому: users@tomcat.apache.org
Тема: version change failure Hi ,
I changed tomcat version
from
8.5.38
to
10.0.5
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
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 Отправлено: 10 апреля 2021 г. 22:08 Кому: users@tomcat.apache.org Тема: version change failure Hi , I changed tomcat version from 8.5.38 to 10.0.5 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
version change failure
Hi , I changed tomcat version from 8.5.38 to 10.0.5 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
