Domino 10 upgrade and XPages POI libraries error - apache-poi

I upgraded my Domino 9.0.1 to 10 after my databases (used POI import/Export) give POI libraries errors. I'm using Eclipse Update Site database for loading POI. I tested po
cant load POI libraries:
import java lib are not load
Domino console POI services status:

Your Target Platform setting in Designer may have been messed up by the V10 upgrade - it's a very-common issue with 9.0.1FP10 and V10. "Fix #1" here may be what you need: https://frostillic.us/blog/posts/058650E080E352178525832B00519D2C

Welcome to Stack Overflow. The first image shows build errors in Domino Designer. Did you upgrade your Designer to 10 too? If so, then you should reinstall the POI libraries in Designer from your update site.

Related

How do you upgrade Apache POI in Lucee 5.3.10.97 from 2.5.1 to 3.17?

I manage a Windows Server 2016 that has Lucee 5.3.10.97 with IIS, and bundled within Lucee is Apache POI 2.5.1. I have requirements to update this to at least Apache POI 3.17. Can I just drop a newer JAR of poi 3.17 over the 2.5.1 bundled in Lucee, or am I unable to do so because this jar is referenced somewhere?
As far as I understand it, Lucee doesn't include POI in its core any longer. The older version you are seeing is probably the one bundled with the Tika library.
The simplest way of using a more recent version of POI is to install the POI Lucee Extension which has POI 5.0.0. Look for it in the Extension > Applications section of the Lucee server admin UI (click the "Pre Releases" button if you don't see it). Or you can download the .lex file from https://download.lucee.org/ (scroll down for extensions) and drop it in your lucee-server/deploy folder.
As Lucee uses OSGi, the different versions won't interfere with each other.

After the Notes 11 upgrade i can not debug databases give apache poi libraries error

I'm using Apache poi 1.3.1 library in many database for xpages export/import actions. when I upgrade notes 10 to 11 and notes 11 give me a library errors.
Since I see that the library is installed but the compiler doesn't resolve the bundle, I expect that it's the Target Platform bug described here, with the workaround being to add the data/workspace/applications/eclipse directory to your TP: https://frostillic.us/blog/posts/2018/10/19/058650e080e352178525832b00519d2c . That recurs frequently during any upgrade involving 9.0.1FP10 through to current versions.

OpenNTF domino api not available for selection in designer

Domino API is not available to be checked in the xpage properties of my databases
I am trying to use domino api to help with some of the recycling problems that we've had with xpages. I've spent days watching the various videos that have been made over the years. I have tried to get this working in both my work environment (9.0.1) and my home dev server (10). In both cases the result is the same - I have installed the extension library and domino api on the server via updatesite and it seems to be fine there. In my designer I can see that both extension library and domino api are installed (by looking in Application Management) but only extension library is available in the databases.
Need to be able to select the org.opentf library in the datbases.
We've tried to clarify in the release page. 4.2.x is for 9.0.1 FP9. Since 10 we've moved to updated version numbering, although Tycho doesn't make it straightforward. So 10.0.0 covers V10. The version in Notes needs to match the Notes version, not the Domino version. It's referenced for compiling only, not pulled into the design. So on the server, the version needs to match the Domino server version. So you may have different versions if DDE and the server are different. That's to do with how OSGi works.

ibm.commons error after upgrade to Notes 9

I have an XPage app that has been working fine. I upgraded my client from 8.5.3 FP6 to 9.0.1 FP1, built the database and now receive the following error on the 8.5.3 server console:
HTTP JVM: java.lang.NoSuchMethodError: com/ibm/commons/util/io/json/JsonJavaObject.put(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/Object;
If I rebuild from an 8.5.3 client it runs fine again.
Any suggestions on what I need to do differently using the 9.0.1 Designer client ?
Thanks...
Have you tried compiling the application to run as an earlier version? There is an option in xsp properties to compile with an earlier version.
If you can compile on your Designer, it's a specific problem for your server. Check plugins and additional Java libraries on your server. There might be a conflict.
On your server, extension library is installed? If yes, which version? (ExtLib for 8.5.3 contains IBM Commons jar, so it may be a reason of conflict), OpenNTF Domino API? Social Enabler?
You might also test with a clean Domino installation to determine the root cause.

How is the correct procedure for uninstalling or upgrading Extension Library on Domino server?

I have Extension Library instaled on Domino server 9.0.1 using update site database. Now when new version of ExtLib is released, how is the proper procedure to update to this new version? I removed documents from update site (for existing ExtLib) and imported new ExLib version but now it seems that I have both versions on Domino when I use tell http osgi ss com.ibm.xsp.extlib
Did you restart HTTP using restart task http?
FYI: XPages uses the latest version of loaded libraries.
You don't need to delete the old content from the update site, although that is a valid approach as well.
You can just disable the old content in the update site. In the image below, I have a 9.0.1 server, with 901_v00_03 of ExtLib & 901_v00_04 of ExtLib installed via update site. However, I have disabled the 901_v00_03 features in the update site (and restarted my server), and they do not show up in the console output.
The 901_v00_04 plugins show up in the console output, as do the core versions that came installed with 901 (901_v00_00_20131004-1200). The latest version of the plugins are the ones that will be used.i.e. 901_v00_04 ExtLib versions.
If you have removed the content from the active updateSite completely, and restarted the server, they should not appear in the console output at all. So we may need more info to find out what went wrong, if that is the case.

Resources