domain driven design - EAV within entity framework 4 and ddd -

some tables in database designed using eav concept. use entities auto generated , represent "static" tables (not "eav" tables) orm entity framework ddd objects.

1. how can use "eav" entities in object model (not in relational in database) using entity framework?

for example,
in database have static table report , eav tables me store reportproperty report.
in domain model want have report that:

report {      icollection<reportproperty> reportproperties{get;set;} } 

i can use report entity generated entity framework , in partial section realise logic in getter retrieving data eav tables fill collection reportproperies. begs next question.

2. what can if decide use nhibernate instead entity framework, because can`t use partial section realize using entity framework?

if use ddd objects, can use entity framework or nhibernate, hardly me, because need call mapping procedures in each procedures in dao.

eav concept of data access layer, while ddd concept of business logic layer. orm entity framework or nhibernate tempt mix both layers, in complex projects complex logic (that ddd needed) should never happen. divide dal , bll. use hand crafted classes ddd objects , use auto generated (or code first) classes entity framework , provide mapping layer between them. eav implementation detail of dal. bll , ddd classes wil not have change, if switch nhibernate. mapping layer would. , way, use dependency inversion. make dal depend on bll , not other way around. if make mapping layer physically separate entity framework parts, use mediator pattern on assembly level (meaning mapping layer depends on bll , dal , not other way around).