Classfinder searching every sub-directory in the Glassfish directory for 
classes to be used for the action finder
-----------------------------------------------------------------------------------------------------------------

                 Key: WW-3307
                 URL: https://issues.apache.org/struts/browse/WW-3307
             Project: Struts 2
          Issue Type: Improvement
          Components: Plugin - Convention
    Affects Versions: 2.1.6
         Environment: Glassfish v2.1
            Reporter: James Cook


Further to :
https://issues.apache.org/struts/browse/WW-3234

The list of classes being given to the filter to look for actions was being 
taken from the Glassfish root directory, this led to anything and everything 
being given to the filter. This led to extremely long deployment times on 
Glassfish instances with multiple domains and applications during the file scan.

After mentioning to Musachy, I propose the following solution (I have an 
implementation running - if needed)

Have an 'include directories' parameter to the convention setting. Allowing for 
explicit setting of the directories to be scanned - thus filtering out the 
other directories from the list of URLs, if this is not specified then it falls 
back to the current scanning.

What are everyones thoughts on this?

  

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

Reply via email to