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=16675>. 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=16675 Requst for more convenient classloading with Java 2 ------- Additional Comments From [EMAIL PROTECTED] 2003-02-18 22:54 ------- Implemented generalized classloading for org.apache.xalan.** but now have several questions. - What to do with org.apache.xpath.** internals? It highly depends on org.apache.xalan.** package and I see no problem. - What to do with org.apache.xml.dtm.FactoryFinder? There were some talks about possibile separation of DTM from Xalan. And more - there is no any dependency of org.apache.xml.** on org.apache.xalan.**. Since there is a need for classloading in org.apache.xml.** too, I think that org.apache.xml.utils is a better place for ObjectFactory than org.apache.xalan.util. What do you think? - What to do with org.apache.xalan.xsltc.** internals? I heard about some deserialization issues and I like to be sure I don't break anything. There is an org.apache.xalan.xsltc.runtime.TransletLoader class which is used for classloading inside xsltc. Could I safely delete it and use generalized ObjectFactory instead?
