Migration of Web applications deployed in WebSphere Application Server Version 5.x is usually not necessary; version 2.2 and 2.3 of the Java Servlet specification and version 1.2 and 1.4 of the JavaServer Pages (JSP) specification are still supported unless the behavior was changed in Servlet 2.4 or JSP 2.0 Specifications.
Servlet migration might be a concern if your application:
Version 4 | Version 5 | Version 6 | |
---|---|---|---|
Default Content-Type | text or html | text or html charset=<default_encoding> | none |
Append Charset on getWriter if the property does not exist on Content-Type | text or html | text or html | text/xml; |
Example: response.setCharacterEncoding("UTF-8"); response.setContentType("text/xml"); response.getWriter(); | charset=UTF-8 | ||
Remove charset from the Content-Type property if the setContentType property is called after getWriter with a ";charset=" portion | text or html | text or html | text or html |
Example: setContentType("text/html;charset=ISO-8859-7"); getWriter(); setContentType("text/xml;charset=UTF-8"); |
JSP migration might be a concern if your application references JSP page implementation classes in unnamed packages, or if you install WebSphere Application Server Version 4.x EAR files (deployed in Version 4.x with the JSP Precompile option), in Version 5.x. You need to recompile all JSP pages when migrating from WebSphere Application Server Version 5.x.
Follow these steps if migration issues apply to your Web application:
In this information ...Related reference
Related information
| IBM Redbooks, demos, education, and more(Index) |