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=16599>. 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=16599 class loading problem [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2003-01-31 15:07 ------- I presume you have xerces in the classpath when you execute your java class. What I think you are seeing is the interaction between Xerces in your loader and the JAXP classes in the system loader. Specifically, the factory comes from the system (parent) loader ResourceStream for META-INF/services/javax.xml.parsers.DocumentBuilderFactory loaded from parent loader Finding class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl but that loader knows nothing of the Xerces classes. Well, I'm guessing a bit here since I don't know what your code is doing nor the classpath setup of your <java> task. Is your code specifically asking for Xerces when it wants a parser? At this stage, it is probably academic. You are probably better off just forking the <java> execution so everything winds up in the system loader. I'm going to close as WONTFIX, but please feel free to add more comments or reopen if required. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
