Results 1 to 2 of 2

Thread: jsonp proxy bug on destroy!

Hybrid View

Previous Post Previous Post   Next Post Next Post
    Success! Looks like we've fixed this one. According to our records the fix was applied for EXTJS-6663 in a recent build.
  1. #1
    Sencha User
    Join Date
    Apr 2010
    Posts
    4
    Vote Rating
    0
      0  

    Default jsonp proxy bug on destroy!

    proxy.jsonp overrided the destroy method irrately:

    //inherit docs
    destroy
    :function()
    {
    this.abort();
    this
    .callParent(arguments);
    },
    this method will be called by 'me.proxy.batch[operation.action]' in 'Batch' object:

    runOneOperation: function(....
    ....
    operation.setStarted();

    me.proxy[operation.action](operation, onProxyReturn, me);
    }
    when the action is 'destroy', the 'BUG' will be occuring..., the calling will be abort!

    why override this method?

  2. #2
    Sencha - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    39,413
    Vote Rating
    1269
      0  

    Default

    I am thinking whomever worked on this was trying to abort any requests open by that proxy when the store and proxy are destroyed.

    Thanks for the report.
    Mitchell Simoens @LikelyMitch
    Sencha Inc, Senior Software Engineer
    ________________
    Learn BBCode and use it!

    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •