I recently upgraded an application Struts 1.2 to 1.3. The actual changes needed to upgrade are quite easy to implement if you have a decent search and replace tool (these changes being detailed on the previously mentioned wiki page).
In addition, if your project makes use of numerous Jar libraries (like Struts, Spring, Hibernate etc.) I would recommend using Maven for assembling the necessary Jar files for your upgraded application. If you've not used Maven before it is worth investing a little time to learn it (it doesn't take long). Essentially you create a Maven XML project file (POM) detailing the Struts version and any other major Jar libraries that you are using (you can cut and paste some of the configuration details from http://www.mvnrepository.com/). Maven can then be used to download the appropriate Struts Jar file, the libraries that Struts depends on, any other libraries and the libraries on which they depend. It will also resolve library version conflicts that might arise. Even if you are not using Maven as your build tool, you can still make use of it inside Ant builds in order to do dependency management (which incidentally is only one aspect of what Maven can offer). http://maven.apache.org/ant-tasks.html For applications of this nature Maven will make future Jar upgrades easier. HTH Mark On 9/5/07, Mark Shifman <[EMAIL PROTECTED]> wrote: > Not particularly. There is a nice discussion on the struts wiki page: > http://wiki.apache.org/struts/StrutsUpgradeNotes12to13 > > Ed snooper wrote: > > Hello, > > > > In general is it hard to migrate an existing application from struts 1.2.x > > to 1.3.x? > > > > Ed > > > -- > Mark Shifman MD. Ph.D. > Yale Center for Medical Informatics > Phone (203)737-5219 > [EMAIL PROTECTED] -- "Paradoxically, the more time saving abstractions you are using the more you actually have to know." - Simon Willison --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
