Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: JNLP gotchas Date: Thu, 22 Dec 2011 06:43:15 -0800 Organization: Canadian Mind Products Lines: 17 Message-ID: Reply-To: Roedy Green NNTP-Posting-Host: Z2l1DcCELS0rATq8NqV4Sw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:10948 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? -- Roedy Green Canadian Mind Products http://mindprod.com If you can't remember the name of some method, consider changing it to something you can remember.