Success! Looks like we've fixed this one. According to our records the fix was applied for DSGNR-3543 in a recent build.
  1. #1
    Ext JS Premium Member
    Join Date
    Dec 2011
    Posts
    231
    Vote Rating
    2
    nicolabaldo is on a distinguished road

      0  

    Default sencha property must begin with a letter

    sencha property must begin with a letter


    I use Architect 2.2 and ExtJS 4.2
    I've got these errors but In my application i didn't found wrong userClassName...
    Any solution?

    Immagine.png

  2. #2
    Sencha - Architect Dev Team aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,358
    Vote Rating
    127
    aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold

      0  

    Default


    Could you send a copy of your project archive over for us to take a look at? You can send privately at architect.feedback at sencha.com.
    Aaron Conran
    @aconran
    Sencha Architect Development Team

  3. #3
    Ext JS Premium Member
    Join Date
    Dec 2011
    Posts
    231
    Vote Rating
    2
    nicolabaldo is on a distinguished road

      0  

    Default


    Ok thanks a lot!

  4. #4
    Sencha - Architect Dev Team jjohnston's Avatar
    Join Date
    Sep 2010
    Posts
    567
    Vote Rating
    20
    jjohnston will become famous soon enough jjohnston will become famous soon enough

      0  

    Default


    Thanks for sending your project. It seems that somehow your project has several proxy and reader instances whose internal metadata has a userClassName containing spaces. This might have been a leftover from a bug in a previous version of Architect, which our new validation doesn't like.

    I'm going to open a bug ticket in our system to handle this situation in a less spammy way. This isn't an error condition and shouldn't affect you other than being annoying, but we don't want to be annoying.

    In the meantime, you can do the following to remove the warnings from your project:
    1. Quit Architect
    2. Make a backup of your project files
    3. Search the files in your project's "metadata" directory for the following strings (there will be about 50 occurrences):
      1. "designer|userClassName": "Ajax Proxy
      2. "designer|userClassName": "Json Reader
    4. Modify those values to remove the space, and save the files
    5. Reopen the project in Architect
    This should allow your project to open without warnings. Let us know if you continue to see this issue.
    Jason Johnston
    @lojjic
    Sencha Architect Development Team

  5. #5
    Ext JS Premium Member
    Join Date
    Dec 2011
    Posts
    231
    Vote Rating
    2
    nicolabaldo is on a distinguished road

      0  

    Default


    Thanks for reply me.
    I followed your instructions but I still have the problem.
    I removed the spaces in this way:

    "designer|userClassName":"Ajax Proxy
    "designer|userClassName":"Json Reader

    Is it correct??

  6. #6
    Sencha - Architect Dev Team jjohnston's Avatar
    Join Date
    Sep 2010
    Posts
    567
    Vote Rating
    20
    jjohnston will become famous soon enough jjohnston will become famous soon enough

      0  

    Default


    No, I meant in the value.

    "designer|userClassName": "AjaxProxy
    Jason Johnston
    @lojjic
    Sencha Architect Development Team

  7. #7
    Ext JS Premium Member
    Join Date
    Dec 2011
    Posts
    231
    Vote Rating
    2
    nicolabaldo is on a distinguished road

      0  

    Default


    Sorry... It works!
    Thanks a lot.

  8. #8
    Ext JS Premium Member
    Join Date
    May 2011
    Posts
    55
    Vote Rating
    1
    h.koch is on a distinguished road

      0  

    Default


    Hello,

    I had the same situation with a migrated project of Ext Designer 1.2.3 (which had to be downgraded to 1.2.2 manually in the project file), imported in SA 2.1, then used in SA 2.2. All userClassNames were built with the schema "Json[whitespace]reader" etc., so it's a topic which would be only resolvable by advanced users who can edit the project metadata directory manually. A better approach would be to change the imported userClassNames without whitespaces.

    Harald