• HCL 11.0.1 Import of Xpage Debug class file no longer resolves

    By Richard Schumann 4 years ago

    Mark,
    Used your toolbar all the time with great success on Domino 9.0.1FP9 and earlier. I recently upgraded our servers and clients to HCL 11.0.1 and your toolbar class no longer solves. I checked my designer client's Preferences –> Plug-in Development\Target Platform to ensure I have a 'Target definition' selected (Active) - and I do. It's pointing to –> ${eclipse_home} - C:\Program Files (x86)\Notes\framework\rcp\eclipse\ 1513 plug-ins available. - but not your's. I bring your 4.0.1 version in through a 'Site Update' nsf and it says it's up to date. Any guidance/ideas as to where else to look?

    • By Mark Leusink 4 years ago

      Using it in 11.0.1 myself. Don't have any issues.

      One thing you might want to check is to see if the plugins are enabled. I've seen sometimes that after a client upgrade, the plugins are disabled. See File > Application > Application Management > 2nd category (workspace\applications\eclipse).

      • By Richard Schumann 4 years ago

        Thanks Mark for your prompt reply and suggestion. I confirmed that the 'workspace\applications\eclipse category was enabled - it was. I then opened a ticket with HCL Tech Support and provided them with the same zip file I downloaded from OpenNTF for your tool bar. They confirmed that they were able to successfully install the XPages Tool Bar in their Release 9.0.1FP9 Designer client (like I had done) - BUT - it failed with the same error message of no features found in the update site (like I'm seeing) when they tried installing in 11.0.1. They pulled down the subversion plugin from OpenNTF and successfully installed it on their 11.0.1 client (as I did too). For whatever reason, 11.0.1 Designer client on my in-place update from 9,.0.1FP9 and HCL's 11.0.1 Designer client (also an in-place upgrade from 9.0.1FP) doesn't like it. I've opened the site.xml to see if there was anything that I could see that didn't 'look right' (mind you, I don't really know what to look for) but I was looking for anything that looked out of the ordinary. I'm now wondering if there could be a dependency in the Feature's JAR that Designer doesn't like.

      • By Richard Schumann 4 years ago

        Mark,
        With a little more research, I came across this Blog posting related to uninstalling plug-ins. I followed the steps and attempted the re-install of your toolbar - SUCCESS!. I believe the root cause was I never removed the reference of the toolbar (before attempting to re-install) from the –> Platform.xml located in the workspace\config\org.eclipse.update\ directory.

        I had deleted the Features and the Plugins JAR files previously in an attempt to retry the installation, but never updated the Platform.xml and cleaned that file of any artifacts.

        Wanted to let you know. Also, I notified HCL Support to provide them feedback as well.

      • By Richard Schumann 4 years ago

        One other item that mattered… After successfully getting the XPages toolbar Plugin to install successfully, when I opened my JAVA Class file that imported the toolbar, the Import class file directive was still not resolving.

        It turned out that the –> 'org.openntf.xsp.debugtoolbar_1.1.0.201403092102.jar' file was NOT appearing in the JAVA Build Path as shown in the 'Properties/Java Build Path' UI in the Domino Designer Package Explorer when selecting my application NSF file.

        By searching for the Xpages debug JAR file name (beginning the search in the root of the \Notes directory), I eventually found the Xpage Toolbar JAR file's location, noted the full path to the JAR, then went back to the 'Java Build Path' UI and clicked on the the 'Add External JARS…' button within the JAVA Build Path UI.

        I navigated to the JAR, selected it, clicked the 'Apply' button and closed the Java Build Path UI dialog and waited a couple of seconds.

        The Designer client immediately updated and resolved my error appearing on my Import. It could now resolve the XPage Toolbar class.

        This detail is for those who might suffer the same pain that I went through to resolve this.

        I'm still not sure what happened during our in-place upgrade from Notes 9.0.1FP9 to Notes 11.0.1, but it clobbered this class file along with mucking up my Designer 'Preferences/Plug-in Development/Target Platform/Target definition choices.

        The XPages Toolbar Plug-in has given me years of non-stop service up through Notes 9.0.1FP9. Only when we performed an in-place upgrade to 11.0.1, did it fail.

        Thank you Mark for a great tool and continued support!