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

[Joshua Davis (Created) (JIRA)]

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
         Environment: JBoss AS 7.0.2.Final
EAR deployment of Seam 2.2.0
            Reporter: Joshua Davis


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}}.

* 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= ...)}}.

Removing the the {{org.jboss.seam.remoting.gwt}} package from {{jboss-seam-remoting.jar}} made the problem go away.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira