You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Craig McClanahan (JIRA)" <ji...@apache.org> on 2007/05/23 21:04:42 UTC

[jira] Created: (SHALE-448) Improve performance of startup scanning

Improve performance of startup scanning
---------------------------------------

                 Key: SHALE-448
                 URL: https://issues.apache.org/struts/browse/SHALE-448
             Project: Shale
          Issue Type: Improvement
          Components: Tiger
    Affects Versions: 1.0.4, 1.1.0-SNAPSHOT
            Reporter: Craig McClanahan
            Priority: Minor


At startup time, the Tiger extensions currently scan classes in JAR files to analyze their annotations.  To reduce overhead, two heuristics (only scan JARs that have a META-INF/faces-config.xml, and/or limit the package names that should be scanned) are applied to reduce the number of classes actually scanned.

It turns out that there is a variant of Class.forName():

    public Class<?> forName(String name, boolean initialize, ClassLoader loader)
      throws ClassNotFoundException

that can load the metadata about a class without running the static initializers yet.  It should be possible to use this variant to further reduce the startup overhead.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.