IIRC, long ago there was a plugin for struts2 that executed struts1...which I guess might provide a way to do the port incrementally, if it still exists. But, in general, Struts1->2 is more of a rewrite than an upgrade. So instead of running old and new in the same jvm, you could just run old and new side-by-side, then "new" becomes completely unconstrained. For example, if your team has higher velocity with tools familiar to them, is the business process simple enough that you could build it quickly with those tools, perhaps reusing (at least parts of) the business and/or dao layers, if the legacy code was written well enough.
Good luck, -Dale > On Jun 3, 2023, at 11:16 PM, Ankit Garg <ankitk.g...@tcs.com> wrote: > > TCS Confidential > > Hi Dale, > Our customer has requested to upgrade legacy apps to version 6.0 aka 2.6. > > Thank you. > > -----Original Message----- > From: Don Brown <donald.br...@gmail.com> > Sent: Sunday, June 4, 2023 11:31 AM > To: Dale Newfield <d...@newfield.org> > Cc: Struts Users Mailing List <user@struts.apache.org>; > user-ow...@struts.apache.org; user-...@struts.apache.org; > user-i...@struts.apache.org > Subject: Re: Urgent and priority help on Struts 1.3 upgrade to Struts 6.0 > > "External email. Open with Caution" > > I'm more excited about the prospect of struts 6.0! Is that based on chatgpt? > >> On Sat, Jun 3, 2023, 22:57 Dale Newfield <d...@newfield.org> wrote: >> >> Am I the only one that finds at least some humor in one sentence that >> includes both "Struts 1" and the word "urgent"? :-) >> >> -Dale >> >> PS: I would guess, based on transitive dependencies, if nothing else, >> that anything still based upon struts1 is rife with vulnerabilities. >> I agree it probably should be decommissioned, if just to eliminate the >> risks resulting from those vulnerabilities. I would also look at this >> as an opportunity to re-envision the business solution and build a >> modern, scalable replacement, perhaps that provides even more >> capabilities to its users. Perhaps that includes more modern versions >> of Struts, perhaps not. This is a chance to shed legacy technical >> debt and leverage modern tools to both simplify the implementation and >> reduce operational costs. > > 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
