[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1142) Improve Seam deployment/scanning speed

[Gavin King (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1142?page=all ]

Gavin King closed JBSEAM-1142.
------------------------------

    Resolution: Duplicate Issue

dupe

> Improve Seam deployment/scanning speed
> --------------------------------------
>
>                 Key: JBSEAM-1142
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1142
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 1.1.6.GA
>         Environment: Any
>            Reporter: Mike Quilleash
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira