Notes V11.0.1 Designer中导入OpenNTF Domino API提示无法解析的问题

I’ve helped a lot of developers work through this exact issue—let’s break down the most likely causes and fixed steps you can take right away:

1. Missing Plugin Dependency in MANIFEST.MF #

This is the most common root cause. Even if you added the library in XSP Properties, your application’s MANIFEST.MF needs to explicitly declare it depends on the OpenNTF Domino API plugin for Java classes to resolve imports. Here’s how to fix it:

• Open your app’s MANIFEST.MF (located in the META-INF folder)
• Switch to the Dependencies tab
• Click Add... under "Required Plug-ins", search for org.openntf.domino, select it, and confirm
• Save the file, then clean your project via Project > Clean...

The MANIFEST error you’re seeing is directly tied to this missing dependency—Designer can’t find the API because the application isn’t telling it to look for the plugin.

2. XSP Library Not Fully Enabled or Synced #

Double-check that the OpenNTF library is properly enabled and that Designer has picked up the change:

• Right-click your app in Package Explorer > Application Properties > XSP Properties
• Go to the Libraries tab, confirm OpenNTF Domino API (sometimes labeled org.openntf.domino.xsp.library) is checked
• Close and re-open Designer, or right-click the project > Refresh to force a sync

3. Incompatible or Incomplete Plugin Installation #

Notes Designer 11.0.1 requires an API version compatible with Domino 11—newer builds targeting Domino 12+ won’t work correctly.

• Verify the API version you downloaded supports Domino 11
• Reinstall the plugin: Go to File > Application > Install, select your configured update site, re-install all OpenNTF Domino API plugins, then restart Designer
• Confirm installation success: Go to Help > About IBM Domino Designer > Installation Details, search for org.openntf.domino to ensure all related plugins are listed

4. Java Class in the Wrong Source Directory #

Designer only recognizes Java classes in specific folders for XPages apps. If your Test class isn’t in WebContent/WEB-INF/src, it won’t have access to API dependencies:

• Move your test.Test class to WebContent/WEB-INF/src/test/ (create the test subfolder if needed)
• If you need a custom source folder, add it to the build path: Right-click project > Properties > Java Build Path > Source > Add Folder and select your folder

5. Missing Library in Java Build Path #

Sometimes the build path doesn’t auto-include the OpenNTF API, even if the plugin is installed:

• Right-click your project > Properties > Java Build Path > Libraries
• If OpenNTF Domino API isn’t listed, click Add Library > OpenNTF Domino API > Next > Finish
• Apply changes and clean the project

After working through these steps, your import error should clear up, and the MANIFEST.MF issues should disappear too.

内容的提问来源于stack exchange，提问作者Tom Van Aken