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

Posted to dev@xalan.apache.org by bu...@apache.org on 2003/08/22 00:23:29 UTC

DO NOT REPLY [Bug 22644] New: - FactoryFinder should attempt to use Context ClassLoader.

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=22644>.
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=22644

FactoryFinder should attempt to use Context ClassLoader.

           Summary: FactoryFinder should attempt to use Context ClassLoader.
           Product: XalanJ2
           Version: 2.5
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: org.apache.xml.dtm
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: cmore@atg.com


In order for web-applications (for example) to be able to supply their
own implementations of components, both the search for the META-INF/services
file and the loading of the configured class should use the current Thread's
context ClassLoader (as xerces now does consistently).

I noticed this issue with org.apache.xml.dtm.DTMManager (and FactoryFinder, which
it uses), but may exist in other places in apache. 

This is particularly bothersome since DTMManager ships with JDK 1.4, and therefore
other implementations are now guaranteed to conflict, and be difficult to override.