Windows Installers and 32/64 bit

[Rhys Smith]

On 25 Sep 2014, at 10:50, Rod Widdowson <rdw at steadingsoftware.com<mailto:rdw at steadingsoftware.com>> wrote:


Thoughts?

For Raptor, I ended up with a single MSI for 32 and 64 bit, and to figure out JAVA_HOME I’ve ended up looking in the registry and figuring it out rather that using the system provided one, like so:

<Property Id='JAVA_VERSION'>
<RegistrySearch Id='JavaVersionSearch' Root='HKLM' Key='SOFTWARE\JavaSoft\Java Runtime Environment' Name='CurrentVersion' Type='raw' />
</Property>
<Property Id='JAVA_HOME'>
<RegistrySearch Id='JavaHomeSearch' Root='HKLM' Key='SOFTWARE\JavaSoft\Java Runtime Environment\[JAVA_VERSION]' Name='JavaHome' Type='raw' />
</Property>

Seems to work for me when I’ve tested on 32 and 64 bit, but I’d need to to a lot more testing (with 32/64 bit JREs on 64 bit windows) to be comfortable that that was a solution that actually worked in all scenarios. I hacked that together as a temporary thing, and so far haven’t had any reports about it not working for anyone, so haven’t had to fix a better solution yet. But whether because it works, or because none has yet deployed it in a context where it won’t work, I don’t know.

Possibly the Wow6432Node might be a better location to use to make it a bit more resilient.

Of course, if you want a system provided JAVA_HOME then that’s obviously the wrong approach to take!

Rhys.
--
Dr Rhys Smith
Identity, Access, and Middleware Specialist
Cardiff University & Janet - the UK's research and education network

email: smith at cardiff.ac.uk<mailto:smith at cardiff.ac.uk> / rhys.smith at ja.net<mailto:rhys.smith at ja.net>
GPG: 0x4638C985
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20140925/cd2234a7/attachment-0001.html