Skip to main content

EXTJS4 - How to handle JavaScript Errors, server exceptions globally

One way to catch JavaScript Errors with window.onerror: 

Fiddle: https://jsfiddle.net/prajavk/d0ywj710/

Handle Ext errors and Javascript errors Globally as below,

Possible cases to handle:
1. success - Ext handled.
2. failure, due to communication problem - Ext handled.
3. failure, due to server-side exception – developer have to handle response failures...

Fiddle: https://fiddle.sencha.com/fiddle/1gsq

Solution1:
Write below method in your Application controller.

//Ajax Response Error Handler
Ext.Ajax.on('requestexception', function(conn, response, options, eOpts) {
                         var error = response.status + ' - ' + response.statusText;
                         console.log('Ajax Request Exception! '+error);
                         if (response.status != 200) {
var errorData = Ext.JSON.decode(response.responseText);  console.log('ajax req error:'+errorData.message);
                      console.log('Ajax request Error', response.status);
Ext.Error.raise(error);
                           }
                  });

Solution2:
when an exception on server occurs, we can send a 500 response header with the reason returned as HTML in the content.

store.on('loadexception',
function(a,conn,resp) {
if (resp.status == '304') {
    Ext.Msg.alert('Content has not changed');
}else if(resp.status == '200') {
return; //Do nothing
}else if (resp.status == '401') {
       Ext.Msg.alert('Authentication required - You need to Login');
}else if (resp.status == '302') {
errorDialog.body.update('Session Has Expired');
errorDialog.show();
}else if(resp.status == '500') {
errorDialog.body.update(resp.responseText);
errorDialog.show();
}else{
errorDialog.body.update('An uncaught exception has occured');
errorDialog.show();
}
}

Solution3:

When sending Ajax or REST requests, a proxy of ExtJs 4 typically expects a response with the following parameters: datasuccess and message. The message parameter is optional, but it may come in handy when you want to show the request results to the user.

function requestMessageProcessor(proxy, response) {
         if (response && proxy) {                   
                 try {                                              
                          var responseData = proxy.reader.getResponseData(response);
                         
                          if (responseData.message) {
                                   var messageDescription = 'Information'; // title of the alert box
                                   var messageIcon = Ext.MessageBox.INFO;
                                  
                                   if (!responseData.success)
                                   {
                                            var messageDescription = 'Error';
                                            var messageIcon = Ext.MessageBox.ERROR;
                                   }
                                  
                                   Ext.MessageBox.show({
                                            title: messageDescription,
                                            msg: responseData.message,
                                            buttons: Ext.MessageBox.OK,
                                            icon: messageIcon
                                   });
                          }
                 }
                 catch(err) {
                          // Malformed response most likely
                          console.log(err);
                 }
         }
}
And here’s the part which should reside in proxy:

proxy: {
 ...
 listeners: { 
  exception: function(proxy, response, options) {
   requestMessageProcessor(proxy, response);
  }
 },
 afterRequest: function(request, success) {
  requestMessageProcessor(request.scope, request.operation.response);
 }
}
Handle Generic error handler for Ajax failures :
Ext.data.Connection.prototype._handleFailure = Ext.data.Connection.prototype.handleFailure;
Ext.data.Connection.prototype.handleFailure = function(response, e) {
 var errorText = Ext.DomQuery.selectValue("Reason/Text", response.responseXML, "Unknown Error");
 Ext.Msg.alert('Error', errorText);
 
 Ext.data.Connection.prototype._handleFailure.call(this, response, e);
};

Comments

Post a Comment

Popular posts from this blog

ExtJS - Grid panel features

What can we do with ExtJS GridPanel? I have to develop a lot of applications in my web app and I see that grid component of ExtJS may fit in. However, I am not aware of what all things I can do with the - off the shelf available framework pieces - available plug-ins in the marketplace and - custom development through my own developers This is a typical question that we hear from the business users who wants to design an application by keeping the framework’s capability in perspective. In this article I have tried to put the list of stuff you can do with grid and hopefully that shall enable you to take advantage of the beauty of ExtJS. Pre-requisites This article assumes that you are familiar with basics of ExtJS What are the available options? In this section I will be taking you through some of the commonly seen usage of ExtJS grid panel. While covering all the capabilities of grid may not be possible, I am sure it will be helpful for the business users who want to

Ext4 Apply Store Filtering

In extjs4.1: There are many way for store filtering . Some of code i give here Filtering by single field: store . filter ( 'eyeColor' , 'Brown' );   Alternatively, if filters are configured with an  id , then existing filters store may be  replaced by new filters having the same  id . Filtering by single field: store . filter ( "email" , /\.com$/ );   Using multiple filters: store . filter ([ { property : "email" , value : /\.com$/ }, { filterFn : function ( item ) { return item . get ( "age" ) > 10 ; }} ]);   Using  Ext.util.Filter  instances instead of config objects (note that we need to specify the root config option in this case): store . filter ([ Ext . create ( ' Ext.util.Filter ' , {   property : "email" , value : /\.com$/ , root : 'data' }),   Ext . create ( ' Ext.util.Filter ' , {   filterFn : function ( item ) {   return item . get ( &

EXT JS 4: EMPTY VALUE IN A COMBOBOX

EXT JS 4: EMPTY VALUE IN A COMBOBOX Often, in an Ext JS combobox, it is difficult to go back to an empty value once you have selected an item, particularly if “forceSelection” is set to true.  Here is my roundup of alternative solutions found from around the web… 1. Override beforeBlur The solution from   http://www.sencha.com/forum/showthread.php?182119-How-To-Re-Empty-ComboBox-when-forceSelection-is-Set-To-TRUE  overrides beforeBlur on the combbox to clear out lastSelection.  Here is a copy of the override from the thread: 1 2 3 4 5 6 7 8 9 10 11 12 13 Ext.create( 'Ext.form.field.ComboBox' , {      ...      allowBlank: true ,      forceSelection: true ,      beforeBlur: function (){          var value = this .getRawValue();          if (value == '' ){              this .lastSelection = [];          }          this .doQueryTask.cancel();         this .assertValue();      } }); Or to apply the o