XML code review

The XML file review provides rules to detect deployment descriptor and other XML file issues.

Table 1. V6.1 to V7.0 migration
Rule Name	Rule Description	Automated Fix
Detect bad attributes of the global-transaction element	This rule flags an invalid transaction timeout attribute of the `global-transaction` element in the ibm-ejb-jar-ext.xml file.	No
Do not use bean-managed persistence in EJB 3.0 projects	This rule detects the use of bean-managed persistence in EJB 3.0 projects, which is valid in the IBM WebSphere Application Server V6.1 Feature Pack for Enterprise JavaBeans 3.0 but not in WebSphere Application Server V7.0.	No
Use application version 1.4 or lower when migrating applications from WebSphere V6.1 or prior	When migrating from WebSphere Version 6.1 or prior, this rule flags any application with a version higher than 1.4.	No
Use the metadata-complete attribute for Java EE 5 modules without annotations	This rule flags Java EE 5 modules that do not have the metadata-complete attribute set.	No
Use web module version 2.4 or lower when migrating applications from WebSphere V6.1 or prior	When migrating from WebSphere Version 6.1 or prior, this rule flags any web module with a version 2.5 or higher which can cause migration issues.	No
Use unique EJB 3.0 binding names	WebSphere Application Server V6.1 Feature Pack for EJB 3.0 allowed the EJB 3.0 binding file to contain duplicate binding names. The V7.0 server runtime environment added uniqueness checks for names used in the EJB 3.0 bindings file. Applications with uniqueness errors do not start in V7.0 even though the same application worked on the Feature Pack for EJB 3.0. This rule validates the EJB 3.0 bindings file to verify binding name uniqueness. It also validates that class names for session interfaces and interceptors are fully qualified.	No

Table 2. V7.0 to V8.0 migration
Rule Name	Rule Description	Automated Fix
Check for a behavior change for EJB presence in a web module	This rule flags a web.xml file of a Web Module Version 2.5 or higher if that module contains a .class file which has an EJB annotation. The .class file must be in a library (a .jar file in WEB-INF/lib).	No
Check for a behavior change in ApplicationException inheritance	This rule flags EJB ApplicationException definitions in ejb-jar.xml files which do not have the inherited attribute set. The inherited attribute was added in EJB 3.1 and changed the default behavior of EJB 3.0 applications.	No
Check for a behavior change in JSP configuration of <is-xml> and <page-encoding> options	This rule flags the <is-xml> and <page-encoding> JSP configuration options. The JSP specification was clarified with respect to these configuration options and included JSP files, and the behavior changed in Version 8.0.	No
Check for a behavior change in web services addressing policy	This rule flags addressing policy configuration found in the WSDL definition. The addressing policy was ignored in the WSDL definition in previous releases. This behavior change would cause problems only if the the addressing policy in the packaged WSDL differs in a significant way from the active configured addressing policy.	No
Detect validation.xml files	This rule flags the existence of XML files named validation.xml within the project contents. In Java EE 6, validation.xml became a reserved filename for use by the Bean Validation API.	No

Table 3. V7.0 to V8.0 or V8.5 migration
Rule Name	Rule Description	Automated Fix
Check for a behavior change in Java Server Faces (JSF) Applications	This rule flags Java Server Faces (JSF) applications because the default implementation for JSF container has changed in WebSphere V8.0.	No

Table 4. V8.0 to V8.5 migration
Rule Name	Rule Description	Automated Fix
Check for a behavior change in JPA cascade strategy	This rule flags projects using JPA entity relationships that use cascade types PERSIST, MERGE, or ALL because there is a potential behavior change in WebSphere Application Server V8.5. There is a corresponding Java rule to detect this behavior change.	No
Check for a behavior change in JPA MetaModel code generation concerning ListAttribute	This rule flags the persistence.xml file for a behavior change in JPA MetaModel code generation concerning ListAttribute in WebSphere V8.5.	No
The ejbdeploy command is supported with Java 6 and 7	When migrating to WebSphere V8.5.5 with Java 8, there is a limitation that the ejbdeploy command must be run using Java 6 or 7.	No

Table 5. V8.5 to V9.0 migration
Rule Name	Rule Description	Automated Fix
SCA was removed	This rule flags the use of Service Component Architecture (SCA) in applications. SCA was removed in WebSphere Application Server V9.0.	No
The JSF SunRI engine was removed	This rule flags references to the JSF SunRI in XML files.	No