[Bug 128] Loading .jar files created by jar fails

http://sablevm.org/bugs/show_bug.cgi?id=128





------- Additional Comments From [email protected]  2005-04-17 12:55 -------
Sorry, the patch does not fix the problem. However, I think we both looked in  
the wrong direction. I am using sablevm embedded in another application, and I  
need to set the boot class path to replace the AWT implementation. 
When I tested your patch now I saw that the problem only occurs when the .jar 
is added using the sablevm.boot.class.path.prepend property: 
 
sablevm -p "sablevm.boot.class.path.prepend=java/testjar.zip" 
de.vdr.ApplicationManager 
 
java.lang.UnsatisfiedLinkError: Native library `vdrmhp' not found (as file 
`libvdrmhp') in gnu.classpath.boot.library.path and java.library.path 
   at java.lang.Runtime.loadLibrary (Runtime.java:778) 
   at java.lang.System.loadLibrary (System.java:518) 
   at de.vdr.ApplicationManager.static{} (ApplicationManager.java:19) 
   at java.lang.VMClass.step8 (VMClass.java) 
   at java.lang.Class.initialize (Class.java:147) 
   at java.lang.VirtualMachine.invokeMain (VirtualMachine.java) 
   at java.lang.VirtualMachine.main (VirtualMachine.java:108) 
 
sablevm -p "sablevm.boot.class.path.prepend=java/testjar.jar" 
de.vdr.ApplicationManager 
 
java.lang.ClassNotFoundException: de.vdr.ApplicationManager not found in 
java.lang.ClassLoader$1
{urls=[file:/home/marcel/freshmeat/vdr/vdr-1.3.23/PLUGINS/src/mhp/mhp/./], 
parent=null} 
   at java.net.URLClassLoader.findClass (URLClassLoader.java:841) 
   at java.lang.ClassLoader.loadClass (ClassLoader.java:360) 
   at java.lang.ClassLoader$1.loadClass (ClassLoader.java:1285) 
   at java.lang.ClassLoader.loadClass (ClassLoader.java:304) 
   at java.lang.VirtualMachine.main (VirtualMachine.java:99) 
 
The first is all right, the jar file can be read (tries to load a library which 
fails of course, but that doesn't matter here). 
Second is the problem, it was not found in the boot class loader, the system 
class loader throws this error. 



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.