The Apache Tomcat team announces the immediate availability of Apache
Tomcat Migration Tool for Jakarta EE 1.0.9
Apache Tomcat Migration Tool for Jakarta EE is an open source software
tool for migrating binary web applications (WAR files) and other binary
artifacts from Java EE 8 to Jakarta EE 9
what you expected instead of what happened.
If you want any further responses on this list, you're going to have to
provide more detail.
And again, remember that we really don't support the Eclipse
Transformer. If you want help with that, you should talk to Eclipse. If
you want to use
detail.
And again, remember that we really don't support the Eclipse
Transformer. If you want help with that, you should talk to Eclipse. If
you want to use Tomcat's Migration Tool, we can probably be of more help.
-chris
On Sunday, December 15, 2024, 12:06 PM, dineshk wrote:
Jakarta but
it doesn’t work. Would you be able to help in this regard ? I was using
transformer cli for this . We would need a tool to do the impact analysis for
third party jars and our application itself where all we do use javax which
require a migration to Jakarta.
ThanksDinesh
Sent from
. We would need a tool to do the impact analysis for
third party jars and our application itself where all we do use javax which
require a migration to Jakarta.
Sorry. I can't help you with the Eclipse Transformer. It isn't a project
I have any involvement in or experience of. My und
impact analysis for
third party jars and our application itself where all we do use javax which
require a migration to Jakarta.
ThanksDinesh
Sent from Yahoo Mail for iPhone
On Sunday, December 15, 2024, 12:01 AM, Christopher Schultz
wrote:
Dinesh,
On 12/14/24 1:36 AM, dineshk wrote:
> We
Java EE specs ?
Currently , we could not move to Jakarta specs for next 2-3 years ,
do we have any back word compatibility w.r.t. to Java EE specs with
higher versions of Tomcat ?
I've had pretty good results with a basic servlet-based application and
Tomcat's auto-migration capabilities
14 Dec 2024 06:36:44 dineshk :
Hi Team,
We are currently using Tomcat 9.0.70 . I would like to know what is
EOL (stretched) for this version ?
None currently planned for 9.x
Based on the typical life time of a Tomcat major version it would be
another ~3 years but as the last version that s
Tomcat provides migration tools to help you upgrade your codes to the
latest Jakarta EE API.
https://tomcat.apache.org/download-migration.cgi
---
Regards,
*Hantsy Bai*
Self-employed consultant, fullstack developer, agile coach,
freelancer/remote worker
GitHub: https://github.com/hantsy
Hi Team,
We are currently using Tomcat 9.0.70 . I would like to know what is EOL
(stretched) for this version ? Secondly , we would like to know if moving to
higher version of Tomcat e.g. 10.X would force us to migrate to Jakarta specs
instead of using the Java EE specs ? Currently , we could
ср, 4 сент. 2024 г. в 02:33, :
>
> I am migrating a Spring MVC app from 4.x to 6.x so I am going from Tomcat
> 9.1 Java 8 to Tomcat 10.1 Java 17.
>
> I noticed that in the migration steps on the Tomcat site that there is a
> tool to help with the javax to Jakarta package conversi
On 04/09/2024 00:33, charliedidon...@gmail.com wrote:
I am migrating a Spring MVC app from 4.x to 6.x so I am going from Tomcat
9.1 Java 8 to Tomcat 10.1 Java 17.
I noticed that in the migration steps on the Tomcat site that there is a
tool to help with the javax to Jakarta package conversions
I am migrating a Spring MVC app from 4.x to 6.x so I am going from Tomcat
9.1 Java 8 to Tomcat 10.1 Java 17.
I noticed that in the migration steps on the Tomcat site that there is a
tool to help with the javax to Jakarta package conversions
I have downloaded the migration tool from Github
Thank you
From: Chuck Caldarale
Sent: Thursday, August 29, 2024 2:57 PM
To: Tomcat Users List
Subject: Re: Tomcat migration tool for .war file going to 10.1x from 9x.
> On Aug 29, 2024, at 14: 46, Mcalexander, Jon J. com. INVALID> wrote: > > I hate asking this question, but I&#
put the .war file in a different
> webapps directory, but I can't find the name of the alternate webapps
> directory. Can someone point me to that documentation please?
I think you’re looking for this:
https://tomcat.apache.org/migration-10.html#Specification_APIs
The section title is
I hate asking this question, but I'm not finding the documentation I'm looking
for. I remember reading that if you DON'T want to migrate your .war file when
moving from 9x to 10.1x, you can put the .war file in a different webapps
directory, but I can't find the name of the alternate webapps dir
deployed on a vanilla Tomcat. Some
applications can probably be deployed on a
Tomcat-plus-a-small-number-of-support-libraries without requiring all of
TomEE. Your developers should be able to help with this decision.
As for migration... just copy the WAR file from WebSphere and drop it
into Tomcat&#
Hi all,
I'm reaching out to the community seeking assistance. I support Tomcat from an
infrastructure perspective and assist our developers with migrating a set of
existing applications from WebSphere and TomEE to Tomcat as the application web
server.
We are trying to come up with a streamlined
2024 5:45 PM
To: users@tomcat.apache.org
Subject: Re: [EXT]Re: [EXT]Re: jakartaee-migration-1.0.7 migration tool failure
[You don't often get email from ma...@apache.org. Learn why this is important
at https://aka.ms/LearnAboutSenderIdentification ]
Confirmed this is user error. There is no
@tomcat.apache.org
Subject: Re: [EXT]Re: [EXT]Re: jakartaee-migration-1.0.7 migration tool failure
[You don't often get email from ma...@apache.org. Learn why this is important
at https://aka.ms/LearnAboutSenderIdentification ]
Confirmed this is user error. There is no bug in the migration
Confirmed this is user error. There is no bug in the migration tool.
Steps to demonstrate this:
- Create new, blank Eclipse dynamic web project
- Add provided servlet code
- Add required libraries
- Remove referenced to internal logging code
- Add web.xml with basic mapping to "/test"
No I cannot compile from command line.
But I do not really care how eclipse compiles my class anyway.
All I know is that eclipse compiles the class without errors. Using the jars I
tell it to. (all the jars run through the migration tool)
But Tomcat 10 can not compile the class using those same
t 10 compiles it does not compile
>
> I have also used the migration tool on my .war that runs in Tomcat 9 and that
> war still fails with same compile error.
>
> So to summarize. the migration tool fails to convert third party jar
> xmlrpc-server3.1.3.jar
> And
I built my app in Eclipse and the build path is set to use the migrated jar.
It compiles without error on Eclipse and using the migrated jar. I have that
same migrated jar in the Tomcat lib
But when tomcat 10 compiles it does not compile
I have also used the migration tool on my .war that
});
return mapping;
}
}
Rick Noel
Systems Programmer | Westwood One
rn...@westwoodone.com
-Original Message-
From: Mark Thomas
Sent: Thursday, February 8, 2024 9:27 AM
To: users@tomcat.apache.org
Subject: Re: [EXT]Re: jakartaee-migration-1.0.7 migration to
}
});
return mapping;
}
}
Rick Noel
Systems Programmer | Westwood One
rn...@westwoodone.com
-Original Message-
From: Mark Thomas
Sent: Thursday, February 8, 2024 9:27 AM
To: users@tomcat.apache.org
Subject: Re: [EXT]Re: jakartaee-migration-1.0.7 migratio
On 08/02/2024 14:17, Rick Noel wrote:
My class is RVXmlRpcServlet and below is the compile error that happens when I
use the xmlrpc-server3.1.3.jar after that jar has been run through the
migration tool jakartaee-migration-1.0.7
That same class throws NO compile error on Tomcat 9 using
My class is RVXmlRpcServlet and below is the compile error that happens when I
use the xmlrpc-server3.1.3.jar after that jar has been run through the
migration tool jakartaee-migration-1.0.7
That same class throws NO compile error on Tomcat 9 using xmlrpc-server3.1.3.jar
Here is the compile
running this jar trough the latest Tomcat 10 migration tool
(jakartaee-migration-1.0.7) which is suppose to alter the jar to make all
classes use jakarta.server. classes
but the tool is not fully converting all the classes, since I still get
compile errors at run time.
Please provide details
10 migration tool
(jakartaee-migration-1.0.7) which is suppose to alter the jar to make all
classes use jakarta.server. classes
but the tool is not fully converting all the classes, since I still get
compile errors at run time.
I think in addition to not using javax.server. the jar should
28 Sept 2023 03:22:26 Muralisankar Srinivasan :
Dear Users,
I am facing the following Exceptions from the Java Maven application
which
is migrated from Javax to Jakarta, using "jakartaee-migration-1.0.7".
The
application was successful in "Apache Tomcat Version 9.0.64".
Dear Users,
I am facing the following Exceptions from the Java Maven application which
is migrated from Javax to Jakarta, using "jakartaee-migration-1.0.7". The
application was successful in "Apache Tomcat Version 9.0.64".
Please suggest the dependencies to be added in pom.xml
The Apache Tomcat team announces the immediate availability of Apache
Tomcat Migration Tool for Jakarta EE 1.0.6
Apache Tomcat Migration Tool for Jakarta EE is an open source software
tool for migrating binary web applications (WAR files) and other binary
artifacts from Java EE 8 to Jakarta EE 9
The Apache Tomcat team announces the immediate availability of Apache
Tomcat Migration Tool for Jakarta EE 1.0.5
Apache Tomcat Migration Tool for Jakarta EE is an open source software
tool for migrating binary web applications (WAR files) and other binary
artefacts from Java EE 8 to Jakarta EE 9
The Apache Tomcat team announces the immediate availability of Apache
Tomcat Migration Tool for Jakarta EE 1.0.4
Apache Tomcat Migration Tool for Jakarta EE is an open source software
tool for migrating binary web applications (WAR files) and other binary
artefacts from Java EE 8 to Jakarta EE 9
The Apache Tomcat team announces the immediate availability of Apache
Tomcat Migration Tool for Jakarta EE 1.0.3
Apache Tomcat Migration Tool for Jakarta EE is an open source software
tool for migrating binary web applications (WAR files) and other binary
artefacts from Java EE 8 to Jakarta EE 9
The Apache Tomcat team announces the immediate availability of Apache
Tomcat Migration Tool for Jakarta EE 1.0.1
Apache Tomcat Migration Tool for Jakarta EE is an open source software
tool for migrating binary web applications (WAR files) and other binary
artefacts from Java EE 8 to Jakarta EE 9
Hi,
This is a follow-up mail. Please help with the below issue.
Regards,
Chetna Agrawal
-Original Message-
From: Chetna Agrawal
Sent: 28 April 2022 17:35
To: users@tomcat.apache.org
Subject: Automated migration for Tomcat 9 to 10
Hi,
I want to migrate my webapp from Java EE8 to
Hi,
I want to migrate my webapp from Java EE8 to Jakarta EE 9 in order to run it on
tomcat 10.0.18. I am trying to run jakartaee migration tool at runtime by
adding - , in my context defined in
server.xml. The tomcat version that I am using is 10.0.18. I am providing the
value of path as
On 3/29/22 10:54, Senguttuvan, Gopalakrishnan (CWM-NR) wrote:
Hi Thomas,
Thanks for the response.
This issue occurred when I have start the Tomcat server in Linux-QA machine.
Regards,
Gopalakrishnan S
Double check your runtime environment - something there is out of whack
I suspect.
--
: Tomcat Users List
Subject: AW: Migration JDK11 - Tomcat 9 - NoClassDefFoundError:
java/sql/Statement
[External]<https://connect.fg.rbc.com/community/techhub/external-email-indicator>
Hello,
does this error show up in IntelliJ ?
Seems like there is a bug in IntelliJ:
https://stackoverfl
> -Ursprüngliche Nachricht-
> Von: Senguttuvan, Gopalakrishnan (CWM-NR)
>
> Gesendet: Freitag, 25. März 2022 17:13
> An: users@tomcat.apache.org
> Betreff: Migration JDK11 - Tomcat 9 - NoClassDefFoundError:
> java/sql/Statement
>
> Hi Team,
>
> We a
Hi Team,
We are migrating our application from JDK8 to JDK11 (RedHat OpenJDK11).
Modified the JAVA_HOME to JDK11 path.
Currently we are using Tomcat version 9. (It is working fine with JDK8).
Since the JDK11 won't support the JAVA_ENDORSED_DIRS, so I have removed the
"-Djava.endorsed.dirs" in cat
The Apache Tomcat team announces the immediate availability of Apache
Tomcat Migration Tool for Jakarta EE 1.0.0
Apache Tomcat Migration Tool for Jakarta EE is an open source software
tool for migrating binary web applications (WAR files) and other binary
artefacts from Java EE 8 to Jakarta EE 9
The Apache Tomcat team announces the immediate availability of Apache
Tomcat Migration Tool for Jakarta EE 0.2.0
Apache Tomcat Migration Tool for Jakarta EE is an open source software
tool for migrating binary web applications (WAR files) and other binary
artefacts from Java EE 8 to Jakarta EE 9
> On Feb 9, 2021, at 1:25 AM, Mark Thomas wrote:
>
> On 08/02/2021 23:40, Rob Sargent wrote:
>> Well, it the 9->10 page, but that form generator is all about
>> 10.x->10.y (Not sure it's doing anything useful either?)
>
> Copy/paste error. Fixed now. Thanks for reporting this.
>
> The conf
On 08/02/2021 23:40, Rob Sargent wrote:
> Well, it the 9->10 page, but that form generator is all about
> 10.x->10.y (Not sure it's doing anything useful either?)
Copy/paste error. Fixed now. Thanks for reporting this.
The configuration difference generator is working but the files haven't
chang
Well, it the 9->10 page, but that form generator is all about
10.x->10.y (Not sure it's doing anything useful either?)
On 2/8/21 4:35 PM, Rob Sargent wrote:
I think there's an error on this page:
http://tomcat.apache.org/migration-10.html
First paragraph under &
I think there's an error on this page:
http://tomcat.apache.org/migration-10.html
First paragraph under "Upgrading 10.0.x"
When upgrading instances of Apache Tomcat from one version of
_Tomcat 9 _to another, particularly when using separate
Which confused me becaus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Lavitesh,
On 6/22/20 07:12, Lavitesh Verma wrote:
> We didn’t use woodstox previously in our application and after we
> updated tomcat to version 8.5.5 we are getting this issue.
>
> We were able to resolve the issue by adding “wstx-asl-2.9.1.jar” t
Issue found during migration of Tomcat version 6.0.35 to 8.5.5
Sorry for the top post. I'm having email formatting problems.
Lavitesh,
15-Jun-2020 07:34:45.122 SEVERE [http-nio-7080-exec-10]
org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for
servlet [MainControllerServl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Niranjan,
On 6/19/20 13:17, Niranjan Rao wrote:
> Hi Mark/Chris,
>
> Thank you for the reply.
>
> It's a spring application, related controllers/methods basically
> return page name as return "pages/Login".
>
> The view resolver maps it WEB-INF/jsp/
Hi Mark/Chris,
Thank you for the reply.
It's a spring application, related controllers/methods basically return
page name as return "pages/Login".
The view resolver maps it WEB-INF/jsp/pages/Login.jsp.
Login.jsp has entry that says
This entry gets resolved correctly in V7, but V9 I get er
On 19/06/2020 13:19, Christopher Schultz wrote:
> Niranjan,
>
> On 6/18/20 13:47, Niranjan Rao wrote:
>> I am trying to migrate from 7.0.73 to 9.0.36 and facing
>> challenges.
>
>> Java version and operating system version remains same in both
>> cases.
>
> ... and what are those versions?
>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Niranjan,
On 6/18/20 13:47, Niranjan Rao wrote:
> I am trying to migrate from 7.0.73 to 9.0.36 and facing
> challenges.
>
> Java version and operating system version remains same in both
> cases.
... and what are those versions?
> I have carefully
Greetings,
I am trying to migrate from 7.0.73 to 9.0.36 and facing challenges.
Java version and operating system version remains same in both cases.
I have carefully reviewed the configurations and everything looks ok.
Version 9 does not report any problems when starting the application
ei
ose sources. Removing it just means you'll get the default.
John
From: Lavitesh Verma
Sent: Monday, June 15, 2020 8:49 AM
To: Tomcat Users List
Subject: RE: Issue found during migration of Tomcat version 6.0.35 to 8.5.5
Hi,
PFA the complete Stack Trace for the Issue.
Thanks &am
All,
From: Christopher Schultz
Sent: Tuesday, June 16, 2020, 23:29
To: users@tomcat.apache.org
Subject: Re: [OT] [tomcat-users] Issue found during migration of Tomcat version
6.0.35 to 8.5.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 6/15/20 10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 6/15/20 10:02, Jason Pyeron wrote:
> A quick brief on etiquette.
>
> 1. Please do not harvest emails and send linked in requests
OMG +1 many many times to this.
If I haven't met you in person, don't send me a LinkedIn request.
> 2.
changes, lib/ JARs, startup parameters, etc)
Based on the limited information you have provided (e.g. no test case I can
run) I do not see any relevant issues in the following guides.
https://tomcat.apache.org/migration-7.html
http://tomcat.apache.org/migration-8.html
http
0 7:33 PM
To: 'Tomcat Users List'
Cc: 'RUBIN, JACOB' ; lsrv...@list.att.com; Vasudev Wadhawan
Subject: RE: [tomcat-users] Issue found during migration of Tomcat version
6.0.35 to 8.5.5
What I see here is that there is a bit of custom code that is &quo
: Monday, June 15, 2020 9:29 AM
To: Jason Pyeron ; 'Tomcat Users List'
Cc: 'RUBIN, JACOB' ; lsrv...@list.att.com; Vasudev Wadhawan
Subject: RE: [tomcat-users] Issue found during migration of Tomcat version
6.0.35 to 8.5.5
Hi Jason,
We have updated the xercesImpl from ver
e 15, 2020 6:49 PM
To: Tomcat Users List
Subject: Re: Issue found during migration of Tomcat version 6.0.35 to 8.5.5
guess looks like jar not found, full stacktrace would be helpful.
On Mon, Jun 15, 2020 at 8:17 PM Lavitesh Verma
wrote:
> Hi Team,
>
>
>
> Below are the de
Hi Jason,
We have updated the xercesImpl from version 2.6.2 to 2.12.0 for the migration
and no new jars were added for the new environment.
We didn't use Woodstox StAX jar with tomcat 6.0.35 and did not face any such
issue.
PFA the complete Stack Trace for the Issue.
Thanks &
guess looks like jar not found, full stacktrace would be helpful.
On Mon, Jun 15, 2020 at 8:17 PM Lavitesh Verma
wrote:
> Hi Team,
>
>
>
> Below are the details of the system and tomcat version
>
> Old tomcat version: *Apache Tomcat/6.0.35*
>
> New tomcat version: *Apache Tomcat/8.5.5*
>
> Opera
@tomcat.apache.org
Cc: RUBIN, JACOB ; lsrv...@list.att.com; Vasudev Wadhawan
Subject: [tomcat-users] Issue found during migration of Tomcat version 6.0.35
to 8.5.5
Importance: High
Hi Team,
Below are the details of the system and tomcat version
Old tomcat version: Apache Tomcat/6.0.35
New tomcat
Hi Team,
Below are the details of the system and tomcat version
Old tomcat version: Apache Tomcat/6.0.35
New tomcat version: Apache Tomcat/8.5.5
Operating System: SunOS
OS Version: 5.10
Architecture: sparcv9
JVM Version: 1.8.0_101-b13
Vendor: Oracle Corporation
We are trying to migrate Apache Tom
Am 2019-06-21 um 14:33 schrieb Mark Thomas:
On 21/06/2019 13:13, Osipov, Michael wrote:
Folks,
we're migrating off old hosts to new ones, but remain at 8.5.x (.34 to
.42 at the moment) and Java 8. Surprisingly, an empty Tomcat wih just
manager installed takes way too long too start. More pre
On 21/06/2019 13:13, Osipov, Michael wrote:
> Folks,
>
> we're migrating off old hosts to new ones, but remain at 8.5.x (.34 to
> .42 at the moment) and Java 8. Surprisingly, an empty Tomcat wih just
> manager installed takes way too long too start. More precisely, the
> Tomcat is fast, deploying
Folks,
we're migrating off old hosts to new ones, but remain at 8.5.x (.34 to
.42 at the moment) and Java 8. Surprisingly, an empty Tomcat wih just
manager installed takes way too long too start. More precisely, the
Tomcat is fast, deploying manager app is horribly slow:
2019-06-21T13:50:35
On 03/06/2019 22:46, Mark Thomas wrote:
>> Florian,
>>
>>> On 5/23/19 06:59, Florian Trimmel wrote: We were able to figure out
>>> what was causing the file descriptor leak.
>>
>>> The leak has occured in the JSF2 MyFaces Implementation we are
>>> using. It is described here:
>>> https://marc.info/
> Florian,
>
>> On 5/23/19 06:59, Florian Trimmel wrote: We were able to figure out
>> what was causing the file descriptor leak.
>
>> The leak has occured in the JSF2 MyFaces Implementation we are
>> using. It is described here:
>> https://marc.info/?l=myfaces-dev&m=152536956716792&w=2 The probl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Florian,
> On 5/23/19 06:59, Florian Trimmel wrote: We were able to figure out
> what was causing the file descriptor leak.
>
> The leak has occured in the JSF2 MyFaces Implementation we are
> using. It is described here:
> https://marc.info/?l=myf
Am Do., 23. Mai 2019 um 17:14 Uhr schrieb Christopher Schultz <
ch...@christopherschultz.net>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Florian,
>
> On 5/23/19 06:59, Florian Trimmel wrote:
> > After migrating from Tomact 7 to Tomcat 9.0.20 (running with same
> > Java Version 1.8.0_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Florian,
On 5/23/19 06:59, Florian Trimmel wrote:
> After migrating from Tomact 7 to Tomcat 9.0.20 (running with same
> Java Version 1.8.0_25) we have a problem with our JSF2 web
> application on Linux RHEL 7. After some time we get Exceptions like
Hi,
After migrating from Tomact 7 to Tomcat 9.0.20 (running with same Java
Version 1.8.0_25) we have a problem with our JSF2 web application on Linux
RHEL 7. After some time we get Exceptions like this:
java.io.FileNotFoundException:
/f4m/tomcat/tomcat_f4mbs/webapps/ACM/WEB-INF/acm-config.xml
On 04/10/2017 15:53, Aquatic Safaris Diver wrote:
>
> I've read the migration manuals and have tried to make the changes to
> my configuration to work correctly in tomcat v8.5, but it's not. I'm
> not an experton XML files and JDK so please help me. I'm sure t
I've read the migration manuals and have tried to make the changes to
my configuration files to work correctly in tomcat v8.5, but it's not. I'm
not an expert on XML files and JDK so please help me. I'm sure this is
crazy simple
for you experts.
The server.xml conf file i
===
===
thanks
PHL.
De : Christopher Schultz
Envoyé : jeudi 3 janvier 2019 14:52
À : users@tomcat.apache.org
Objet : Re: Migration tomcat 7 to 9 : export static files
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 1/3/19 03:56, andre seame wrote:
> Hello,
>
> In tomcat 7, I have a server.xml config file. In the host section I
> have
>
>
>
> So, I can access to static file :
> http://server:8080/testresults/myfile.png, where the file is stored
>
Hello,
In tomcat 7, I have a server.xml config file. In the host section I have
So, I can access to static file : http://server:8080/testresults/myfile.png,
where the file is stored in d:\TESTRESULTS\myfile.png
When using the HTML gui management interface -http://server:8080/manager/html),
I
e: Tomcat
> 5.5.17 migration to 6.0.53
>
> David,
>
> On 7/24/18 10:54 AM, David Babooram wrote:
>> I will try to be as clear as possible.
>
> :)
>
>> The files that were originally in
>> /usr/local/tomcat/jakarta-tomcat-5.5.17/webapps/MYAPP/WEB-INF/lib
>&
>> junit.jar
>
> Are you sure you need the junit runtime in your running
> application? My guess is "no" and you might want to see if things
> still work is you remove this. But it can wait until later.
>
> Finally (and I say this as a proud Apache Struts 1.x use
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Tuesday, 24 July 2018 12:41 PM
To: users@tomcat.apache.org
Subject: [EXTERNAL] Re: Tomcat 5.5.17 migration to 6.0.53
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 7/24/18 10:54 AM
ched, publicly-reported security
vulnerabilities in the version you are using (1.3.10). You should
really research those vulnerabilities and make sure that you have
mitigated them all, or you risk exposing your users and servers to
exploitation.
Hope that helps,
- -chris
> -Original Message-
re using (1.3.10). You should
really research those vulnerabilities and make sure that you have
mitigated them all, or you risk exposing your users and servers to
exploitation.
Hope that helps,
- -chris
> -Original Message- From: Christopher Schultz
> [mailto:ch...@christophersch
Subject: [EXTERNAL] Re: Tomcat 5.5.17 migration to 6.0.53
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 7/23/18 12:51 PM, David Babooram wrote:
> Hello
>
> I have begun a migration from 5.5 to 6. Yes I know 6 is EOL but the
> migration from 5.5 to 6 has some more d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 7/23/18 12:51 PM, David Babooram wrote:
> Hello
>
> I have begun a migration from 5.5 to 6. Yes I know 6 is EOL but
> the migration from 5.5 to 6 has some more documentation compared to
> 5.5 to the latest version.
>
Hello
I have begun a migration from 5.5 to 6. Yes I know 6 is EOL but the migration
from 5.5 to 6 has some more documentation compared to 5.5 to the latest version.
I followed the standard migration of libs and classes from /common /shared etc
to the new /lin directory for 6..
The server
I can tell you that going from 5.5 -> 6.0 is exactly
as difficult as it will be to go from 5.5 -> 8.5. I personally
recommend 8.5 over 9.0 due to some potential
backward-incompatibilities you may encounter with 9.0 that don't exist
in 8.5. An eventual migration from 8.5 -> 9.0 should b
018, David Babooram
wrote:
Good morning
My intent is to migrate from 5.5.17 to 6 with the intent to upgrade to
6.0.48. , mainly due to a vulnerability notice.
I understand the changes listed from the Apache site wrt the migration.
but I have not gotten any steps on how to proceed.
Is there
On 14.07.2018 22:53, David Babooram wrote:
Alright.
I guess the thought the process was to upgrade to 6, then 7, 8
If your application doesn't do anything too tomcat specific, but is
rather a standard web application, you might be able to just deploy it
on Tomcat 8.5 and check if it all work
Re: Re: Tomcat 5.5.17 migration to 6
> But by decision was based on what was presented in the Apache site. In
that, upgrade from
> 5.5 was known to only go to 6.
Seriously, don't even think about "upgrading" to another very dead level.
There haven't been updates to Tomc
> From: David Babooram [mailto:david.baboo...@digicelgroup.com]
> Subject: Re: Re: Tomcat 5.5.17 migration to 6
> But by decision was based on what was presented in the Apache site. In
that, upgrade from
> 5.5 was known to only go to 6.
Seriously, don't even think about "
ate from 5.5.17 to 6 with the intent to upgrade to
> 6.0.48. , mainly due to a vulnerability notice.
>
> I understand the changes listed from the Apache site wrt the migration.
> but I have not gotten any steps on how to proceed.
>
> Is there any proper documentation on how to
ntent is to migrate from 5.5.17 to 6 with the intent to upgrade to
> 6.0.48. , mainly due to a vulnerability notice.
>
> I understand the changes listed from the Apache site wrt the migration.
> but I have not gotten any steps on how to proceed.
>
> Is there any proper documentation on how to proceed
>
Good morning
My intent is to migrate from 5.5.17 to 6 with the intent to upgrade to 6.0.48.
, mainly due to a vulnerability notice.
I understand the changes listed from the Apache site wrt the migration. but I
have not gotten any steps on how to proceed.
Is there any proper documentation
Hi Marek, Hi Mark.
Thank you very much.
Best regards
G
-Ursprüngliche Nachricht-
Von: Mark Thomas [mailto:ma...@apache.org]
Gesendet: Mittwoch, 7. Februar 2018 09:51
An: Tomcat Users List
Betreff: [EXTERNAL] Re: Migration from Tomcat 8.0.37 to 8.5.24 , changes to
protocol at
Hi Lauria,
This seems like everything is the same for you on both Tomcat 8 and 8.5;
what changed is that the SSL implementation gets displayed in the console.
JSSE means you're using Java runtime JSSE implementation. There's the
possibility to use OpenSSL implementation as well. See the docs
On 07/02/18 08:41, Lauria Giuseppe wrote:
> Hi tomcat users.
>
>
> We are in transition from Tomcat 8.0.37 to 8.5.24.
> What is the meaning of this ? Is this just naming change ?
> Or did functionality change ? If yes, what is different between http-nio and
> https-jsse-nio ?
8.0.x only supp
1 - 100 of 297 matches
Mail list logo
