Multiple DAO instances = Bad?
Two projects (A and B) use hibernate to retrieve the same entities out of a database. Should a DAO be instantiated in each project or should there be a separate project (C) that contains the only instance of the DAO and exposes a service (e.g. RMI) for A and B to use?

If the latter case is true then what is the common practise for preventing loading exceptions? I think my plan currently is to use RMI and create a DTO for each domain object. My only reservation is that entities in A and B won't be able to reference entities in C. Is this a common strategy?


Multiple DAO instances = Bad?
===

Two projects (A and B) use hibernate to retrieve the same entities out of a database. Should a DAO be instantiated in each project or should there be a separate project (C) that contains the only instance of the DAO and exposes a service (e.g. RMI) for A and B to use?

If the latter case is true then what is the common practise for preventing loading exceptions? I think my plan currently is to use RMI and create a DTO for each domain object. My only reservation is that entities in A and B won't be able to reference entities in C. Is this a common strategy?

