Suggestions for implementing a dynamic database behind CMS app

[picc09]

We are developing a CMS in SaaS in enterprise-class cloud computing using Grails 2.2 framework.
The application will be used by many customers (100 +) and every customer as well as the domains that we enable basic GUI can create additional domains by adding fields and validation rules.

Our problem is to understand how best to manage different Data Source (1 customer = 1 data source) but also the ability to add fields and validation rules in RUNTIME (or understand that approach have to arrive at the same solution).

Currently, we have tried to analyze the dynamic domain plugin but it is not compatible with the version 2.2 (http://grails.org/plugin/dynamic-domain-class).

Has anyone had a similar problem?

[burtbeckwith]

Good question. Unfortunately this forum doesn't get much traffic. Try the User mailing list, lots more activity there: http://grails.org/Mailing+Lists

[picc09]

Thank you very much, I'll try just get the email subscription!