If I'm understanding right, you want me to explain what I did?<br><br>I wish I could say it were more glamerous. I just added the package of the class you said was being looked up but not found to the sun.jdk module, then added the sun.jdk module to the javax.api module so that all modules requiring classes from the Java APIs would have access to the JDK sun classes as well.<br>
<br>Not a great fix, but it works I guess.<br><br>~Lincoln<br><br><div class="gmail_quote">On Thu, Apr 26, 2012 at 5:49 PM, Thomas Frühbeck <span dir="ltr"><<a href="mailto:fruehbeck@aon.at">fruehbeck@aon.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">OS: SuSE Linux 3.1.10-1.9, x64<br>
JVM: Java(TM) SE Runtime Environment (build 1.6.0_31-b04)<br>
Java(TM) SE Runtime Environment (build 1.7.0_03-b04)<br>
OpenJDK Runtime Environment (IcedTea6 1.11.1) (suse-3.1-x86_64)<br>
<br>
no UTF-8 warnings detected.<br>
<br>
By the way, I feel inclined to think that this highly valuable technology JBossModules brings some intricacies with it.<br>
Lincoln, would you please let us have part in the story of your adventurous ride of the tiger?<br>
I am sure, that this issue will become one of the cornerstones of experiences with class loading :-)<span class="HOEnZb"><font color="#888888"><br>
<br>
Thomas<br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."<br>