You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@struts.apache.org by bu...@apache.org on 2003/03/21 16:53:45 UTC

DO NOT REPLY [Bug 18227] New: - ConfigRuleSet should use Digester's class loader

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18227>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18227

ConfigRuleSet should use Digester's class loader

           Summary: ConfigRuleSet should use Digester's class loader
           Product: Struts
           Version: 1.1 RC1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Digester
        AssignedTo: struts-dev@jakarta.apache.org
        ReportedBy: jogoussard@hotmail.com


ConfigRuleSet does not make use of the Digester class loader, which


can give troubles if a struts-config is dynamically loaded at


runtime.


ConfigRuleSet.ActionMappingFactory uses  RequestUtils.applicationInstance


to load ActionMappings instances. In turn the RequestUtils.applicationInstance


hardcodes the use of the Thread.currentThread.getContextClassLoader().


However, the Digester could be using a different classloader.


Suggested fix:


- RequestUtil.applicationClass & applicationInstance should take 


a ClassLoader as argument


- ConfigRuleSet should save a reference to the Digester and give


digester.getClassLoader() to RequestUtil.applicationInstance

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org