too much recursion in custom build Dojo 0.9

Submitted by hmehta on Fri, 03/28/2008 - 19:36.

Hi,

Recently, I have been experimenting with custom build in Dojo 0.9.

I have been successful with just dojo, dijit, dojox modules. However, when I introduced my custom widgets, it doesn't work.

I get the following error in firebug.

too much recursion in dojo.js line 20: if(typeof dojo=="undefined"){(function(){ .....

Here is my profile file.

dependencies = {
	layers: [
		{
			name: "customLoadDojo.js",
			dependencies: [
				"dojo.parser",
				"dijit.layout.ContentPane",
				"dijit.form.FilteringSelect",
				"dojox.collections.Dictionary",
				"custom.widget.Grid",
				"custom.widget.Profile",
				"custom.widget.MySlider"
			]
		}
	],
	prefixes: [
		[ "dijit", "../dijit"],
		[ "dojox", "../dojox"],
		[ "custom", "../custom"]
	]
};

I didn't get any errors when creating this custom build.

Any help will be appreciated.

Thank you.

Login or register to post comments
Unsubscribe post

It is hard to say: you might

Submitted by jburke on Sat, 03/29/2008 - 13:31.

It is hard to say: you might try loading dojo.js.uncompressed.js instead of dojo.js, and you might get a better indication in the error where the "too much recursion" comes from.

After including dojo.js.uncompressed.js

Submitted by hmehta on Mon, 03/31/2008 - 13:10.

Thanks jburke.

After following your advice, I included dojo.js.uncompressed.js instead of dojo.js. This is what I get from Firebug.

too much recursion
if(ii=c.prototype._constructor){ii.apply(this, args);} line: 1685

I got this error twice.

Thanks.

Hmm, not sure what could

Submitted by jburke on Mon, 03/31/2008 - 13:32.

Hmm, not sure what could cause this. Does this error occur when you do not use a custom build?

The error seems to come from the machinery in dojo.declare. Do you have something like CustomWidgetA inheriting from CustomWidgetB, but then CustomWidgetB inherits from CustomWidgetA? Not sure what would happen in that scenario, just guessing.

When I don't use the custom

Submitted by hmehta on Mon, 03/31/2008 - 18:02.

When I don't use the custom build, the error does not occur. I don't have a any custom widgetA inheriting custom widgetB and then custom widgetB inheriting custom widgetA.

I tried creating a custom build in which I don't specify any dependency (so with just one layer -- the default dojo).

dependencies = {
	layers: [
		{
			name: "dojo.js",
			dependencies: [
				
			]
		}
	],
	prefixes: [
		[ "dijit", "../dijit"],
		[ "customWidget", "../"customWidget"],
		[ "dojox", "../dojox"]
	]
};

This failed as well! It came up with the same error. But in a different location.

It would probably be good to

Submitted by jburke on Mon, 03/31/2008 - 19:32.

It would probably be good to have a publicly visible test page to see the problem. It is hard to know based on the above info. Maybe more than one dojo.js is being loaded in the page? Something overwriting the dijit base code somehow?

Search