Question

I’m working on a project in Grails 2.0.RC1 and I’d like to be able to save the scaffolded controllers and views for my domain objects to have as a “low-level”, developer only access to still tinker with things while being able to develop the production version of the views and controllers (with similar names, especially for controllers). I’d like to preserve them as-is, so I can re-generate them as I make updates to the domain layer, so just moving them is most likely not going to work.

I’m hoping there’s a way to do some UrlMapping magic that would let me have requests for “/mgr/book” go to the scaffolded Book controller, but “/book” would go to my production controller. I can’t find anything in the docs about how to have mappings for specific groups of controllers (without specifying each controller by name versus a $controller notation).

My other thought is to turn my domain layer into a plug-in and then create a separate project that would be just for the scaffolded views. This would be easier to remove before going to production, but also seems like more work, and raises the issue of running two grails apps at the same time on the same box.

Answer 1

I would advance you to go like your last idea. This is also my common approach:

1. Create an embeddable plugin for your domain model and common services. This also includes common plugins, like spring security and stuff. This will also reduce your dependency resolution time for the main-app btw.
2. Create an embeddable plugin for your scaffolded views. Change the template of the scaffolded controllers to require authentication and admin-group.
3. Your main-app uses both plugins.

This keeps your main-app clean and simple and you can still regenerate all your scaffolded views & controllers as you wish. And at least Eclipse STS hot-deployment will still work!

However there is no simple solution for seperating your scaffolded controllers URL-wise yet.