portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21131] - Using Jetspeed with J2SE 1.4.2-beta breaks portlets
Date Wed, 02 Jul 2003 18:08:14 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=21131>.
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=21131

Using Jetspeed with J2SE 1.4.2-beta breaks portlets





------- Additional Comments From sgala@hisitech.com  2003-07-02 18:08 -------
The standard classloading (because of security) always starts by the
bootclasspath classloader (endorsed, rt.jar, ...), and only if the class is not
found proceeds using other classloaders. So, as soon as xerces or xalan classes
as in rt.jar, they will never be loaded from an application unless they are in
some "endorsed" directory. I have no URL, but Google knows about it.

This is to avoid, for instance, java loading the funny java.lang.System class I
provided in my jar (or other similar nasty things you can imagine).

This workaround enables us to close the bug, possibly, when we document it in
the installation notes, isn't it?

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


Mime
View raw message