Build error: "failed to find meta class definition for name reader.null"

[jweber]

I'm getting a new build error with Sencha Cmd v3.0.0.190 and ST 2.1rc1.

[INFO ]		Compiling app.js and dependencies
[INFO ]		Processing classPath entry : /project/sencha-compile-temp-dir
[INFO ]		Processing classPath entry : /project/touch/src
[INFO ]		Processing classPath entry : /project/app.js
[INFO ]		Processing classPath entry : /project/MyAppDir
[INFO ]		Processing classPath entry : /project/lib
[WARN ]		[ [1000] : Yui Compressor Warning <> Trailing comma is not legal in an ECMA-262 object initializer => }, function() { ] :: ( /project/touch/src/app/Controller.js => 625 : 1 )
[ERROR]		def was null
[ERROR]		failed to find meta class definition for name reader.null
[ERROR]		Exception running app build : JavaException: com.sencha.exceptions.BasicException: null
[ERROR]		javax.script.ScriptException: sun.org.mozilla.javascript.internal.JavaScriptException: [object Error] (<Unknown source>#709) in <Unknown source> at line number 709

I have a custom application directory (MyAppDir), and another directory (lib) for other classes. I edited .sencha/app/sencha.cfg as follows:

app.classpath=${app.dir}/app.js,${app.dir}/MyAppDir,${app.dir}/lib

How would I go about debugging this? I'm not sure where it's trying to look up "reader.null".

[mitchellsimoens]

Are you requiring the reader you are trying to use in your store/model?

[jweber]

Yep, the required files were included. I think I've found the problem, and I'm not sure if it's a ST bug, but it's definitely a change. I have a custom proxy, which uses a custom reader. In my store, I use this custom proxy, and configure some values for the custom reader:

Ext.define('MyProxy', {
	extend: 'Ext.data.proxy.Ajax',
	requires: ['MyReader'],
	alias: 'proxy.myproxy',
	config: {
		reader: {
			type: 'myreader'
		}
	}
});

Ext.define('MyStore', {
	extend: 'Ext.data.Store',
	requires: ['MyProxy'],
	config: {
		proxy: {
			type: 'myproxy',
			reader: {
				rootProperty: 'myRoot'
			}
		}
	}
});

This was working before 2.1rc1. But now, it fails unless I add a "type: 'myreader'" to the store's "reader" config. That seems a little redundant, since myproxy already defaults to using myreader.

[doobsiss]

I am having similar issues trying to get SQliteProxy to work... Can you post your full working code so that I can see what you mean?

I have just upgraded from ST2 to ST2.1-rc2 and the sencha command tools and am having trouble trying to fix this up.

Thanks

IP

[mtajur]

I'm getting the same thing. Nothing custom with folder paths here though. SDK version 3.0.0.190, Sencha Touch 2.1 beta.

[jweber]

@doobsiss and @mtajur: you're sure you're getting the same "reader: null" error? If so, are you doing what I'm doing with a custom proxy that uses a custom reader? My earlier post has the solution.

[mtajur]

I actually solved this by "hacking" a bit. Basically I created a null reader, as in Ext.data.Reader.null (and same for proxy) - simply extending these on the core functionality. Got it all working now.

[mtajur]

and yes, we are using custom reader and a custom proxy.

[jweber]

OK, that sounds like a pretty horrible solution, if you don't mind me saying so. Just re-define the reader type when you configure the proxy, e.g.

proxy: {
  reader: {
    type: 'myreader',
    rootProperty: 'myroot'
  }
}

[mtajur]

it is horrible indeed. We are testing the new beta (ST 2.1) but likely will wait for a general availability release before proceeding, hoping the bug will be fixed. Then again, I'll play around with this a bit more, perhaps can solve more elegantly indeed