JNLP gotchas

R

Roedy Green

I was reading over the latest spec, and it seems to me, there are
still two gotchas.

There does not appear to be a way to request the 32-bit windows
version of the JVM. If you only have 32-bit JNI, often it will attempt
to use the 64-bit version and fail.

There is no naming convention to keep track of whether a Windows DLL
(Dynamic Link Library) is 32-bit or 64-bit.

Do you agree?
 
R

Roedy Green

There is no naming convention to keep track of whether a Windows DLL
(Dynamic Link Library) is 32-bit or 64-bit.

The one tool you do have is the arch parameter which you set to x86
for 32-bit and amd64 for 64-bit.
 
A

Arne Vajhøj

I was reading over the latest spec, and it seems to me, there are
still two gotchas.

There does not appear to be a way to request the 32-bit windows
version of the JVM. If you only have 32-bit JNI, often it will attempt
to use the 64-bit version and fail.

\whereveryouinstalled64bitjava\bin\java
\whereveryouinstalled32bitjava\bin\java

should work fine.
There is no naming convention to keep track of whether a Windows DLL
(Dynamic Link Library) is 32-bit or 64-bit.

There are no naming convention, but the info is available in
the header.

Arne
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,781
Messages
2,569,615
Members
45,297
Latest member
EngineerD

Latest Threads

Top