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

Improve Seam deployment/scanning speed

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate Issue
    • Affects Version/s: 1.1.6.GA
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Environment:

      Any

      Description

      Currently the Seam component scanning takes prohibitively long in development when scanning a large project. My project has several thousand java files of which <1% are Seam components. For a Tomcat deployment changing from explicitly specifying the components to using the Seam scanning increases the startup time from 25 seconds to 50 seconds. Most of the 25 seconds is building a hibernate session factory.

      A possible enhancement would be to allow restriction of the packages that will be scanned via something in the components.xml.

      e.g.

      <scanning-config>
      <include-package name="com.xxx.web.seam.component"/>
      </scanning-config>

      Without this present behaviour is default. With it, it will only scan specified packages.

      Current workaround would be to package into separate jars but that's not always possible esp in development.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  quilleashm Mike Quilleash
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: