#dominoforever | Product Ideas Portal

 

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Allow in-code trap/handling of CLFAD* errors for XPages Partial Refresh and similar situations, not via xsp.properties

v10 XPages' Partial Refresh runtime now throws CLFAD* errors which did not occur in earlier releases. IBM has provided a means to ignore based on xsp.properties setting. However, to merely ignore globally via the properties override, side steps the reason for IBM exposing the error.  As a software developer, we would prefer to see a means to trap for these specific errors when expected, such as when we need to do a Partial Refresh on a null tag but have the error issued for other situations which were caused for unknown/unexpected events.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • May 30 2019
  • Needs review
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    22 Oct, 2019 09:04pm

    We were told the CLDAD errors are being issued due to security concerns, and there isn't a plan to allow trapping on an individual basis.  So you end up with either generating the error or bulk ignore.

    The bulk ignore merely perpetuates the security issue. If the application developer knows when to expect the situation and can implement a trap for those known routines, we can mitigate the security issue for all the unexpected situations.

    Due to limitations in how Xpages has been structured, there are situations when a partial refresh is needed without a specified tag. 

    While thankful there is an override to grandfather old behavior, it does not allow for improved security handling for an application in this regard.