Re: UnsatisfiedLinkError


"Roedy Green" <my_email_is_posted_on_my_website@xxxxxxxxxxxxxx> wrote in
message news:8hr052ttddiljt77bopkrllh5sjrv9jsbc@xxxxxxxxxx
On Thu, 27 Apr 2006 00:01:55 -0400, "Rhino"
<no.offline.contact.please@xxxxxxxxxx> wrote, quoted or indirectly
quoted someone who said :

I did exactly that and Wassup ran
fine - but it did NOT tell me a value for java.library.path. So, to use
the
vernacular, "wassup with that?".

The advice reads
"Use Wassup to determine the java.library.path system property. It is
restricted, so make sure you flip the Wassup display from safe to
restricted. Your DLL must live either on that path, or in your jar
without any package name."


Did you follow the instructions in the second sentence?

Yes, I ran it in both 'safe' and 'restricted' modes and neither showed me
any property called java.library.path. The same thing happened just now when
I tried it again. Lots of properties got displayed in each case, just
nothing called java.library.path. It correctly reported my Java version,
1.5.0_06 and my user name so the applet itself seems to be working fine.

--
Rhino


.

Relevant Pages

  • Re: CPU detection
    ... >a way to detect how many CPUs the current machine has? ... look at the system property: ... to view use wassup http://mindprod.com/wassup.html ... Coaching, problem solving, economical contract programming. ...
    (comp.lang.java.programmer)
  • Re: UnsatisfiedLinkError
    ... vernacular, "wassup with that?". ... The advice reads ... "Use Wassup to determine the java.library.path system property. ...
    (comp.lang.java.databases)