Skip to main content

Posts

Showing posts from 2022

XPages and RichText (part I) - ACF

 This post is long overdue. I originally planned to write it to document the issues and solutions while working on the app, but as the problems kept appearing I wanted to make sure that I have all the answers. Now I know that I probably won't have them in the near future as I'm seeing new issues even after having the app in production for some time.  The project was about a webization of an existing app that served well in Notes client UI for many years. It's a classic support/helpdesk app that once used to be a great example of Notes flexibility and integration of mail functions with app code. After all the mail database was just another app using the same APIs (mostly). Unfortunately, this is not the case for XPages as iNotes or Verse has nothing in common with XPages, so the APIs are not battle-tested for all the scenarios. I remember doing a similar project during the early days of XPages and I must admit that it was more painful, but mostly due to a lack of community

HCL Domino 12.0.1 Comparison tool quick-fix for XSP

 I finally found an opportunity to try the new Database comparison tool that comes with 12.0.1 -  official documentation . Unfortunately, it did not work for me - all I got was a report for database.xml comparison and an error: Unable to output because no output object has been specified //DDDESIGNELEM.SAVE:1184-6 ... cc_body_xsp.xml ... My setup is: 12.0.1 - of course on Windows database configured to use WinMerge for comparison The error mentioned a Custom Control and the code contains a special if for *.xsp. After a bit of checking of the source code it seems that my problem can be fixed with a simple line that sets the output of the midDomp object - line 1117 on the screenshot. Now it outputs results for all elements and no errors anymore. Now I can continue to check the reports. Update: There is an official support article for this problem -  https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0096095  (but without a fix)