This rule flags the presence of the Seam Framework in the project. In order to run Seam on WebSphere application server, you will need to make sure its configuration is correct for WebSphere. The application migration tool has two rules that detect the use of the Seam framework.
One rule is a Java rule that checks for the use of the package org.jboss.seam in Java files.
The second rule is an XML file rule that checks for Seam framework configuration.
The XML rule looks for any of the following items:
web.xml file that has a <listener-class> element with a value set to: org.jboss.seam.servlet.SeamListenerweb.xml file that has a <servlet-class> element with a value set to: org.jboss.seam.servlet.ResourceServletweb.xml file that has a <filter-class> element with a value set to: org.jboss.seam.web.SeamFilterfaces-config.xml file that has a <phase-listener> element with a value set to: org.jboss.seam.jsf.SeamPhaseListener<components> as a root element and any of these XML name spaces:
http://jboss.com/products/seam/componentshttp://jboss.com/products/seam/corehttp://jboss.com/products/seam/droolshttp://jboss.com/products/seam/frameworkhttp://jboss.com/products/seam/jmshttp://jboss.com/products/seam/remotinghttp://jboss.com/products/seam/theme<components> as a root element with a DOCTYPE that has a system ID value that starts with: http://jboss.com/products/seam/References to Seam are only flagged once per project. Even if you have both Java and XML Seam artifacts in your application, only one rule per project will have results. Moreover, only the first entry in a Java file that triggers the Java rule will be flagged, and all other entries that match the rule criteria will be skipped. Similarly, only the first entry in an XML file that triggers the XML rule will be flagged, and all other entries that match the rule criteria will be skipped.
For additional information, see: