[ https://issues.jboss.org/browse/JBSEAM-4862?page=com.atlassian.jira.plugi... ] Joshua Davis updated JBSEAM-4862: --------------------------------- Description: 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. was: 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

[ https://issues.jboss.org/browse/JBSEAM-4862?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-4862: --------------------------------------- I suspect JBoss AS 7 web console, which uses GWT and brings somewhere com.google.gwt.user.client.rpc.RemoteService class and Seam fires installation of org.jboss.seam.remoting.gwt.GWT14Service. I will have to check that possibility. -- 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

[ https://issues.jboss.org/browse/JBSEAM-4862?page=com.atlassian.jira.plugi... ] Joshua Davis commented on JBSEAM-4862: -------------------------------------- Nope. I checked. No GWT anywhere. -- 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

[ https://issues.jboss.org/browse/JBSEAM-4862?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-4862: ---------------------------------- Fix Version/s: 2.3.0.Final -- 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

[ https://issues.jboss.org/browse/JBSEAM-4862?page=com.atlassian.jira.plugi... ] Vaclav Dedik edited comment on JBSEAM-4862 at 8/30/12 6:44 AM: --------------------------------------------------------------- The problem is the GWT interface (SerializationPolicyProvider) of the abstract superclass of the org.jboss.seam.remoting.gwt.GWT14Service which is not on the classpath when the application is being deployed. If you remove the interface (and modify the class so that it compiles), the exception no longer occurs. I guess that the JBoss AS classloader (or some underlying classloader) is incapable of loading a class that has an invalid interface (which make sense, I think), so I don't think there is an easy and pretty fix for this. was (Author: vdedik): The problem is the interface (SerializationPolicyProvider) of the abstract superclass of the org.jboss.seam.remoting.gwt.GWT14Service. If you remove the interface (and modify the class so that it compiles), the exception no longer occurs. I guess that the JBoss AS classloader (or some underlying classloader) is incapable of loading a class that has an invalid interface (which make sense, I think), so I don't think there is an easy and pretty fix for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4862?page=com.atlassian.jira.plugi... ] Vaclav Dedik edited comment on JBSEAM-4862 at 8/30/12 7:23 AM: --------------------------------------------------------------- The problem is the GWT interface (SerializationPolicyProvider) of the abstract superclass of the org.jboss.seam.remoting.gwt.GWT14Service which is not on the classpath when the application is being deployed. If you remove the interface (and modify the class so that it compiles), the exception no longer occurs. I guess that the JBoss AS classloader (or some underlying classloader) is incapable of loading a class that has an invalid interface (which make sense, I think), so I don't think there is an easy and pretty fix for this. was (Author: vdedik): The problem is the GWT interface (SerializationPolicyProvider) of the abstract superclass of the org.jboss.seam.remoting.gwt.GWT14Service which is not on the classpath when the application is being deployed. If you remove the interface (and modify the class so that it compiles), the exception no longer occurs. I guess that the JBoss AS classloader (or some underlying classloader) is incapable of loading a class that has an invalid interface (which make sense, I think), so I don't think there is an easy and pretty fix for this (except for catching the exception of course). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4862?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-4862: --------------------------------------- The exception doesn't relate to @Install(classDependencies) at all. The warning thrown by classloader is because the AbstractScanner is doing pre-loading due performance. I call it by design - initial feature req https://issues.jboss.org/browse/JBSEAM-3276. And in history it was changed the log level from INFO to DEBUG, so you can't see the log message from Seam and only from classloader, which may be is confusing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira