OK, here’s a somewhat interesting question.  Has anyone given any thought as to how to persist Ecore definitions?  Say I want to define a system where Ecore definitions are definable at runtime, along with all their persistable attributes.  The next time the system starts up, these Ecore definitions can be read in from the database and bootstrapped into the Teneo environment.  I can setup the annotations on the Ecore.ecore definition, but it clearly is not designed with RDBMS persistence in mind as there are no surrogate keys, no versioning, etc.

Anyway, just a thought.

Thanks,

--Doug