Date: Tue, 19 Mar 2024 05:48:16 +0000 (UTC) Message-ID: <1854557869.54381.1710827296902@cwiki-he-fi.apache.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_54380_544811844.1710827296902" ------=_Part_54380_544811844.1710827296902 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The migration strategy of Struts 1 developers moving to Struts 2= involves four non-exclusive paths:
=
*.action
requests s and let S1 handle *.do
requests. S1=
and S2 can run side by side, within the same web application. Teams can im=
plement new features in the latest version, and migrate older pieces as nee=
ded. Optionally, some common resources may be shared between S1 and S2, lik=
e messages, validation rules, and Tiles configurations, making for an even =
smoother migration.web.xml
and S1 configuration files, and=
generates the corresponding S2 classes, pages, and configuration files. Wh=
ile 100% compatibility is unlikely, we could make a strong effort to conver=
t the application, marking areas that need attention. Comparing the convert=
ed files with the originals could also serve as a training tool.This page originally adopted from http://wiki.= apache.org/struts/MigrationStrategy.