<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">It's not so much that the link is broken but that Oracle deleted the thread.<div><br></div><div>Here is the gist of what it said:</div><div>The OP complained that his bug report against Java was deleted regarding regarding XLST no longer running under WebStart since 6 u23 and still in Java 7 was deleted.</div><div><br></div><div>He posted the small example that demonstrated the problem.</div><div><br></div><div>I posted that I had the same problem and asked whether using xalan directly solved the problem.</div><div><br></div><div>My guess is that this fault or the underlying one can be used maliciously to take over someone's computer.</div><div><br></div><div>This has nothing to do with the class path lookup. Which I'll respond in a separate post.</div><div><br></div><div>In Him,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div><div><br></div><div><br><div><div>On Feb 27, 2013, at 2:48 PM, Chris Burrell <<a href="mailto:christopher@burrell.me.uk">christopher@burrell.me.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi DM<div><br></div><div>The link seems broken. Is this related to our use of classloaders? I still think we shouldn't be using classloaders. Usually, one introduces classloaders to isolate parts of the application from other parts. For example Tomcat isolates different webapps from each other, but each webapp has access to the parent classloader. Or for example, within a webapp, Spring might isolate various components such as the servlets from the services declared.</div>
<div><br></div><div style="">What stops us from doing something like:</div><div style=""><br></div><div style="">Resource r = readFileFromJSwordHomes();</div><div style="">if(r == null) {</div><div style=""> r = readFileFromClassPath();<br>
}</div><div style=""><br></div><div style="">This seems much simpler. And even if it is unrelated to the bug you mention above, would reduce the complexity in JSword further. </div><div><br></div><div style="">Chris</div><div style="">
<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 27 February 2013 11:57, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There's a bug in Java WebStart that is rendering BibleDesktop unusable. The symptom is that it won't show any module content, but puts up an error message.<br>
<br>
This started with Java 6 update 23 and is still a bug with the latest Java 7.<br>
<br>
You can read about the bug here: <a href="https://forums.oracle.com/forums/thread.jspa?messageID=10786421" target="_blank">https://forums.oracle.com/forums/thread.jspa?messageID=10786421</a><br>
<br>
I'll be removing the WebStart links until this is fixed.<br>
<br>
In Him,<br>
DM<br>
<br>
<br>
<br>
_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
</blockquote></div><br></div>
_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>http://www.crosswire.org/mailman/listinfo/jsword-devel<br></blockquote></div><br></div></body></html>