-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andres,
On 2/9/12 11:26 AM, Andres Aguado wrote: > Hi, first, for me there is a powerfull reason for maintain 5.5 > version. This is the initial version and application is working > fine now, and I think that i'm not prepare to execute the upgrade, > i don't know how and where to begin. Upgrading from 5.5 to 7.0 should ideally be as painless as installing Tomcat 7 and dropping your WAR into the webapps directory. The APIs are all backward-compatible. You may run into trouble in the following areas: 0. Don't have a META-INF/context.xml file? Make one. Don't use server.xml for webapp deployment anymore. 1. Non-spec-standard behavior Newer versions of Tomcat have become increasingly cranky about bad code, configurations, etc. You may have some warnings and/or errors that you will have to fix. You should fix those /anyway/, but now Tomcat complains about them. 2. Logging Logging has changed a lot over the years and so you'll have to read the documentation if things don't work for you. 3. Edge cases There are lots more settings in the later versions of Tomcat to get it to behave in ways that used to be the standard (or at least expected behavior). If you find that your webapp is acting strangely, check Tomcat's changelog to see what might have changed. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk80NmcACgkQ9CaO5/Lv0PDfswCeMmlkGkP9Q57W1uthyie/txvw 7rsAnikU1dpAc8lQM+zYVxNcB/Zk5Fky =idKe -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
