Results 1 to 7 of 7

Thread: Ext.data.proxyAjax: An autogenerated constructor with failures Sencha Architect 2.2

    This duplicates another bug already reported in our system: DSGNR-3842
  1. #1
    Sencha User
    Join Date
    Dec 2011
    Location
    Mxico
    Posts
    11
    Vote Rating
    0
      0  

    Default Ext.data.proxyAjax: An autogenerated constructor with failures Sencha Architect 2.2

    REQUIRED INFORMATION Architect Build tested:
    • Build: 971

    Project Type:
    • Touch 2.x

    Description:
    • When I create a listener to manage exceptions in an Ext.data.proxyAjax, Sencha Architect generates a constructor with failures.

    Steps to reproduce the problem:
    • Add a Store (JsonP or Json)
    • Set the model
    • Add and Event Binding (exception) to the Ajax Proxy
    • Autogenerated constructor appears in the Store

    The result that was expected:
    • No constructor or a complete autogenerated constructor

    The result that occurs instead:
    • Autogenerated constructor with failures:
      constructor: function() {
      var me = this;
      me.callParent(arguments);
      me.getProxy().on([
      },

    HELPFUL INFORMATION Screenshot, Project, or Video:

    Possible fix:
    • not provided

    Operating System:
    • Win7 Pro

  2. #2
    Sencha User Phil.Strong's Avatar
    Join Date
    Mar 2007
    Location
    Olney, MD
    Posts
    1,953
    Vote Rating
    65
      0  

    Default

    Thanks for the report! I have opened a bug in our bug tracker.

  3. #3
    Sencha User joostvanhassel's Avatar
    Join Date
    Jan 2012
    Location
    Rotterdam, The Netherlands
    Posts
    102
    Vote Rating
    1
      0  

    Default

    same bug as filed under DSGNR-3755, a temporary workaround can be found in this thread:
    http://www.sencha.com/forum/showthre...on-event-error

    Would love to see this fixed though, it's a lot of work to maintain projects that use a lot of exception handlers.

  4. #4
    Sencha User
    Join Date
    Dec 2011
    Location
    Mxico
    Posts
    11
    Vote Rating
    0
      0  

    Default

    Joostvanhassel: Thanks for the temporary workaround.
    I hope this problem can be fixed soon.

  5. #5
    Sencha User joostvanhassel's Avatar
    Join Date
    Jan 2012
    Location
    Rotterdam, The Netherlands
    Posts
    102
    Vote Rating
    1
      0  

    Question

    Any news on this issue? It has been first reported a few weeks back and I can't much longer hold off my clients who want updates to their apps (and I'm not looking forward to replacing all exception handlers with the workaround).

  6. #6
    Sencha User joostvanhassel's Avatar
    Join Date
    Jan 2012
    Location
    Rotterdam, The Netherlands
    Posts
    102
    Vote Rating
    1
      0  

    Default

    Unfortunately, this hasn't been solved in 2.2.2 b991. Maybe it's a good idea to add this to the 'known bugs in Architect 2.2.2' thread at http://www.sencha.com/forum/showthre...rchitect-2.2.2 ?

  7. #7
    Sencha User
    Join Date
    Sep 2012
    Posts
    2
    Vote Rating
    0
      0  

    Default

    Dear joostvanhassel or anybody else watching this bug: I followed the workaround but I didn't have any success in cathing the browser exceptions like 500 or 404 or anything else. I am new to sencha and I don't know what I am doing wrong and I can't catch any errors. Is there any simple working example? Maybe there are some configs that I have not done right?

Tags for this Thread

Posting Permissions

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