Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

AD1279 "Marty, You're Not Thinking Fourth Dimensionally" - Troubleshooting XPages


Published on

AD1279 best practices track session from IBM Connect 2016

Published in: Software
  • Be the first to comment

AD1279 "Marty, You're Not Thinking Fourth Dimensionally" - Troubleshooting XPages

  1. 1. "Marty, You're Just Not Thinking Fourth Dimensionally": Troubleshooting XPages Paul Withers / 2nd Feb 2016
  2. 2. Acknowledgements and Disclaimers Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. © Copyright IBM Corporation 2015. All rights reserved. • U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. • IBM, the IBM logo,, and IBM Domino are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at
  3. 3. About Me “My name is Darth Vader. I am an extraterrestrial from the planet Vulcan”
  4. 4. Why This Session? • XPages often doesn’t work “as expected”  Custom Control -> XPage -> Browser  Browser -> Server -> Browser  SSJS / CSJS  State management  Partial Refresh • Lots of StackOverflow questions  Which wouldn’t be referenced here unless many developers hit the same issues!
  5. 5. Agenda • Buzz-Quote Bingo! • Twin Pines Mall / Lone Pine Mall • Marty’s Family Photo • Marty McFly and the Tannens • Power of Love • Alternate 1985 • Indians! • It’s Erased!
  6. 6. BuzzQuote Bingo • • Enter Name and Email • Click when you hear • Shout if you win!
  7. 7. Twin Pines Mall / Lone Pine Mall
  8. 8. Some Questions • code-write-out-two-documents/32259533#32259533 • cancel-actions-scenario • documents-why-it-is-changing • is-created-everytime-a-document-is-saved
  9. 9. 1. Retrieve/Create Code in documentId • ALWAYS use ${…} when calculating properties like documentId • Otherwise calculated FOUR times on page load  If attached to a Panel, TWICE AFTER beforePageLoad  If attached to XPage, TWICE BEFORE beforePageLoad • Can’t use scoped variables set in beforePageLoad!  Always TWICE DURING render response
  10. 10. 1a. Timing of Initialisations • viewScoped variables can’t be set before PAGE LOAD  Controller frameworks put variable in requestScope and move to viewScope • data, dataContexts etc  attached to XPage / Custom Control - initialised alongside component  Attached to Panel – initialised during PAGE LOAD
  11. 11. 2. ignoreRequestParams • ALWAYS use ignoreRequestParams where appropriate  If no params, computed settings respected  If params passed, computed settings overwritten
  12. 12. 3. Submit Button Type • DON’T use save=“true” (“Submit” button type)  Use script, not simple actions • Greater control, less risk • You save only what should be saved • Preparing you for Java / beans / beyond • Form with single rich text field can cause problems even with script
  13. 13. Marty’s Family Photo
  14. 14. Some Questions • unresponsive-after-4-ajax-calls/33260337#33260337 • viewscoped-bean-again/32633453#32633453 • out-of-server-side-cache/32483154#32483154 • loosing-context-weird-behaviour • viewscoped-bean-again/32633453#32633453
  15. 15. 4. Keep Pages In Memory • XPages is stateful • Number of component trees restricted for performance • Dumped xsp.session.timeout minutes after browser closed  Browser doesn’t tell server session is no longer used!
  16. 16. 5. viewState=“nostate” • viewState=“nostate”  Don’t store a component tree for this page  Best practice for XAgents / REST services
  17. 17. 6. Explanation of “nostate” • DataView and nostate  Toggle expand/collapse is fine  Navigating to specific pages is fine  Next / Previous is relative to defaults  Toggle detail is relative to defaults • Unless detailsOnClient=“true” • Details pushed to browser along with rest of content • “Toggle” is client-side show/hide
  18. 18. Marty and the Tannens
  19. 19. Some Questions • a-repeat-control-from-the-outside-e-g-via- csjs/31575723#31575723 • xedataview/27982614#27982614 • from-repeatcontrol-in-nested-custom- controls/34158954#34158954 • control-and-manipulation-of-text-via- jouery/34653561#34653561
  20. 20. 7. Repeat Controls and Component Tree • Only one set of components in component tree • repeatControls=“true” changes behaviour  x many sets of components  Hard-wired to specific entries at page load  Pagers have no effect because of hard-wiring  Allows “loaded” computations within the repeat, e.g. id’s • Cannot compute repeatControls=“true” within compositeData
  21. 21. 8. Dynamic Content Control • Only components from current facet exist in component tree • Component tree dynamically updated • Better than showing / hiding via rendered property
  22. 22. 9. Custom Controls and Scope • Custom control is inserted into component tree • Variable names outside custom control available • As long as same variable used, no need to pass • Same rules as for any component  Is variable available by navigating upwards in tree?  Cannot retrieve variables from another branch • E.g. different repeat entry, repeat entry from outside repeat
  23. 23. Power of Love
  24. 24. ControllingViewHandler • Creates component tree for specific XPage • Runs before beforePageLoad event • super.createView() loads component tree • Also creates viewScope  Not available before call to super.createView()  Load variables to requestScope before super.createView()  Move to viewScope after super.createView()
  25. 25. ControllingViewHandler
  26. 26. PhaseListener • Handles XPages lifecycle • On page load, only RENDER RESPONSE triggered • Runs for every partial refresh  Ensure optimised  Ensure error handling • Crucial for identifying why partial refresh is not behaving “as expected”
  27. 27. PhaseListener
  28. 28. Some Questions • validation-errors-havent-been-displayed-to-the-user • action-will-not-fire-on-xpage/28340759#28340759 • do-partial-refresh-correctly • • and-components-with-events/
  29. 29. 10. Understanding Partial Refresh • Partial Refresh is SIX Phases
  30. 30. 10. Understanding Partial Refresh • 1. RESTORE VIEW  Get component tree again • 2. APPLY REQUEST VALUES  Pass String values from browser to executed component tree • 3. PROCESS VALIDATIONS  Run validators AND converters for executed component tree
  31. 31. 10. Understanding Partial Refresh • 4. UPDATE MODEL VALUES  Convert string values and update executed component tree • 5. INVOKE APPLICATION  Run application logic (SSJS / Java) • 6. RENDER RESPONSE  Update HTML for executed component tree and post refresh area
  32. 32. 11. Conditionally Hidden Save Button • Set rendered property on button  For best practice, use view.isRenderingPhase()  Ensure set to true for other phases or code will not run • Add partial refresh where appropriate  Ensure refresh area correct or button will not show  Ensure disableValidators=“true” or button will not hide again if invalid
  33. 33. 12. Reasons Code May Not Work! • CSJS returning false – check Firebug for POST event • Conversion error – 1,2,3,6 • Validation error – 1,2,3,6 • Exec id not including components being used by application logic • Exec id not including component triggering application logic • Event handler not rendered in phase 4 • Refresh area not including errors control
  34. 34. 13. Troubleshooting • Use PhaseListener • java.util.logging.ConsoleHandler.level manages console logging of server validation errors, since 8.5.3  In • ALWAYS including errors control in refresh area • Be conscious of rendered property
  35. 35. BONUS 1: Data View • dataCache=“id” setting available on View datasource • Better for performance, only caches id, not full ViewEntry (wrapped) • “var” not available during Apply Request Values  Compute value only in Render Response
  36. 36. BONUS 2 - Dialog • To refresh area, getComponent(“dialog1”).hide(“myRefreshArea”)  POST • Run SSJS • view.postScript - XSP.closeDialog  GET • Refresh myRefreshArea
  37. 37. Alternate 1985
  38. 38. 14. What Requires Restart Task HTTP? • Picked up immediately  Classic design elements  XPages*  Custom Controls*  Java classes* * Provided not in SCXD - some-learning-and-why-its-not-for-me/
  39. 39. 14. What Requires Restart Task HTTP? • Require “res task http”  JAR files • lotus-notes-database-not-being-picked-up-by-domino-server  SCXD  OSGi plugin* • in-xpages-libraries-changes-are-not-picked-up/33234041#33234041  Servlet / OSGi application* * Without JRebel
  40. 40. Indians!
  41. 41. Question • error-typeerror-resp-is-null-in-xpages/33210520#33210520
  42. 42. 15. “Resp is null” • Understand page load and dynamically  “resp is null” – options for picker are not available  Picker is client-side, but values are passed to renderer server- side
  43. 43. 16. SSJS in CSJS • SSJS in CSJS  Computed server-side as part of script renderer  Only re-computed by partial refresh • To access component values  Use dojo.byId or variants to access client-side element  Trigger partial refresh to update SSJS embedded into CSJS
  44. 44. It’s Erased!
  45. 45. Some Questions • storing-datetime-values-in-xpages • notserializableexception-on- datetime/34417335?noredirect=1#comment56612210_344173 35 • javascript-function/33168732#33168732
  46. 46. 17. Domino Objects in Scopes • Domino objects can’t be stored in scopes.  DateTimes are the most common culprit  Use .toJavaDate() to store Java Date • Similar issues with SSJS functions stored in variables
  47. 47. 18. Impact of Persistence Setting • For Domino objects in scopes, depending on persistence setting  Keep pages in memory – value just lost  Keep pages on disk – error thrown to server, redirect to error page (fails to display)  Keep current page in memory – value just lost, error 500 on navigating
  48. 48. Summary • Understand ignoreRequestParams • Avoid simple actions • Keep Pages in Memory – understand impacts • Use viewState=“nostate” • Understand detailsOnClient=“true” • Understand repeatControls=“true”
  49. 49. Summary • Understand scope and custom controls • Understand partial refresh is more than just “partial refresh” • Understand SSJS is computed and injected into CSJS • Use Firebug or comparable tool • Don’t store Domino objects in scopes • Understand impact of serialization
  50. 50. Thank You! Paul Withers Intec Systems Ltd IBM Champion OpenNTF Board Member @paulswithers
  51. 51. Thank you