Currently Cormo.Data.EntityFramework will automatically setup your entities using attribute-based mapping, just exactly like the JPA spec in both spring and java-ee.
However EF also supports custom fluent-api and convention-based mapping. Even though fluent-api and conventions are generally not in the cormo/spring/java-ee style (which are more in favour of explicit attribute-based), I think it would still be useful for Cormo to still supports what comes out of EF, especially since many projects have historically been using those approaches more than attribute-based.
Cormo should automatically locates any mapping/convention classes within the application and registers them to EF.
Currently Cormo.Data.EntityFramework will automatically setup your entities using attribute-based mapping, just exactly like the JPA spec in both spring and java-ee.
However EF also supports custom fluent-api and convention-based mapping. Even though fluent-api and conventions are generally not in the cormo/spring/java-ee style (which are more in favour of explicit attribute-based), I think it would still be useful for Cormo to still supports what comes out of EF, especially since many projects have historically been using those approaches more than attribute-based.
Cormo should automatically locates any mapping/convention classes within the application and registers them to EF.