Notes/Domino 12.0.2 Fallout

Nov 17, 2022, 1:45 PM

Tags: designer java
  1. AbstractCompiledPage, Missing Plugins, and MANIFEST.MF in FP10 and V10
  2. Domino 11's Java Switch Fallout
  3. fontconfig, Java, and Domino 11
  4. Notes/Domino 12.0.2 Fallout

Notes and Domino 12.0.2 came out today. Generally, there are some neat features in development and on the server, but there are also a couple things you may run into depending on your workflow and installation type.

Update Site NSF

The update site NSF that ships with Domino uses SWT for some of its GUI elements when importing contents. This still works fine in the 32-bit client, but is broken in the 64-bit client. My guess on that front is that the 64-bit client doesn't come with a 64-bit native SWT JAR, probably because the SWT version used for this likely pre-dates x64's popularity on the desktop.

For now, the workaround is to use a 32-bit client if you're working with the Update Site NSF. Karsten said he's going to patch the OpenNTF version of the NSF to deal with this, so you can also wait for that one.

Domino Update Site Generator

I maintain the generate-domino-update-site Maven plugin that can be used to generate update sites for OSGi development against the Domino stack. These sites are replacements for the IBM Domino Update Site for Build Management, which was released for 9.0.1 and never updated since. Only HCL can make a new distributable version of that, so my tool lets you generate one for yourself from a Notes or Domino installation.

In 12.0.2, HCL shunted the NAPI implementation JAR down to jvm/lib/ext to support the shared JARs between XPages and agents feature. As a side effect, existing versions of my plugin would lack the NAPI classes.

Today, I released version 4.2.0, which fixes this and also contains improvements to let the plugin work on current Java versions and generate sites based on 12+ macOS clients.

Along these lines, I made Aha idea DDXP-I-352 a couple years ago to request that HCL provide such sites themselves or give OpenNTF permission to provide them, so I'd appreciate it if you voted for that.

The Target Platform Bug

This isn't a new thing, but it's worth mentioning here since it comes up frequently: the target platform bug from 9.0.1FP10 remains. As of earlier this year, defect article KB0086688 mentions this, though the status is "Deferred". If this afflicts you, it may help to bring it up with Support and reference that article.

Commenter Photo

Lars Berntrop-Bos - Nov 17, 2022, 2:32 PM

The platform bug never bit me before cuz of upgrades. Today I installed a fresh 64 DDE, and it's there... What is realy confusing is that when you first click target platform, the location of {eclipse_home} is listed as \framework\eclipse\ . Then when you edit the target platform (for safety I chose Add, and to copy the current settings) and Edit the default location, {eclipse_home} is shown to be "//workspace/.config/" very confusing, the starting forward slash. And the fact that {eclipse_home} != {eclipse_home}

Commenter Photo

Lars Berntrop-Bos - Nov 17, 2022, 2:52 PM

That entry got botched, I used angled brackets... the entries are C:/HCL/Notes/framework/eclipse/ and /C:/HCL/Notes/Data/workspace/.config/

Commenter Photo

Lars Berntrop-Bos - Nov 17, 2022, 2:57 PM

Oh I am daft. I mistook the configuration area for the resultant path...

Commenter Photo

don - Nov 18, 2022, 8:58 AM


New Comment