Are you using interfaces for your entities or your repositories (DAOs)? If you'd like a library to start from, check out Domdrides (a DOMain-DRIven DESign library):
http://domdrides.sourceforge.net Basically, it provides a common API for doing domain-driven design and also provides some useful superclasses for doing repositories using different ORM implementations (currently Hibernate, JPA, and iBATIS, but a DB4O implementation would be welcomed). On Wed, Oct 15, 2008 at 9:00 PM, Edgar Merino <[EMAIL PROTECTED]> wrote: > Hello, > > I couldn't find any other place to post this, so I'm doing it here, (it's > related to java web development anyway). I've been working on a project > where wicket has access to the domain layer through interfaces because I > didn't want my project to depend on any dbms, however I've been thinking and > the main problem here lies with db4o, since it cannot make use of JPA > annotations on entities (domain models). I would like to get rid of those > interfaces and use concrete implementations to handle business code inside > the entities, but then the above problem arises. So what recommendations can > you give to have a fully implemented domain model (using jpa annotations) > but still be able to use any dbms (or orm/dmbs) without having to map those > the domain model at the service layer? I hope I can get some feedback on > this, as it has been the main problem I've been facing when coding scalable > web applications. > > Regards, > Edgar Merino > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
