[seam-issues] [JBoss JIRA] (JBSEAM-4862) Seam Remoting GWT support not being skipped in AS 7.0.2

Seam Remoting GWT support not being skipped in AS 7.0.2 ------------------------------------------------------- Key: JBSEAM-4862 URL: https://issues.jboss.org/browse/JBSEAM-4862 Project: Seam 2 Issue Type: Bug Components: Framework Affects Versions: 2.3.0.ALPHA Environment: JBoss AS 7.0.2.Final EAR deployment of Seam 2.2.0 Reporter: Joshua Davis Assignee: Marek Novotny Fix For: 2.3.0.Final Attachments: gwt-exception.txt Original Estimate: 4 hours Remaining Estimate: 4 hours When deploying a Seam 2.2.0 EAR in JBoss AS 7.0.2.Final, the Seam Remoting GWT support components are not disabled in a nice way. Seam's scanner is trying to instantiate these components, even though the GWT classes are not available, resulting in a {{java.lang.LinkageError}} when Seam's scanner tries to load the class. * The application is deployed as an EAR. * {{jboss-seam.jar}} is in the root directory of the EAR, and is declared as an EJB module in {{META-INF/application.xml}}. * {{jboss-seam-remoting.jar}} is in the {{lib}} directory of the EAR, along with all the other Seam 2 jars. When JBoss AS 7 is deploying the application, the Seam 2 scanner is looking for components in {{lib/jboss-seam-remoting.jar}}. It finds {{GWT14Service}} and {{GWTToSeamAdapter}}, _even though_ these two components are declared with {{@Install(..., classDependencies= ...)}}. Expected behavior: The {{classDependencies}} in the {{@Install}} annotation prevents Seam's scanner from loading the class in the first place. Removing the the {{org.jboss.seam.remoting.gwt}} package from {{jboss-seam-remoting.jar}} made the problem go away.