@works in chrome on windows. sounds like the soapi.generated.js code is not being executed properly. it builds the routemaps at runtime from metadata. I will fire up my linux test farm later tonight and give it a once over.

I just clicked on the url in your answer, stackoverflow.quickmediasolutions.com/stackad , and I get an alert of '9' - seems to be working. and disregard my snide remark about apiVersion above, I misread the comment. I don't know why you are not getting a valid instance of RouteFactory but your online example is working just fine. Use it as a point of reference.

And whatever you copied likely wasn't mine. or wasn't copied verbatim.

Also - you will probably the reason you cannot find apiVersion on stats is that there is no member of that name. try api_version. Ok? If you have questions about a member of the api in it's running state look @ soapi.info/Services/Watch.aspx and see if you can figure it out.

@george - the api had some drama last night. check twitter.com/soapiwatch and twitter.com/soapigen and then download new js files from soapi.info/Services/CodeGeneration.aspx - I suggest that if you want to write code against an evolving beta api that you take advantage of the notification and discovery tools i have provided on soapi.info. You gotta keep up, dude. ;-)

Kevin, the site node on stats is gone on .3. Was this intentional?

good. see stackapps.com/questions/711/… for a few bugs

off-topic: my luck: the one path I used to document usage of the soapi wrappers is the one that gets removed. =-\ I was being lazy and used it because I could whip up examples that I knew would work instead of looking up post id's. Bottom line: I am tickled pink that ugly redheaded step-child of a path is gone. thanks.

the meta icon_url is relative.