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:
It seems like your error is not the same as mine....
- I finally hacked a solution by unloading the page each save. Since it would reliably work on the first save and only the first save, what I did set a sessionScope variable to what that save should have done, then load a different page entirely. That page would check the sessionScope variable to see if an action was required, and it if was required, it would perform that action using an AJAX call. If that AJAX call resulted in an error, it would then reload the previous page to show the user the error and allow resolution.
- It was an ugly reverse polish kludge, but it did provide a consistent, repeatable event sequence that WQS used to trivially accomplish, and XPages would not do under any circumstance.
- This was using 8.5.1 FP1 HF472, that exact version being the only one at deployment time that would actually keep attachments on resaving a page. I haven't had the opportunity to sample the runWithDocumentContext() call in 8.5.2 in this application, and I don't see how I ever will, so I can't say if that would make it work or not.
Feedback response number DGIE8EUM5P created by ~Holly Zekhipisonnivu on 03/11/2011
It seems like your error is not the same as mine....
Return to top
. . . . . . . . . . . . . . It seems like your error is not the... (~Zelda Ekresask... 11.Mar.11) 
