As you have probably already realised, Struts 1 to Struts 2 is a major upgrade. 
The joke in our team was "the one thing that is common between the two versions 
is the word Struts". 

If the existing project is not very complex(I realise this is a relative term), 
I would actually suggest designing and writing from the ground up with Struts 
2. You would be able to reuse a good portion of the existing Struts1 code, but 
by doing the basic designs with Struts 2, you would be able to leverage a lot 
of new features from Struts 2. For large complex projects you might need to 
code the Struts2 part around your existing Struts 1 code base, but please be 
prepared for complete rewrite of whole classes. 

~Krishnaraj V

-----Original Message-----
From: Ankit Garg 
Sent: 04 June 2023 10:02
To: user-ow...@struts.apache.org; user@struts.apache.org; 
user-...@struts.apache.org; user-i...@struts.apache.org
Subject: [External] : Urgent and priority help on Struts 1.3 upgrade to Struts 
6.0

TCS Confidential

Dear Team,

We seek help to upgrade our 1.3.x legacy application upgrade to Struts 6.0 with 
JDK 1.8.
Need help and expert connect to understand more on impact and approaches, 
effort estimation etc.
Appreciate your early attention and support please. Thank you.

Regards,
Ankit Garg


TCS Confidential
=====-----=====-----=====
Notice: The information contained in this e-mail message and/or attachments to 
it may contain confidential or privileged information. If you are not the 
intended recipient, any dissemination, use, review, distribution, printing or 
copying of the information contained in this e-mail message and/or attachments 
to it are strictly prohibited. If you have received this communication in 
error, please notify us by reply e-mail or telephone and immediately and 
permanently delete the message and any attachments. Thank you



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

Reply via email to