I often need to specify the root class (leading ‘::’ thing), so I’m happy with that. But, a couple of my controllers had the leading ‘::’ specified in my routes file. There was no good reason for this, it didn’t cause any problems on the dev server - but did cause intermittent “unitialized constant” errors on the production server.

The fix was to remove the leading :: in the config/routes.rb file.

Again, I had similar sub-class hierarchies which seem to be conflicting, depending on when things were loaded.

Personally, I don’t see any reason to step on my throat and force myself into using these frameworks if I can do Rails. I mean, why? Just to be on the Java side or because I spent more than 7 years programming on it? I’m not bound by corporate obligations and regulations, and I choose whatever works best for me and aids my freelancing business — that’s the essence of being pragmatic programmer, by the way.

I don’t value my past achievements as much as I do the opportunities. If new approaches and technologies overpass the past, it makes it even better and far more fun.

Downloading your presentation on Grails now to see your position better…

Thanks for the comment!

As I can see you’ve faced with RoR much later than with Java, so the Grails framewok could be interesting for you because it has RoR ideology, and you can stil use your Java code with it.