cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 7175] - Class loading issues when using own XML parser
Date Sat, 16 Mar 2002 23:24:28 GMT
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=7175>.
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=7175

Class loading issues when using own XML parser





------- Additional Comments From patrick.luby@sun.com  2002-03-16 23:24 -------
I agree with Remy that you should stop trying to override the default XML parser. 
While you *may* be able to override it when using JDK 1.3, you will absolutely 
not be able to do it with JDK 1.4 as JDK 1.4 treats the XML parsing classes (also 
known as "endorsed" classes) as system classes. Hence, once the JVM is started, 
JDK 1.4 will not all any class loader in the process load alternate XML parsing 
classes that fall in any package names listed in the following URL:

  http://java.sun.com/j2se/1.4/docs/guide/standards/index.html

The only way around this JDK 1.4 restriction for your webapp only is to create an 
XML parser with package names that are not listed in the above URL (i.e. a very 
non-standard parser).

There is another way around this restriction. However, it will force all webapps 
(and the container itself) to use your XML parser. You can put your parser jar 
files in the common/lib directory (4.0.x) or in the common/endorsed directory 
(HEAD).

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message