add FacesMessage to FacesContext, either for the entire page with

 

if (doc.isInConflictMode()){

    FacesMessage m2 = new FacesMessage("doc is edited by someone else");

    FacesContext.getCurrentInstance().addMessage(null, m2);

 }

 

or to individual UIComponent
if (doc.isInConflictMode()){
                com.getClientId(FacesContext.getCurrentInstance()), m2);

}

put "display error" or "display errors" control on designer, then it will display those error messages. 

 

 Unfortunately this does not cause the onError() call back to be executed, onStart executes correctly before the post to the server, and then onComplete executes once the response is received. BTW, there is a helper function @ErrorMessage that encapsulates much of the work related to the facesContext.addMessage stuff.

 

I was able to get the error message to show in an xp:messages control, if it was within the context being refreshed (this action only does a partial refresh). Ideally I would have a single error control that displays a dialog when there is something to report, and I could cascade the partial refresh in my onError callback.

 

Rich 

 

 

To put FacesMessage in FacesContext does not mean it is Error, its just a message, therefore it can not be caught in onError()
If need to cast the facesMessages as error, then make a custom validator, then throw an exception wrapping the FacesMessage, then onError() should be able to catch it? (I never used onError() before, did not know that script there will be invoked once there is serverSide error)throw new javax.faces.validator.ValidatorException(
                    new javax.faces.application.FacesMessage("doc is inConflictMode");

 

If there is just a dialog rendering FacesMessages (not Error), why not just render the dialog with serverSide script?

var dialogA = getComponent('dialog1')
dialogA.show()

 

and inside of this dialog you can access all the FacesMessage through FacesContext

 Thank you again for your input. The facesMessage solves part of the problem (what message to display), but as I am using partial refresh, and the error dialog will be outside the context of the partial refresh, even if I do show() the dialog on the server side, it won't be updated on the client side until I do a XSP.partialRefreshGet() on the dialog's container on the client. For this I need the onError()  function to trigger.

 

'throw"ing an exception does not trigger onError(). In fact it just returns the server generated error page for unhandled exceptions. 

I did not know that onError you mentioned was associated with xhrpost/xhrget,

was thinking that validation+error management should be handled together at either server side or client side. to perform validation and error management at different sides is new stuff for me as well........always believe that code at client side runs at render response phase, and facesmessage is requestScope, will vanish after invoke application phrase,

 

just to put some final effort here eventhough I am aware that I am not at that level to answer this question

 

 

to synchronize client/server side script as in http://nodejs.org/, use Remote Services from extension library...then client side script will catch real object from server side, call back function not exists only in onError but also in that editor that we normally use....

 Just to answer my own question, now that I have found it, you can trigger the onError() client script for a partial refresh if the status of the response is an error code like 500:

 

 facesContext.getExternalContext().getResponse().setStatus(500);

 

Rich