This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal



Sep 13, 2011, 10:29 AM
122 Posts

Performance of Java Class vs Domino collections

  • Category: Managed Beans in NSF
  • Platform: All
  • Release: 8.5.2
  • Role: Developer
  • Tags: Java,Managed Beans,performance
  • Replies: 1
I've been using managed beans more and more recently for, amongst other things, ease of use. What are the performance implications of using a managed bean to create Java objects from collections, to manage CRUD processes? Are they much slower?
 
I assume that although the normal XPage lifecycle recycles the relevant NotesDocuments and does not write to disk / store in memory (because of serialization). But I guess that the values written to the XPage or bound via Expression Language do actually get written to disk / stored in memory, along with the UNID / note ID to allow the NotesDocument to be accessed again. So there is no memory impact of using a Java bean rather than Domino documents.
Oct 3, 2011, 8:36 PM
18 Posts
Re: Performance of Java Class vs Domino collections
Paul,
 
were just getting into this here, have you come to any conclusions ?

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal