This content has been marked as final. Show 3 replies
Why not just specify the native libraries directly in the JNLP using the native tag?
nroduit wrote:You might need to experiment with -Xbootclasspath: or -Xbootclasspath/p:
With he parameter "<property name="java.ext.dirs"/>" or "<property name="java.ext.dirs" value="" />" in jnlp, Java Web Start still loads libraries located in this ext folder.
I need to use this parameter to prevent library conflicts. It works well without Java Web Start with the VM parameter -Djava.ext.dirs="".
Is it a bug ? Is there a workaround ?
[url http://mindprod.com/jgloss/ext.html#INTRODUCTION]use the -verbose:class command line option to dump out the source of each class as it is loaded
[url http://download.oracle.com/javase/1.4.2/docs/tooldocs/findingclasses.html]How Classes are Found
Thanks for your suggestions. I can confirm that classes located in the JRE ext directory are loaded when running Java Web Start with the property <property name="java.ext.dirs" value="" /> in jnlp.
Jars located in the ext folder are not referenced in the boot class path. It seems there is no solution to avoid loading libraries installed in the ext directory with JWS.