JBoss Application Server XML file review rules
The XML file review provides a number of rules to detect migration issues with deployment descriptors, web services, and other XML files.
Rule Name | Rule Description | Automated Fix |
---|---|---|
Do not use local JNDI names |
This rule detects <local-jndi-name> tags in jboss.xml files. The quick fix scans all the projects associated with the application where the local JNDI name is found. If Java code is found that references the local JNDI name, an <ejb-local-ref> is added to that project. The Web or EJB bindings are also updated. |
No |
Manually migrate resource references for URLs and resource managers |
This rule detects <res-ref-name> elements in jboss-web.xml or jboss.xml files that define URL resources or resource manager resources. These resource references must be manually migrated. |
No |
Migrate JBoss login modules |
This rule detects <security-domain> elements in the jboss-web.xml file and <login-config> elements in the WEB-INF/web.xml file that might indicate that login modules require migration. |
No |
Use WebSphere bindings to define EJB JNDI names |
This rule detects the <jndi-name> tag in jboss.xml files for EJB definitions. The quick fix migrates the value found to the EJB bindings file. |
No |
Use WebSphere bindings to define EJB local reference JNDI names |
This rule detects <ejb-local-ref> tags in jboss.xml files for EJB definitions. The quick fix migrates the value found to the EJB bindings file. |
No |
Use WebSphere bindings to define EJB reference names |
This rule detects <ejb-ref-name> in jboss-web.xml or jboss.xml files. The quick fix adds the JNDI name of the EJB reference to the EJB bindings file. |
No |
Use WebSphere bindings to define message-driven Bean JNDI names |
This rule detects <destination-jndi-name> for message-driven beans. The quick fix sets the destination JNDI name in the EJB bindings file. |
No |
Use WebSphere bindings to define resource environment reference JNDI names | This rule detects the JBoss Application Server resource environment reference JNDI names in the jboss-web.xml or jboss.xml files. The quick fix migrates the JNDI name to the bindings file. | No |
Use WebSphere bindings to define resource reference names |
This rule detects <res-ref-name> elements in jboss-web.xml or jboss.xml files. The quick fix adds JNDI name of the resource reference to the EJB bindings file. |
No |
Use WebSphere extensions to define web module context root |
This rule detects the <context-root> element in jboss-web.xml files. The quick fix defines the context root value in the Web extensions file. |
No |
Do not use JBoss web services deployment descriptor |
This WebSphere Application Server traditional rule flags webservices.xml J2EE deployment descriptor files. The quick fix generates an Ant script that uses IBM WebSphere Ant tasks, which generate the appropriate artifacts for the list of web services based on the information collected from the deployment descriptors. Depending on the deployment descriptor, the fix might also generate the Service Endpoint Interface (SEI) for the service and add it to the project class path. You can then run the Ant script, copy the generated artifacts to the project, and possibly add additional targets such as the endpoint enabler. |
No |
Use WebSphere extensions to define CMP mappings |
This WebSphere Application Server traditional rule detects <jbosscmp-jdbc> elements in jbosscmp-jdbc.xml files. The quick fix uses the jbosscmp-jdbc.xml file to generate the EJB to RDB mapping files used by WebSphere Application Server for CMP. |
No |
The following rule flags any JBoss Application Server unhandled or partially handled XML file:
Rule Name | Rule Description | Automated Fix |
---|---|---|
Do not use jboss.xml file |
This rule flags the jboss.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
Do not use jboss-app.xml file |
This rule flags the jboss-app file so that you can look for any unmigrated elements at the end of the application migration. |
No |
Do not use jboss-client.xml file |
This rule flags the jboss-client.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
Do not use jbosscmp-jdbc.xml file |
This rule flags the jbosscmp-jdbc.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
Do not use jboss-web.xml file |
This rule flags the jboss-web.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |