On Thu, 5 Jun 2003, Qingye Jiang (John) wrote:
> >Dan, > >How wonderful! It worked! For years I have been puting all my jars >into the jre/lib/ext directory, and this is the first time that it >would not work. I would greatly appreciate if someone can give me >a further explaination. I'm not certain on the details, but I think that JARs in the ext directory are handled differently than those in the environment-variable CLASSPATH. For example, I believe that they get different security handling than other classes (i.e. they are more "trusted"), but I'm not sure about the details. Anyway, I suspect that in this case it's simply a bug in your java package. The javah program seems to be getting confused because the JARs were in the jre ext directory. I'm guessing that everything should work now that it's compiled, if you put the JARs in your ext directory. Although, I never do that myself :) -- Dan Streetman [EMAIL PROTECTED] --------------------- 186,272 miles per second: It isn't just a good idea, it's the law! ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ javax-usb-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
