|
 Andre Iltchenko, OptimalJ Development Lead
With a more prominent position of feature-rich, UI designer-based web front ends in OptimalJ 4.2, it is becoming important that the increase in usability coincides with the overall effectiveness of the entire J2EE application when it comes to inter-tier communication between presentation and business logic code. In OptimalJ 4.2 we added an important enhancement to Business Façade components that avoids re-retrievals of large data sets when the re-retrieval is not strictly necessary. We call this feature ‘store-on-store’ and I have documented it in the new version of the ‘Using DataObjects and UpdateObjects’ white paper that you can find on JavaCentral. If your presentation code uses editable grids with master-detail functionality, you can consider improving your application’s performance by following this tip:
- Navigate to the controller code of your WEBComponent’s store action.
- Search for a ‘store-on-store limitation’ comment. What you’ll find will look like this:
if (actionForward==null) {
// Store was successful. Make sure the business facade performs a new retrieval.
// This is needed because of a current store-on-store limitation.
request.removeAttribute(AlturaConstants.KEY_BACKWARD);
} else {
request.setAttribute(AlturaConstants.KEY_BACKWARD, AlturaConstants.ANYVALUE);
}
// Additional code here
Add the following statement to the Additional code here freeblock:
request.setAttribute(AlturaConstants.KEY_BACKWARD, AlturaConstants.ANYVALUE);
This statement will avoid re-retrieving master records and enable you to benefit from the new ‘store-on-store’ support. |
