Migrating a component may fail if it contains something that is not backward-compatible, and has not been flagged for checking in the migration tool. For example, because of increased specification compliance a program entity deployed to EAServer 5.x, may not be allowed in EAServer 6.0. This is not detected until the entity is deployed to EAServer 6.0. You must update any such entities to meet the specification.
The JSP compiler in EAServer 6.0 is more strict with syntax checking than EAServer 5.x. This example has an extra comma in the JSP import statement, which works in EAServer 5.x, but results in a compilation error in EAServer 6.0:
<%@ page import="java.io.IOException," %>
<%
out.println("This is a test");
%>
There may be other errors (with datatypes, for example) deployment failures because of backward-compatibility issues.
