Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-4862

Seam Remoting GWT support not being skipped in AS 7.0.2

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.3.0.ALPHA
    • Fix Version/s: None
    • Component/s: Framework
    • Labels:
      None
    • Environment:

      JBoss AS 7.0.2.Final
      EAR deployment of Seam 2.2.0

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  manaRH Marek Novotny
                  Reporter:
                  pgmjsd Joshua Davis
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 4 hours
                    4h
                    Remaining:
                    Remaining Estimate - 4 hours
                    4h
                    Logged:
                    Time Spent - Not Specified
                    Not Specified